From owner-urn-ietf@LISTS.NETSOL.COM Fri Jun 1 04:58:35 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA03081 for ; Fri, 1 Jun 2001 04:58:35 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id EAA05186; Fri, 1 Jun 2001 04:52:47 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1485 for URN-IETF@LISTS.NETSOL.COM; Fri, 1 Jun 2001 04:48:57 -0400 Received: from fregat18.cs.vu.nl (root@fregat18.cs.vu.nl [130.37.16.64]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id EAA05168 for ; Fri, 1 Jun 2001 04:48:55 -0400 (EDT) Received: by fregat18.cs.vu.nl (Smail #66) id m155kWO-002ej3C; Fri, 1 Jun 2001 10:43 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Approved-By: Gerco Ballintijn Message-ID: <20010601104304.A8113@fregat18.cs.vu.nl> Date: Fri, 1 Jun 2001 10:43:04 +0200 Reply-To: Gerco Ballintijn From: Gerco Ballintijn Subject: Scalability Analysis of NAPTR Approach To: URN-IETF@LISTS.NETSOL.COM Hi, For my PhD research, I am interested in wide-area naming systems, and I have therefore been following the work of this working group for a couple of years. While the various RFCs and internet-drafts describe the requirements and mechanisms for URN based naming, I am particularly interested in a *scientific analyses* of the proposed methods. I am therefore looking for publications (of any kind) describing mathematical analysis or performance experiments of the DNS based Resolver Discovery System. Since there are no such pointers on the working group web page, I was hoping somebody on this list could point me in the right direction. Gerco. ----------------------------------v------------------------------------ G.C. Ballintijn | Oh, Fortuna mailto:gerco@cs.vu.nl | Velut luna http://www.cs.vu.nl/~gerco/ | Statu variabilis..... From owner-urn-ietf@LISTS.NETSOL.COM Fri Jun 1 08:19:32 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA06113 for ; Fri, 1 Jun 2001 08:19:31 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id IAA06249; Fri, 1 Jun 2001 08:14:31 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1576 for URN-IETF@LISTS.NETSOL.COM; Fri, 1 Jun 2001 08:14:26 -0400 Received: from mail004.syd.optusnet.com.au (mail004.syd.optusnet.com.au [203.2.75.228]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id IAA06241 for ; Fri, 1 Jun 2001 08:14:23 -0400 (EDT) Received: from vlc.com.au (lisax4-236.dialup.optusnet.com.au [198.142.18.236]) by mail004.syd.optusnet.com.au (8.11.1/8.11.1) with ESMTP id f51C8OU10673; Fri, 1 Jun 2001 22:08:25 +1000 X-Mailer: Mozilla 4.76 [en]C-{C-UDP; OWL-18191} (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 References: <20010601104304.A8113@fregat18.cs.vu.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Justin Couch Message-ID: <3B178638.663EB04B@vlc.com.au> Date: Fri, 1 Jun 2001 22:10:32 +1000 Reply-To: Justin Couch From: Justin Couch Organization: The Virtual Light Company Subject: Re: Scalability Analysis of NAPTR Approach To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Gerco Ballintijn wrote: > interested in a *scientific analyses* of the proposed methods. I am > therefore looking for publications (of any kind) describing mathematical > analysis or performance experiments of the DNS based Resolver Discovery > System. Since there are no such pointers on the working group web page, > I was hoping somebody on this list could point me in the right direction. Are you looking for less research based information or information that does not use DNS for the resolver mechanism? I've been using them in commercial and military applications for the past 2 years at least and can give you quite a lot of anecdotal evidence. This uses custom resolvers, combination resolvers (eg THTTP + custom + caching mechanisms). Drop me a line privately if it is of interest. -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Fri Jun 1 09:22:33 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA07787 for ; Fri, 1 Jun 2001 09:22:33 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA06810; Fri, 1 Jun 2001 09:14:31 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1667 for URN-IETF@LISTS.NETSOL.COM; Fri, 1 Jun 2001 09:14:26 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA06750 for ; Fri, 1 Jun 2001 09:03:17 -0400 (EDT) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id IAA05620; Fri, 1 Jun 2001 08:53:30 -0400 (EDT) References: <20010601104304.A8113@fregat18.cs.vu.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i Message-ID: <20010601085330.J27001@bailey.dscga.com> Date: Fri, 1 Jun 2001 08:53:30 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: Re: Scalability Analysis of NAPTR Approach To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <20010601104304.A8113@fregat18.cs.vu.nl>; from gerco@cs.vu.nl on Fri, Jun 01, 2001 at 10:43:04AM +0200 On Fri, Jun 01, 2001 at 10:43:04AM +0200, Gerco Ballintijn wrote: > For my PhD research, I am interested in wide-area naming systems, and > I have therefore been following the work of this working group for a > couple of years. While the various RFCs and internet-drafts describe > the requirements and mechanisms for URN based naming, I am particularly > interested in a *scientific analyses* of the proposed methods. I am > therefore looking for publications (of any kind) describing mathematical > analysis or performance experiments of the DNS based Resolver Discovery > System. Since there are no such pointers on the working group web page, > I was hoping somebody on this list could point me in the right direction. We never did anything beyond simply looking at the affect of certain optimizations such as additional information records, etc. Most of the data you would get would be dependent on how the namespace was delegated. Something that was very deep and granular would have a poor performance characteristic. In the case of something like the PIN space which is flat the total number of DNS lookups is very close to 1. We never really went beyond that fairly simple analysis since we had no namespaces to use as input. I suppose one could create some fake namespaces to test how each additional delegation affects resolution time but I'm sure it would be pretty much 1:1 with the number of delegations in the namespace itself. If you do find something or end up writing something yourself I'm sure the list would be very interested! -MM -- -------------------------------------------------------------------------------- Michael Mealling | mailto:michael@research.netsol.com Advanced Naming Research Manager | go:Michael Mealling Verisign Applied Research | urn:pin:1 From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 4 13:01:36 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12877 for ; Mon, 4 Jun 2001 13:01:35 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA24132; Mon, 4 Jun 2001 12:56:09 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 2080 for URN-IETF@LISTS.NETSOL.COM; Mon, 4 Jun 2001 12:55:00 -0400 Received: from serrano.hesketh.net (serrano.hesketh.net [66.45.6.210]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA24113 for ; Mon, 4 Jun 2001 12:54:58 -0400 (EDT) Received: from [192.168.124.14] (syr-24-24-11-230.twcny.rr.com [24.24.11.230]) by serrano.hesketh.net (8.11.3/8.11.3) with ESMTP id f54Gn3F29293; Mon, 4 Jun 2001 12:49:06 -0400 X-Received-From: simonstl@simonstl.com X-Delivered-To: URN-IETF@LISTS.NETSOL.COM X-Spam-Filter: check_local@serrano.hesketh.net by digitalanswers.org X-More-Information: http://spamfighter.hesketh.net References: <20010601104304.A8113@fregat18.cs.vu.nl> <20010601085330.J27001@bailey.dscga.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Mime-Version: 1.0 Approved-By: "Simon St.Laurent" Message-ID: <991659026.12181.4.camel@localhost.localdomain> Date: Mon, 4 Jun 2001 12:50:22 +0000 Reply-To: "Simon St.Laurent" From: "Simon St.Laurent" Subject: Latest DDDS draft To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <20010601085330.J27001@bailey.dscga.com> Is this the latest DDDS draft? http://www.ietf.org/internet-drafts/draft-ietf-urn-ddds-04.txt Seems to have expired 8 February, though I'm not sure it matters. From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 4 13:25:48 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13634 for ; Mon, 4 Jun 2001 13:25:48 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA24439; Mon, 4 Jun 2001 13:21:15 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 2137 for URN-IETF@LISTS.NETSOL.COM; Mon, 4 Jun 2001 13:21:09 -0400 Received: from serrano.hesketh.net (serrano.hesketh.net [66.45.6.210]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA24432 for ; Mon, 4 Jun 2001 13:21:08 -0400 (EDT) Received: from [192.168.124.14] (syr-24-24-11-230.twcny.rr.com [24.24.11.230]) by serrano.hesketh.net (8.11.3/8.11.3) with ESMTP id f54HFHF30313; Mon, 4 Jun 2001 13:15:17 -0400 X-Received-From: simonstl@simonstl.com X-Spam-Filter: check_local@serrano.hesketh.net by digitalanswers.org X-More-Information: http://spamfighter.hesketh.net References: <20010601104304.A8113@fregat18.cs.vu.nl> <20010601085330.J27001@bailey.dscga.com> <991659026.12181.4.camel@localhost.localdomain> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Mime-Version: 1.0 Approved-By: "Simon St.Laurent" Message-ID: <991660596.12179.6.camel@localhost.localdomain> Date: Mon, 4 Jun 2001 13:16:36 +0000 Reply-To: "Simon St.Laurent" From: "Simon St.Laurent" Subject: Re: Latest DDDS draft To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <991659026.12181.4.camel@localhost.localdomain> On 04 Jun 2001 12:50:22 +0000, Simon St.Laurent wrote: > Is this the latest DDDS draft? > > http://www.ietf.org/internet-drafts/draft-ietf-urn-ddds-04.txt > > Seems to have expired 8 February, though I'm not sure it matters. Sorry - my coffee must be decaf today. That was the publication date. Bah. From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 11 01:45:02 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA21306 for ; Mon, 11 Jun 2001 01:45:01 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id BAA02315; Mon, 11 Jun 2001 01:22:24 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3022 for URN-IETF@LISTS.NETSOL.COM; Mon, 11 Jun 2001 01:14:18 -0400 Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id BAA02282 for ; Mon, 11 Jun 2001 01:14:11 -0400 (EDT) Received: from jim (ip-111-95-79.chicago-n.navipath.net [64.111.95.79]) by pimout4-int.prodigy.net (8.11.0/8.11.0) with SMTP id f5B58Lm216548 for ; Mon, 11 Jun 2001 01:08:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Approved-By: JIM FLEMING Message-ID: Date: Mon, 11 Jun 2001 00:09:34 -0500 Reply-To: JIM FLEMING From: JIM FLEMING Subject: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM X-MIME-Autoconverted: from 8bit to quoted-printable by lists.netsol.com id BAA02315 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA21306 As many people are aware, the "toy" IPv4 Internet is useful for doing “proof-of-concept” development of a TLD and all the needed infrastructure, prior to becoming a commercial fixture, set in bedrock on stable IPv6, IPv8 and/or IPv16 networks. As shown below, there are several companies participating in this grand experiment. I think everyone agrees that the Internet will not “crash”. Multiple “roots” are no longer needed. At best they are out-dated publishers of information about TLD Nameserver Clusters. Some people apparently still find it useful to depend on a “root”, as opposed to finding the “dominant” TLD Clusters via simple software. Multiple TLD Clusters are new. There is merit in having redundancy. Unfortunately, consumers will have to learn through their registrar or registry, that they would be prudent to register in BOTH TLD Cluster for the most reliable, stable service, with the widest reach. The SLD.TLD cluster is of course usually unique. How an end user’s resolver locates the SLD.TLD Cluster does not impact the end-users’s resolver interaction with the SLD.TLD Cluster. In this grand “proof-of-concept” experiment, it appears that the TLDs, .SHOP, .TRAVEL, .FREE and possibly .INFO may be the landmark TLDs which test the notion of multiple TLD Clusters. There do not appear to be hundreds in this class, as many people claimed there would be. For some users, it might be more desirable to use the multiple TLD Cluster approach to ensure more stability. In the future, the .COM TLD will also likely become structured this way, in order to ensure that the underlying registry can be changed, by turning off the old one and allowing traffic to be handled by the new .COM TLD Cluster. If that does not occur, the claim will always be made that the incumbent registry can not be changed. People want registries to be changed, without impacting service. It will be interesting to see how this grand “proof-of-concept” experiment evolves on the legacy IPv4 Internet. If multiple TLD Clusters prove to be useful, more desirable, more stable, etc. I would think all engineers would recommend them for future Internet architectures. The IETF seems to be silent about Multiple TLD Clusters. Jim Fleming http://www.unir.com/images/architech.gif http://www.unir.com/images/address.gif http://www.unir.com/images/headers.gif http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp ------------- Dominant Proof-of-Concept Participants http://www.name-space.com http://www.icann.org/tlds/ads1/NameSpace-gtld-appBP.html (* first 20 TLDs) .SHOP <<<<< .SPACE .SEX .ART .ZONE .MUSIC .ONLINE .CONSULTING .DESIGN .TRAVEL <<<<< .MEDIA .NEWS .DIRECT .MAIL .WORLD .MAG .AUCTION .FREE <<<<< .CAM .SERVICE ----------------------- http://www.New.Net .SHOP <<<<< .MP3 .INC .KIDS .SPORT .FAMILY .CHAT .VIDEO .CLUB .HOLA .SOC .MED .LAW .TRAVEL <<<<< .GAME .FREE <<<< .LTD .GMBH .TECH .XXX ---------------------- ISOC/ICANN http://www.dnso.org/clubpublic/ga-full/Arc07/msg02817.html http://www.icann.org/tlds/ .FIRM .STORE .WEB .ARTS .REC .INFO <<<< .NOM .AERO .BIZ .COOP .INFO <<<< .MUSEUM .NAME .PRO _____ _____ _____ _____ _____ _____ --------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 11 03:10:16 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA04131 for ; Mon, 11 Jun 2001 03:10:16 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id CAA02984; Mon, 11 Jun 2001 02:49:52 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3114 for URN-IETF@LISTS.NETSOL.COM; Mon, 11 Jun 2001 02:43:34 -0400 Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id CAA02959 for ; Mon, 11 Jun 2001 02:43:23 -0400 (EDT) Received: from jim (ip-111-95-79.chicago-n.navipath.net [64.111.95.79]) by pimout4-int.prodigy.net (8.11.0/8.11.0) with SMTP id f5B6bGm73522; Mon, 11 Jun 2001 02:37:17 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Approved-By: JIM FLEMING Message-ID: Date: Mon, 11 Jun 2001 01:38:27 -0500 Reply-To: JIM FLEMING From: JIM FLEMING Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <20970567.992247950@localhost> Content-Transfer-Encoding: 7bit Your comments have been noted for future reference. -----Original Message----- From: Patrik Faltstrom [mailto:paf@cisco.com] Sent: Monday, June 11, 2001 1:26 AM To: JIM FLEMING; URN-IETF@LISTS.NETSOL.COM Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters Leslie Daigle, working group chair for the URN wg (which doesn't have email access at the moment) have after getting this email read to her asked me to as Area Director post this message to this mailing list: The message posted by mr Fleming is out of scope for this mailing list. Patrik Faltstrom Co-Area Director, Applications Area From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 11 04:46:33 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04878 for ; Mon, 11 Jun 2001 04:46:32 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id EAA03726; Mon, 11 Jun 2001 04:30:44 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3206 for URN-IETF@LISTS.NETSOL.COM; Mon, 11 Jun 2001 04:24:21 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from cisco.com (nordic.cisco.com [64.103.48.45]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id CAA02916 for ; Mon, 11 Jun 2001 02:33:27 -0400 (EDT) Received: from [0.0.0.0] (ams-vpdn-client-110.cisco.com [144.254.46.111]) by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA11314; Mon, 11 Jun 2001 08:26:50 +0200 (MET DST) References: X-Mailer: Mulberry/2.1.0a6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <20970567.992247950@localhost> Date: Mon, 11 Jun 2001 08:25:50 +0200 Reply-To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: Content-Transfer-Encoding: 7bit Leslie Daigle, working group chair for the URN wg (which doesn't have email access at the moment) have after getting this email read to her asked me to as Area Director post this message to this mailing list: The message posted by mr Fleming is out of scope for this mailing list. Patrik Faltstrom Co-Area Director, Applications Area From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 11 11:29:26 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12688 for ; Mon, 11 Jun 2001 11:29:25 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA06158; Mon, 11 Jun 2001 11:12:47 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3467 for URN-IETF@LISTS.NETSOL.COM; Mon, 11 Jun 2001 11:06:08 -0400 Received: from serrano.hesketh.net (serrano.hesketh.net [66.45.6.210]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA06129 for ; Mon, 11 Jun 2001 11:05:57 -0400 (EDT) Received: from [192.168.124.14] (syr-24-24-11-230.twcny.rr.com [24.24.11.230]) by serrano.hesketh.net (8.11.3/8.11.3) with ESMTP id f5BExhk31767; Mon, 11 Jun 2001 10:59:43 -0400 X-Received-From: simonstl@simonstl.com X-Delivered-To: URN-IETF@LISTS.NETSOL.COM X-Spam-Filter: check_local@serrano.hesketh.net by digitalanswers.org X-More-Information: http://spamfighter.hesketh.net References: <20970567.992247950@localhost> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.10 (Preview Release) Mime-Version: 1.0 Approved-By: "Simon St.Laurent" Message-ID: <992271667.4698.12.camel@localhost.localdomain> Date: Mon, 11 Jun 2001 11:01:07 -0400 Reply-To: "Simon St.Laurent" From: "Simon St.Laurent" Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <20970567.992247950@localhost> On 11 Jun 2001 08:25:50 +0200, Patrik Fältström wrote: > Leslie Daigle, working group chair for the URN wg (which doesn't have email > access at the moment) have after getting this email read to her asked me to > as Area Director post this message to this mailing list: > > > The message posted by mr Fleming is out of scope for this mailing list. Inasmuch as TLDs affect some forms of URI construction fairly fundamentally, it doesn't seem wildly out of scope. Is it possible to request a clarification of why this is out of scope and where at the IETF it would be more appropriate to discuss its impact on URIs? The only other forum for URI discussion I'm aware of is uri@w3.org, and that's not a part of the IETF. I'm aware that this is a complex political issue, and that the scope of this list is technically URNs, but there's plenty of work being done here on URI resolution. http://www.ietf.org/html.charters/urn-charter.html From owner-urn-ietf@LISTS.NETSOL.COM Mon Jun 11 12:27:45 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14077 for ; Mon, 11 Jun 2001 12:27:45 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA06786; Mon, 11 Jun 2001 12:13:03 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3557 for URN-IETF@LISTS.NETSOL.COM; Mon, 11 Jun 2001 12:06:54 -0400 Received: from pimout3-int.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA06748 for ; Mon, 11 Jun 2001 12:06:43 -0400 (EDT) Received: from jim (ip-111-152-204.chicago-n.navipath.net [64.111.152.204]) by pimout3-int.prodigy.net (8.11.0/8.11.0) with SMTP id f5BFxag122498; Mon, 11 Jun 2001 11:59:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Approved-By: JIM FLEMING Message-ID: Date: Mon, 11 Jun 2001 11:00:36 -0500 Reply-To: JIM FLEMING From: JIM FLEMING Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <992271667.4698.12.camel@localhost.localdomain> Content-Transfer-Encoding: 8bit If you live in 2 dimensions... you might consider ietf@ietf.org http://www.ietf.org/mail-archive/ietf/Current/msg12215.html ...for those in 3 dimensions**... http://www.DOT-BIZ.com Jim Fleming http://www.unir.com/images/architech.gif http://www.unir.com/images/address.gif http://www.unir.com/images/headers.gif http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp ** for 4 dimensions... http://www.flatland.com/ http://eldred.ne.mediaone.net/eaa/FL.HTM -----Original Message----- From: Simon St.Laurent [mailto:simonstl@SIMONSTL.COM] Sent: Monday, June 11, 2001 10:01 AM To: URN-IETF@LISTS.NETSOL.COM Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters On 11 Jun 2001 08:25:50 +0200, Patrik Fältström wrote: > Leslie Daigle, working group chair for the URN wg (which doesn't have email > access at the moment) have after getting this email read to her asked me to > as Area Director post this message to this mailing list: > > > The message posted by mr Fleming is out of scope for this mailing list. Inasmuch as TLDs affect some forms of URI construction fairly fundamentally, it doesn't seem wildly out of scope. Is it possible to request a clarification of why this is out of scope and where at the IETF it would be more appropriate to discuss its impact on URIs? The only other forum for URI discussion I'm aware of is uri@w3.org, and that's not a part of the IETF. I'm aware that this is a complex political issue, and that the scope of this list is technically URNs, but there's plenty of work being done here on URI resolution. http://www.ietf.org/html.charters/urn-charter.html From owner-urn-ietf@LISTS.NETSOL.COM Tue Jun 12 06:32:37 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11455 for ; Tue, 12 Jun 2001 06:32:36 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id GAA11578; Tue, 12 Jun 2001 06:10:36 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3767 for URN-IETF@LISTS.NETSOL.COM; Tue, 12 Jun 2001 06:01:23 -0400 Received: from urz07.urz.uni-bamberg.de (urz07.urz.uni-bamberg.de [141.13.240.7]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id GAA11542 for ; Tue, 12 Jun 2001 06:01:22 -0400 (EDT) Received: from urz01.urz.uni-bamberg.de (urz01.urz.uni-bamberg.de [141.13.240.3]) by urz07.urz.uni-bamberg.de (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with ESMTP id LAA02348 for ; Tue, 12 Jun 2001 11:55:35 +0200 Received: from URZ01/SpoolDir by urz01.urz.uni-bamberg.de (Mercury 1.47); 12 Jun 01 11:55:33 GMT+0200 Received: from SpoolDir by URZ01 (Mercury 1.47); 12 Jun 01 11:55:20 GMT+0200 Received: from ppp.uni-bamberg.de (213.7.42.168) by urz01.urz.uni-bamberg.de (Mercury 1.47) with ESMTP; 12 Jun 01 11:55:18 GMT+0200 X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: de,en MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.netsol.com id GAA11543 Approved-By: Dieter =?iso-8859-1?Q?K=F6hler?= Message-ID: <3B25E6BD.967F61F5@ppp.uni-bamberg.de> Date: Tue, 12 Jun 2001 11:54:05 +0200 Reply-To: Dieter =?iso-8859-1?Q?K=F6hler?= From: Dieter =?iso-8859-1?Q?K=F6hler?= Subject: Formal Namespace Discussion List? To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 8bit I am interested in developing a formal URN namespace for philological text references, and therefore looking for some advice how to proceed. Is the IETF planing to establish a formal namespace working group where a discussion about such a proposal may take place? Are there similar activities elsewhere I can join? Beside that: If some individual on this list is interested in reviewing a proposal, please contact me. Dieter Köhler, M.A. Philosophy Chair II Staff University of Bamberg (Germany) -- ===================================================================== Dieter Köhler, M. A. - dieter.koehler@ppp.uni-bamberg.de Mittlere Kaulberg 22, D-96049 Bamberg, +49(0)951-5190726 "http://www.philo.de/Philosophie-Seiten/": 1000+ Philosophie-Links "http://www.philo.de/VirtualLibrary/14.de.htm": Deutsche Philo-Links "http://www.philo.de/xml/": Open XML - XML-Komponenten für Delphi ===================================================================== From owner-urn-ietf@LISTS.NETSOL.COM Tue Jun 12 10:41:06 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16669 for ; Tue, 12 Jun 2001 10:41:06 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA12914; Tue, 12 Jun 2001 10:25:41 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3861 for URN-IETF@LISTS.NETSOL.COM; Tue, 12 Jun 2001 10:18:37 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from sh.w3.mag.keio.ac.jp (sh.w3.mag.keio.ac.jp [133.27.194.41]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id GAA11630 for ; Tue, 12 Jun 2001 06:20:22 -0400 (EDT) Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243]) by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id TAA01146; Tue, 12 Jun 2001 19:14:15 +0900 (JST) X-Sender: duerst@sh.w3.mag.keio.ac.jp X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J References: <20970567.992247950@localhost> <20970567.992247950@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: <4.2.0.58.J.20010612173606.00d48cd0@sh.w3.mag.keio.ac.jp> Date: Tue, 12 Jun 2001 17:44:39 +0900 Reply-To: Martin Duerst From: Martin Duerst Subject: Re: Proof of Concept TLD Development...and Multiple TLD Clusters To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <992271667.4698.12.camel@localhost.localdomain> At 11:01 01/06/11 -0400, Simon St.Laurent wrote: >Is it possible to request a clarification of why this is out of scope >and where at the IETF it would be more appropriate to discuss its impact >on URIs? The only other forum for URI discussion I'm aware of is >uri@w3.org, and that's not a part of the IETF. uri@w3.org is the continuation of the IETF uri mailing list (see http://lists.w3.org/Archives/Public/uri/). W3C offered to host it in mid 1999 when bunyip (the former host) looked for a new host. As the URI WG has completed, this mailing list has the same status as any other mailing list of an IETF WG that has completed. I'm not sure whether the formal status of such lists is defined/discussed anywhere, but I guess it's fairly usual to use such lists for discussions related to the topic, because it's always possible that questions come up after a WG has completed. Regards, Martin. From owner-urn-ietf@LISTS.NETSOL.COM Tue Jun 12 11:14:27 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17436 for ; Tue, 12 Jun 2001 11:14:26 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA13258; Tue, 12 Jun 2001 11:00:50 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 3910 for URN-IETF@LISTS.NETSOL.COM; Tue, 12 Jun 2001 10:55:18 -0400 Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA13202 for ; Tue, 12 Jun 2001 10:55:11 -0400 (EDT) Received: from world.std.com (world-f.std.com [199.172.62.5]) by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id KAA5336487 for ; Tue, 12 Jun 2001 10:49:08 -0400 (EDT) Received: from [24.218.56.92] (h000a2792745c.ne.mediaone.net [24.218.56.92]) by world.std.com (8.9.3/8.9.3) with ESMTP id KAA23927 for ; Tue, 12 Jun 2001 10:49:07 -0400 (EDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Approved-By: "Arnold G. Reinhold" Message-ID: Date: Tue, 12 Jun 2001 10:49:01 -0400 Reply-To: "Arnold G. Reinhold" From: "Arnold G. Reinhold" Subject: a META URN? To: URN-IETF@LISTS.NETSOL.COM I am new to this list and have been reviewing the archives. In reading the thread on the OID names space a thought occurred to me that may be of interest. I realized that it may have been discussed before or be way out of scope, but here it is for what is is worth. One point of discussion was whether or not the OID namespace should include the text tags for each node of the OID tree as seen here: urn:oid:itu-t(0)/identified-organization(4)/etsi(0)/electronic-signatu re-standard(1733)/part1(1)/idupMechanism(4)/etsiESv1(1) or, as ultimately proposed, only include the digits themselves as seen here: urn:oid:0.4.0.1733.1.4.1 While I agree that text tags should be omitted, nonetheless, it would be helpful to have a way of obtaining the text tags for a full or partial OID URN. The same might be true of other URN name spaces. While it seems clear that the choice to provide such a service should be up to the name space owner, it might be useful to have a standard way to reference such a service. This lead me to think about other such services and I came up with a rather long list of meta data services that might be of general use over the spectrum of NIDs. It might be useful to have a standard name for these meta services, whenever the service exists. One could reserve names within each name space, perhaps by using a character that is now reserved. A less intrusive approach would be to create a new NID for meta services. URN:META: where: meta-service-ID is the number assigned to a service meta-service-modifiers might designate language requested, meta data subfields, etc. the meta-special-charcter would be serve as a delimiter and would be illegal in the meta-service-ID and meta-service-modifiers fields, but could occur subsequently in the referenced URN. Here are some possible meta services I came up with that would apply to an entire name space: Name space owner Owner contact information Available Meta services Meta data encoding (ISO, Unicode, UTF-8,...) Available languages for Meta data (rfc1766) Owner public key NID RFC NID RFC version history URN assignment information (how to register a name) Content purchase/subscription information Content licensing information Pricing currency Legal notices (copyright, privacy restrictions, license terms, etc) Integrity verification executable object Signature executable object Decompression executable object Software library Search service Here are some metadata types that would apply on a per-URN basis. Where possible, the types here might be coordinated with the Dublin Core Metadata Initiative http://dublincore.org/ Interpretation of URN string Title Abstract Table of Contents Date File size Integrity verifier (e.g. hash value) File format Language (rfc1766) Price Signature Integrity verification algorithm Signature algorithm Compression algorithm At the least, it would be useful to reserve the URN name META for this type of service. Arnold Reinhold From owner-urn-ietf@LISTS.NETSOL.COM Wed Jun 13 11:55:51 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25803 for ; Wed, 13 Jun 2001 11:55:50 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA20103; Wed, 13 Jun 2001 11:37:25 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 4232 for URN-IETF@LISTS.NETSOL.COM; Wed, 13 Jun 2001 11:29:05 -0400 Received: from donald.zblmath.fiz-karlsruhe.de (donald.zblmath.FIZ-Karlsruhe.DE [141.66.176.200]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA20070 for ; Wed, 13 Jun 2001 11:28:58 -0400 (EDT) Received: from zblmath.fiz-karlsruhe.de (minux.zblmath.fiz-karlsruhe.de [141.66.176.15]) by donald.zblmath.fiz-karlsruhe.de (8.9.3/8.9.3) with ESMTP id SAA24242; Wed, 13 Jun 2001 18:42:32 +0200 X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: derr@ZBLMATH.FIZ-KARLSRUHE.DE Message-ID: <3B278720.D1FC0E9B@zblmath.fiz-karlsruhe.de> Date: Wed, 13 Jun 2001 17:30:40 +0200 Reply-To: Michael Derr From: Michael Derr Subject: [Fwd: questions about managing URN-namespaces / progress of implementation] To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit To the IETF URN WG: I forwarded this massage to the URN WG, because I sent it several month ago to the IANA organization without getting any answere . I think this is also a right place to ask for your comments. May be you have some answeres or suggestions. Thank you very much for your support. regards Michael ###################################################################### Michael Derr wrote: Date: Mon, 22 Jan 2001 11:20:56 +0100 From: Michael Derr To: iana@iana.org Subject: questions about managing URN-namespaces / progress of implementation > To the IANA organization: > > As a member of the project CARMEN/sub task AP4 > (http://www.bis.uni-oldenburg.de/carmen_ap4/index.html), part of the > Global Info Project (http://www.global-info.org/index.html.en) I am > busy with the potentials of URN concepts for scientific documents on > the web. My interests concern managing URNs and namespaces. Of course > current developments of URN technology on global scale are my > interests too. > > My motivation for writing this mail is the hope to clear the role of > IANA concerning the matter of URN technology and progress of > implementation. > > The IETF-URN working group published many contributions concerning > perspectives of URN. One of the results of steady discussion in the > forum of URN working group is, that the IANA is proposed to manage the > procedure of namespace registration for URNs. > > Recently, in RFC2915 IANA was designated as the institution to > administer > globally unique namespaces to be createwd for URNs. > > Here are my questions and I would be very grateful to receive your > comments: > > - In the draft "draft-mealling-iana-urn-00.txt" published Nov, > 17th, 2000 in the IETF-URN forum, a IANA URN namespace is > > proposed. Is IANA intending special administration procedures for > URNs or is this a obligatory standard procedure for namespace > registration (first formulated in RFC2141)? > > - Does IANA agree with the proposals as formulated in RFC2915 and is > there a schedule for implementation so that namespaces could > resolved > on global scale in near future? Is IANA yet involved in the > process of realizing URN-technology? > > - Implementing and maintaining URNs will cause costs and effort. > What are the plans, if they exist, about financing these services? > > - There are some technical aspects besides the pure URN concepts: IDF, > > OCLC-PURL service, PlugIn solutions for namespaces (e.g. ISSN). > These projects solve the problem of unstable URLs and give > stable references for electronic documents a perspective. Could > these > conventional techniques be "the solution" and maybe supersede the > realization of URN techniques or even obsolets it? > > Please inform me as well if you think that IANA is *not* the > appropriate adress for the above questions. > > Thank you very much for your support! > > Any response is appreciated. > > Regards > > Michael Derr > > ------------------------ > >> Michael Derr > >> FIZ Karlsruhe, > >> Zentralblatt fuer Mathematik > >> Franklinstr. 11 > >> D 10587 Berlin /FRG > > >> Tel: (49)(30) 399 93 4 - 25 > >> Fax: (49)(30) 392 70 09 > ------------------------ ###################################################################### From owner-urn-ietf@LISTS.NETSOL.COM Wed Jun 13 12:59:32 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27347 for ; Wed, 13 Jun 2001 12:59:32 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA20737; Wed, 13 Jun 2001 12:44:15 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 4309 for URN-IETF@LISTS.NETSOL.COM; Wed, 13 Jun 2001 12:36:41 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA20542 for ; Wed, 13 Jun 2001 12:20:30 -0400 (EDT) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id MAA06320; Wed, 13 Jun 2001 12:09:33 -0400 (EDT) References: <3B278720.D1FC0E9B@zblmath.fiz-karlsruhe.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i Message-ID: <20010613120933.B6005@bailey.dscga.com> Date: Wed, 13 Jun 2001 12:09:33 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: Re: [Fwd: questions about managing URN-namespaces / progress of implementation] To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <3B278720.D1FC0E9B@zblmath.fiz-karlsruhe.de>; from derr@zblmath.FIZ-Karlsruhe.DE on Wed, Jun 13, 2001 at 05:30:40PM +0200 On Wed, Jun 13, 2001 at 05:30:40PM +0200, Michael Derr wrote: > To the IETF URN WG: > > I forwarded this massage to the URN WG, because I sent it several month ago > to the IANA organization without getting any answere . > > I think this is also a right place to ask for your comments. > May be you have some answeres or suggestions. I'll take a stab at these since 2915 is mostly my puppy. ;-) To be clear the documents we're talking about here are being updated as we speak by the following documents: Dynamic Delegation Discovery System (DDDS) draft-ietf-urn-ddds-04.txt A DDDS Database Using The Domain Name System draft-ietf-urn-dns-ddds-database-05.txt URI Resolution using the Dynamic Delegation Discovery System draft-ietf-urn-uri-res-ddds-03.txt Assignment Procedures for the URI Resolution using DNS draft-ietf-urn-net-procedures-08.txt URN Namespace Definition Mechanisms draft-ietf-urn-rfc2611bis-03.txt > > As a member of the project CARMEN/sub task AP4 > > (http://www.bis.uni-oldenburg.de/carmen_ap4/index.html), part of the > > Global Info Project (http://www.global-info.org/index.html.en) I am > > busy with the potentials of URN concepts for scientific documents on > > the web. My interests concern managing URNs and namespaces. Of course > > current developments of URN technology on global scale are my > > interests too. > > > > My motivation for writing this mail is the hope to clear the role of > > IANA concerning the matter of URN technology and progress of > > implementation. With respect to URNs the IANA is only in a registration role. They don't interact with technology or standards development beyond simply acting as the place where we stick all of our registered numbers... > > The IETF-URN working group published many contributions concerning > > perspectives of URN. One of the results of steady discussion in the > > forum of URN working group is, that the IANA is proposed to manage the > > procedure of namespace registration for URNs. Yep. The specific document that lays all of that out is RFC 2611 which is currently being updated at the request of the IESG. See above for the current draft. > > Recently, in RFC2915 IANA was designated as the institution to > > administer globally unique namespaces to be createwd for URNs. Not really. 2915 references the definitive document which is 2611. 2611 is the one that designates the IANA as the authority and specifies the policies/procedures that the IANA has to adhere to. > > Here are my questions and I would be very grateful to receive your > > comments: > > > > - In the draft "draft-mealling-iana-urn-00.txt" published Nov, > > 17th, 2000 in the IETF-URN forum, a IANA URN namespace is > > proposed. Is IANA intending special administration procedures for > > URNs or is this a obligatory standard procedure for namespace > > registration (first formulated in RFC2141)? This document is still in discussion but what it is proposing is seperate from URN namespace id registration in general. The IANA has a large number of different values in its registration database (port numbers, enterprise numbers, http parameters, etc). draft-mealling-iana-urn-00.txt is an attempt at creating a new URN namespace that is specifically for assigning a permanent name to all of the parameters that the IANA maintains so that they can be talked about in other protocols such as SOAP and RDF. So its not really talking about the general URN NID registration process. > > - Does IANA agree with the proposals as formulated in RFC2915 and is > > there a schedule for implementation so that namespaces could > > resolved on global scale in near future? The IANA reviews the IANA Considerations section of all RFCs to make sure they can handle what the document is asking of it. But beyond that the IANA generally doesn't comment officially on standards... > > Is IANA yet involved in the process of realizing URN-technology? In 2915 (which is being udpated by draft-ietf-urn-net-procedures-08.txt and is the document you should be looking at) the IANA is tasked with running the uri.arpa and urn.arpa nameservers and with putting the records in those zones according to the policies/procedures in draft-ietf-urn-net-procedures-08.txt. Beyond that the IANA is not involved in 'realizing' any technology. > > - Implementing and maintaining URNs will cause costs and effort. > > What are the plans, if they exist, about financing these services? Questions such as this are left up to the individual namespace. The IETF does not deal with these issues at all since it is not an industry consortium like the W3C where questions like that are in scope. > > - There are some technical aspects besides the pure URN concepts: IDF, > > > > OCLC-PURL service, PlugIn solutions for namespaces (e.g. ISSN). > > These projects solve the problem of unstable URLs and give > > stable references for electronic documents a perspective. Could > > these conventional techniques be "the solution" and maybe supersede the > > realization of URN techniques or even obsolets it? It depends on what problem you are trying to solve. PURLs depend on OCLC existing for thousands of years. URNs on the other hand only depend on some other entity not attempting to pirate your namespace. > > Please inform me as well if you think that IANA is *not* the > > appropriate adress for the above questions. Generally no. The IANA is just a database with a human face. It can't answer questions about who/why/how something in it was created. It can only tell you the values in the database and the procedures for putting something in it. -MM -- -------------------------------------------------------------------------------- Michael Mealling | mailto:michael@research.netsol.com Advanced Naming Research Manager | go:Michael Mealling Verisign Applied Research | urn:pin:1