From mailnull@www1.ietf.org Mon Apr 7 10:06:08 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20209 for ; Mon, 7 Apr 2003 10:06:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h37EAMc13803 for urn-nid-archive@odin.ietf.org; Mon, 7 Apr 2003 10:10:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37EAM813800 for ; Mon, 7 Apr 2003 10:10:22 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20153 for ; Mon, 7 Apr 2003 10:05:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37EA6813757; Mon, 7 Apr 2003 10:10:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h33N4CK08087 for ; Thu, 3 Apr 2003 18:04:12 -0500 Received: from ithilien.qualcomm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18142 for ; Thu, 3 Apr 2003 18:01:12 -0500 (EST) Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h33N3Zks014639 for ; Thu, 3 Apr 2003 15:03:39 -0800 (PST) Received: from qualcomm.com (carbuncle.qualcomm.com [129.46.227.161]) by magus.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h33N3Xcr015476 for ; Thu, 3 Apr 2003 15:03:34 -0800 (PST) Date: Thu, 3 Apr 2003 15:03:31 -0800 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Fwd: draft-walsh-urn-web3d-00.txt From: Ted Hardie To: urn-nid@apps.ietf.org Content-Transfer-Encoding: 7bit Message-Id: <7D3B3CA9-6628-11D7-83A5-000393CB0816@qualcomm.com> X-Mailer: Apple Mail (2.551) Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, draft-walsh-urn-web3d-00 has come in as a proposal for a URN NID. If you have a chance, please review the document and send any comments to me. best regards, Ted Hardie Begin forwarded message: > From: ned.freed@mrochek.com > Date: Wed Mar 19, 2003 8:04:44 PM US/Pacific > To: hardie@qualcomm.com > Cc: ned.freed@mrochek.com, paf@cisco.com > Subject: draft-walsh-urn-web3d-00.txt > > I have been seriously remiss in not looking at this individual > submission, so I > just did so. I found that it is a definition of a URN scheme, and > hence seemed > more in Ted's camp than mine. So I took the liberty of switching it > over to > Ted. Feel free to switch it back to me if that's appropriate. Patrik, > if you > know of some reason why this was assigned to me, please let me know. > > Ned > From mailnull@www1.ietf.org Mon Apr 7 10:06:08 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20224 for ; Mon, 7 Apr 2003 10:06:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h37EANq13819 for urn-nid-archive@odin.ietf.org; Mon, 7 Apr 2003 10:10:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37EAN813816 for ; Mon, 7 Apr 2003 10:10:23 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20155 for ; Mon, 7 Apr 2003 10:05:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37EAA813780; Mon, 7 Apr 2003 10:10:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37A40828604 for ; Mon, 7 Apr 2003 06:04:00 -0400 Received: from mail.gmx.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13485 for ; Mon, 7 Apr 2003 05:59:20 -0400 (EDT) Received: (qmail 19271 invoked by uid 65534); 7 Apr 2003 10:01:50 -0000 Received: from p5082DBB1.dip.t-dialin.net (EHLO gmx.de) (80.130.219.177) by mail.gmx.net (mp009-rz3) with SMTP; 07 Apr 2003 12:01:50 +0200 Message-ID: <3E914C67.6070805@gmx.de> Date: Mon, 07 Apr 2003 12:01:11 +0200 From: Benja Fallenstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4 X-Accept-Language: en MIME-Version: 1.0 To: urn-nid@apps.ietf.org Subject: Update to urn-5 informal namespace registration Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, below, please find an updated version of our urn-5 application. The following changes have been made: - For new identifiers, 27 random characters (162 bits) rather than 26 characters (156 bits) are required. - "160 bytes" has been changed to "160 bits" in two places. - The notion that using the local part for anything but counting is 'strongly discouraged' has been removed. Please review the updated application. Thanks, - Benja -- snip -- Namespace ID: urn-5 Registration Information: Version 2 Date: Declared registrant of the namespace: Name: University of Jyväskylä Hyperstructure Group Address: Dept. of Mathematical Information Technology University of Jyväskylä PO. Box 35 (Agora) FIN-40014 Jyväskylä Finland Contact: B. Fallenstein Declaration of syntactic structure: The identifier structure is: urn::[:] where is a string consisting of at least 27 of the following characters: Lowercase (a-z) and uppercase (A-Z) letters, digits (0-9), the hyphen (-) and the plus sign (+). If present, the optional is an arbitrary string of characters allowed in a URN without escaping. The is a pseudo-random number (160 or more bits) encoded in base64 [RFC-2045]. As slashes (/) are not currently allowed as part of URNs, hyphens (-) are used instead. The padding character (=) is not used. (An earlier version of this specification allowed to be only 26 characters long, making for only 156 random bits. Such identifiers must still be recognized, but new identifiers should contain at least 27 random characters.) The is a counter, intended to allow re-use of a pseudo-random number; this allows a program to generate only one pseudo-random number per session, only incrementing a counter each time a new identifier is generated. Compression of documents containing many different identifiers of this form is improved if some of the identifiers share the part. Examples of possible URNs in this namespace include: urn:urn-n:-URS6S2A3+chjjHVlTkQ9KT5nu2 urn:urn-n:JtTCacwJ1e1N0yqTULRG7C1GLq8:4 urn:urn-n:Od4rB2QNOLt1e5wITWSJ+9U2Ve+Zon6N3d:17 (In these examples, urn-n is a placeholder for the namespace id to be assigned by IANA. The examples are not URNs in actual use.) Relevant ancillary documentation: RFC 2045 [RFC-2045] defines the base64 encoding. Note that the hyphen (-) is used instead of the slash (/). Identifier uniqueness considerations: Provided that the source of pseudo-random data used is good enough, it can be reasonably assumed that identifiers are unique (for example, SHA-1 [FIPS-180-1] also assumes uniqueness of 160 bit identifiers). Identifier persistence considerations: Users must not re-assign an identifier. This is not a problem, since they are free to create new identifiers at any time. Process of identifier assignment: Identifiers can be informally assigned by users at any time. There is no central authority assigning identifiers or specifying meaning for them. New identifiers are created when a user or program wants to name some entity globally without contacting a naming authority first. Examples include RDF resources [RDF] and XML namespace names [XML-namespaces]. Users specify meaning for identifiers by starting to use them, for example in an RDF graph. If local parts are not used, an identifier is created by generating 160 or more bits of pseudo-random data from a trusted source and encoding them in base64, using the characters allowable in the part as defined above. If local parts are used, the part is generated beforehand (usually when the program generating the identifiers is started, or when the first identifier in a particular session is created); each time a new identifier is needed, a counter is incremented and used as the . Process for identifier resolution: None specified. Note that the namespace is primarily meant for resources that are only named, not resolved (such as XML namespace names). Rules for Lexical Equivalence: The normal rules for lexical equivalence of URNs apply. Conformance with URN Syntax: No special considerations. Validation mechanism: The namespace-specific string (nss) must abide the following ABNF [RFC-2234] grammar: nss = random-number / (random-number ":" urn-string) random-number = 26*base64 urn-string = ALPHA / DIGIT / other base64 = ALPHA / DIGIT / "+" / "-" other = "(" / ")" / "+" / "," / "-" / "." / ":" / "=" / "@" / ";" / "$" / "_" / "!" / "*" / "'" For new identifiers, random-number must be at least 27 characters long. Scope: Global. References: [FIPS-180-1] NIST, FIPS PUB 180-1: Secure Hash Standard, April 1995. http://csrc.nist.gov/fips/fip180-1.txt (ascii) http://csrc.nist.gov/fips/fip180-1.ps (postscript) [RDF] RDF Model and Syntax. http://www.w3.org/TR/1999/REC-rdf-syntax-19990222 [RFC-2045] Freed, N., and Borenstein, N., "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996. [RFC-2234] Crocker, D., and Overell, P., "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997. [XML-Namespaces] Namespaces in XML. http://www.w3.org/TR/1999/REC-xml-names-19990114 From mailnull@www1.ietf.org Mon Apr 7 11:05:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23133 for ; Mon, 7 Apr 2003 11:05:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h37FA7Z18433 for urn-nid-archive@odin.ietf.org; Mon, 7 Apr 2003 11:10:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37FA7818430 for ; Mon, 7 Apr 2003 11:10:07 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23124 for ; Mon, 7 Apr 2003 11:05:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37FA1818420; Mon, 7 Apr 2003 11:10:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37F9H818379 for ; Mon, 7 Apr 2003 11:09:17 -0400 Received: from neonym.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23072 for ; Mon, 7 Apr 2003 11:04:28 -0400 (EDT) Received: from [207.120.28.115] ([::ffff:207.120.28.115]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Sun, 06 Apr 2003 21:39:55 -0400 Subject: Re: Fwd: draft-walsh-urn-web3d-00.txt From: Michael Mealling To: Ted Hardie Cc: urn-nid@apps.ietf.org In-Reply-To: <7D3B3CA9-6628-11D7-83A5-000393CB0816@qualcomm.com> References: <7D3B3CA9-6628-11D7-83A5-000393CB0816@qualcomm.com> Organization: Harriman Heavy Industries, Inc. Message-Id: <1049727851.8029.1.camel@blackdell.neonym.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.2.2 Date: 07 Apr 2003 11:04:11 -0400 Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Thu, 2003-04-03 at 18:03, Ted Hardie wrote: > Hi, > draft-walsh-urn-web3d-00 has come in as a proposal > for a URN NID. If you have a chance, please review the > document and send any comments to me. Hi Ted, We've reviewed it here. It was posted to the list here: http://lists.research.netsol.com/pipermail/urn-nid/2002-March/000286.html And it has long been finished with its review process. Its ready to be published.... -MM > Begin forwarded message: > > > From: ned.freed@mrochek.com > > Date: Wed Mar 19, 2003 8:04:44 PM US/Pacific > > To: hardie@qualcomm.com > > Cc: ned.freed@mrochek.com, paf@cisco.com > > Subject: draft-walsh-urn-web3d-00.txt > > > > I have been seriously remiss in not looking at this individual > > submission, so I > > just did so. I found that it is a definition of a URN scheme, and > > hence seemed > > more in Ted's camp than mine. So I took the liberty of switching it > > over to > > Ted. Feel free to switch it back to me if that's appropriate. Patrik, > > if you > > know of some reason why this was assigned to me, please let me know. > > > > Ned > > > From mailnull@www1.ietf.org Mon Apr 7 18:27:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09232 for ; Mon, 7 Apr 2003 18:27:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h37MW9318977 for urn-nid-archive@odin.ietf.org; Mon, 7 Apr 2003 18:32:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37MW8818974 for ; Mon, 7 Apr 2003 18:32:08 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09225 for ; Mon, 7 Apr 2003 18:27:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37MW5818965; Mon, 7 Apr 2003 18:32:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37MVq818951 for ; Mon, 7 Apr 2003 18:31:52 -0400 Received: from neonym.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09219 for ; Mon, 7 Apr 2003 18:26:57 -0400 (EDT) Received: from [207.120.28.115] ([::ffff:207.120.28.115]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Mon, 07 Apr 2003 05:03:08 -0400 Subject: Re: Fwd: draft-walsh-urn-web3d-00.txt From: Michael Mealling To: "Aaron E. Walsh" Cc: Ted Hardie , urn-nid@apps.ietf.org In-Reply-To: <3E91F94C.6070004@mantiscorp.com> References: <7D3B3CA9-6628-11D7-83A5-000393CB0816@qualcomm.com> <1049727851.8029.1.camel@blackdell.neonym.net> <3E91F94C.6070004@mantiscorp.com> Organization: Harriman Heavy Industries, Inc. Message-Id: <1049754446.8029.27.camel@blackdell.neonym.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.2.2 Date: 07 Apr 2003 18:27:26 -0400 Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Mon, 2003-04-07 at 18:18, Aaron E. Walsh wrote: > Thanks Michael and Ted. I submitted this last March on behalf of the > Web3D Consortium, before which I posted the draft to the IETF URN-NID > group for review as well. The Web3D Consortium has been using "web3d" > for many years now (notes on that in my earlier posts to > urn-nid@apps.ietf.org) and this was the final stage to formally register > the NID. As the review process expired long ago (with no comments or > objections) it's ready to be published as Michael suggests. > > With this in mind can I safely report to the Web3D Consortium that the > web3d NID is officially registered? Not quite yet. I'd say you can say that as soon as the publication announcement happens. I suspect that will be a day or so from now since I doubt this will require an IETF last call... Usually the IANA gets around to putting the item in the actual repository about the same time as the authors 48 hours. In your case I suspect that would be about two weeks after the publication announcement. But that's just a wild, hairy guess.... If you want to watch its progress go here: https://datatracker.ietf.org/public/pidtracker.cgi and enter your draft's file name (draft-walsh-urn-web3d is sufficient). -MM From mailnull@www1.ietf.org Thu Apr 10 14:11:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28978 for ; Thu, 10 Apr 2003 14:11:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3AIH9700702 for urn-nid-archive@odin.ietf.org; Thu, 10 Apr 2003 14:17:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIH9800699 for ; Thu, 10 Apr 2003 14:17:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28940 for ; Thu, 10 Apr 2003 14:10:50 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 193gFZ-0003Fh-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:13 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 193gFY-0003Fe-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:12 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIH4800686; Thu, 10 Apr 2003 14:17:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h38MqU807283 for ; Tue, 8 Apr 2003 18:52:30 -0400 Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07127 for ; Tue, 8 Apr 2003 18:47:04 -0400 (EDT) Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h38MnZbj025354 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 8 Apr 2003 15:49:35 -0700 (PDT) Received: from qualcomm.com (carbuncle.qualcomm.com [129.46.227.161]) by magus.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h38MnXcr016619 for ; Tue, 8 Apr 2003 15:49:34 -0700 (PDT) Date: Tue, 8 Apr 2003 15:49:39 -0700 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Please review http://www.ietf.org/internet-drafts/draft-smith-urn-mpeg-01.txt From: Ted Hardie To: urn-nid@apps.ietf.org Content-Transfer-Encoding: 7bit Message-Id: <61944012-6A14-11D7-A412-000393CB0816@qualcomm.com> X-Mailer: Apple Mail (2.551) Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Please review this proposal for an MPEG URN NID and let me know your thoughts, regards, Ted Hardie From mailnull@www1.ietf.org Thu Apr 10 14:11:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28992 for ; Thu, 10 Apr 2003 14:11:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3AIHAU00718 for urn-nid-archive@odin.ietf.org; Thu, 10 Apr 2003 14:17:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIHA800715 for ; Thu, 10 Apr 2003 14:17:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28944 for ; Thu, 10 Apr 2003 14:10:51 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 193gFa-0003Fn-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:14 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 193gFZ-0003Fk-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIH2800654; Thu, 10 Apr 2003 14:17:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37MLN818385 for ; Mon, 7 Apr 2003 18:21:23 -0400 Received: from smtp.9netave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08924 for ; Mon, 7 Apr 2003 18:16:26 -0400 (EDT) Received: from mantiscorp.com (pool-151-203-247-56.bos.east.verizon.net [151.203.247.56]) by smtp.9netave.com (8.9.3p2/8.8.8) with ESMTP id SAA32095; Mon, 7 Apr 2003 18:08:18 -0400 (EDT) Message-ID: <3E91F94C.6070004@mantiscorp.com> Date: Mon, 07 Apr 2003 18:18:52 -0400 From: "Aaron E. Walsh" Organization: Mantis Development Corp. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Mealling CC: Ted Hardie , urn-nid@apps.ietf.org Subject: Re: Fwd: draft-walsh-urn-web3d-00.txt References: <7D3B3CA9-6628-11D7-83A5-000393CB0816@qualcomm.com> <1049727851.8029.1.camel@blackdell.neonym.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thanks Michael and Ted. I submitted this last March on behalf of the Web3D Consortium, before which I posted the draft to the IETF URN-NID group for review as well. The Web3D Consortium has been using "web3d" for many years now (notes on that in my earlier posts to urn-nid@apps.ietf.org) and this was the final stage to formally register the NID. As the review process expired long ago (with no comments or objections) it's ready to be published as Michael suggests. With this in mind can I safely report to the Web3D Consortium that the web3d NID is officially registered? Regards, Aaron -- ------------------------------------------------------------------- Aaron E. Walsh http://www.mantiscorp.com/people/aew/ 617.536.3279 ------------------------------------------------------------------- Michael Mealling wrote: > On Thu, 2003-04-03 at 18:03, Ted Hardie wrote: > >>Hi, >> draft-walsh-urn-web3d-00 has come in as a proposal >>for a URN NID. If you have a chance, please review the >>document and send any comments to me. > > > Hi Ted, > We've reviewed it here. It was posted to the list here: > http://lists.research.netsol.com/pipermail/urn-nid/2002-March/000286.html > And it has long been finished with its review process. Its ready to be > published.... > > -MM > > > >>Begin forwarded message: >> >> >>>From: ned.freed@mrochek.com >>>Date: Wed Mar 19, 2003 8:04:44 PM US/Pacific >>>To: hardie@qualcomm.com >>>Cc: ned.freed@mrochek.com, paf@cisco.com >>>Subject: draft-walsh-urn-web3d-00.txt >>> >>>I have been seriously remiss in not looking at this individual >>>submission, so I >>>just did so. I found that it is a definition of a URN scheme, and >>>hence seemed >>>more in Ted's camp than mine. So I took the liberty of switching it >>>over to >>>Ted. Feel free to switch it back to me if that's appropriate. Patrik, >>>if you >>>know of some reason why this was assigned to me, please let me know. >>> >>> Ned >>> >> > > > > From mailnull@www1.ietf.org Thu Apr 10 14:11:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29006 for ; Thu, 10 Apr 2003 14:11:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3AIHC400744 for urn-nid-archive@odin.ietf.org; Thu, 10 Apr 2003 14:17:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIHC800741 for ; Thu, 10 Apr 2003 14:17:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28951 for ; Thu, 10 Apr 2003 14:10:54 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 193gFc-0003Fz-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:16 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 193gFc-0003Fw-00 for urn-nid-web-archive@ietf.org; Thu, 10 Apr 2003 13:54:16 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIH3800670; Thu, 10 Apr 2003 14:17:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h38MpK807206 for ; Tue, 8 Apr 2003 18:51:20 -0400 Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07097 for ; Tue, 8 Apr 2003 18:45:53 -0400 (EDT) Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h38MmQbj025230 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 8 Apr 2003 15:48:26 -0700 (PDT) Received: from qualcomm.com (carbuncle.qualcomm.com [129.46.227.161]) by neophyte.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h38MmOLq019804 for ; Tue, 8 Apr 2003 15:48:24 -0700 (PDT) Date: Tue, 8 Apr 2003 15:48:30 -0700 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Please review http//www.ietf.org/internet-drafts/draft-gustin-goyens-urn-id-02.txt From: Ted Hardie To: urn-nid@apps.ietf.org Content-Transfer-Encoding: 7bit Message-Id: <382477C0-6A14-11D7-A412-000393CB0816@qualcomm.com> X-Mailer: Apple Mail (2.551) Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Please review this proposal for swift URN namespace, and let me know your thoughts, regards, Ted Hardie From mailnull@www1.ietf.org Fri Apr 11 13:02:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21329 for ; Fri, 11 Apr 2003 13:02:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3BH97X11142 for urn-nid-archive@odin.ietf.org; Fri, 11 Apr 2003 13:09:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3BH97811139 for ; Fri, 11 Apr 2003 13:09:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21320 for ; Fri, 11 Apr 2003 13:02:22 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 1941xR-0004Ft-00 for urn-nid-web-archive@ietf.org; Fri, 11 Apr 2003 13:04:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1941xR-0004Fq-00 for urn-nid-web-archive@ietf.org; Fri, 11 Apr 2003 13:04:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3BH93811131; Fri, 11 Apr 2003 13:09:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3BH8g811107 for ; Fri, 11 Apr 2003 13:08:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21309 for ; Fri, 11 Apr 2003 13:01:57 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 1941x2-0004Ff-00 for urn-nid@apps.ietf.org; Fri, 11 Apr 2003 13:04:32 -0400 Received: from [209.10.143.221] (helo=neonym.net) by ietf-mx with esmtp (Exim 4.12) id 1941x2-0004Fc-00 for urn-nid@apps.ietf.org; Fri, 11 Apr 2003 13:04:32 -0400 Received: from [207.120.28.115] ([::ffff:207.120.28.115]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Thu, 10 Apr 2003 23:37:43 -0400 Subject: Registration request for the 'liberty' URN namespace From: Michael Mealling To: urn-nid@apps.ietf.org Organization: Harriman Heavy Industries, Inc. Message-Id: <1050080533.8088.153.camel@blackdell.neonym.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.2.2 Date: 11 Apr 2003 13:02:14 -0400 Content-Transfer-Encoding: 7bit Sender: urn-nid-admin@ietf.org Errors-To: urn-nid-admin@ietf.org X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: discussion of new namespace identifiers for URNs List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Included below is draft-mealling-liberty-urn-00.txt, a registration draft for the 'liberty' formal URN namespace. It has been sent to the Internet Drafts repository. Enjoy! -MM Network Working Group M. Mealling Internet-Draft VeriSign, Inc. Expires: October 10, 2003 April 11, 2003 A URN Namespace For The Liberty Alliance Project draft-mealling-liberty-urn-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 except that the right to produce derivative works is not granted. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 10, 2003. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract This document describes a URN namespace that will identify various objects within the Liberty Architecture for federated network identity. 1. Introduction The Liberty Architecture seeks to provide federated network identity in such a way that enhances security, privacy and trust; thus creating a networked world across which individuals and businesses can engage in virtually any transaction without compromising the privacy and security of vital identity information. Mealling Expires October 10, 2003 [Page 1] Internet-Draft The Liberty URN Namespace April 2003 One fundamental component of this architecture is its use of XML [4], and specifically, XML Schema [6] and Namespaces [5]. These components require identifiers that will live far beyond the lifetime of the organization that produced them. As such, a URN namespace for those components that adheres to the assumptions and policies of the Liberty specification is required. This namespace specification is for a formal namespace. 2. Specification Template Namespace ID: "liberty" requested. Registration Information: Registration Version Number: 1 Registration Date: 2003-04-01 Declared registrant of the namespace: Liberty Alliance Project c/o IEEE-ISTO 445 Hoes Lane Piscataway, NJ 08855-1331, USA info@projectliberty.org Declaration of structure: The Namespace Specific Strings (NSS) of all URNs assigned by Liberty will conform to the syntax defined in section 2.2 of RFC2141 [1]. In addition, all Liberty URN NSSs will consist of a left-to-right series of tokens delimited by colons. The left-to-right sequence of colon-delimited tokens corresponds to descending nodes in a tree. To the right of the lowest naming Mealling Expires October 10, 2003 [Page 2] Internet-Draft The Liberty URN Namespace April 2003 authority node there may be zero, one or more levels of hierarchical (although not in the RFC 2396 [3] sense of 'hierarchy') naming nodes terminating in a rightmost leaf node. See the section entitled "Identifier assignment" below for more on the semantics of NSSs. This syntax convention is captured in the following normative ABNF [2] rules for Liberty NSSs: Liberty-NSS = 1*(subStChar) 0*(":" 1*(subStChar)) subStChar = trans / "%" HEXDIG HEXDIG trans = ALPHA / DIGIT / other / reserved other = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved = "%" / "/" / "?" / "#" The exclusion of the colon from the list of "other" characters means that the colon can only occur as a delimiter between string tokens. Note that this ABNF rule set guarantees that any valid Liberty NSS is also a valid RFC2141 NSS. For example: urn:liberty:schemas:authctx:2002:05 urn:liberty:schemas:core:2002:12 Relevant ancillary documentation: Liberty Architecture Overview [7] Version 1.1 Liberty Alliance Project January 15, 2003 Identifier uniqueness considerations: Identifiers are assigned by the Liberty Project within its various standards. In the process of publishing a specification all newly minted names are checked against the record of previously assigned names. Mealling Expires October 10, 2003 [Page 3] Internet-Draft The Liberty URN Namespace April 2003 Identifier persistence considerations: The assignment process guarantees that names are not reassigned and that the binding between the name and and its resource is permanent, regardless of any standards or organizational changes. Process of identifier assignment: Names are assigned by the Liberty standards publication process. Process of identifier resolution: At this time no resolution mechanism is specified. Rules for Lexical Equivalence: The entire URN is case-insensitive. Conformance with URN Syntax: There are no additional characters reserved. Validation mechanism: None other than verifying with the correct Liberty specifications. Scope: Global Mealling Expires October 10, 2003 [Page 4] Internet-Draft The Liberty URN Namespace April 2003 3. IANA Considerations This document includes a URN Namespace registration that is to be entered into the IANA registry for URN NIDs. 4. Community Considerations While there is no resolution mechanism for this namespace, the names themselves are used in public implementations of the Liberty specifications. There are circumstances where objects from the Liberty system will become exposed to the general Internet. In these cases the use of the Liberty namespace will provide general interoperability benefits to the Internet at large. Additionally, there may be subcomponents of the Liberty specifications that may be adopted by other standards, in which case the URNs used to identify those components and specifications can be easily used to enhance other, non-Liberty based, systems. 5. Security Considerations Since there is no defined resolution mechanism for Liberty URNs it is difficult to authenticate the fact that a given namespace actually adheres to the standard, thus applications should be be careful to not take some unverified sources assertion that what it is sending adheres to what the actual URN is assigned to. References [1] Moats, R., "URN Syntax", RFC 2141, May 1997. [2] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997. [3] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [4] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, . [5] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, . [6] Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, . Mealling Expires October 10, 2003 [Page 5] Internet-Draft The Liberty URN Namespace April 2003 [7] Hodges, J. and T. Watson, "Liberty Architecture Overview", Liberty 1.1, January 2003, . Author's Address Michael Mealling VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166 US Phone: +1 678 581 9656 EMail: michael@neonym.net URI: http://www.verisignlabs.com Mealling Expires October 10, 2003 [Page 6] Internet-Draft The Liberty URN Namespace April 2003 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Mealling Expires October 10, 2003 [Page 7] Internet-Draft The Liberty URN Namespace April 2003 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Mealling Expires October 10, 2003 [Page 8]