
From nobody Mon Apr 21 10:17:03 2014
Return-Path: <prvs=1188c5390b=david.roh@dolby.com>
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 9D0C21A0247; Mon, 21 Apr 2014 10:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.283
X-Spam-Level: 
X-Spam-Status: No, score=-0.283 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 OUyDPXBDPuyM; Mon, 21 Apr 2014 10:16:58 -0700 (PDT)
Received: from mx0b-000fd501.pphosted.com (mx0b-000fd501.pphosted.com [67.231.152.235]) by ietfa.amsl.com (Postfix) with ESMTP id F30121A0238; Mon, 21 Apr 2014 10:16:57 -0700 (PDT)
Received: from pps.filterd (m0000695 [127.0.0.1]) by mx0b-000fd501.pphosted.com (8.14.5/8.14.5) with SMTP id s3LH9iKF021163; Mon, 21 Apr 2014 10:16:52 -0700
Received: from dlb-xmrpw02.dolby.net (dcd-outbound.dolby.com [67.216.182.43]) by mx0b-000fd501.pphosted.com with ESMTP id 1kctdd9ggd-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 21 Apr 2014 10:16:52 -0700
Received: from DLB-XCHPW01.dolby.net ([169.254.1.100]) by DLB-XMRPW02.dolby.net ([10.213.22.205]) with mapi id 14.02.0318.004; Mon, 21 Apr 2014 10:16:51 -0700
From: "Roh, David" <david.roh@dolby.com>
To: "postmaster@ietf.org" <postmaster@ietf.org>
Subject: Informal URN Namespace NID Registration for Dolby Labs
Thread-Topic: Informal URN Namespace NID Registration for Dolby Labs
Thread-Index: AQHPXYV8kBpvtL44HkCRDyS+jW7UWg==
Importance: high
X-Priority: 1
Date: Mon, 21 Apr 2014 17:16:50 +0000
Message-ID: <E6B5D58009034D49A5FCC464B96D5B9633D7A955@DLB-XCHPW01.dolby.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.213.76.1]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E85342FF6C9F8A4D815451974F91E721@dolby.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96, 1.0.14,  0.0.0000 definitions=2014-04-21_02:2014-04-21,2014-04-21,1970-01-01 signatures=0
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/J02mramyMrMJWR3TEukfJf_Yo00
Cc: "urn-nid@apps.ietf.org" <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 <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 17:17:02 -0000

Dear Sir or Madam:

I am following up on my email below.  Could you let me know whether this
email was received and processed by the appropriate parties at IETF?
Please let me know at your earliest convenience.  Thank you.

Best,
David

David Roh
Business DevelopmentDolby Laboratories, Inc.
100 Potrero Ave.San Francisco, CA 94103
T: 415-558-0312 <tel:415-558-0312>  C: 415-314-9030 <tel:415-314-9030>
www.dolby.com <http://www.dolby.com/> | david.roh@dolby.com

=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=
=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B

On 3/28/14, 11:15 AM, "urn-nid@ietfa.amsl.com" <urn-nid@ietfa.amsl.com>
wrote:

>
>Confirmation of list posting -- confirmation ID: UzW8JQUZirvh
>
>The ietf.org mailing-list server has received a list posting from
>david.roh@dolby.com to urn-nid@ietfa.amsl.com with the subject
>'Informal URN Namespace NID Registration for Dolby Laboratories,
> Inc. '
>
>As the sender address isn't subscribed to the list, and has not been
>confirmed earlier, we have to request a confirmation of the address.
>To confirm the address, send a message to urn-nid@ietfa.amsl.com,
>with the same subject line as this message.
>
>(Simply sending a 'reply' to this message should work from most email
>interfaces, since that usually leaves the subject line in the right
>form.  The reply's additional "Re:" is ok.)
>
>If you do not wish your posting to the list to go through, simply
>disregard this message.  Questions to postmaster@ietf.org.

=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=8B=
=8B=8B=8B=8B=8B=8B=8B=8B=8B-

From: Roh, David=20
Sent: Freitag, 28. M=E4rz 2014 19:15
To: urn-nid@apps.ietf.org
Cc: Krauss, Kurt; Ward, Mike
Subject: Informal URN Namespace NID Registration for Dolby Laboratories,
Inc.


=20
Dear Sir or Madam:

=20

The intent of this email is to submit an Informal URN Namespace NID
Registration request for Dolby Laboratories, Inc.  To this effect, we have
filled out the registration template per the guideline referenced in RFC
3406.  Please see below the registration information and it is attached as
a pdf file as well for your review.

=20

Please let me know if you have any questions or comments before we can
proceed forward with respect to IANA.  Thank you.

=20

Regards,

David

=20

David Roh
Business Development
Dolby Laboratories, Inc.
100 Potrero Ave.
San Francisco, CA 94103
T: 415-558-0312 <tel:415-558-0312>  C: 415-314-9030 <tel:415-314-9030>
www.dolby.com <http://www.dolby.com/> | david.roh@dolby.com

=20

Informal URN Namespace NID Registration

=20
Namespace ID:
=20
      To be assigned by IANA
=20

Registration Information:
=20
      Registration Version Number: 1

      Date: <when submitted to IANA>
=20
Declared registrant of the namespace:
=20

      Name:  Dolby Laboratories, Inc.
      Address:  100 Potrero Ave.
      San Francisco, CA 94103
    =20
      Contact:  David Roh
      Phone: +1 415 314 9030
      E-mail: david.roh@dolby.com
=20

Declaration of structure:
=20
      The identifier structure is as follows:
=20
urn:urn-<assigned number>:<namespace-specific-identifier>:<assigned
US-ASCII string>
=20
      where <assigned-number> is the number assigned to this urn scheme
=20
      where <namespace-specific-identifier> is a US-ASCII string that
conforms to URN Syntax requirements as in RFC2141 and is a name to be
assigned by the registrant
=20
     where  <assigned US-ASCII string> is a US-ASCII string that conforms
to URN Syntax requirements as described in RFC2141.
    =20

Examples of possible URNs in this namespace include:
=20
        urn:urn-n:dash:manifestdescriptor:2014
        urn:urn-n:metadataclass:parameter:2014:test045
        urn:urn-n:specification:table:2014
        urn:urn-n:profile-example:parameter:level-2:20140101
        urn:urn-n:dash:audio_channel_configuration:2014
=20

    (In these examples, =B3urn-n=B2 is a placeholder for the Namespace ID t=
o
be assigned by IANA.)
=20

Relevant ancillary documentation:
=20
      None.
=20

Identifier uniqueness considerations:
=20
    Identifiers are assigned by Dolby Laboratories, Inc.  In the process
of identifier assignment, the registration authority confirms assignment
against the record of previously assigned names.
=20

Identifier persistence considerations:
=20
    The assignment process guarantees that names are not reassigned and
that the binding between the name and its resource is permanent,
regardless of any organizational changes.
=20

Process of identifier assignment:
=20
    Names are assigned by Dolby Laboratories, Inc.
=20

Process for identifier resolution:
=20
    The namespace is not listed with an RDS; this is not relevant
=20

Rules for Lexical Equivalence:
=20
   The leading =B3urn:" token and the Namespace Identifier, which will be a
number assigned by IANA, are case-insensitive, as defined by RFC2141.  The
other parts of the structure <namespace-specific-identifier> and <assigned
US-ASCII string> are case-sensitive.
=20

Conformance with URN Syntax:
=20
   No special considerations.
=20

Validation mechanism:
=20
   None specified.
=20

Scope:
=20
   Global.




From nobody Mon Apr 21 11:03:26 2014
Return-Path: <ted.ietf@gmail.com>
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 9F42D1A0224 for <urn-nid@ietfa.amsl.com>; Mon, 21 Apr 2014 11:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.026
X-Spam-Level: 
X-Spam-Status: No, score=-0.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 jYyO9ev6pwWW for <urn-nid@ietfa.amsl.com>; Mon, 21 Apr 2014 11:03:19 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6118F1A01FA for <urn-nid@apps.ietf.org>; Mon, 21 Apr 2014 11:03:19 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id rd18so4253323iec.29 for <urn-nid@apps.ietf.org>; Mon, 21 Apr 2014 11:03:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u3NQRbBmwxPpdzwK2Fiq9m17VKe/gLpfHK/WT6zHTe4=; b=x+jUSKb4nEq4VaXyHppw1fGCTaN+j1ppNQlOOcFrEwsv0jr3gfWU1FTg+fSgtxpz8M tjvi4jmzjKGwNhSHN5hKekrXN4WuUh/g+dIQGyLwpffWSEpVp5JyOgFpPvjt9HEMaXl7 puwO8r8Jw8gBTWTXgprD9HItqwIPoCkwmiSdGCqC2WNOl4+Frpq/nKZc3FCS2OWHplNV zlOUWmlA3n/mF/a/E270vzhlOzfyvICqVtq1viN4S2yb4RgA4ytQUhzBFvVmOYPAOLUJ hxRTH3cfMjzz4zU8nW8IXXyQ+hmIabG5BfimgoUFEpEsk6k5nNj7U/QjKTP13j1b4lL4 vsMA==
MIME-Version: 1.0
X-Received: by 10.43.163.200 with SMTP id mp8mr32164008icc.18.1398103394104; Mon, 21 Apr 2014 11:03:14 -0700 (PDT)
Received: by 10.42.200.204 with HTTP; Mon, 21 Apr 2014 11:03:14 -0700 (PDT)
In-Reply-To: <E6B5D58009034D49A5FCC464B96D5B9633D7A955@DLB-XCHPW01.dolby.net>
References: <E6B5D58009034D49A5FCC464B96D5B9633D7A955@DLB-XCHPW01.dolby.net>
Date: Mon, 21 Apr 2014 11:03:14 -0700
Message-ID: <CA+9kkMB+9TBRdrL3vNdGghY0s3w_y1x-ahuVMfVx47P4_5gnVA@mail.gmail.com>
Subject: Re: Informal URN Namespace NID Registration for Dolby Labs
From: Ted Hardie <ted.ietf@gmail.com>
To: "Roh, David" <david.roh@dolby.com>
Content-Type: multipart/alternative; boundary=001a11c30cc82a3bf104f79150a8
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/GeLOwyhuOGCGitESx96ZM94_pqE
Cc: "urn-nid@apps.ietf.org" <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 <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 18:03:23 -0000

--001a11c30cc82a3bf104f79150a8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi David,

This has been posted to the URN-NID list; you can confirm this on the
public archives:
http://www.ietf.org/mail-archive/web/urn-nid/current/maillist.html.

regards,

Ted Hardie


On Mon, Apr 21, 2014 at 10:16 AM, Roh, David <david.roh@dolby.com> wrote:

> Dear Sir or Madam:
>
> I am following up on my email below.  Could you let me know whether this
> email was received and processed by the appropriate parties at IETF?
> Please let me know at your earliest convenience.  Thank you.
>
> Best,
> David
>
> David Roh
> Business DevelopmentDolby Laboratories, Inc.
> 100 Potrero Ave.San Francisco, CA 94103
> T: 415-558-0312 <tel:415-558-0312>  C: 415-314-9030 <tel:415-314-9030>
> www.dolby.com <http://www.dolby.com/> | david.roh@dolby.com
>
> =E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=
=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9=E2=80=B9
>
> On 3/28/14, 11:15 AM, "urn-nid@ietfa.amsl.com" <urn-nid@ietfa.amsl.com>
> wrote:
>
> >
> >Confirmation of list posting -- confirmation ID: UzW8JQUZirvh
> >
> >The ietf.org mailing-list server has received a list posting from
> >david.roh@dolby.com to urn-nid@ietfa.amsl.com with the subject
> >'Informal URN Namespace NID Registration for Dolby Laboratories,
> > Inc. '
> >
> >As the sender address isn't subscribed to the list, and has not been
> >confirmed earlier, we have to request a confirmation of the address.
> >To confirm the address, send a message to urn-nid@ietfa.amsl.com,
> >with the same subject line as this message.
> >
> >(Simply sending a 'reply' to this message should work from most email
> >interfaces, since that usually leaves the subject line in the right
> >form.  The reply's additional "Re:" is ok.)
> >
> >If you do not wish your posting to the list to go through, simply
> >disregard this message.  Questions to postmaster@ietf.org.
>
> =E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=
=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9-
>
> From: Roh, David
> Sent: Freitag, 28. M=C3=A4rz 2014 19:15
> To: urn-nid@apps.ietf.org
> Cc: Krauss, Kurt; Ward, Mike
> Subject: Informal URN Namespace NID Registration for Dolby Laboratories,
> Inc.
>
>
>
> Dear Sir or Madam:
>
>
>
> The intent of this email is to submit an Informal URN Namespace NID
> Registration request for Dolby Laboratories, Inc.  To this effect, we hav=
e
> filled out the registration template per the guideline referenced in RFC
> 3406.  Please see below the registration information and it is attached a=
s
> a pdf file as well for your review.
>
>
>
> Please let me know if you have any questions or comments before we can
> proceed forward with respect to IANA.  Thank you.
>
>
>
> Regards,
>
> David
>
>
>
> David Roh
> Business Development
> Dolby Laboratories, Inc.
> 100 Potrero Ave.
> San Francisco, CA 94103
> T: 415-558-0312 <tel:415-558-0312>  C: 415-314-9030 <tel:415-314-9030>
> www.dolby.com <http://www.dolby.com/> | david.roh@dolby.com
>
>
>
> Informal URN Namespace NID Registration
>
>
> Namespace ID:
>
>       To be assigned by IANA
>
>
> Registration Information:
>
>       Registration Version Number: 1
>
>       Date: <when submitted to IANA>
>
> Declared registrant of the namespace:
>
>
>       Name:  Dolby Laboratories, Inc.
>       Address:  100 Potrero Ave.
>       San Francisco, CA 94103
>
>       Contact:  David Roh
>       Phone: +1 415 314 9030
>       E-mail: david.roh@dolby.com
>
>
> Declaration of structure:
>
>       The identifier structure is as follows:
>
> urn:urn-<assigned number>:<namespace-specific-identifier>:<assigned
> US-ASCII string>
>
>       where <assigned-number> is the number assigned to this urn scheme
>
>       where <namespace-specific-identifier> is a US-ASCII string that
> conforms to URN Syntax requirements as in RFC2141 and is a name to be
> assigned by the registrant
>
>      where  <assigned US-ASCII string> is a US-ASCII string that conforms
> to URN Syntax requirements as described in RFC2141.
>
>
> Examples of possible URNs in this namespace include:
>
>         urn:urn-n:dash:manifestdescriptor:2014
>         urn:urn-n:metadataclass:parameter:2014:test045
>         urn:urn-n:specification:table:2014
>         urn:urn-n:profile-example:parameter:level-2:20140101
>         urn:urn-n:dash:audio_channel_configuration:2014
>
>
>     (In these examples, =C2=B3urn-n=C2=B2 is a placeholder for the Namesp=
ace ID to
> be assigned by IANA.)
>
>
> Relevant ancillary documentation:
>
>       None.
>
>
> Identifier uniqueness considerations:
>
>     Identifiers are assigned by Dolby Laboratories, Inc.  In the process
> of identifier assignment, the registration authority confirms assignment
> against the record of previously assigned names.
>
>
> Identifier persistence considerations:
>
>     The assignment process guarantees that names are not reassigned and
> that the binding between the name and its resource is permanent,
> regardless of any organizational changes.
>
>
> Process of identifier assignment:
>
>     Names are assigned by Dolby Laboratories, Inc.
>
>
> Process for identifier resolution:
>
>     The namespace is not listed with an RDS; this is not relevant
>
>
> Rules for Lexical Equivalence:
>
>    The leading =C2=B3urn:" token and the Namespace Identifier, which will=
 be a
> number assigned by IANA, are case-insensitive, as defined by RFC2141.  Th=
e
> other parts of the structure <namespace-specific-identifier> and <assigne=
d
> US-ASCII string> are case-sensitive.
>
>
> Conformance with URN Syntax:
>
>    No special considerations.
>
>
> Validation mechanism:
>
>    None specified.
>
>
> Scope:
>
>    Global.
>
>
>
>

--001a11c30cc82a3bf104f79150a8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif">Hi David,<br><br>This has been posted to the URN-NID list; you can c=
onfirm this on the public archives: <a href=3D"http://www.ietf.org/mail-arc=
hive/web/urn-nid/current/maillist.html">http://www.ietf.org/mail-archive/we=
b/urn-nid/current/maillist.html</a>.<br>
<br></div><div class=3D"gmail_default" style=3D"font-family:georgia,serif">=
regards,<br><br>Ted Hardie<br></div></div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">On Mon, Apr 21, 2014 at 10:16 AM, Roh, David <=
span dir=3D"ltr">&lt;<a href=3D"mailto:david.roh@dolby.com" target=3D"_blan=
k">david.roh@dolby.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear Sir or Madam:<br>
<br>
I am following up on my email below. =C2=A0Could you let me know whether th=
is<br>
email was received and processed by the appropriate parties at IETF?<br>
Please let me know at your earliest convenience. =C2=A0Thank you.<br>
<br>
Best,<br>
David<br>
<br>
David Roh<br>
Business DevelopmentDolby Laboratories, Inc.<br>
100 Potrero Ave.San Francisco, CA 94103<br>
T: <a href=3D"tel:415-558-0312" value=3D"+14155580312">415-558-0312</a> &lt=
;tel:<a href=3D"tel:415-558-0312" value=3D"+14155580312">415-558-0312</a>&g=
t; =C2=A0C: <a href=3D"tel:415-314-9030" value=3D"+14153149030">415-314-903=
0</a> &lt;tel:<a href=3D"tel:415-314-9030" value=3D"+14153149030">415-314-9=
030</a>&gt;<br>

<a href=3D"http://www.dolby.com" target=3D"_blank">www.dolby.com</a> &lt;<a=
 href=3D"http://www.dolby.com/" target=3D"_blank">http://www.dolby.com/</a>=
&gt; | <a href=3D"mailto:david.roh@dolby.com">david.roh@dolby.com</a><br>
<br>
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=
=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9=E2=80=B9<br>
<br>
On 3/28/14, 11:15 AM, &quot;<a href=3D"mailto:urn-nid@ietfa.amsl.com">urn-n=
id@ietfa.amsl.com</a>&quot; &lt;<a href=3D"mailto:urn-nid@ietfa.amsl.com">u=
rn-nid@ietfa.amsl.com</a>&gt;<br>
wrote:<br>
<br>
&gt;<br>
&gt;Confirmation of list posting -- confirmation ID: UzW8JQUZirvh<br>
&gt;<br>
&gt;The <a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a> mailing-=
list server has received a list posting from<br>
&gt;<a href=3D"mailto:david.roh@dolby.com">david.roh@dolby.com</a> to <a hr=
ef=3D"mailto:urn-nid@ietfa.amsl.com">urn-nid@ietfa.amsl.com</a> with the su=
bject<br>
&gt;&#39;Informal URN Namespace NID Registration for Dolby Laboratories,<br=
>
&gt; Inc. &#39;<br>
&gt;<br>
&gt;As the sender address isn&#39;t subscribed to the list, and has not bee=
n<br>
&gt;confirmed earlier, we have to request a confirmation of the address.<br=
>
&gt;To confirm the address, send a message to <a href=3D"mailto:urn-nid@iet=
fa.amsl.com">urn-nid@ietfa.amsl.com</a>,<br>
&gt;with the same subject line as this message.<br>
&gt;<br>
&gt;(Simply sending a &#39;reply&#39; to this message should work from most=
 email<br>
&gt;interfaces, since that usually leaves the subject line in the right<br>
&gt;form. =C2=A0The reply&#39;s additional &quot;Re:&quot; is ok.)<br>
&gt;<br>
&gt;If you do not wish your posting to the list to go through, simply<br>
&gt;disregard this message. =C2=A0Questions to <a href=3D"mailto:postmaster=
@ietf.org">postmaster@ietf.org</a>.<br>
<br>
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=
=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=
=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=80=B9=E2=
=80=B9-<br>
<br>
From: Roh, David<br>
Sent: Freitag, 28. M=C3=A4rz 2014 19:15<br>
To: <a href=3D"mailto:urn-nid@apps.ietf.org">urn-nid@apps.ietf.org</a><br>
Cc: Krauss, Kurt; Ward, Mike<br>
Subject: Informal URN Namespace NID Registration for Dolby Laboratories,<br=
>
Inc.<br>
<br>
<br>
<br>
Dear Sir or Madam:<br>
<br>
<br>
<br>
The intent of this email is to submit an Informal URN Namespace NID<br>
Registration request for Dolby Laboratories, Inc. =C2=A0To this effect, we =
have<br>
filled out the registration template per the guideline referenced in RFC<br=
>
3406. =C2=A0Please see below the registration information and it is attache=
d as<br>
a pdf file as well for your review.<br>
<br>
<br>
<br>
Please let me know if you have any questions or comments before we can<br>
proceed forward with respect to IANA. =C2=A0Thank you.<br>
<br>
<br>
<br>
Regards,<br>
<br>
David<br>
<br>
<br>
<br>
David Roh<br>
Business Development<br>
Dolby Laboratories, Inc.<br>
100 Potrero Ave.<br>
San Francisco, CA 94103<br>
T: <a href=3D"tel:415-558-0312" value=3D"+14155580312">415-558-0312</a> &lt=
;tel:<a href=3D"tel:415-558-0312" value=3D"+14155580312">415-558-0312</a>&g=
t; =C2=A0C: <a href=3D"tel:415-314-9030" value=3D"+14153149030">415-314-903=
0</a> &lt;tel:<a href=3D"tel:415-314-9030" value=3D"+14153149030">415-314-9=
030</a>&gt;<br>

<a href=3D"http://www.dolby.com" target=3D"_blank">www.dolby.com</a> &lt;<a=
 href=3D"http://www.dolby.com/" target=3D"_blank">http://www.dolby.com/</a>=
&gt; | <a href=3D"mailto:david.roh@dolby.com">david.roh@dolby.com</a><br>
<br>
<br>
<br>
Informal URN Namespace NID Registration<br>
<br>
<br>
Namespace ID:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 To be assigned by IANA<br>
<br>
<br>
Registration Information:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Registration Version Number: 1<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Date: &lt;when submitted to IANA&gt;<br>
<br>
Declared registrant of the namespace:<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Name: =C2=A0Dolby Laboratories, Inc.<br>
=C2=A0 =C2=A0 =C2=A0 Address: =C2=A0100 Potrero Ave.<br>
=C2=A0 =C2=A0 =C2=A0 San Francisco, CA 94103<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Contact: =C2=A0David Roh<br>
=C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:%2B1%20415%20314%209030" value=
=3D"+14153149030">+1 415 314 9030</a><br>
=C2=A0 =C2=A0 =C2=A0 E-mail: <a href=3D"mailto:david.roh@dolby.com">david.r=
oh@dolby.com</a><br>
<br>
<br>
Declaration of structure:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 The identifier structure is as follows:<br>
<br>
urn:urn-&lt;assigned number&gt;:&lt;namespace-specific-identifier&gt;:&lt;a=
ssigned<br>
US-ASCII string&gt;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 where &lt;assigned-number&gt; is the number assigned t=
o this urn scheme<br>
<br>
=C2=A0 =C2=A0 =C2=A0 where &lt;namespace-specific-identifier&gt; is a US-AS=
CII string that<br>
conforms to URN Syntax requirements as in RFC2141 and is a name to be<br>
assigned by the registrant<br>
<br>
=C2=A0 =C2=A0 =C2=A0where =C2=A0&lt;assigned US-ASCII string&gt; is a US-AS=
CII string that conforms<br>
to URN Syntax requirements as described in RFC2141.<br>
<br>
<br>
Examples of possible URNs in this namespace include:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 urn:urn-n:dash:manifestdescriptor:2014<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 urn:urn-n:metadataclass:parameter:2014:test045<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 urn:urn-n:specification:table:2014<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 urn:urn-n:profile-example:parameter:level-2:201=
40101<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 urn:urn-n:dash:audio_channel_configuration:2014=
<br>
<br>
<br>
=C2=A0 =C2=A0 (In these examples, =C2=B3urn-n=C2=B2 is a placeholder for th=
e Namespace ID to<br>
be assigned by IANA.)<br>
<br>
<br>
Relevant ancillary documentation:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 None.<br>
<br>
<br>
Identifier uniqueness considerations:<br>
<br>
=C2=A0 =C2=A0 Identifiers are assigned by Dolby Laboratories, Inc. =C2=A0In=
 the process<br>
of identifier assignment, the registration authority confirms assignment<br=
>
against the record of previously assigned names.<br>
<br>
<br>
Identifier persistence considerations:<br>
<br>
=C2=A0 =C2=A0 The assignment process guarantees that names are not reassign=
ed and<br>
that the binding between the name and its resource is permanent,<br>
regardless of any organizational changes.<br>
<br>
<br>
Process of identifier assignment:<br>
<br>
=C2=A0 =C2=A0 Names are assigned by Dolby Laboratories, Inc.<br>
<br>
<br>
Process for identifier resolution:<br>
<br>
=C2=A0 =C2=A0 The namespace is not listed with an RDS; this is not relevant=
<br>
<br>
<br>
Rules for Lexical Equivalence:<br>
<br>
=C2=A0 =C2=A0The leading =C2=B3urn:&quot; token and the Namespace Identifie=
r, which will be a<br>
number assigned by IANA, are case-insensitive, as defined by RFC2141. =C2=
=A0The<br>
other parts of the structure &lt;namespace-specific-identifier&gt; and &lt;=
assigned<br>
US-ASCII string&gt; are case-sensitive.<br>
<br>
<br>
Conformance with URN Syntax:<br>
<br>
=C2=A0 =C2=A0No special considerations.<br>
<br>
<br>
Validation mechanism:<br>
<br>
=C2=A0 =C2=A0None specified.<br>
<br>
<br>
Scope:<br>
<br>
=C2=A0 =C2=A0Global.<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--001a11c30cc82a3bf104f79150a8--


From nobody Tue Apr 29 18:06:35 2014
Return-Path: <barryleiba@gmail.com>
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 27CDB1A099F for <urn-nid@ietfa.amsl.com>; Tue, 29 Apr 2014 18:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.978
X-Spam-Level: 
X-Spam-Status: No, score=-2.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, SPF_PASS=-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 yzQcnjovmPX7 for <urn-nid@ietfa.amsl.com>; Tue, 29 Apr 2014 18:06:25 -0700 (PDT)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 22DC11A0909 for <urn-nid@ietf.org>; Tue, 29 Apr 2014 18:06:25 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id x3so1139036qcv.40 for <urn-nid@ietf.org>; Tue, 29 Apr 2014 18:06:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=E5tsCpwV7QBuAZH0I9DggnvGHNEWOK9segKB4sHV7TE=; b=FwkoYNNKZH3s9sRMqHpp2kH/Y+H9lZx+HbeRev2jgYQ+n9yxX3icU7u0qSSDsAoMgj 0+8Q0DfeYArCd0Z/ajzwXIh0VBZI80HIGfXIQUeW5AIaS/FB8uczn8IRV53N+vf0mz5n CJtRnPcgveytSsGRqeQVP1r85akO0PwMtliUOFOyScWDaoJYGb3bgkX0WFNpzwdv3cRq 0ps1lQ7+ziglHvVwx+WtMuyRL/3NdRPOoObLtjJLj8LSjasscLrGsgdIPdb6IdVNxzWU +s+4z0vFCXN6d0hgQhhRYdjoGSB1g3U8lKo5NDTlnRguxqJpA+7qTgvOElVVEYhHvgP7 a2Bg==
MIME-Version: 1.0
X-Received: by 10.140.82.229 with SMTP id h92mr1155847qgd.51.1398819982676; Tue, 29 Apr 2014 18:06:22 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.136.134 with HTTP; Tue, 29 Apr 2014 18:06:22 -0700 (PDT)
Date: Tue, 29 Apr 2014 21:06:22 -0400
X-Google-Sender-Auth: T_akBdCwPBiaH9OfMYuWD0RzmS8
Message-ID: <CALaySJJk5YiCQZqt6WoWkqfAzi2A04HEAH=vG0pVAy8e45N5aQ@mail.gmail.com>
Subject: Publication request for draft-spinosa-urn-lex
From: Barry Leiba <barryleiba@computer.org>
To: draft-spinosa-urn-lex.all@tools.ietf.org, Ted Hardie <ted.ietf@gmail.com>,  =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/5Rg-oCWm--Sx21o2Iui67HWSqbQ
Cc: urn-nid@ietf.org, Andrew Newton <andy@hxr.us>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 01:06:29 -0000

This document was discussed on the urn-nid list between late March and
mid-April 2013.  At the time, Ted Hardie and Patrik F=C3=A4ltstr=C3=B6m
commented, and the authors addressed some of their comments.  In the
end, I think that not all of their comments were adequately addressed,
so I'm explicitly including Ted and Patrik in the "to" field here, to
bring their attention to the publication request and to my AD review.
Ted, Patrik, please check whether the current version

https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/

...addresses your issues to your satisfaction, and also let me know if
any of my comments below are totally off base.

---
I am very uncomfortable with this document, for a number of reasons:

1. The use of two-character jurisdiction identifiers was brought up by
Ted, and I'm not happy with the resolution, which seems to recommend
massive renaming of existing -- possibly quite old -- documents in
cases where the identifiers change.  This is simply not practical, and
goes against the concept that URNs be persistent.  Obviously, no one
can guarantee permanence, and persistence doesn't mean permanence.
Nevertheless, when we can anticipate issues (and particularly when we
have a demonstration than an issue has occurred, as is the case with
"ai"), we should deal with them in a way that doesn't upset the entire
apple cart.  Ted suggested three-letter jurisdictions, which seems a
reasonable approach.  There might be others.  Massive renaming of
perhaps many thousands of years-old documents isn't a reasonable
approach.

2. The whole "national characters" discussion in 3.4 seems odd.  It
was mentioned in the reviews, and corrections have been made.  I can
live with what's there now, but it still seems wrong to specify things
this way -- see item 3 for more.

3. Section 3.5 is grossly language-dependent, and was so obviously
written by people whose language supports what's demanded there.  As
it happens, turning "Ministry of Finance" into "ministry.finance"
works fine in Italian, as well as in Spanish, French, and English.  We
have words that mean "the" and "of", and such, which we can eliminate.
 Languages such as Russian do not; the noun forms themselves change
with the case, to give the meaning of the word "of" in "of finance" in
the noun itself.  "Ministry of Finance" in Russian is "=D0=BC=D0=B8=D0=BD=
=D0=B8=D1=81=D1=82=D0=B5=D1=80=D1=81=D1=82=D0=B2=D0=BE
=D1=84=D0=B8=D0=BD=D0=B0=D0=BD=D1=81=D0=BE=D0=B2" (Ministerstvo Finansov), =
but the nominative word for
"Finance" would be "=D1=84=D0=B8=D0=BD=D0=B0=D0=BD=D1=81=D1=8B" (Finansy). =
 Should the Section 3.5
process have it normalized to "=D0=BC=D0=B8=D0=BD=D0=B8=D1=81=D1=82=D0=B5=
=D1=80=D1=81=D1=82=D0=B2=D0=BE.=D1=84=D0=B8=D0=BD=D0=B0=D0=BD=D1=81=D1=8B",=
 to eliminate the
"of" that's implicit in the case of "=D1=84=D0=B8=D0=BD=D0=B0=D0=BD=D1=81=
=D0=BE=D0=B2"?  Does it matter?  (And
I don't even want to try to think about how this gets done in Chinese
languages.)

All this stuff in Sections 3.4 and 3.5 (and the later sections as
well) would be fine if it were in a non-normative example of how one
jurisdiction has chosen to create the names.  But apart from the
protocol requirements that have to do with required encoding of
non-US-ASCII characters, having this stuff be normative just strikes
me as wrong.  And pointless: does it really matter *how* the names are
assigned?  It should simply be up to the jurisdiction to create the
names, and if my jurisdiction chooses to name its documents as
"urn:lex:barryland:000000000001", then
"urn:lex:barryland:000000000002", and so on... or perhaps I want to
use SHA-1 hashes, as in RFC 6920.  Is that really a problem?

If you really are trying to set up a system wherein the URN can be
computed correctly from the document's title and other metadata, I
submit that such an effort may work for some situations, but is doomed
to fail in general.

4. You appear to be requiring that "urn:lex:" names work as locators
in HTML hrefs.  From Section 1.5:

   LEX names will be used on a large scale in references as a HREF
   attribute value of the hypertext link to the referred document.

...along with the whole "lex.urn.arpa" setup described in Section 6,
and the registration of the NAPTR records.

This is unprecedented, and, again, strikes me as wrong.  URNs can be
mapped into corresponding URLs, and being able to do so is what makes
them useful, but it seems that such mappings will be very much
jurisdiction-dependent, and it seems *very* unlikely that

   <a href=3D"urn:lex:barryland:000000000001">

...could be dereferenced as it stands.  That would require that every
browser (and every other application that processes these things) know
how to dereference every jurisdiction's LEX names -- and you're
depending upon the entire world building their resolution around your
structure and the registry you aim to set up.  Unless I'm seriously
misunderstanding something, this just seems like it won't work.  In
any case, what you're describing in Section 6 is not a URN namespace,
but a URI locator scheme.

---
I have a couple of other comments, at a much lower severity than the others=
:

- What's with the reference to W3C in the abstract?

- Section 3.9 specifies what to do with ordinal numbers.  Why are
those called out specifically, while cardinal numbers aren't?  Why
should I handle "law relating to a second home" one way (ordinal
number), and "law relating to two homes" (cardinal number) in a
different way?  But, again, this is related to my comment above about
why any of this is normative, and that comment applies to all sections
from 3.4 to 3.9.

There seems to be a lot of stuff in Section 4's subsections that also
specifies how these names should behave in practice, but is doing it
with normative requirements on the contruction of the name itself.  As
with the things in Section 3, these seem nice as explanations of
desirable (even required) characteristics, but wrong as normative
mechanisms with respect to the name structure.

Barry, Applications AD

