From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 13:17:46 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03890 for ; Tue, 14 Mar 2000 13:17:43 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id NAA23207; Tue, 14 Mar 2000 13:07:07 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8627535 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 13:07:03 -0500 Received: from sjgw.ipo.att.com (gate.ipo.att.com [135.197.57.2]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id MAA20619 for ; Tue, 14 Mar 2000 12:57:00 -0500 (EST) Received: from exchsj06.ipo.att.com (exchsj06.ipo.att.com [135.197.72.26]) by sjgw.ipo.att.com (8.8.5/8.8.8) with ESMTP id JAA06502; Tue, 14 Mar 2000 09:51:01 -0800 (PST) Received: from larry (mp-dhcp-2-211.attlabs.att.com [135.197.2.211]) by exchsj06.ipo.att.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id GTXF1DMR; Tue, 14 Mar 2000 09:47:25 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Message-ID: Date: Tue, 14 Mar 2000 09:51:41 -0800 Reply-To: Larry Masinter From: Larry Masinter Subject: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET Content-Transfer-Encoding: 7bit I looked through the archives but didn't see this discussed in the past, and would like opinions about creating a URN name space for IANA registrations. Some protocols (especially those within W3C) wish to use URIs uniformly as the moral equivalent of OIDs in ISO protocols, i.e., a way of having assigned parameter names & values be notated and referenced. In IETF protocols, there are some protocol elements that are, instead, registered with IANA and then listed in one of the categories in http://www.iana.org/numbers.html. The general idea is to create a way to refer to these IANA registrations using a URI. While it might be as reasonable to use http://www.iana.org// as a template for such URIs, it might also be more stable to use URN:IANA:: as the URI. I suppose either mechanism would require a BCP which would instruct IANA to maintain the registry in such a fashion to fit into the syntactic rules of URLs/URNs (respectively). For the most part, this is imposed by the file name restrictions in ftp://www.isi.edu/in-notes/iana/assignments/ but the BCP and namespace registration would formalize the conventions. What do you think? Doing this would help resolve a number of irritations in the URI-vs-registry debates, since it would create a URI for registered values. Larry -- http://larry.masinter.net From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 15:09:51 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19542 for ; Tue, 14 Mar 2000 15:09:46 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id OAA19634; Tue, 14 Mar 2000 14:56:56 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8627710 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 14:56:54 -0500 Received: from ns.datafusion.net (datafusion.net [208.224.117.2]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id OAA17308 for ; Tue, 14 Mar 2000 14:46:48 -0500 (EST) Received: from ns.datafusion.net (root@localhost) by ns.datafusion.net with ESMTP id LAA11917 for ; Tue, 14 Mar 2000 11:41:21 -0800 (PST) Received: from datafusionnt1.DATAFUSION.NET (datafusionnt1.datafusion.net [10.1.1.10]) by ns.datafusion.net with ESMTP id LAA11909 for ; Tue, 14 Mar 2000 11:41:21 -0800 (PST) Received: by datafusionnt1 with Internet Mail Service (5.5.2650.21) id ; Tue, 14 Mar 2000 11:41:21 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Message-ID: <0D611E39F997D0119F9100A0C931315C52FD82@datafusionnt1> Date: Tue, 14 Mar 2000 11:41:20 -0800 Reply-To: Ron Daniel From: Ron Daniel Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET Larry Masinter said: The general idea is to create a way to refer to these IANA registrations using a URI. While it might be as reasonable to use http://www.iana.org// as a template for such URIs, it might also be more stable to use URN:IANA:: as the URI. Hmmm, an interesting suggestion. I like it. The BCP document seems a reasonable way forward. Regards, Ron Daniel Jr. Metacode Technologies, Inc. 139 Townsend Street, Suite 100 San Francisco, CA 94107 415.836.7813 fax 415.222.0150 rdaniel@metacode.com > I suppose either mechanism would require a BCP which would instruct > IANA to maintain the registry in such a fashion to fit into > the syntactic rules of URLs/URNs (respectively). > > For the most part, this is imposed by the file name restrictions > in ftp://www.isi.edu/in-notes/iana/assignments/ but the BCP and > namespace registration would formalize the conventions. > > What do you think? Doing this would help resolve a number of > irritations in the URI-vs-registry debates, since it would > create a URI for registered values. > > Larry > > > > > > > -- > http://larry.masinter.net From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 20:08:47 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09172 for ; Tue, 14 Mar 2000 20:08:44 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id TAA10908; Tue, 14 Mar 2000 19:56:47 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628022 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 19:56:45 -0500 Received: from tor-smtp1.netcom.ca (tor-smtp1.netcom.ca [207.181.101.69]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id TAA10878 for ; Tue, 14 Mar 2000 19:56:41 -0500 (EST) Received: from thinkingcat.com (mon-pq11-49.netcom.ca [209.146.134.49]) by tor-smtp1.netcom.ca (8.8.7-s-4/8.8.7) with ESMTP id TAA13786; Tue, 14 Mar 2000 19:50:33 -0500 (EST) X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <38CEDCD5.71359FCD@thinkingcat.com> Date: Tue, 14 Mar 2000 19:44:05 -0500 Reply-To: ldaigle@netcom.ca From: Leslie Daigle Organization: Thinking Cat Enterprises Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET Content-Transfer-Encoding: 7bit Howdy, Larry Masinter wrote: > The general idea is to create a way to refer to these IANA > registrations using a URI. While it might be as reasonable > to use http://www.iana.org// as a template > for such URIs, it might also be more stable to use > URN:IANA:: > as the URI. [...] > What do you think? Doing this would help resolve a number of > irritations in the URI-vs-registry debates, since it would > create a URI for registered values. Sounds like a fine idea, assuming IANA's comfortable with it. I would imagine the BCP could/would be the namespace definition (RFC2611) -- i.e., not a lot more than what you've described, probably following loosely on what Ryan Moats did for the proposed "IETF" namespace for documents (RFC2648). Are you volunteering? :-> Leslie. -- ------------------------------------------------------------------- "My body obeys Aristotelian laws of physics." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 21:38:52 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09529 for ; Tue, 14 Mar 2000 21:38:52 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id VAA26374; Tue, 14 Mar 2000 21:30:44 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628125 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 21:30:42 -0500 Received: from sh.w3.mag.keio.ac.jp (sh.w3.mag.keio.ac.jp [133.27.194.41]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id VAA24109 for ; Tue, 14 Mar 2000 21:20:39 -0500 (EST) Received: from enoshima (dhcp-100-224.mag.keio.ac.jp [133.27.195.224]) by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with SMTP id LAA00978; Wed, 15 Mar 2000 11:15:00 +0900 (JST) X-Sender: duerst@sh.w3.mag.keio.ac.jp X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-J (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <200003150215.LAA00978@sh.w3.mag.keio.ac.jp> Date: Wed, 15 Mar 2000 11:16:10 +0900 Reply-To: "Martin J. Duerst" From: "Martin J. Duerst" Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET In-Reply-To: Hello Larry, I think the direction you point out makes very much sense. I have had some thoughts in this direction, which I will add below. At 09:51 00/03/14 -0800, Larry Masinter wrote: > I looked through the archives but didn't see this discussed > in the past, and would like opinions about creating a URN name > space for IANA registrations. > > Some protocols (especially those within W3C) wish to use > URIs uniformly as the moral equivalent of OIDs in ISO protocols, > i.e., a way of having assigned parameter names & values > be notated and referenced. > > In IETF protocols, there are some protocol elements that are, > instead, registered with IANA and then listed in one of the > categories in http://www.iana.org/numbers.html. > > > The general idea is to create a way to refer to these IANA > registrations using a URI. While it might be as reasonable > to use http://www.iana.org// as a template > for such URIs, it might also be more stable to use > URN:IANA:: > as the URI. URN:IANA:: MAY be more stable. http://www.iana.org// would have some important operational benefits, mainly to force IANA to keep their site clean and to be able to find the relevant data quickly on deployed infrastructure. > I suppose either mechanism would require a BCP which would instruct > IANA to maintain the registry in such a fashion to fit into > the syntactic rules of URLs/URNs (respectively). Yes. And in both cases, it would involve quite some work, both for checking through all the registrations and deciding how to best allocate/identify them, and then for IANA to clean up things. Although this does by way not apply to all registrations, there are quite a few of them where the content of the registration can be expressed in a machine-readable form. > For the most part, this is imposed by the file name restrictions > in ftp://www.isi.edu/in-notes/iana/assignments/ but the BCP and > namespace registration would formalize the conventions. > > What do you think? Doing this would help resolve a number of > irritations in the URI-vs-registry debates, since it would > create a URI for registered values. Definitely an idea worth working on. Regards, Martin. #-#-# Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium #-#-# mailto:duerst@w3.org http://www.w3.org/People/D%C3%BCrst From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 22:46:57 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04526 for ; Tue, 14 Mar 2000 22:46:56 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id WAA09600; Tue, 14 Mar 2000 22:32:10 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628196 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 22:32:07 -0500 Received: from marine.sonic.net (marine.sonic.net [208.201.224.37]) by lists.internic.net (8.9.3/8.9.3) with SMTP id WAA07759 for ; Tue, 14 Mar 2000 22:22:04 -0500 (EST) Received: (qmail 27954 invoked from network); 15 Mar 2000 03:16:36 -0000 Received: from prop.sonic.net (208.201.224.193) by marine.sonic.net with SMTP; 15 Mar 2000 03:16:36 -0000 Received: from sonic.net (bolt [208.201.224.36]) by prop.sonic.net (8.8.8/8.8.5) with ESMTP id TAA27431 for ; Tue, 14 Mar 2000 19:16:37 -0800 X-envelope-info: Received: from localhost (tallen@localhost) by sonic.net (8.8.8/8.7.3) with SMTP id TAA05616 for ; Tue, 14 Mar 2000 19:16:36 -0800 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-ID: Date: Tue, 14 Mar 2000 19:16:36 -0800 Reply-To: Terry Allen From: Terry Allen Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET In-Reply-To: Larry wrote: | The general idea is to create a way to refer to these IANA | registrations using a URI. While it might be as reasonable | to use http://www.iana.org// as a template | for such URIs, it might also be more stable to use | URN:IANA:: | as the URI. The meaning of the word "namespace" has been confused by its use for the syntactic device yclept "XML Namespaces"; could you explain what it means here? Is it a sort of sub-NID? regards, Terry Terry Allen Document Engineering Group Commerce One, Inc. Mountain View, Calif. tallen[at]sonic.net From owner-urn-ietf@LISTS.INTERNIC.NET Tue Mar 14 23:01:56 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09728 for ; Tue, 14 Mar 2000 23:01:56 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id WAA12820; Tue, 14 Mar 2000 22:48:05 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628260 for URN-IETF@LISTS.INTERNIC.NET; Tue, 14 Mar 2000 22:48:03 -0500 Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id WAA12795 for ; Tue, 14 Mar 2000 22:48:00 -0500 (EST) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id WAA09205; Tue, 14 Mar 2000 22:32:01 -0500 (EST) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i Message-ID: <20000314223201.F9005@bailey.dscga.com> Date: Tue, 14 Mar 2000 22:32:01 -0500 Reply-To: michaelm@netsol.com From: Michael Mealling Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET In-Reply-To: ; from tallen@SONIC.NET on Tue, Mar 14, 2000 at 07:16:36PM -0800 On Tue, Mar 14, 2000 at 07:16:36PM -0800, Terry Allen wrote: > Larry wrote: > | The general idea is to create a way to refer to these IANA > | registrations using a URI. While it might be as reasonable > | to use http://www.iana.org// as a template > | for such URIs, it might also be more stable to use > | URN:IANA:: > | as the URI. > > The meaning of the word "namespace" has been confused by its > use for the syntactic device yclept "XML Namespaces"; could > you explain what it means here? Is it a sort of sub-NID? We use the term namespace as more of a general term. In this particular example any identifiable chunk of the URN defines some set of names which we call a namespace. namespace = a defined set of names -MM -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | www.rwhois.net/michael Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#: 14198821 Network Solutions | www.lp.org | michaelm@netsol.com From owner-urn-ietf@LISTS.INTERNIC.NET Wed Mar 15 02:33:05 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08764 for ; Wed, 15 Mar 2000 02:33:05 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id CAA26918; Wed, 15 Mar 2000 02:22:40 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628399 for URN-IETF@LISTS.INTERNIC.NET; Wed, 15 Mar 2000 02:22:37 -0500 Received: from sh.w3.mag.keio.ac.jp (sh.w3.mag.keio.ac.jp [133.27.194.41]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id CAA24877 for ; Wed, 15 Mar 2000 02:12:34 -0500 (EST) Received: from enoshima (dhcp-100-224.mag.keio.ac.jp [133.27.195.224]) by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with SMTP id QAA02030 for ; Wed, 15 Mar 2000 16:07:04 +0900 (JST) X-Sender: duerst@sh.w3.mag.keio.ac.jp X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-J (32) References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <200003150707.QAA02030@sh.w3.mag.keio.ac.jp> Date: Wed, 15 Mar 2000 14:55:32 +0900 Reply-To: "Martin J. Duerst" From: "Martin J. Duerst" Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET In-Reply-To: <200003150215.LAA00978@sh.w3.mag.keio.ac.jp> At 11:16 00/03/15 +0900, Martin J. Duerst wrote: > At 09:51 00/03/14 -0800, Larry Masinter wrote: > > I suppose either mechanism would require a BCP which would instruct > > IANA to maintain the registry in such a fashion to fit into > > the syntactic rules of URLs/URNs (respectively). > > Yes. And in both cases, it would involve quite some work, > both for checking through all the registrations and deciding > how to best allocate/identify them, and then for IANA to > clean up things. > > > Although this does by way not apply to all registrations, > there are quite a few of them where the content of the registration > can be expressed in a machine-readable form. Sorry, wasn't quite finished. If such a representation is available, this is what the URI should point to. That way, it is possible both to use the URI as a pure identifier (your app already knows what's registered) as well as to get apps updated on new registrations. Regards, Martin. #-#-# Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium #-#-# mailto:duerst@w3.org http://www.w3.org/People/D%C3%BCrst From owner-urn-ietf@LISTS.INTERNIC.NET Wed Mar 15 18:51:12 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01127 for ; Wed, 15 Mar 2000 18:51:11 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id SAA08973; Wed, 15 Mar 2000 18:44:43 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8628969 for URN-IETF@LISTS.INTERNIC.NET; Wed, 15 Mar 2000 18:44:41 -0500 Received: from marine.sonic.net (marine.sonic.net [208.201.224.37]) by lists.internic.net (8.9.3/8.9.3) with SMTP id SAA08951 for ; Wed, 15 Mar 2000 18:44:39 -0500 (EST) Received: (qmail 23395 invoked from network); 15 Mar 2000 23:39:11 -0000 Received: from ultra.sonic.net (208.201.224.22) by marine.sonic.net with SMTP; 15 Mar 2000 23:39:11 -0000 Received: from sonic.net (bolt [208.201.224.36]) by ultra.sonic.net (8.9.3/8.8.5) with ESMTP id PAA26900 for ; Wed, 15 Mar 2000 15:38:33 -0800 X-envelope-info: Received: (from tallen@localhost) by sonic.net (8.8.8/8.7.3) id PAA15025 for URN-IETF@LISTS.INTERNIC.NET; Wed, 15 Mar 2000 15:39:10 -0800 Message-ID: <200003152339.PAA15025@sonic.net> Date: Wed, 15 Mar 2000 15:39:10 -0800 Reply-To: Terry Allen From: Terry Allen Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET Michael replied | On Tue, Mar 14, 2000 at 07:16:36PM -0800, Terry Allen wrote: | > Larry wrote: | > | The general idea is to create a way to refer to these IANA | > | registrations using a URI. While it might be as reasonable | > | to use http://www.iana.org// as a template | > | for such URIs, it might also be more stable to use | > | URN:IANA:: | > | as the URI. | > | > The meaning of the word "namespace" has been confused by its | > use for the syntactic device yclept "XML Namespaces"; could | > you explain what it means here? Is it a sort of sub-NID? | | We use the term namespace as more of a general term. | In this particular example any identifiable chunk of the URN | defines some set of names which we call a namespace. | namespace = a defined set of names I agree with the definition; let me ask the question another way. In the context of IANA registrations, what sets of names count as namespaces for the purpose of this proposal? From owner-urn-ietf@LISTS.INTERNIC.NET Wed Mar 15 19:31:28 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17318 for ; Wed, 15 Mar 2000 19:31:27 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id TAA18438; Wed, 15 Mar 2000 19:25:54 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8629055 for URN-IETF@LISTS.INTERNIC.NET; Wed, 15 Mar 2000 19:25:52 -0500 Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id TAA18416 for ; Wed, 15 Mar 2000 19:25:50 -0500 (EST) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id TAA11965; Wed, 15 Mar 2000 19:09:51 -0500 (EST) References: <200003152339.PAA15025@sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i Message-ID: <20000315190950.B11674@bailey.dscga.com> Date: Wed, 15 Mar 2000 19:09:50 -0500 Reply-To: michaelm@netsol.com From: Michael Mealling Subject: Re: URN scheme for IANA registrations To: URN-IETF@LISTS.INTERNIC.NET In-Reply-To: <200003152339.PAA15025@sonic.net>; from tallen@SONIC.NET on Wed, Mar 15, 2000 at 03:39:10PM -0800 On Wed, Mar 15, 2000 at 03:39:10PM -0800, Terry Allen wrote: > Michael replied > | On Tue, Mar 14, 2000 at 07:16:36PM -0800, Terry Allen wrote: > | > Larry wrote: > | > | The general idea is to create a way to refer to these IANA > | > | registrations using a URI. While it might be as reasonable > | > | to use http://www.iana.org// as a template > | > | for such URIs, it might also be more stable to use > | > | URN:IANA:: > | > | as the URI. > | > > | > The meaning of the word "namespace" has been confused by its > | > use for the syntactic device yclept "XML Namespaces"; could > | > you explain what it means here? Is it a sort of sub-NID? > | > | We use the term namespace as more of a general term. > | In this particular example any identifiable chunk of the URN > | defines some set of names which we call a namespace. > | namespace = a defined set of names > > I agree with the definition; let me ask the question another > way. In the context of IANA registrations, what sets of names > count as namespaces for the purpose of this proposal? Ahh.. sorry. I misunderstood. I'll probably be putting words in Larry's mouth by guessing but I'm betting that the value would be logically equivalent to the sub-headings found on this page: http://www.iana.org/numbers.html I.e. under the 'A' section we have "AS numbers". Thus that would translate to a value you would put in the part something like this: urn:iana:as:6245 (6245 is our AS number) One problem is that some of these have additional subsections. The DNS parameters section has various subsections (class, rr types, etc). Does each one get a or is the namespace further subdivided as in: urn:iana:dns-parms:class:3 (chaos class) Just some thoughts.... -MM -MM urn:iana:dns-parm:class: -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | www.rwhois.net/michael Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#: 14198821 Network Solutions | www.lp.org | michaelm@netsol.com From owner-urn-ietf@LISTS.INTERNIC.NET Thu Mar 16 16:52:40 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05625 for ; Thu, 16 Mar 2000 16:52:39 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id QAA21182; Thu, 16 Mar 2000 16:37:13 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8629605 for URN-IETF@LISTS.INTERNIC.NET; Thu, 16 Mar 2000 16:37:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id QAA18706 for ; Thu, 16 Mar 2000 16:27:07 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24355; Thu, 16 Mar 2000 16:21:36 -0500 (EST) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Message-ID: <200003162121.QAA24355@ietf.org> Date: Thu, 16 Mar 2000 16:21:36 -0500 Reply-To: Internet-Drafts@ietf.org Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-urn-net-procedures-03.txt To: URN-IETF@LISTS.INTERNIC.NET --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : Assignment Procedures for the URI Resolution using DNS Author(s) : M. Mealling, R. Daniel Filename : draft-ietf-urn-net-procedures-03.txt Pages : 9 Date : 15-Mar-00 RFCXXXX defines a how DNS is used as a Resolver Discovery System database that contains URI delegation rules (sometimes called resolution hints). That document specifies that the first step in that algorithm is to append 'URI.NET' to the URI scheme and retrieve the NAPTR record for that domain-name. I.e., the first step in resolving 'http://foo.com/' would be to look up a NAPTR record for the domain 'http.URI.NET'. URN resolution also follows a similar procedure but uses the 'URN.NET' zone as its root. This document describes the procedures for inserting a new rule into the 'URI.NET' and 'URN.NET' zones. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-03.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-net-procedures-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-net-procedures-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000315133105.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-net-procedures-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-net-procedures-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000315133105.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.INTERNIC.NET Fri Mar 24 02:00:31 2000 Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22117 for ; Fri, 24 Mar 2000 02:00:31 -0500 (EST) Received: from lists.internic.net (lists.internic.net [198.41.0.15]) by lists.internic.net (8.9.3/8.9.3) with ESMTP id BAA22549; Fri, 24 Mar 2000 01:45:07 -0500 (EST) Received: from LISTS.INTERNIC.NET by LISTS.INTERNIC.NET (LISTSERV-TCP/IP release 1.8d) with spool id 8633388 for URN-IETF@LISTS.INTERNIC.NET; Fri, 24 Mar 2000 01:45:04 -0500 Received: from mail.vest.co.jp (psnsv01.vest.co.jp [210.141.111.170]) by lists.internic.net (8.9.3/8.9.3) with SMTP id BAA20489 for ; Fri, 24 Mar 2000 01:35:01 -0500 (EST) Received: from localhost (unverified [63.249.254.3]) by mail.vest.co.jp (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 24 Mar 2000 15:30:16 +0900 Content-Type: text/plain Sensitivity: Personal MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Mailer: Microsoft Outlook Express 4.72.3110.4 X-Other-References: 08EAFA6D4 Message-ID: <4h5vugbz60e12bj.240320000044@localhost> Date: Fri, 24 Mar 2000 01:45:04 -0500 Reply-To: larp2@ANGELFAN.COM From: larp2@ANGELFAN.COM Subject: Freedom, Security and Profits To: URN-IETF@LISTS.INTERNIC.NET If you would like to pay off your bills, buy a new car, take long vacations, build a new home, start a generous college fund for your children, or just spend more time with your family then you need to seriously review the easy to implement business opportunity offered by the US. Congress approved Tax Relief System. Freedom, Security and Profits CALL NOW 1-800-962-5441