W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Section 3.2.2

From: Paul Leach <paulle@microsoft.com>
Date: Fri, 31 May 1996 15:01:13 -0700
Message-Id: <c=US%a=_%p=msft%l=RED-77-MSG-960531220113Z-5374@abash1.microsoft.com>
To: "'http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com'" <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/653
Section 3.2.2 says:

Note: Although the HTTP protocol is independent of the transport layer
protocol, the http URL only identifies resources by their TCP location,
and thus non-TCP resources MUST be identified by some other URI scheme. 

I don't think this is really true. "http:" URLs identify resources by
DNS names, and IMHO it is the presence of an A record for that DNS name
that signals that one must use TCP.  In the future, the presence of an
AAAA (IPv6) record would presumably mean to use TCP/IPv6 to access the
resource (if this isn't true, isn't someone on the IAB going to kill
us?).  Similarly, if one were to invent an RR for IPX addresses or ATM
addresses (if they haven't already), one could presumably run HTTP/SPX
or HTTP/ATM (or HTTP/X.25,..., etc.) with "http:" URLs.

In any case, I'm not sure what compelling purpose this note serves, and
rather than debate it, it might be better just to nuke it.

Paul J. Leach            Email: paulle@microsoft.com
Microsoft                Phone: 1-206-882-8080
1 Microsoft Way          Fax:   1-206-936-7329
Redmond, WA 98052
Received on Friday, 31 May 1996 15:42:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC