From smartin@mcs.anl.gov Mon Jan 4 16:36:57 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3371ACDC7 for ; Mon, 4 Jan 2016 16:36:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.697 X-Spam-Level: X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, MPART_ALT_DIFF_COUNT=1.112, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5EXuKEi_jGzN for ; Mon, 4 Jan 2016 16:36:54 -0800 (PST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75C9A1ACDAB for ; Mon, 4 Jan 2016 16:36:54 -0800 (PST) Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mailrelay.anl.gov (Postfix) with ESMTPS id EBF9F2000A9 for ; Mon, 4 Jan 2016 18:36:53 -0600 (CST) X-IronPort-AV: E=Sophos;i="5.20,523,1444712400"; d="txt'?scan'208,217";a="105051895" Received: from nagurski.anl.gov ([146.137.81.22]) by mailgateway.anl.gov with ESMTP/TLS/AES256-SHA; 04 Jan 2016 18:36:53 -0600 Received: from wireless-s1-no-150-17-16.uchicago.edu (146.137.81.4) by smtp.anl.gov (146.137.81.38) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 4 Jan 2016 18:36:52 -0600 From: Stuart Martin Content-Type: multipart/alternative; boundary="Apple-Mail=_2BA34C62-1438-451D-BDB9-A3D40A23FBFF" Subject: Request for a formal URN Namespace ID for "globus" Date: Mon, 4 Jan 2016 18:36:52 -0600 Message-ID: <9AF891B8-C5A8-435A-BDB6-5018BCA8328B@mcs.anl.gov> To: "urn-nid@apps.ietf.org" MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) Archived-At: Cc: Stuart Martin X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 00:38:28 -0000 --Apple-Mail=_2BA34C62-1438-451D-BDB9-A3D40A23FBFF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Dear IESG, Please find attached a draft request for a formal URN Namespace ID for = =E2=80=9Cglobus=E2=80=9D. Regards, Stu Martin --------------------------------------- Software Development Manager University of Chicago / Globus 401 N. Michigan Ave., Suite 900 Chicago, IL 60611 Office: 630-677-6892 --Apple-Mail=_2BA34C62-1438-451D-BDB9-A3D40A23FBFF Content-Type: multipart/mixed; boundary="Apple-Mail=_C294DAA0-85AE-4269-AF66-993DC2AA9A92" --Apple-Mail=_C294DAA0-85AE-4269-AF66-993DC2AA9A92 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Dear IESG,

Please find attached a draft request for a formal URN = Namespace ID for =E2=80=9Cglobus=E2=80=9D.

Regards,
Stu Martin

---------------------------------------
Software Development Manager
University of Chicago / Globus
401 N. Michigan = Ave., Suite 900
Chicago, IL = 60611
Office: 630-677-6892

= --Apple-Mail=_C294DAA0-85AE-4269-AF66-993DC2AA9A92 Content-Disposition: attachment; filename="draft-martin-urn-globus-00.txt" Content-Type: text/plain; name="draft-martin-urn-globus-00.txt" Content-Transfer-Encoding: quoted-printable Network Working Group S. Martin=0D= Internet Draft University of Chicago=0D= Intended status: Informational S. Tuecke=0D= Expires: June 2016 University of Chicago=0D= B. McCollam=0D= University of Chicago=0D= M. Lidman=0D= University of Chicago=0D= December 8, 2015=0D= =0D =0D A URN Namespace for Globus=0D draft-martin-urn-globus-00=0D =0D =0D Status of this Memo=0D =0D This Internet-Draft is submitted in full conformance with the=0D provisions of BCP 78 and BCP 79. This document may not be modified,=0D= and derivative works of it may not be created, except to publish it=0D= as an RFC and to translate it into languages other than English.=0D =0D Internet-Drafts are working documents of the Internet Engineering=0D Task Force (IETF), its areas, and its working groups. Note that=0D other groups may also distribute working documents as Internet-=0D Drafts.=0D =0D Internet-Drafts are draft documents valid for a maximum of six=0D months and may be updated, replaced, or obsoleted by other documents=0D= at any time. It is inappropriate to use Internet-Drafts as=0D reference material or to cite them other than as "work in progress."=0D= =0D The list of current Internet-Drafts can be accessed at=0D http://www.ietf.org/ietf/1id-abstracts.txt=0D =0D The list of Internet-Draft Shadow Directories can be accessed at=0D http://www.ietf.org/shadow.html=0D =0D This Internet-Draft will expire on June 8, 2009.=0D =0D Copyright Notice=0D =0D Copyright (c) 2015 IETF Trust and the persons identified as the=0D document authors. All rights reserved.=0D =0D This document is subject to BCP 78 and the IETF Trust's Legal=0D Provisions Relating to IETF Documents=0D (http://trustee.ietf.org/license-info) in effect on the date of=0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 1]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D publication of this document. Please review these documents=0D carefully, as they describe your rights and restrictions with=0D respect to this document.=0D =0D Abstract=0D =0D This document describes a URN (Uniform Resource Name) namespace that=0D= is used by Globus for naming persistent resources.=0D =0D Table of Contents=0D =0D 1. Introduction...................................................2=0D= 2. Specification Template.........................................3=0D= 2.1. Namespace ID..............................................3=0D= 2.2. Registration Information..................................3=0D= 2.3. Declared Registrant of the Namespace......................3=0D= 2.4. Declaration of the Syntactic Structure....................3=0D= 2.5. Relevant Ancillary Documentation..........................4=0D= 2.6. Identifier Uniqueness Considerations......................4=0D= 2.7. Identifier Persistence Considerations.....................4=0D= 2.8. Process of Identifier Assignment..........................4=0D= 2.9. Process of Identifier Resolution..........................5=0D= 2.10. Rules for Lexical Equivalence............................5=0D= 2.11. Conformance with URN syntax..............................5=0D= 2.12. Validation Mechanism.....................................5=0D= 2.13. Scope....................................................5=0D= 3. Examples (Informative).........................................5=0D= 4. Namespace Considerations.......................................6=0D= 5. Community Considerations.......................................6=0D= 6. Security Considerations........................................6=0D= 7. IANA Considerations............................................6=0D= 8. References.....................................................6=0D= 8.1. Normative References......................................6=0D= 8.2. Informative References....................................7=0D= 9. Acknowledgments................................................7=0D= =0D 1. Introduction=0D =0D Globus (https://www.globus.org) is a software-as-a-service provider=0D= that develops and operates services and tools for the global=0D research and education community.=0D =0D Globus provides multiple services for users across many=0D institutions, primarily for High Performance Computing driven=0D research. Globus creates unique identifiers which will be persisted=0D= in external systems, and which must be identifiable as references to=0D= Globus entities.=0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 2]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D To address this need, this document requests that a formal URN space=0D= type be assigned as described in Sect = ion 4.3 of RFC 3406.=0D =0D 2. Specification Template=0D =0D 2.1. Namespace ID=0D =0D The Namespace ID "globus" is requested.=0D =0D 2.2. Registration Information=0D =0D Version 1=0D =0D Date: 2015-12-08=0D =0D 2.3. Declared Registrant of the Namespace=0D =0D Globus Project Lead=0D 401 N Michigan Ave=0D Suite 900=0D Chicago, Illinois, 60611=0D USA=0D =0D Email: tuecke@globus.org=0D =0D The position of Globus Project Lead is currently filled by Steve=0D Tuecke.=0D =0D 2.4. Declaration of the Syntactic Structure=0D =0D The Namespace Specific String (NSS) of all URNs that use the=0D "globus" NID shall have the following structure:=0D =0D ::=3D "urn: " "globus" ":" =0D =0D ::=3D | ":" =0D =0D ::=3D 1*=0D =0D ::=3D 1*=0D =0D ::=3D | "%" =0D =0D ::=3D | | | =0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 3]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D ::=3D "(" | ")" | "+" | "," | "-" | "." | "=3D" |=0D= "@" | ";" | "$" | "_" | "!" | "*" | "'"=0D =0D The "SNID" is the top-level segment of the NSS. It is a=0D required US-ASCII string, subject to the above syntax, that conforms=0D= to the URN syntax requirements (see [RFC 2141]). It identifies a=0D category of Globus entities, often associated with a particular=0D Globus service. For example "auth" could be used as an SNID for=0D identifiers generated by the Globus authentication and authorization=0D= service (Globus Auth).=0D =0D The "SUBNAMESPACE-SPECIFIC-STRING" is an optional US-ASCII string=0D and second-level segment of the NSS, belonging to the "SNID"=0D context, subject to the above syntax and conformant to the URN=0D syntax requirements (see [RFC 2141]). "SUBNAMESPACE-SPECIFIC-STRING"=0D= identifies a category of thing within that Globus service, such as=0D "scope:transfer.api.globus.org:all"=0D =0D 2.5. Relevant Ancillary Documentation=0D =0D None.=0D =0D 2.6. Identifier Uniqueness Considerations=0D =0D Identifier uniqueness will be enforced by the Globus Project Lead.=0D The Globus Project Lead may sub-delegate part of the namespace to=0D third parties. It will not be permissible, neither by the Globus=0D Project Lead nor any third party, to re-assign previously=0D assigned URNs. A practical consequence is that a previously=0D assigned subnamespace cannot be re-assigned, unless additional=0D arrangements are made to prevent identifier re-assignements.=0D =0D 2.7. Identifier Persistence Considerations=0D =0D Identifiers will never be reassigned, but in some circumstances they=0D= may be invalidated by the Globus Project Lead or by a third party.=0D =0D 2.8. Process of Identifier Assignment=0D =0D Assignment of subnamespace identifiers is limited to the Globus=0D Project Lead and those authorities that are specifically designated=0D= by the Globus Project Lead. The Globus Project Lead may assign=0D portions of the globus namespace (specifically, those under=0D designated subnamespace identifiers) for assignment by third=0D parties.=0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 4]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D 2.9. Process of Identifier Resolution=0D =0D None currently.=0D =0D Future versions of this document may define resources that can be=0D used to resolve Globus identifiers.=0D =0D 2.10. Rules for Lexical Equivalence=0D =0D No additional rules beyond those specified in RFC2141.=0D =0D 2.11. Conformance with URN syntax=0D =0D No special considerations.=0D =0D 2.12. Validation Mechanism=0D =0D None currently.=0D Future versions of this document may define resources that can be=0D used to validate Globus identifiers.=0D =0D 2.13. Scope=0D =0D Global.=0D =0D 3. Examples (Informative)=0D =0D The following examples are based on plans for the Globus URN. They=0D= are therefore not guaranteed to be valid.=0D =0D The Globus Auth service defines the "auth" SNID, and contains the=0D following URNs.=0D =0D o urn:globus:auth:scope:transfer.api.globus.org:all=0D =0D o urn:globus:auth:grants:dependent_token=0D =0D A hypothetical service, the Globus Groups service, would have a=0D distinct SNID. If that SNID were "groups", it might have URNs such=0D as the following.=0D =0D o urn:globus:groups:group:669b572e-9de4-11e5-966e-3c970e0c9cc4=0D =0D o urn:globus:groups:memberships:72e1c6c6-9de4-11e5-966e-=0D 3c970e0c9cc4=0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 5]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D 4. Namespace Considerations=0D =0D The use of the Globus namespace is expected to be broad, including=0D but not limited to usage for:=0D =0D o OAuth2 scopes=0D =0D o OAuth2 custom extension grants=0D =0D o Entity identification for Globus Services=0D =0D 5. Community Considerations=0D =0D Members of the Globus community will benefit from persistent and=0D globally unique identifiers for use in software and in conformance=0D with protocols developed and used by Globus and third-party=0D collaborators.=0D =0D 6. Security Considerations=0D =0D There are no additional security considerations other than those=0D normally associated with the use and resolution of URNs in general,=0D= which are described in [RFC1737], [RFC2141], and [RFC3406].=0D =0D 7. IANA Considerations=0D =0D IANA is kindly requested to register the "globus" namespace=0D identifier (NID) into the IANA registry located at=0D =0D =0D 8. References=0D =0D 8.1. Normative References=0D =0D [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate=0D Requirement Levels", BCP 14, RFC 2119, March 1997.=0D =0D [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.=0D =0D [RFC5234] Crocker, D. and Overell, P., "Augmented BNF for Syntax=0D Specifications: ABNF", STD 68, RFC 5234, January 2008.=0D =0D [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", RFC=0D 6749, October 2012.=0D =0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 6]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D 8.2. Informative References=0D =0D None.=0D =0D 9. Acknowledgments=0D =0D The authors would like to thank Stephen Rosen and Vas Vasiliadis for=0D= proofreading this document and providing valuable feedback.=0D =0D This document was prepared using 2-Word-v2.0.template.dot.=0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 7]=0D= =0C=0D Internet-Draft A URN Namespace for Globus December 2015=0D= =0D =0D Authors' Addresses=0D =0D Stuart Martin=0D University of Chicago=0D 401 N Michigan Ave=0D Suite 900=0D Chicago, Illinois, 60611=0D USA=0D =0D Email: sjmartin@uchicago.edu=0D =0D Steve Tuecke=0D University of Chicago=0D 401 N Michigan Ave=0D Suite 900=0D Chicago, Illinois, 60611=0D USA=0D =0D Email: tuecke@globus.org=0D =0D Brendan McCollam=0D University of Chicago=0D 401 N Michigan Ave=0D Suite 900=0D Chicago, Illinois, 60611=0D USA=0D =0D Email: bmccollam@uchicago.edu=0D =0D =0D Mattias Lidman=0D University of Chicago=0D 401 N Michigan Ave=0D Suite 900=0D Chicago, Illinois, 60611=0D USA=0D =0D Email: mattias@uchicago.edu=0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D Martin, et. al. Expires June 8, 2016 [Page 8]=0D= =0C=0D --Apple-Mail=_C294DAA0-85AE-4269-AF66-993DC2AA9A92 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii" --Apple-Mail=_C294DAA0-85AE-4269-AF66-993DC2AA9A92-- --Apple-Mail=_2BA34C62-1438-451D-BDB9-A3D40A23FBFF-- From nobody Sat Jan 9 09:12:15 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE751B2BB1 for ; Fri, 8 Jan 2016 12:58:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.209 X-Spam-Level: X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixDMJYftVZ6z for ; Fri, 8 Jan 2016 12:58:31 -0800 (PST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A9F91B2BAB for ; Fri, 8 Jan 2016 12:58:31 -0800 (PST) Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mailrelay.anl.gov (Postfix) with ESMTPS id 7A80B200093 for ; Fri, 8 Jan 2016 14:58:30 -0600 (CST) X-IronPort-AV: E=Sophos;i="5.20,540,1444712400"; d="scan'208,217";a="105547681" Received: from hybrid-luckman.anl.gov (HELO LUCKMAN.anl.gov) ([146.137.81.14]) by mailgateway.anl.gov with ESMTP/TLS/AES256-SHA; 08 Jan 2016 14:58:30 -0600 Received: from [10.0.1.5] (146.137.81.4) by smtp.anl.gov (146.137.81.37) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 8 Jan 2016 14:58:16 -0600 Content-Type: multipart/alternative; boundary="Apple-Mail=_B8EAB817-D16D-4185-ABFE-2B7FEC233C76" MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Request for a formal URN Namespace ID for "globus" From: Stuart Martin In-Reply-To: <9AF891B8-C5A8-435A-BDB6-5018BCA8328B@mcs.anl.gov> Date: Fri, 8 Jan 2016 14:57:35 -0600 Message-ID: References: <9AF891B8-C5A8-435A-BDB6-5018BCA8328B@mcs.anl.gov> To: "urn-nid@apps.ietf.org" X-Mailer: Apple Mail (2.3112) Archived-At: X-Mailman-Approved-At: Sat, 09 Jan 2016 09:12:13 -0800 X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 20:58:35 -0000 --Apple-Mail=_B8EAB817-D16D-4185-ABFE-2B7FEC233C76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" There is now a copy of the globus doc uploaded in datatracker here: https://datatracker.ietf.org/doc/draft-martin-urn-globus/ = It has the same =E2=80=9C00=E2=80=9D version, but the one in datatracker = has a few updates. - Fixed double spacing throughout doc. - Fixed some wrongs dates/years. Looking forward to your input. -Stu > On Jan 4, 2016, at 6:36 PM, Stuart Martin wrote: >=20 > Dear IESG, >=20 > Please find attached a draft request for a formal URN Namespace ID for = =E2=80=9Cglobus=E2=80=9D. >=20 > Regards, > Stu Martin >=20 > --------------------------------------- > Software Development Manager > University of Chicago / Globus > 401 N. Michigan Ave., Suite 900 > Chicago, IL 60611 > Office: 630-677-6892 >=20 > --Apple-Mail=_B8EAB817-D16D-4185-ABFE-2B7FEC233C76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
There is now a copy of the globus doc = uploaded in datatracker here:
https://datatracker.ietf.org/doc/draft-martin-urn-globus/

It has the same =E2=80=9C00=E2=80=9D version, but the one in = datatracker has a few updates.
- Fixed = double spacing throughout doc.
- Fixed = some wrongs dates/years.

Looking forward to your input.

-Stu

On Jan 4, 2016, at 6:36 PM, = Stuart Martin <smartin@mcs.anl.gov> wrote:

Dear IESG,

Please find attached a draft request for a formal URN = Namespace ID for =E2=80=9Cglobus=E2=80=9D.

Regards,
Stu Martin

---------------------------------------
Software Development Manager
University of Chicago / Globus
401 N. Michigan = Ave., Suite 900
Chicago, IL = 60611
Office: 630-677-6892

<draft-martin-urn= -globus-00.txt>

= --Apple-Mail=_B8EAB817-D16D-4185-ABFE-2B7FEC233C76-- From nobody Mon Jan 11 12:19:45 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5A91A90DC for ; Mon, 11 Jan 2016 12:19:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.465 X-Spam-Level: * X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B362nEVuUMw1 for ; Mon, 11 Jan 2016 12:19:42 -0800 (PST) Received: from resqmta-po-05v.sys.comcast.net (resqmta-po-05v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:164]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E49E1A90DF for ; Mon, 11 Jan 2016 12:19:42 -0800 (PST) Received: from resomta-po-10v.sys.comcast.net ([96.114.154.234]) by resqmta-po-05v.sys.comcast.net with comcast id 4kHe1s00B53iAfU01kKhSU; Mon, 11 Jan 2016 20:19:41 +0000 Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-po-10v.sys.comcast.net with comcast id 4kKg1s00Y1nMCLR01kKhK8; Mon, 11 Jan 2016 20:19:41 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u0BKJel5027264; Mon, 11 Jan 2016 15:19:40 -0500 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u0BKJdwA027257; Mon, 11 Jan 2016 15:19:39 -0500 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: Stuart Martin Subject: Re: Request for a formal URN Namespace ID for "globus" In-Reply-To: (smartin@mcs.anl.gov) Sender: worley@ariadne.com (Dale R. Worley) Date: Mon, 11 Jan 2016 15:19:39 -0500 Message-ID: <874mejq36s.fsf@hobgoblin.ariadne.com> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1452543581; bh=mSl11IsQ16ejemMT859ykIZUZoQ/vH8mAOLQHF0ff9U=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=gkT8jVE1ejiknNP/2fszoCLMcgBhMB8MOakR6X4ZQI6oXRr53HLxzJWBHDEzO6Q9B RjLc2ol/NxVoRKYJMsSoKduBq7P/2hNxiEXAS51FBhskEGKSNwi3Ao/i+NSDE84HMT Q5h8w54sEepITmxuWsx916kRTNEcuUT3/M4ARFF2v1Waz9gB/mUqWNl78gdwIDwPhF vyx2UhAu8EHglZBWvAtWm6i217zdGRm5fs4QpvynVB+u7BBEhLgzSR0E1p+Q5FnNom bwmWOVwAfZ1urjUbfxZmOkPVQuLy8CYRfWmcG64CKBe6E8eGhrq/JcvSUpCm7Ce+Fs UsaXL22MqQi3w== Archived-At: Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2016 20:19:43 -0000 I have some nits: 2.4. Declaration of the Syntactic Structure ::= "urn: " "globus" ":" ------------------^ Remove this space. ::= | ":" You might want to change "SUBNAMESPACE-SPECIFIC-STRING" to "subnamespace-specific-string" or "SNSS". ::= 1* ::= 1* ::= | "%" ::= | | | ::= "(" | ")" | "+" | "," | "-" | "." | "=" | "@" | ";" | "$" | "_" | "!" | "*" | "'" IMO, "" should be "", etc. (Though I admit that RFC 2141 uses "".) Dale From nobody Mon Jan 11 14:03:56 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DEE1AC3C4 for ; Mon, 11 Jan 2016 14:03:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q_aARhB7-PDa for ; Mon, 11 Jan 2016 14:03:53 -0800 (PST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8274C1AC3C3 for ; Mon, 11 Jan 2016 14:03:53 -0800 (PST) Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mailrelay.anl.gov (Postfix) with ESMTPS id D9F29200128 for ; Mon, 11 Jan 2016 16:03:52 -0600 (CST) X-IronPort-AV: E=Sophos;i="5.20,554,1444712400"; d="scan'208,217";a="105780966" Received: from hybrid-george.anl.gov (HELO GEORGE.anl.gov) ([146.137.81.15]) by mailgateway.anl.gov with ESMTP/TLS/AES256-SHA; 11 Jan 2016 16:03:52 -0600 Received: from wireless-s1-no-150-28-42.uchicago.edu (146.137.81.4) by smtp.anl.gov (146.137.81.39) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 11 Jan 2016 16:03:39 -0600 Content-Type: multipart/alternative; boundary="Apple-Mail=_9A9DAE5C-9758-49F2-BEC0-D515D29F1DCF" MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Request for a formal URN Namespace ID for "globus" From: Stuart Martin In-Reply-To: <874mejq36s.fsf@hobgoblin.ariadne.com> Date: Mon, 11 Jan 2016 16:03:34 -0600 Message-ID: <7EDF7698-B115-4453-A383-C852392AD744@mcs.anl.gov> References: <874mejq36s.fsf@hobgoblin.ariadne.com> To: "Dale R. Worley" X-Mailer: Apple Mail (2.3112) Archived-At: Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2016 22:03:55 -0000 --Apple-Mail=_9A9DAE5C-9758-49F2-BEC0-D515D29F1DCF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Hi Dale, In the new =E2=80=9C01=E2=80=9D version = (https://www.ietf.org/id/draft-martin-urn-globus-01.txt = ), I changed the = following based on your input: 1) Remove the space from =E2=80=9Curn: =E2=80=9C to be =E2=80=9Curn:" 2) "SUBNAMESPACE-SPECIFIC-STRING=E2=80=9D to = "subnamespace-specific-string 3) a. to b. and to be = and Thanks for the feedback. Let me know if any other changes are needed. -Stu > On Jan 11, 2016, at 2:19 PM, Dale R. Worley = wrote: >=20 > I have some nits: >=20 > 2.4. Declaration of the Syntactic Structure >=20 > ::=3D "urn: " "globus" ":" > ------------------^ >=20 > Remove this space. >=20 > ::=3D | ":" >=20 > You might want to change "SUBNAMESPACE-SPECIFIC-STRING" to > "subnamespace-specific-string" or "SNSS". >=20 > ::=3D 1* >=20 > ::=3D 1* >=20 > ::=3D | "%" >=20 > ::=3D | | | other> >=20 > ::=3D "(" | ")" | "+" | "," | "-" | "." | "=3D" | > "@" | ";" | "$" | "_" | "!" | "*" | "'" >=20 > IMO, "" should be "", etc. (Though = I > admit that RFC 2141 uses "".) >=20 > Dale --Apple-Mail=_9A9DAE5C-9758-49F2-BEC0-D515D29F1DCF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Hi Dale,

In the new =E2=80=9C01=E2=80=9D version = (https://www.ietf.org/id/draft-martin-urn-globus-01.txt), = I changed the following based on your input:

1) Remove the space from =E2=80=9Curn: = =E2=80=9C to be =E2=80=9Curn:"
2) = "SUBNAMESPACE-SPECIFIC-STRING=E2=80=9D to = "subnamespace-specific-string
3)
    a. <non-colon char> to = <non-colon-char>
    = b. <non-colon trans> and <non-colon other> to be = <non-colon-trans> and <non-colon-other>

Thanks for the feedback. =  Let me know if any other changes are needed.

-Stu

On = Jan 11, 2016, at 2:19 PM, Dale R. Worley <worley@ariadne.com> = wrote:

I have some nits:

=   2.4. Declaration of the Syntactic Structure

  <URN> ::=3D "urn: " "globus" ":" = <NSS>
------------------^

Remove this space.

=   <NSS> ::=3D <SNID> | <SNID> ":" = <SUBNAMESPACE-SPECIFIC-STRING>

You = might want to change "SUBNAMESPACE-SPECIFIC-STRING" to
"subnamespace-specific-string" or "SNSS".

  <SNID> ::=3D 1*<non-colon chars>

=   <SUBNAMESPACE-SPECIFIC-STRING> ::=3D 1*<URN = chars>

  <non-colon = chars> ::=3D <non-colon trans> | "%" <hex> <hex>

  <non-colon trans> ::=3D = <upper> | <lower> | <number> | <non-colon
  other>

=   <non-colon other> ::=3D "(" | ")" | "+" | "," | "-" | = "." | "=3D" |
=             &n= bsp;           "@" = | ";" | "$" | "_" | "!" | "*" | "'"

IMO, = "<non-colon chars>" should be "<non-colon-chars>", etc. =  (Though I
admit that RFC 2141 uses "<URN = chars>".)

Dale

= --Apple-Mail=_9A9DAE5C-9758-49F2-BEC0-D515D29F1DCF-- From nobody Tue Jan 19 06:50:49 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8A6B1B2FDD for ; Tue, 19 Jan 2016 06:50:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmKh7aBPgIrZ for ; Tue, 19 Jan 2016 06:50:46 -0800 (PST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E2571B2FDB for ; Tue, 19 Jan 2016 06:50:46 -0800 (PST) Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mailrelay.anl.gov (Postfix) with ESMTPS id 712AB200100 for ; Tue, 19 Jan 2016 08:50:45 -0600 (CST) X-IronPort-AV: E=Sophos;i="5.22,317,1449554400"; d="scan'208,217";a="106589200" Received: from hybrid-george.anl.gov (HELO GEORGE.anl.gov) ([146.137.81.15]) by mailgateway.anl.gov with ESMTP/TLS/AES256-SHA; 19 Jan 2016 08:50:25 -0600 Received: from [10.0.1.5] (146.137.81.4) by smtp.anl.gov (146.137.81.39) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 19 Jan 2016 08:50:22 -0600 Content-Type: multipart/alternative; boundary="Apple-Mail=_719C18FF-8FAD-4594-AC30-55978218E96A" MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Request for a formal URN Namespace ID for "globus" From: Stuart Martin In-Reply-To: <7EDF7698-B115-4453-A383-C852392AD744@mcs.anl.gov> Date: Tue, 19 Jan 2016 08:50:22 -0600 Message-ID: References: <874mejq36s.fsf@hobgoblin.ariadne.com> <7EDF7698-B115-4453-A383-C852392AD744@mcs.anl.gov> To: "Dale R. Worley" X-Mailer: Apple Mail (2.3112) Archived-At: Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 14:50:48 -0000 --Apple-Mail=_719C18FF-8FAD-4594-AC30-55978218E96A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Hi Dale and all, Are there any more reviews coming? We (Globus) would like to start = using these Globus URNs in an upcoming software release and would like = to prevent a future change to them if possible. Thanks, Stu > On Jan 11, 2016, at 4:03 PM, Stuart Martin = wrote: >=20 > Hi Dale, >=20 > In the new =E2=80=9C01=E2=80=9D version = (https://www.ietf.org/id/draft-martin-urn-globus-01.txt = ), I changed the = following based on your input: >=20 > 1) Remove the space from =E2=80=9Curn: =E2=80=9C to be =E2=80=9Curn:" > 2) "SUBNAMESPACE-SPECIFIC-STRING=E2=80=9D to = "subnamespace-specific-string > 3) > a. to > b. and to be = and >=20 > Thanks for the feedback. Let me know if any other changes are needed. >=20 > -Stu >=20 >> On Jan 11, 2016, at 2:19 PM, Dale R. Worley > wrote: >>=20 >> I have some nits: >>=20 >> 2.4. Declaration of the Syntactic Structure >>=20 >> ::=3D "urn: " "globus" ":" >> ------------------^ >>=20 >> Remove this space. >>=20 >> ::=3D | ":" >>=20 >> You might want to change "SUBNAMESPACE-SPECIFIC-STRING" to >> "subnamespace-specific-string" or "SNSS". >>=20 >> ::=3D 1* >>=20 >> ::=3D 1* >>=20 >> ::=3D | "%" >>=20 >> ::=3D | | | > other> >>=20 >> ::=3D "(" | ")" | "+" | "," | "-" | "." | "=3D" | >> "@" | ";" | "$" | "_" | "!" | "*" | "'" >>=20 >> IMO, "" should be "", etc. (Though = I >> admit that RFC 2141 uses "".) >>=20 >> Dale >=20 --Apple-Mail=_719C18FF-8FAD-4594-AC30-55978218E96A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Hi Dale and all,

Are there any more reviews coming? =  We (Globus) would like to start using these Globus URNs in an = upcoming software release and would like to prevent a future change to = them if possible.

Thanks,
Stu

On = Jan 11, 2016, at 4:03 PM, Stuart Martin <smartin@mcs.anl.gov>= wrote:

Hi Dale,

In the new =E2=80=9C01=E2=80=9D version (https://www.ietf.org/id/draft-martin-urn-globus-01.txt), = I changed the following based on your input:

1) Remove the space from =E2=80=9Curn: = =E2=80=9C to be =E2=80=9Curn:"
2) = "SUBNAMESPACE-SPECIFIC-STRING=E2=80=9D to = "subnamespace-specific-string
3)
    a. <non-colon char> to = <non-colon-char>
    = b. <non-colon trans> and <non-colon other> to be = <non-colon-trans> and <non-colon-other>

Thanks for the feedback. =  Let me know if any other changes are needed.

-Stu

On Jan 11, 2016, at 2:19 PM, Dale R. Worley <worley@ariadne.com> = wrote:

I have some nits:

=   2.4. Declaration of the Syntactic Structure

  <URN> ::=3D "urn: " "globus" ":" = <NSS>
------------------^

Remove this space.

=   <NSS> ::=3D <SNID> | <SNID> ":" = <SUBNAMESPACE-SPECIFIC-STRING>

You = might want to change "SUBNAMESPACE-SPECIFIC-STRING" to
"subnamespace-specific-string" or "SNSS".

  <SNID> ::=3D 1*<non-colon chars>

=   <SUBNAMESPACE-SPECIFIC-STRING> ::=3D 1*<URN = chars>

  <non-colon = chars> ::=3D <non-colon trans> | "%" <hex> <hex>

  <non-colon trans> ::=3D = <upper> | <lower> | <number> | <non-colon
  other>

=   <non-colon other> ::=3D "(" | ")" | "+" | "," | "-" | = "." | "=3D" |
=             &n= bsp;           "@" = | ";" | "$" | "_" | "!" | "*" | "'"

IMO, = "<non-colon chars>" should be "<non-colon-chars>", etc. =  (Though I
admit that RFC 2141 uses "<URN = chars>".)

Dale


= --Apple-Mail=_719C18FF-8FAD-4594-AC30-55978218E96A-- From jwold@ad-id.org Fri Jan 29 08:12:05 2016 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071B41B3100 for ; Fri, 29 Jan 2016 08:12:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.332 X-Spam-Level: * X-Spam-Status: No, score=1.332 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wnxMLqTTkXe for ; Fri, 29 Jan 2016 08:12:02 -0800 (PST) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55E371B30FF for ; Fri, 29 Jan 2016 08:12:02 -0800 (PST) Received: by mail-wm0-x22c.google.com with SMTP id l66so61012884wml.0 for ; Fri, 29 Jan 2016 08:12:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ad-id.org; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=aQrgbBir+EzJVFAQKzVY/Cfi/ty1vYW0r0WMXsEs2ds=; b=GBmNbIQyAIunN+Gke8bPv6oS9KCFCgR9I1N+6AzSOqu5QV5jrXwL0Uk20xpQGdLkDH 5DItssQ26MUnEtv1M9Qni9QKbhOUQe4p0q8PmbdWpZyuC9Bqady07748G+/EjV2F/5LM 6f6PpOtDXHvdVrmEcCzxfupU7EJBESJV1+kws= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=aQrgbBir+EzJVFAQKzVY/Cfi/ty1vYW0r0WMXsEs2ds=; b=Nq65qGMBwCygwwlmjIen6xZ9ahZU/y408QT48FTW9JhbxS/9fxZ1F9lmuqwpG+ZYVr Ex0ubTlzL/XE6Mhnk9z+8/w32zCQx+kLrk9+FZqOAS3GOAuUkz+tVW1j6yeCGUXiYT/e kIb+G3AHZ2UjsgFupuMm6XUMd44A15YJ8+mw4cE9YQ+Cc9ss6Ra/jK5OpWx7kTofQlFl FAN8pnrxQ+RjHyqBmtjAq7ax/Trktnke6Dz3WA/t5QBduBvpBid/D7s/mgRxReNZ3FKI iqI5MfBx8CoB4hPZ3pgyufAcv9SL0bFYutQSz0jfc1jD69PfjFl5401IeyCZIJEk+pg4 4Ufw== X-Gm-Message-State: AG10YOTwrgjtT9Q4fgvrmht8eEndG0crxUXAZsQUk32HDcFSyheo369b/9Fo9irRDArYJhDQ7ojLCdQ0w2mC0WvQ X-Received: by 10.194.216.100 with SMTP id op4mr9150103wjc.85.1454083920514; Fri, 29 Jan 2016 08:12:00 -0800 (PST) From: Jarrett Wold MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdFar6TfbX8pV9DMQyWaIGT6zl2pNQ== Date: Fri, 29 Jan 2016 11:12:01 -0500 Message-ID: <798adff9c52a63eaed9f2325ae8f20bc@mail.gmail.com> Subject: URN namespaces Submission for Ad-ID (www.ad-id.org) To: urn-nid@apps.ietf.org Content-Type: multipart/alternative; boundary=089e014935f48e6ab7052a7b4b36 Archived-At: X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 16:13:13 -0000 --089e014935f48e6ab7052a7b4b36 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am submitting a request for an URN Namespace for Advertising Digital (Ad-ID). Thank You *Jarrett Wold *| *Ad-ID LLC* Director of Technology & Platforms 646-708-8131 jwold@ad-id.org BEGIN TEMPLATE The namespace definition according to the template in [RFC3406 ] is as follows: Namespace ID: adid Registration Information: Version 1 2015-12-21 Declared registrant of the namespace: Name: Advertising Digital Identification, LLC Address: Advertising Digital Identification, LLC 11020 David Taylor Drive, Suite 305 Charlotte, NC 28262-1103 USA Contact: URL: http://www.ad-id.org/contact Email: cs@ad-id.org Declaration of syntactic structure: The identifier structure is as follows: An Ad-ID Identifier consists of an eleven or twelve character string. This string is divided into three parts: 1. a four-character alphanumeric (non-leading zero) Company Prefix 2. a seven-character alphanumeric Unique Code 3. a one-character Video Format Identifier. Non alphanumeric (=E2=80=9Cspecial=E2=80=9D) characters and spaces are not = valid within the structure of an Ad-ID. A Canonical Full Ad-ID Identifier shall conform to the syntax specified below using ABNF (as specified in IETF RFC 5234): The URN representation URN-ADID of an ADID Identifier conforms to the syntax (expressed using ABNF (as specified in [RFC5234 ]): FULL_ADID_IDENTIFIER =3D FULL_ADID_PREFIX1 FULL_ADID_PREFIX2 FULL_ADID_CODE {FULL_ADID_SUFFIX} FULL_ADID_PREFIX1 =3D 1*ALPHANUM =3D %x41-5A; A-Z / %x31-39; 1-9 FULL_ADID_PREFIX2 =3D 3*ALPHANUM =3D %x41-5A; A-Z / %x30-39; 0-9 FULL_ADID_CODE =3D 7*ALPHANUM FULL_ADID_SUFFIX =3D =E2=80=9CH=E2=80=9D / =E2=80=9CD=E2=80=9D DIGIT =3D %x30-39; 0-9 ALPHA =3D %x41-5A; A-Z ALPHANUM =3D ALPHA / DIGIT The following is an example of the string representation of an ADID as a = URN: urn:adid:ABCD0001000 urn:adid:ABCD0001000H 32-BIT unique representation of the FULL_ADID_CODE; The short version (compact unique identifier) of the identifier is as follo= ws: urn:adid:cuid: Example: urn:adid:cuid:36faeaba where CUID is a 32-BIT unique representation of the full Ad-ID code as defined above. Relevant ancillary documentation: [SMPTERP2092-1] specifies the representation of Ad-ID. Identifier uniqueness considerations: The ADID Registrar is responsible for managing the assignment of the ADID and shall ensure the uniqueness of all ADID URNs by checking such names against the list of existing ids. ADID assigns the identifier, adid, in such a way that the uniqueness of the 'adid' will be maintained. Furthermore, an ADID Identifier is associated with a single URN-ADID. Identifier persistence considerations: The assignment process guarantees that =E2=80=98adids=E2=80=99 are not reas= signed or reused and the binding between the id and its resource is permanent. By reference this URN namespace inherits those rules Process of identifier assignment: ADIDs are generated by Ad-ID=E2=80=99s proprietary registration pr= ocedures. Process for identifier resolution: ADID URNs are resolved via URN resolvers run under ADID responsibility. Rules for Lexical Equivalence: Lexical equivalence of ADID-URN is defined by case-insensitive string match. Conformance with URN Syntax: As specified above, the syntax of ADID-URN is a subset of the URN syntax specified in [RFC2141 ]. Validation mechanism: The validity of an ADID-URN can be checked using AD-ID=E2=80=99s web = services. Scope: ADID Identifiers are centrally registered, globally unique identifiers for use with advertising assets worldwide. --089e014935f48e6ab7052a7b4b36 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <= div class=3D"WordSection1">

I am submitting a request= for an URN Namespace for Advertising Digital (Ad-ID).

=C2=A0

Thank You

= =C2=A0

Jarrett Wold | Ad-ID LLC
Director of Technology & Platforms
646-70= 8-8131

jwold@ad-id.org

=C2=A0

BEGIN TEMPLATE

<= span style=3D"font-size:10.0pt;font-family:"Courier New"">=C2=A0= =C2=A0 The namespace definition according to the template in [RFC3406] is as

=C2=A0=C2=A0 follows:

=C2=A0

=C2=A0=C2=A0 Namespace ID:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 adid

=C2=A0

=C2=A0=C2=A0 Regi= stration Information:

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Version 1

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2015-12-= 21

=C2=A0

=C2=A0=C2= =A0 Declared registrant of the namespace:

= =C2=A0=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Name:

=

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Advertising Digital Identification, LLC

=

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Address:

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 11020 David Taylor Drive, Suite 305

= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0USA

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Conta= ct:

=C2=A0

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 URL: http://www.ad-id.org/contact

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Email: cs@ad-id.org

=C2=A0

=C2=A0=C2=A0 Declaration of syntactic structure:

=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The iden=
tifier structure is as follows:
=C2=A0

An Ad-ID Identifier consists of = an eleven or twelve character string.=C2=A0

This string is divided into three parts:=

1.=C2=A0 a four-character al= phanumeric (non-leading zero) Company Prefix

2.=C2=A0 a seven-character alphanumeric Unique Code =

3.=C2=A0 a one-charac= ter Video Format Identifier.

Non alphanumeric (=E2=80=9Cspecial=E2=80=9D) c= haracters and spaces are not valid within the structure of an Ad-ID.

A Canonical Full Ad-ID Ide= ntifier shall conform to the syntax specified below using ABNF (as specifie= d in IETF RFC 5234): The URN representation URN-ADID of an ADID Identifier= conforms to the syntax (expressed using ABNF (as specified in [RFC5234]):

= =C2=A0

FULL_ADID_IDENTIFIER =3D FULL_ADID_PREFIX1= =C2=A0FULL_ADID_PREFIX2=C2=A0FULL_ADID_CODE {FULL_ADID_SUFFIX}

FULL_ADID_PREFIX1 =3D 1*ALPHANUM =3D %x4= 1-5A; A-Z / %x31-39; 1-9=C2=A0

FULL_ADID_PREFIX2 =3D 3*ALPHANUM =3D %x41-5A; A-Z / %x30-39; 0-9=C2=A0

FULL_ADID_CODE =3D 7*ALPHANUM=

FULL_ADID_SUFFIX =3D =E2=80= =9CH=E2=80=9D / =E2=80=9CD=E2=80=9D

DIGIT =3D %x30-39; 0-9

ALPHA =3D %x41-5A; A-Z=C2=A0

ALPHANUM =3D ALPHA / DIGIT

=C2=A0<= /span>

The following is an example of th=
e string representation of an ADID as=C2=A0=C2=A0 a URN:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0

= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 urn:adid:ABCD0001000=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0urn:adid:ABCD0001000H=

=C2=A0

=C2=A0

32-BIT unique= representation of the FULL_ADID_CODE;
=C2=A0
The short version (comp=
act unique identifier) of the identifier is as follows: 
=C2=A0
=C2=A0
=C2=A0=C2=A0 =C2=
=A0=C2=A0=C2=A0urn:adid:cuid:<CUID>
=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Example: urn:adid:cuid:36faeaba
=C2=A0=

where CUID is a 32-BIT unique representation of the full Ad-ID code as d=
efined above. 
=C2=A0
=C2=A0<=
/p>
=C2=A0=C2=A0 Relevant ancillary documentation:
=C2=A0
=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 [SMPTERP2092-1] specifies the representation of Ad-ID.
=

=C2=A0
=C2=A0
=C2=A0=C2=A0 Identifier uniqueness considerations:
=C2=A0
The ADID Regi=
strar is responsible for managing the assignment of the ADID and shall ensu=
re the uniqueness of all ADID URNs by checking such names against the list =
of existing ids.
=C2=A0
ADID assigns the identifier, adid, in such a way
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the uniqueness of the 'adid&=
#39; will be maintained.
=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 
=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0Furthermore, an ADID Identifier is associated wi=
th a single
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 URN-A=
DID.
=C2=A0
=C2=A0
=C2=A0=C2=A0 Identifier persistence considerations=
:
=C2=A0
The assignment process guarantees that =E2=80=98adids=E2=80=99 are not r=
eassigned or reused and the binding between the id and its resource is perm=
anent.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 
=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 By reference this URN namespace inherits those =
rules
=C2=A0
=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 
=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 
=C2=A0=C2=A0=C2=
=A0Process of identifier assignment:
=C2=A0
ADIDs are generated by Ad-ID=E2=80=99=
s proprietary registration=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 procedures.
=C2=A0
=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 
=C2=A0
=C2=A0=C2=A0 Process for identifier resolution:
=C2=A0
ADID URN=
s are resolved via URN resolvers run under ADID=C2=A0=C2=A0=C2=A0=C2=A0 res=
ponsibility.
=C2=A0
=C2=A0
=C2=A0
=C2=A0
=C2=A0
=C2=A0
=C2=
=A0
=C2=A0=C2=A0 Rules for Lexical Equivalence:<=
/span>
=C2=A0
=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 Lexical equivalence of ADID-URN is defined by case-insen=
sitive
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 string mat=
ch.
=C2=A0
=C2=A0=C2=
=A0 Conformance with URN Syntax:
=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As specified above, the s=
yntax of ADID-URN is a subset of the URN
<=
span style=3D"font-size:10.0pt;font-family:"Courier New"">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 syntax specified in [RFC2141].
=C2=A0
=C2=A0=C2=A0 Validatio=
n mechanism:
=C2=A0
=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The validity of an ADID-URN can be checked u=
sing AD-ID=E2=80=99s web services.
=C2=A0=

=C2=A0
=C2=A0=C2=A0 Scope:<=
/span>
=C2=A0
=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 ADID Identifiers are centrally registered, globally uniq=
ue
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 identifiers fo=
r use with advertising assets worldwide.
=
=C2=A0
=C2=A0
=C2=A0
--089e014935f48e6ab7052a7b4b36--