Re: URI-protocol mapping (was Re: How to add new "protocols" ?)
touch@isi.edu Fri, 21 February 1997 16:48 UTC
Received: from cnri by ietf.org id aa12224; 21 Feb 97 11:48 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa16526; 21 Feb 97 11:48 EST
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id KAA00706 for uri-out; Fri, 21 Feb 1997 10:54:53 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id KAA00696 for <uri@services.bunyip.com>; Fri, 21 Feb 1997 10:54:49 -0500 (EST)
From: touch@isi.edu
Received: from zephyr.isi.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03390 (mail destined for uri@services.bunyip.com); Fri, 21 Feb 97 10:54:48 -0500
Received: from ash.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA09627>; Fri, 21 Feb 1997 07:54:45 -0800
Date: Fri, 21 Feb 1997 07:54:43 -0800
Posted-Date: Fri, 21 Feb 1997 07:54:43 -0800
Message-Id: <199702211554.AA05345@ash.isi.edu>
Received: by ash.isi.edu (5.65c/4.0.3-6) id <AA05345>; Fri, 21 Feb 1997 07:54:43 -0800
To: rdaniel@acl.lanl.gov, connolly@w3.org
Subject: Re: URI-protocol mapping (was Re: How to add new "protocols" ?)
Cc: liberte@ncsa.uiuc.edu, touch@isi.edu, uri@bunyip.com
X-Auto-Sig-Adder-By: faber@isi.edu
Sender: owner-uri@bunyip.com
Precedence: bulk
> OK, I'll bite: how is it that "location-dependent" vs. > "location-independent" is a technical distinction? > What mechanism depends on or uses the distinction in > any way? What's the test for "location dependent"? > > For 20 points: tell me the location of http://www.w3.org/. 1. the protocol is completely specified in this, i.e., HTTP over TCP on the default port of 80 2. www.w3.org is a fully-qualified DNS name The fact that DNS round-robining maps this to different addresses depending on when the query is posed is no different from the fact that all DNS names are symbolic, and that the mapping to IP addresses is done at resolution time. > The evidence you give -- that you would have a hard time calling > it a URN -- is exactly the sort of _non-technical_ difference > in perspective that I'm talking about. It's very technical. The host requirements RFC specifies locations as either fully-qualified DNS names or IP addresses. And that's what you have here. I.e., you have as much of a location as the internet allows. Joe ---------------------------------------------------------------------- Joe Touch - touch@isi.edu http://www.isi.edu/~touch/ ISI / Project Leader, ATOMIC-2, LSAM http://www.isi.edu/atomic2/ USC / Research Assistant Prof. http://www.isi.edu/lsam/
- URI-protocol mapping (was Re: How to add new "pro… Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Roy T. Fielding
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.
- Re: URI-protocol mapping Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.