From urn-nid-bounces@apps.ietf.org Thu May 11 07:17:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fe9Ax-0001Az-Sc; Thu, 11 May 2006 07:17:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fe9Aw-0001Au-GO for urn-nid@apps.ietf.org; Thu, 11 May 2006 07:17:46 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fe9Au-0003MS-R8 for urn-nid@apps.ietf.org; Thu, 11 May 2006 07:17:46 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060511111729.IZPF4387.mta1.siol.net@edge2.siol.net> for ; Thu, 11 May 2006 13:17:29 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060511111721.VQQA7870.edge2.siol.net@[193.77.158.12]>; Thu, 11 May 2006 13:17:21 +0200 Mime-Version: 1.0 Message-Id: In-Reply-To: <4436C8C3.1050808@thinkingcat.com> References: <4436C8C3.1050808@thinkingcat.com> Date: Thu, 11 May 2006 13:17:19 +0200 To: Leslie Daigle From: Tomaz Kalin Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: urn-nid@apps.ietf.org Subject: Re: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org At 16:17 -0400 7/4/06, Leslie Daigle wrote: >I'm not seeing this in the Internet-Drafts repository -- can I assume >you've heard back from the I-D administrator indicating that you have >to resubmit it in ascii text (not MS Word)? > >Thanks, >Leslie. Leslie, Thank you for the warning. I have not heard anything before from the I-D administrator, but am resubmitting the draft today. Regards Tomaz From urn-nid-bounces@apps.ietf.org Thu May 11 07:17:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fe9B5-0001Hl-Vt; Thu, 11 May 2006 07:17:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fe9B4-0001ED-JY for urn-nid@apps.ietf.org; Thu, 11 May 2006 07:17:54 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fe9B2-0003Nu-IU for urn-nid@apps.ietf.org; Thu, 11 May 2006 07:17:54 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060511111746.JAJT4387.mta1.siol.net@edge2.siol.net>; Thu, 11 May 2006 13:17:46 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060511111746.VQZI7870.edge2.siol.net@[193.77.158.12]>; Thu, 11 May 2006 13:17:46 +0200 Mime-Version: 1.0 Message-Id: Date: Thu, 11 May 2006 13:17:42 +0200 To: internet-drafts@ietf.org From: Tomaz Kalin Content-Type: multipart/mixed; boundary="============_-1064776229==_============" X-Spam-Score: 0.8 (/) X-Scan-Signature: fe6e20eef2d8927c50910823cd0d1c84 Cc: urn-nid@apps.ietf.org Subject: Fwd: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org --============_-1064776229==_============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" >Date: Tue, 21 Mar 2006 13:56:15 +0200 >To: internet-drafts@ietf.org >From: Tomaz Kalin >Subject: URN Namespace for GEANT - Internet - Draft >Cc: urn-nid@apps.ietf.org >Bcc: maurizio.molina@dante.org.uk >X-Attachments: :Macintosh HD:1970819:GEANT-URN-draft.doc: > >Dear Sirs, > >Attached please find the Internet - Draft for the URN Namespace for GEANT. > >It is our understanding that DANTE, on behalf of the European NREN >community, fulfills the requirement for the application of a formal >URN namespace, and therefore, we are submitting a request in the >form of a RFC proposal, following RFC 3406 template. > >Best regards > >Tomaz Kalin ------------------------------------------------------------------- I am am resubmitting the draft - now in ascii text format Regards Tomaz Kalin --============_-1064776229==_============ Content-Id: Content-Type: text/plain; name="GEANT-URN-draftv4"; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GEANT-URN-draftv4" ; modification-date="Thu, 11 May 2006 13:13:19 +0200" Network Working Group T.Kalin Internet-Draft DANTE Expires: November 5, 2006 M.Molina DANTE May 5, 2006 A URN Namespace for GEANT draft-kalin-geant-urn-namespace-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 November 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. Abstract This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE for naming persistent resources defined by GEANT, its projects, activities, working groups and other designated subordinates. Kalin & Molina Expires November 5, 2006 [Page 1] =0C Internet-Draft A URN Namespace for GEANT May 2006 1. Introduction and community considerations The Consortium of European Academic and Research Networks (GEANT) provides high-speed, high-quality network connectivity for education institutions, universities, and research centres in Europe. The network infrastructure is composed by several National Research and Education Networks (NRENs) and their European-wide interconnection, GEANT. The current network is G=C9ANT2 [6], and is the seventh gene- ration of pan-European research and education network, successor to the pan-European multi-gigabit research network G=C9ANT. DANTE [7] is a UK based organization representing the members of the Consortium and operating the GEANT2 Network. This cooperative work is mainly done in the framework of EU funded projects. The biggest of such activities is currently the Gn2 project [6], started Sep 2004, that follows other successful ones having evolved the European Networks for Research and Education for almost two decades. Itis expected that these activities and the network evolution will continue to be supported by European Union and all European Governments in the years to come, as the existence of a state of the art network for Research in Europe is viewed as top strategic importance by them. We will refer to the organisation involved in these projects or benefiting from their outcome as the "GEANT community". The GEANT community produces many kinds of documents: specifications, working drafts, project reports, schemas, stylesheets, etc. The community wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements. The GEANT community and other GEANT-affiliated groups would benefit from the GEANT URN proposal by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of GEANT work is that it is carried out to serve the needs of many communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers would be of great value for GEANT, its affiliates and the higher education community generally. The possibility of fitting the naming needs under existing namespaces has been considered, but the conclusion was that the number of the activities and the size of the developers community is such that creating a lot of (possibly uncoordinated) dependencies from other namespaces is undesirable The proposed URN namespace specification is for a formal namespace. Kalin & Molina Expires November 5, 2006 [Page 2] =0C Internet-Draft A URN Namespace for GEANT May 2006 2. Specification Template Namespace ID: "geant" requested. Registration Information: Registration Version Number 1 Registration Date: 2006-03-21 Registrant of the namespace: DANTE ATTN: Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom Phone: +44 1223 371340 Contact: Tomaz Kalin Affiliation: DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ tomaz.kalin@dante.org.uk Phone: +386 1 430 3055 Syntactic structure: The Namespace Specific Strings (NSS) of all URNs assigned by GEANT will conform to the syntax defined in section 2.2 of RFC2141, "URN Syntax." [1] In addition, all GEANT 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 Kalin & Molina Expires November 5, 2006 [Page 3] =0C Internet-Draft A URN Namespace for GEANT May 2006 lowest naming authority node there may be zero, one or more levels of hierarchical 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 rules for GEANT NSSs (see RFC2234): [2] GEANT-NSS =3D 1*(subStChar) 0*(":" 1*(subStChar)) subStChar =3D trans / "%" HEXDIG HEXDIG trans =3D ALPHA / DIGIT / other / reserved other =3D "(" / ")" / "+" / "," / "-" / "." / "=3D" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved =3D "%" / "/" / "?" / "#" 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 GEANT NSS is also a valid RFC2141 NSS. Relevant ancillary documentation: None. Identifier uniqueness: It is the responsibility of DANTE to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree. Kalin & Molina Expires November 5, 2006 [Page 4] =0C Internet-Draft A URN Namespace for GEANT May 2006 Identifier persistence: DANTE bears ultimate responsibility for maintaining the usability of GEANT urns over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in the case a subordinate naming authority ceases to function. Identifier assignment: DANTE will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of GEANT will be invited to designate a naming authority and to suggest one or more candidate names. Institutions and communities affiliated with GEANT may request, through their designated GEANT liaison, that they be granted GEANT-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if e.g. the German National Research and Education Network wished to be designated a subordinate naming authority under GEANT, the institutional GEANT liaison could propose to DANTE to be delegated control over names beginning with, "urn:geant:dfn.de." Institutions seeking affiliation with GEANT should send email to geant-submit@dante.org.uk, nominating an institutional liaison and providing contact information for that person. On at least an annual basis, DANTE will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to GEANT. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority. Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. DANTE will assign names of immediately subordinate Kalin & Molina Expires November 5, 2006 [Page 5] =0C Internet-Draft A URN Namespace for GEANT May 2006 naming authorities in lower case only. This forestalls the registration of two GEANT-subordinate naming authorities whose names differ only in case. Identifier resolution: DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html. That index will map URNs to resource identifiers, usually URLs. GEANT- affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable. Lexical equivalence: Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. Conformance with URN syntax: All GEANT NSSs fully conform to RFC2141 syntax rules for NSSs. Validation mechanism: As specified in the "Identifier resolution" section above, DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html Presence in that index implies that a given URN is valid. GEANT-affiliated naming authorities will specify how to validate the URNs they assign. Scope: Global. Kalin & Molina Expires November 5, 2006 [Page 6] =0C Internet-Draft A URN Namespace for GEANT May 2006 3. Security Considerations There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Kalin & Molina Expires November 5, 2006 [Page 7] =0C Internet-Draft A URN Namespace for GEANT May 2006 4. Namespace Considerations Registration of an NID specific to GEANT is reasonable given the following considerations: 1. GEANT would like to assign URNs to some very fine-grained objects This does not seem to be the primary intended use of the XMLORG namespace (RFC3120) [3], or the more tightly controlled OASIS namespace (RFC 3121) [4]. 2. GEANT seeks naming autonomy. GEANT is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. 3. GEANT will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for GEANT. Some GEANT-developed schema and namespaces may be good candidates for inclusion in the XMLORG or possible future "EU" registry. The fact that such an object might already have a GEANT-assigned URN shouldn't be a hindrance. Work in progress to update RFC2611 [5] includes an explicit statement that two or more URNs may point to the same resource. A resource with a GEANT-assigned namespace-specific-string would, of course, be given an XMLORG or EU namespace-specific-string as it enters the XMLORG or "EU" registry. Kalin & Molina Expires November 5, 2006 [Page 8] =0C Internet-Draft A URN Namespace for GEANT May 2006 5. IANA Considerations This document is intended as a formal request to IANA for the registration of a "GEANT" NID within the IANA registry of URN NIDs. Kalin & Molina Expires November 5, 2006 [Page 9] =0C Internet-Draft A URN Namespace for GEANT May 2006 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] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001. [4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001. [5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. [6] G=C9ANT2 project's website http://www.geant2.net/ [7] DANTE's company website http://www.dante.net/ Authors' Addresses T. Kalin c/o DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ Unired Kingdom EMail: tomaz.kalin@dante.org.uk Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom EMail: maurizio.molina@dante.org.uk Kalin & Molina Expires November 5, 2006 [Page 10] =0C Internet-Draft A URN Namespace for GEANT May 2006 =46ull Copyright Statement Copyright (C) The Internet Society (2002). 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 assigns. 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 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. Kalin & Molina Expires November 5, 2006 [Page 11] --============_-1064776229==_============-- From urn-nid-bounces@apps.ietf.org Mon May 15 04:55:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfYrM-0004Ic-JH; Mon, 15 May 2006 04:55:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfYrL-0004IJ-BG for urn-nid@apps.ietf.org; Mon, 15 May 2006 04:55:23 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfYrI-0006o8-3D for urn-nid@apps.ietf.org; Mon, 15 May 2006 04:55:23 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060515085509.MKLI4387.mta1.siol.net@edge2.siol.net>; Mon, 15 May 2006 10:55:09 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060515085508.OPRD7870.edge2.siol.net@[193.77.158.12]>; Mon, 15 May 2006 10:55:08 +0200 Mime-Version: 1.0 Message-Id: Date: Mon, 15 May 2006 10:55:04 +0200 To: internet-drafts@ietf.org From: Tomaz Kalin Content-Type: multipart/mixed; boundary="============_-1064439189==_============" X-Spam-Score: 0.8 (/) X-Scan-Signature: e4e7b084ad5ab70bec6636d1707b49c1 Cc: urn-nid@apps.ietf.org Subject: Fwd: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org --============_-1064439189==_============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" >Date: Tue, 21 Mar 2006 13:56:15 +0200 >To: internet-drafts@ietf.org >From: Tomaz Kalin >Subject: URN Namespace for GEANT - Internet - Draft >Cc: urn-nid@apps.ietf.org >Bcc: maurizio.molina@dante.org.uk >X-Attachments: :Macintosh HD:1970819:GEANT-URN-draft.doc: > >Dear Sirs, > >Attached please find the Internet - Draft for the URN Namespace for GEANT. > >It is our understanding that DANTE, on behalf of the European NREN >community, fulfills the requirement for the application of a formal >URN namespace, and therefore, we are submitting a request in the >form of a RFC proposal, following RFC 3406 template. > >Best regards > >Tomaz Kalin ------------------------------------------------------------------- I am am resubmitting the draft - now in ascii text format Regards Tomaz Kalin ------------------------------------------------------------------------ At 12:17 -0400 12/5/06, ids@ietf.org wrote: > >The Secretariat CANNOT process your Internet-Draft submission due to >following reason(s): * All Internet-Drafts must include the following >statement: Resubmitting the draft, following the above request for amendments. Tomaz Kalin --============_-1064439189==_============ Content-Id: Content-Type: text/plain; name="GEANT-URN-draftv5"; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GEANT-URN-draftv5" ; modification-date="Mon, 15 May 2006 10:49:53 +0200" Network Working Group T.Kalin Internet-Draft DANTE Expires: November 5, 2006 M.Molina DANTE May 5, 2006 A URN Namespace for GEANT draft-kalin-geant-urn-namespace-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 November 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. Abstract This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE for naming persistent resources defined by GEANT, its projects, activities, working groups and other designated subordinates. Kalin & Molina Expires November 5, 2006 [Page 1] =0C Internet-Draft A URN Namespace for GEANT May 2006 1. Introduction and community considerations The Consortium of European Academic and Research Networks (GEANT) provides high-speed, high-quality network connectivity for education institutions, universities, and research centres in Europe. The network infrastructure is composed by several National Research and Education Networks (NRENs) and their European-wide interconnection, GEANT. The current network is G=C9ANT2 [6], and is the seventh gene- ration of pan-European research and education network, successor to the pan-European multi-gigabit research network G=C9ANT. DANTE [7] is a UK based organization representing the members of the Consortium and operating the GEANT2 Network. This cooperative work is mainly done in the framework of EU funded projects. The biggest of such activities is currently the Gn2 project [6], started Sep 2004, that follows other successful ones having evolved the European Networks for Research and Education for almost two decades. Itis expected that these activities and the network evolution will continue to be supported by European Union and all European Governments in the years to come, as the existence of a state of the art network for Research in Europe is viewed as top strategic importance by them. We will refer to the organisation involved in these projects or benefiting from their outcome as the "GEANT community". The GEANT community produces many kinds of documents: specifications, working drafts, project reports, schemas, stylesheets, etc. The community wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements. The GEANT community and other GEANT-affiliated groups would benefit from the GEANT URN proposal by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of GEANT work is that it is carried out to serve the needs of many communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers would be of great value for GEANT, its affiliates and the higher education community generally. The possibility of fitting the naming needs under existing namespaces has been considered, but the conclusion was that the number of the activities and the size of the developers community is such that creating a lot of (possibly uncoordinated) dependencies from other namespaces is undesirable The proposed URN namespace specification is for a formal namespace. Kalin & Molina Expires November 5, 2006 [Page 2] =0C Internet-Draft A URN Namespace for GEANT May 2006 2. Specification Template Namespace ID: "geant" requested. Registration Information: Registration Version Number 1 Registration Date: 2006-03-21 Registrant of the namespace: DANTE ATTN: Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom Phone: +44 1223 371340 Contact: Tomaz Kalin Affiliation: DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ tomaz.kalin@dante.org.uk Phone: +386 1 430 3055 Syntactic structure: The Namespace Specific Strings (NSS) of all URNs assigned by GEANT will conform to the syntax defined in section 2.2 of RFC2141, "URN Syntax." [1] In addition, all GEANT 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 Kalin & Molina Expires November 5, 2006 [Page 3] =0C Internet-Draft A URN Namespace for GEANT May 2006 lowest naming authority node there may be zero, one or more levels of hierarchical 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 rules for GEANT NSSs (see RFC2234): [2] GEANT-NSS =3D 1*(subStChar) 0*(":" 1*(subStChar)) subStChar =3D trans / "%" HEXDIG HEXDIG trans =3D ALPHA / DIGIT / other / reserved other =3D "(" / ")" / "+" / "," / "-" / "." / "=3D" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved =3D "%" / "/" / "?" / "#" 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 GEANT NSS is also a valid RFC2141 NSS. Relevant ancillary documentation: None. Identifier uniqueness: It is the responsibility of DANTE to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree. Kalin & Molina Expires November 5, 2006 [Page 4] =0C Internet-Draft A URN Namespace for GEANT May 2006 Identifier persistence: DANTE bears ultimate responsibility for maintaining the usability of GEANT urns over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in the case a subordinate naming authority ceases to function. Identifier assignment: DANTE will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of GEANT will be invited to designate a naming authority and to suggest one or more candidate names. Institutions and communities affiliated with GEANT may request, through their designated GEANT liaison, that they be granted GEANT-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if e.g. the German National Research and Education Network wished to be designated a subordinate naming authority under GEANT, the institutional GEANT liaison could propose to DANTE to be delegated control over names beginning with, "urn:geant:dfn.de." Institutions seeking affiliation with GEANT should send email to geant-submit@dante.org.uk, nominating an institutional liaison and providing contact information for that person. On at least an annual basis, DANTE will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to GEANT. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority. Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. DANTE will assign names of immediately subordinate Kalin & Molina Expires November 5, 2006 [Page 5] =0C Internet-Draft A URN Namespace for GEANT May 2006 naming authorities in lower case only. This forestalls the registration of two GEANT-subordinate naming authorities whose names differ only in case. Identifier resolution: DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html. That index will map URNs to resource identifiers, usually URLs. GEANT- affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable. Lexical equivalence: Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. Conformance with URN syntax: All GEANT NSSs fully conform to RFC2141 syntax rules for NSSs. Validation mechanism: As specified in the "Identifier resolution" section above, DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html Presence in that index implies that a given URN is valid. GEANT-affiliated naming authorities will specify how to validate the URNs they assign. Scope: Global. Kalin & Molina Expires November 5, 2006 [Page 6] =0C Internet-Draft A URN Namespace for GEANT May 2006 3. Security Considerations There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Kalin & Molina Expires November 5, 2006 [Page 7] =0C Internet-Draft A URN Namespace for GEANT May 2006 4. Namespace Considerations Registration of an NID specific to GEANT is reasonable given the following considerations: 1. GEANT would like to assign URNs to some very fine-grained objects This does not seem to be the primary intended use of the XMLORG namespace (RFC3120) [3], or the more tightly controlled OASIS namespace (RFC 3121) [4]. 2. GEANT seeks naming autonomy. GEANT is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. 3. GEANT will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for GEANT. Some GEANT-developed schema and namespaces may be good candidates for inclusion in the XMLORG or possible future "EU" registry. The fact that such an object might already have a GEANT-assigned URN shouldn't be a hindrance. Work in progress to update RFC2611 [5] includes an explicit statement that two or more URNs may point to the same resource. A resource with a GEANT-assigned namespace-specific-string would, of course, be given an XMLORG or EU namespace-specific-string as it enters the XMLORG or "EU" registry. Kalin & Molina Expires November 5, 2006 [Page 8] =0C Internet-Draft A URN Namespace for GEANT May 2006 5. IANA Considerations This document is intended as a formal request to IANA for the registration of a "GEANT" NID within the IANA registry of URN NIDs. Kalin & Molina Expires November 5, 2006 [Page 9] =0C Internet-Draft A URN Namespace for GEANT May 2006 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] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001. [4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001. [5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. [6] G=C9ANT2 project's website http://www.geant2.net/ [7] DANTE's company website http://www.dante.net/ Authors' Addresses T. Kalin c/o DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ Unired Kingdom EMail: tomaz.kalin@dante.org.uk Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom EMail: maurizio.molina@dante.org.uk Kalin & Molina Expires November 5, 2006 [Page 10] =0C Internet-Draft A URN Namespace for GEANT May 2006 =46ull Copyright Statement Copyright (C) The Internet Society (2006). 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 assigns. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights." This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 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. Kalin & Molina Expires November 5, 2006 [Page 11] --============_-1064439189==_============-- From urn-nid-bounces@apps.ietf.org Mon May 15 04:56:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfYsm-0004TR-91; Mon, 15 May 2006 04:56:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfYsk-0004T7-DB for urn-nid@apps.ietf.org; Mon, 15 May 2006 04:56:50 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfYsj-0006uT-Ar for urn-nid@apps.ietf.org; Mon, 15 May 2006 04:56:50 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060515085648.MOJG4387.mta1.siol.net@edge2.siol.net>; Mon, 15 May 2006 10:56:48 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060515085647.ORBQ7870.edge2.siol.net@[193.77.158.12]>; Mon, 15 May 2006 10:56:47 +0200 Mime-Version: 1.0 Message-Id: Date: Mon, 15 May 2006 10:55:04 +0200 To: internet-drafts@ietf.org From: Tomaz Kalin Content-Type: multipart/mixed; boundary="============_-1064439090==_============" X-Spam-Score: 0.8 (/) X-Scan-Signature: e4e7b084ad5ab70bec6636d1707b49c1 Cc: urn-nid@apps.ietf.org Subject: Fwd: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org --============_-1064439090==_============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" >Date: Tue, 21 Mar 2006 13:56:15 +0200 >To: internet-drafts@ietf.org >From: Tomaz Kalin >Subject: URN Namespace for GEANT - Internet - Draft >Cc: urn-nid@apps.ietf.org >Bcc: maurizio.molina@dante.org.uk >X-Attachments: :Macintosh HD:1970819:GEANT-URN-draft.doc: > >Dear Sirs, > >Attached please find the Internet - Draft for the URN Namespace for GEANT. > >It is our understanding that DANTE, on behalf of the European NREN >community, fulfills the requirement for the application of a formal >URN namespace, and therefore, we are submitting a request in the >form of a RFC proposal, following RFC 3406 template. > >Best regards > >Tomaz Kalin ------------------------------------------------------------------- I am am resubmitting the draft - now in ascii text format Regards Tomaz Kalin ------------------------------------------------------------------------ At 12:17 -0400 12/5/06, ids@ietf.org wrote: > >The Secretariat CANNOT process your Internet-Draft submission due to >following reason(s): * All Internet-Drafts must include the following >statement: Resubmitting the draft, following the above request for amendments. Tomaz Kalin --============_-1064439090==_============ Content-Id: Content-Type: text/plain; name="GEANT-URN-draftv5"; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GEANT-URN-draftv5" ; modification-date="Mon, 15 May 2006 10:49:53 +0200" Network Working Group T.Kalin Internet-Draft DANTE Expires: November 5, 2006 M.Molina DANTE May 5, 2006 A URN Namespace for GEANT draft-kalin-geant-urn-namespace-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 November 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. Abstract This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE for naming persistent resources defined by GEANT, its projects, activities, working groups and other designated subordinates. Kalin & Molina Expires November 5, 2006 [Page 1] =0C Internet-Draft A URN Namespace for GEANT May 2006 1. Introduction and community considerations The Consortium of European Academic and Research Networks (GEANT) provides high-speed, high-quality network connectivity for education institutions, universities, and research centres in Europe. The network infrastructure is composed by several National Research and Education Networks (NRENs) and their European-wide interconnection, GEANT. The current network is G=C9ANT2 [6], and is the seventh gene- ration of pan-European research and education network, successor to the pan-European multi-gigabit research network G=C9ANT. DANTE [7] is a UK based organization representing the members of the Consortium and operating the GEANT2 Network. This cooperative work is mainly done in the framework of EU funded projects. The biggest of such activities is currently the Gn2 project [6], started Sep 2004, that follows other successful ones having evolved the European Networks for Research and Education for almost two decades. Itis expected that these activities and the network evolution will continue to be supported by European Union and all European Governments in the years to come, as the existence of a state of the art network for Research in Europe is viewed as top strategic importance by them. We will refer to the organisation involved in these projects or benefiting from their outcome as the "GEANT community". The GEANT community produces many kinds of documents: specifications, working drafts, project reports, schemas, stylesheets, etc. The community wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements. The GEANT community and other GEANT-affiliated groups would benefit from the GEANT URN proposal by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of GEANT work is that it is carried out to serve the needs of many communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers would be of great value for GEANT, its affiliates and the higher education community generally. The possibility of fitting the naming needs under existing namespaces has been considered, but the conclusion was that the number of the activities and the size of the developers community is such that creating a lot of (possibly uncoordinated) dependencies from other namespaces is undesirable The proposed URN namespace specification is for a formal namespace. Kalin & Molina Expires November 5, 2006 [Page 2] =0C Internet-Draft A URN Namespace for GEANT May 2006 2. Specification Template Namespace ID: "geant" requested. Registration Information: Registration Version Number 1 Registration Date: 2006-03-21 Registrant of the namespace: DANTE ATTN: Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom Phone: +44 1223 371340 Contact: Tomaz Kalin Affiliation: DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ tomaz.kalin@dante.org.uk Phone: +386 1 430 3055 Syntactic structure: The Namespace Specific Strings (NSS) of all URNs assigned by GEANT will conform to the syntax defined in section 2.2 of RFC2141, "URN Syntax." [1] In addition, all GEANT 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 Kalin & Molina Expires November 5, 2006 [Page 3] =0C Internet-Draft A URN Namespace for GEANT May 2006 lowest naming authority node there may be zero, one or more levels of hierarchical 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 rules for GEANT NSSs (see RFC2234): [2] GEANT-NSS =3D 1*(subStChar) 0*(":" 1*(subStChar)) subStChar =3D trans / "%" HEXDIG HEXDIG trans =3D ALPHA / DIGIT / other / reserved other =3D "(" / ")" / "+" / "," / "-" / "." / "=3D" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved =3D "%" / "/" / "?" / "#" 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 GEANT NSS is also a valid RFC2141 NSS. Relevant ancillary documentation: None. Identifier uniqueness: It is the responsibility of DANTE to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree. Kalin & Molina Expires November 5, 2006 [Page 4] =0C Internet-Draft A URN Namespace for GEANT May 2006 Identifier persistence: DANTE bears ultimate responsibility for maintaining the usability of GEANT urns over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in the case a subordinate naming authority ceases to function. Identifier assignment: DANTE will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of GEANT will be invited to designate a naming authority and to suggest one or more candidate names. Institutions and communities affiliated with GEANT may request, through their designated GEANT liaison, that they be granted GEANT-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if e.g. the German National Research and Education Network wished to be designated a subordinate naming authority under GEANT, the institutional GEANT liaison could propose to DANTE to be delegated control over names beginning with, "urn:geant:dfn.de." Institutions seeking affiliation with GEANT should send email to geant-submit@dante.org.uk, nominating an institutional liaison and providing contact information for that person. On at least an annual basis, DANTE will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to GEANT. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority. Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. DANTE will assign names of immediately subordinate Kalin & Molina Expires November 5, 2006 [Page 5] =0C Internet-Draft A URN Namespace for GEANT May 2006 naming authorities in lower case only. This forestalls the registration of two GEANT-subordinate naming authorities whose names differ only in case. Identifier resolution: DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html. That index will map URNs to resource identifiers, usually URLs. GEANT- affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable. Lexical equivalence: Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. Conformance with URN syntax: All GEANT NSSs fully conform to RFC2141 syntax rules for NSSs. Validation mechanism: As specified in the "Identifier resolution" section above, DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html Presence in that index implies that a given URN is valid. GEANT-affiliated naming authorities will specify how to validate the URNs they assign. Scope: Global. Kalin & Molina Expires November 5, 2006 [Page 6] =0C Internet-Draft A URN Namespace for GEANT May 2006 3. Security Considerations There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Kalin & Molina Expires November 5, 2006 [Page 7] =0C Internet-Draft A URN Namespace for GEANT May 2006 4. Namespace Considerations Registration of an NID specific to GEANT is reasonable given the following considerations: 1. GEANT would like to assign URNs to some very fine-grained objects This does not seem to be the primary intended use of the XMLORG namespace (RFC3120) [3], or the more tightly controlled OASIS namespace (RFC 3121) [4]. 2. GEANT seeks naming autonomy. GEANT is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. 3. GEANT will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for GEANT. Some GEANT-developed schema and namespaces may be good candidates for inclusion in the XMLORG or possible future "EU" registry. The fact that such an object might already have a GEANT-assigned URN shouldn't be a hindrance. Work in progress to update RFC2611 [5] includes an explicit statement that two or more URNs may point to the same resource. A resource with a GEANT-assigned namespace-specific-string would, of course, be given an XMLORG or EU namespace-specific-string as it enters the XMLORG or "EU" registry. Kalin & Molina Expires November 5, 2006 [Page 8] =0C Internet-Draft A URN Namespace for GEANT May 2006 5. IANA Considerations This document is intended as a formal request to IANA for the registration of a "GEANT" NID within the IANA registry of URN NIDs. Kalin & Molina Expires November 5, 2006 [Page 9] =0C Internet-Draft A URN Namespace for GEANT May 2006 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] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001. [4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001. [5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. [6] G=C9ANT2 project's website http://www.geant2.net/ [7] DANTE's company website http://www.dante.net/ Authors' Addresses T. Kalin c/o DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ Unired Kingdom EMail: tomaz.kalin@dante.org.uk Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom EMail: maurizio.molina@dante.org.uk Kalin & Molina Expires November 5, 2006 [Page 10] =0C Internet-Draft A URN Namespace for GEANT May 2006 =46ull Copyright Statement Copyright (C) The Internet Society (2006). 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 assigns. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights." This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 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. Kalin & Molina Expires November 5, 2006 [Page 11] --============_-1064439090==_============-- From urn-nid-bounces@apps.ietf.org Wed May 17 04:36:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgHWN-0001l7-SL; Wed, 17 May 2006 04:36:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgHWM-0001kn-Mj for urn-nid@apps.ietf.org; Wed, 17 May 2006 04:36:42 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgHWK-0000X5-I9 for urn-nid@apps.ietf.org; Wed, 17 May 2006 04:36:42 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060517083634.YBEN4387.mta1.siol.net@edge2.siol.net>; Wed, 17 May 2006 10:36:34 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060517083633.TAHA7870.edge2.siol.net@[193.77.158.12]>; Wed, 17 May 2006 10:36:33 +0200 Mime-Version: 1.0 Message-Id: Date: Wed, 17 May 2006 10:36:28 +0200 To: internet-drafts@ietf.org From: Tomaz Kalin Content-Type: multipart/mixed; boundary="============_-1064267505==_============" X-Spam-Score: 0.0 (/) X-Scan-Signature: cb592aae7f4601895f35714165597859 Cc: urn-nid@apps.ietf.org, ids@ietf.org Subject: Fwd: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org --============_-1064267505==_============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" At 11:24 -0400 15/5/06, ids@ietf.org wrote: >Please delete the following sentense and resubmit the draft. Thank you. > > This document is an Internet-Draft and is in full conformance with > all provisions of Section 10 of RFC2026. Done, and resubmitting Sorry for making so many mistakes :-[ Thank you Tomaz Kalin --============_-1064267505==_============ Content-Id: Content-Type: text/plain; name="GEANT-URN-draftv6"; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GEANT-URN-draftv6" ; modification-date="Wed, 17 May 2006 10:35:51 +0200" Network Working Group T.Kalin Internet-Draft DANTE Expires: November 5, 2006 M.Molina DANTE May 5, 2006 A URN Namespace for GEANT draft-kalin-geant-urn-namespace-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 November 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. Abstract This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE for naming persistent resources defined by GEANT, its projects, activities, working groups and other designated subordinates. Kalin & Molina Expires November 5, 2006 [Page 1] =0C Internet-Draft A URN Namespace for GEANT May 2006 1. Introduction and community considerations The Consortium of European Academic and Research Networks (GEANT) provides high-speed, high-quality network connectivity for education institutions, universities, and research centres in Europe. The network infrastructure is composed by several National Research and Education Networks (NRENs) and their European-wide interconnection, GEANT. The current network is G=C9ANT2 [6], and is the seventh gene- ration of pan-European research and education network, successor to the pan-European multi-gigabit research network G=C9ANT. DANTE [7] is a UK based organization representing the members of the Consortium and operating the GEANT2 Network. This cooperative work is mainly done in the framework of EU funded projects. The biggest of such activities is currently the Gn2 project [6], started Sep 2004, that follows other successful ones having evolved the European Networks for Research and Education for almost two decades. Itis expected that these activities and the network evolution will continue to be supported by European Union and all European Governments in the years to come, as the existence of a state of the art network for Research in Europe is viewed as top strategic importance by them. We will refer to the organisation involved in these projects or benefiting from their outcome as the "GEANT community". The GEANT community produces many kinds of documents: specifications, working drafts, project reports, schemas, stylesheets, etc. The community wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements. The GEANT community and other GEANT-affiliated groups would benefit from the GEANT URN proposal by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of GEANT work is that it is carried out to serve the needs of many communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers would be of great value for GEANT, its affiliates and the higher education community generally. The possibility of fitting the naming needs under existing namespaces has been considered, but the conclusion was that the number of the activities and the size of the developers community is such that creating a lot of (possibly uncoordinated) dependencies from other namespaces is undesirable The proposed URN namespace specification is for a formal namespace. Kalin & Molina Expires November 5, 2006 [Page 2] =0C Internet-Draft A URN Namespace for GEANT May 2006 2. Specification Template Namespace ID: "geant" requested. Registration Information: Registration Version Number 1 Registration Date: 2006-03-21 Registrant of the namespace: DANTE ATTN: Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom Phone: +44 1223 371340 Contact: Tomaz Kalin Affiliation: DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ tomaz.kalin@dante.org.uk Phone: +386 1 430 3055 Syntactic structure: The Namespace Specific Strings (NSS) of all URNs assigned by GEANT will conform to the syntax defined in section 2.2 of RFC2141, "URN Syntax." [1] In addition, all GEANT 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 Kalin & Molina Expires November 5, 2006 [Page 3] =0C Internet-Draft A URN Namespace for GEANT May 2006 lowest naming authority node there may be zero, one or more levels of hierarchical 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 rules for GEANT NSSs (see RFC2234): [2] GEANT-NSS =3D 1*(subStChar) 0*(":" 1*(subStChar)) subStChar =3D trans / "%" HEXDIG HEXDIG trans =3D ALPHA / DIGIT / other / reserved other =3D "(" / ")" / "+" / "," / "-" / "." / "=3D" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved =3D "%" / "/" / "?" / "#" 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 GEANT NSS is also a valid RFC2141 NSS. Relevant ancillary documentation: None. Identifier uniqueness: It is the responsibility of DANTE to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree. Kalin & Molina Expires November 5, 2006 [Page 4] =0C Internet-Draft A URN Namespace for GEANT May 2006 Identifier persistence: DANTE bears ultimate responsibility for maintaining the usability of GEANT urns over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in the case a subordinate naming authority ceases to function. Identifier assignment: DANTE will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of GEANT will be invited to designate a naming authority and to suggest one or more candidate names. Institutions and communities affiliated with GEANT may request, through their designated GEANT liaison, that they be granted GEANT-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if e.g. the German National Research and Education Network wished to be designated a subordinate naming authority under GEANT, the institutional GEANT liaison could propose to DANTE to be delegated control over names beginning with, "urn:geant:dfn.de." Institutions seeking affiliation with GEANT should send email to geant-submit@dante.org.uk, nominating an institutional liaison and providing contact information for that person. On at least an annual basis, DANTE will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to GEANT. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority. Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. DANTE will assign names of immediately subordinate Kalin & Molina Expires November 5, 2006 [Page 5] =0C Internet-Draft A URN Namespace for GEANT May 2006 naming authorities in lower case only. This forestalls the registration of two GEANT-subordinate naming authorities whose names differ only in case. Identifier resolution: DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html. That index will map URNs to resource identifiers, usually URLs. GEANT- affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable. Lexical equivalence: Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. Conformance with URN syntax: All GEANT NSSs fully conform to RFC2141 syntax rules for NSSs. Validation mechanism: As specified in the "Identifier resolution" section above, DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html Presence in that index implies that a given URN is valid. GEANT-affiliated naming authorities will specify how to validate the URNs they assign. Scope: Global. Kalin & Molina Expires November 5, 2006 [Page 6] =0C Internet-Draft A URN Namespace for GEANT May 2006 3. Security Considerations There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Kalin & Molina Expires November 5, 2006 [Page 7] =0C Internet-Draft A URN Namespace for GEANT May 2006 4. Namespace Considerations Registration of an NID specific to GEANT is reasonable given the following considerations: 1. GEANT would like to assign URNs to some very fine-grained objects This does not seem to be the primary intended use of the XMLORG namespace (RFC3120) [3], or the more tightly controlled OASIS namespace (RFC 3121) [4]. 2. GEANT seeks naming autonomy. GEANT is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. 3. GEANT will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for GEANT. Some GEANT-developed schema and namespaces may be good candidates for inclusion in the XMLORG or possible future "EU" registry. The fact that such an object might already have a GEANT-assigned URN shouldn't be a hindrance. Work in progress to update RFC2611 [5] includes an explicit statement that two or more URNs may point to the same resource. A resource with a GEANT-assigned namespace-specific-string would, of course, be given an XMLORG or EU namespace-specific-string as it enters the XMLORG or "EU" registry. Kalin & Molina Expires November 5, 2006 [Page 8] =0C Internet-Draft A URN Namespace for GEANT May 2006 5. IANA Considerations This document is intended as a formal request to IANA for the registration of a "GEANT" NID within the IANA registry of URN NIDs. Kalin & Molina Expires November 5, 2006 [Page 9] =0C Internet-Draft A URN Namespace for GEANT May 2006 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] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001. [4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001. [5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. [6] G=C9ANT2 project's website http://www.geant2.net/ [7] DANTE's company website http://www.dante.net/ Authors' Addresses T. Kalin c/o DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ Unired Kingdom EMail: tomaz.kalin@dante.org.uk Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom EMail: maurizio.molina@dante.org.uk Kalin & Molina Expires November 5, 2006 [Page 10] =0C Internet-Draft A URN Namespace for GEANT May 2006 =46ull Copyright Statement Copyright (C) The Internet Society (2006). 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 assigns. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights." This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 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. Kalin & Molina Expires November 5, 2006 [Page 11] --============_-1064267505==_============-- From urn-nid-bounces@apps.ietf.org Mon May 22 01:19:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi2ov-0004b9-9L; Mon, 22 May 2006 01:19:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi2ou-0004aX-EY for urn-nid@apps.ietf.org; Mon, 22 May 2006 01:19:08 -0400 Received: from mail34.paran.com ([211.41.82.106]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fi2or-00048e-0A for urn-nid@apps.ietf.org; Mon, 22 May 2006 01:19:08 -0400 Received: from 59.6.65.199 ([59.6.65.199]) by mail34.paran.com (ParanMail Web 0.1) with ESMTP id 1148275126.10029.mail34x0; Mon, 22 May 2006 14:18:46 +0900 From: "=?euc-kr?B?U3RldmUgWWFuZyA=?=" To: Date: Mon, 22 May 2006 14:18:46 +0900 Message-ID: <1148275126.10029.mail34x0@mail34> X-MsgID: 1148275126.10029.mail34x0 X-Mailer: ParanMail Web 0.1 X-Priority: 3 X-Paran-Attach: N MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=euc-kr X-Spam-Score: 3.8 (+++) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: Not receiving any comments yet about our NID internet-draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?euc-kr?B?U3RldmUgWWFuZyA=?= List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org
Dear URN NID Admin,

We've sent the Internet-draft for NID.
On March 7, we could find the draft on the Internet-Drafts Database Interface page.

The draft name is,
draft-kyungsoo-name-urn-00.txt

Several months by, we didn't receive any comments yet.
We're wondering if the discussion period for technical review is finished.
Don't we need to update our draft?
Should we request for RFC publication?
If we should, what would we do?
Please check it out and inform us ASAP.

Thanks.




여대생 K양, 맞고로 100만원 벌었다는데 그 비결이 궁금해요.
From urn-nid-bounces@apps.ietf.org Mon May 22 04:23:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi5hR-0006bm-Dg; Mon, 22 May 2006 04:23:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi5hP-0006bg-Qb for urn-nid@apps.ietf.org; Mon, 22 May 2006 04:23:35 -0400 Received: from mta1.siol.net ([193.189.160.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fi5hO-0003ya-R9 for urn-nid@apps.ietf.org; Mon, 22 May 2006 04:23:35 -0400 Received: from edge2.siol.net ([10.10.10.211]) by mta1.siol.net with ESMTP id <20060522082329.IWVF4387.mta1.siol.net@edge2.siol.net>; Mon, 22 May 2006 10:23:29 +0200 Received: from [193.77.158.12] by edge2.siol.net with ESMTP id <20060522082320.EXAK7870.edge2.siol.net@[193.77.158.12]>; Mon, 22 May 2006 10:23:20 +0200 Mime-Version: 1.0 Message-Id: In-Reply-To: <2769.10.31.30.121.1147879145.squirrel@stiedprstage1> References: <2769.10.31.30.121.1147879145.squirrel@stiedprstage1> Date: Mon, 22 May 2006 10:23:15 +0200 To: internet-drafts@ietf.org From: Tomaz Kalin Content-Type: multipart/mixed; boundary="============_-1063836297==_============" X-Spam-Score: 0.0 (/) X-Scan-Signature: c11d54fae0b5a4f2b2d9ece4929bab8a Cc: urn-nid@apps.ietf.org Subject: Re: Fwd: URN Namespace for GEANT - Internet - Draft X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org --============_-1063836297==_============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" At 11:19 -0400 17/5/06, ids@ietf.org wrote: > >Is draft-kalin-geant-urn-namespace-01 initial submission? If yes, it >should be submitted with -00 version. Please do so. Thank you. Thank you for the remainder T Kalin --============_-1063836297==_============ Content-Id: Content-Type: text/plain; name="GEANT-URN-draftv00"; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GEANT-URN-draftv00" ; modification-date="Mon, 22 May 2006 10:12:05 +0200" Network Working Group T.Kalin Internet-Draft DANTE Expires: November 5, 2006 M.Molina DANTE May 22, 2006 A URN Namespace for GEANT draft-kalin-geant-urn-namespace-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 November 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. Abstract This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE for naming persistent resources defined by GEANT, its projects, activities, working groups and other designated subordinates. Kalin & Molina Expires November 22, 2006 [Page 1] =0C Internet-Draft A URN Namespace for GEANT May 2006 1. Introduction and community considerations The Consortium of European Academic and Research Networks (GEANT) provides high-speed, high-quality network connectivity for education institutions, universities, and research centres in Europe. The network infrastructure is composed by several National Research and Education Networks (NRENs) and their European-wide interconnection, GEANT. The current network is G=C9ANT2 [6], and is the seventh gene- ration of pan-European research and education network, successor to the pan-European multi-gigabit research network G=C9ANT. DANTE [7] is a UK based organization representing the members of the Consortium and operating the GEANT2 Network. This cooperative work is mainly done in the framework of EU funded projects. The biggest of such activities is currently the Gn2 project [6], started Sep 2004, that follows other successful ones having evolved the European Networks for Research and Education for almost two decades. Itis expected that these activities and the network evolution will continue to be supported by European Union and all European Governments in the years to come, as the existence of a state of the art network for Research in Europe is viewed as top strategic importance by them. We will refer to the organisation involved in these projects or benefiting from their outcome as the "GEANT community". The GEANT community produces many kinds of documents: specifications, working drafts, project reports, schemas, stylesheets, etc. The community wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements. The GEANT community and other GEANT-affiliated groups would benefit from the GEANT URN proposal by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of GEANT work is that it is carried out to serve the needs of many communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers would be of great value for GEANT, its affiliates and the higher education community generally. The possibility of fitting the naming needs under existing namespaces has been considered, but the conclusion was that the number of the activities and the size of the developers community is such that creating a lot of (possibly uncoordinated) dependencies from other namespaces is undesirable The proposed URN namespace specification is for a formal namespace. Kalin & Molina Expires November 22, 2006 [Page 2] =0C Internet-Draft A URN Namespace for GEANT May 2006 2. Specification Template Namespace ID: "geant" requested. Registration Information: Registration Version Number 1 Registration Date: 2006-03-21 Registrant of the namespace: DANTE ATTN: Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom Phone: +44 1223 371340 Contact: Tomaz Kalin Affiliation: DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ tomaz.kalin@dante.org.uk Phone: +386 1 430 3055 Syntactic structure: The Namespace Specific Strings (NSS) of all URNs assigned by GEANT will conform to the syntax defined in section 2.2 of RFC2141, "URN Syntax." [1] In addition, all GEANT 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 Kalin & Molina Expires November 22, 2006 [Page 3] =0C Internet-Draft A URN Namespace for GEANT May 2006 lowest naming authority node there may be zero, one or more levels of hierarchical 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 rules for GEANT NSSs (see RFC2234): [2] GEANT-NSS =3D 1*(subStChar) 0*(":" 1*(subStChar)) subStChar =3D trans / "%" HEXDIG HEXDIG trans =3D ALPHA / DIGIT / other / reserved other =3D "(" / ")" / "+" / "," / "-" / "." / "=3D" / "@" / ";" / "$" / "_" / "!" / "*" / "'" reserved =3D "%" / "/" / "?" / "#" 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 GEANT NSS is also a valid RFC2141 NSS. Relevant ancillary documentation: None. Identifier uniqueness: It is the responsibility of DANTE to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree. Kalin & Molina Expires November 22, 2006 [Page 4] =0C Internet-Draft A URN Namespace for GEANT May 2006 Identifier persistence: DANTE bears ultimate responsibility for maintaining the usability of GEANT urns over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in the case a subordinate naming authority ceases to function. Identifier assignment: DANTE will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of GEANT will be invited to designate a naming authority and to suggest one or more candidate names. Institutions and communities affiliated with GEANT may request, through their designated GEANT liaison, that they be granted GEANT-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if e.g. the German National Research and Education Network wished to be designated a subordinate naming authority under GEANT, the institutional GEANT liaison could propose to DANTE to be delegated control over names beginning with, "urn:geant:dfn.de." Institutions seeking affiliation with GEANT should send email to geant-submit@dante.org.uk, nominating an institutional liaison and providing contact information for that person. On at least an annual basis, DANTE will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to GEANT. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority. Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. DANTE will assign names of immediately subordinate Kalin & Molina Expires November 22, 2006 [Page 5] =0C Internet-Draft A URN Namespace for GEANT May 2006 naming authorities in lower case only. This forestalls the registration of two GEANT-subordinate naming authorities whose names differ only in case. Identifier resolution: DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html. That index will map URNs to resource identifiers, usually URLs. GEANT- affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable. Lexical equivalence: Lexical equivalence of two GEANT namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. Conformance with URN syntax: All GEANT NSSs fully conform to RFC2141 syntax rules for NSSs. Validation mechanism: As specified in the "Identifier resolution" section above, DANTE will maintain an index of all GEANT and GEANT workgroup assigned URNs on its web site, http://www.dante.net/urn-geant/urn-geant.html Presence in that index implies that a given URN is valid. GEANT-affiliated naming authorities will specify how to validate the URNs they assign. Scope: Global. Kalin & Molina Expires November 22, 2006 [Page 6] =0C Internet-Draft A URN Namespace for GEANT May 2006 3. Security Considerations There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Kalin & Molina Expires November 22, 2006 [Page 7] =0C Internet-Draft A URN Namespace for GEANT May 2006 4. Namespace Considerations Registration of an NID specific to GEANT is reasonable given the following considerations: 1. GEANT would like to assign URNs to some very fine-grained objects This does not seem to be the primary intended use of the XMLORG namespace (RFC3120) [3], or the more tightly controlled OASIS namespace (RFC 3121) [4]. 2. GEANT seeks naming autonomy. GEANT is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. 3. GEANT will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for GEANT. Some GEANT-developed schema and namespaces may be good candidates for inclusion in the XMLORG or possible future "EU" registry. The fact that such an object might already have a GEANT-assigned URN shouldn't be a hindrance. Work in progress to update RFC2611 [5] includes an explicit statement that two or more URNs may point to the same resource. A resource with a GEANT-assigned namespace-specific-string would, of course, be given an XMLORG or EU namespace-specific-string as it enters the XMLORG or "EU" registry. Kalin & Molina Expires November 22, 2006 [Page 8] =0C Internet-Draft A URN Namespace for GEANT May 2006 5. IANA Considerations This document is intended as a formal request to IANA for the registration of a "GEANT" NID within the IANA registry of URN NIDs. Kalin & Molina Expires November 22, 2006 [Page 9] =0C Internet-Draft A URN Namespace for GEANT May 2006 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] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001. [4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001. [5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. [6] G=C9ANT2 project's website http://www.geant2.net/ [7] DANTE's company website http://www.dante.net/ Authors' Addresses T. Kalin c/o DANTE City House 126 - 130 Hills Road Cambridge CB2 1PQ Unired Kingdom EMail: tomaz.kalin@dante.org.uk Maurizio Molina City House 126 - 130 Hills Road Cambridge CB2 1PQ United Kingdom EMail: maurizio.molina@dante.org.uk Kalin & Molina Expires November 22, 2006 [Page 10] =0C Internet-Draft A URN Namespace for GEANT May 2006 =46ull Copyright Statement Copyright (C) The Internet Society (2006). 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 assigns. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights." This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 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. Kalin & Molina Expires November 22, 2006 [Page 11] --============_-1063836297==_============-- From urn-nid-bounces@apps.ietf.org Wed May 31 14:59:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlVuk-0000wH-SZ; Wed, 31 May 2006 14:59:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlVkY-0004Cs-KB for urn-nid@apps.ietf.org; Wed, 31 May 2006 14:48:58 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlVkX-0002Cx-Ek for urn-nid@apps.ietf.org; Wed, 31 May 2006 14:48:58 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k4VImuWR018138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 May 2006 18:48:56 GMT Received: from [127.0.0.1] (helo=stiedprstage1) by stiedprstage1.ietf.org with esmtp (Exim 4.43) id 1FlVkW-0005hW-Dz; Wed, 31 May 2006 14:48:56 -0400 Received: from 10.31.30.121 (SquirrelMail authenticated user ids) by stiedprstage1 with HTTP; Wed, 31 May 2006 14:48:56 -0400 (EDT) Message-ID: <2796.10.31.30.121.1149101336.squirrel@stiedprstage1> In-Reply-To: References: Date: Wed, 31 May 2006 14:48:56 -0400 (EDT) From: ids@ietf.org To: "Miller Abel" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: 0.2 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 X-Mailman-Approved-At: Wed, 31 May 2006 14:59:30 -0400 Cc: "urn-nid@apps.ietf.org" , "TPM@nfc-forum.org" Subject: Re: Internet Draft: A Uniform Resource Name (URN) Namespace for The Near Field Communication Forum (NFC Forum) X-BeenThere: urn-nid@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: urn-nid-bounces@apps.ietf.org Please delete the following sentence from the draft and resubmit. Thank you. This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [i]. > Attached please find an Internet Draft requesting assignment of the URN > NID "nfc" and including a full and complete registration request following > the namespace specification process as defined in [RFC3406]. > > This Internet Draft is submitted according to the I-D Guidelines dated > March 25, 2005. Comments are solicited and may be sent to > TPM@nfc-forum.org or the author. > > Regards, > > Miller Abel > URN Technical Program Manager > Technical Committee > NFC Forum > >