
From pal@sandflow.com  Tue Feb  4 22:32:59 2014
Return-Path: <pal@sandflow.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 64B531A0055 for <urn-nid@ietfa.amsl.com>; Tue,  4 Feb 2014 22:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 lEvteSRXCWuv for <urn-nid@ietfa.amsl.com>; Tue,  4 Feb 2014 22:32:57 -0800 (PST)
Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com [209.85.216.174]) by ietfa.amsl.com (Postfix) with ESMTP id B70CA1A0054 for <urn-nid@apps.ietf.org>; Tue,  4 Feb 2014 22:32:57 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id x13so15198892qcv.5 for <urn-nid@apps.ietf.org>; Tue, 04 Feb 2014 22:32:57 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=ALdyNkwdFn5szWtOKw2g1Pdue9hGyLlsCipagiqGruI=; b=AlyjWyHohvrGrIUei4hl3yR13G2+Z/D97XUVxnntDIAkLieWE2KTmJ79JCrdTyH7UB Uucj4XzqeyCzTTEP1I18RVu72vPuoyk8u2LeD8PQdd1O21bXoDYTUlyZAgIhZL71Uc2C NRS1E7QYWKsg+VW5VMXfeyvMvH5RCLM03/v2CLV0U+7c+0FimtQjVTC6cMdcsEJXBsXN 0LGFeA9pjU2F7d0uibKZl8USSowbCECtq4Saob2bZozkOE7gA40cyS7epPXd+GW0v0DM 1mow7LKyd2hOq4mLzorrgRRW2pGn3wJUBulHn29QQ/Av60An3v7Es23aj8e7F6bi/hog GZMA==
X-Gm-Message-State: ALoCoQnWl1f2M5aCeewaTcKaoO3y9piR/56QUZZz89lRSXGjOPjf6FJUoSYXMTayjBWz0bvSJptZ
X-Received: by 10.140.49.109 with SMTP id p100mr68969165qga.52.1391581976823;  Tue, 04 Feb 2014 22:32:56 -0800 (PST)
Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177]) by mx.google.com with ESMTPSA id g10sm74277761qaf.9.2014.02.04.22.32.56 for <urn-nid@apps.ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 22:32:56 -0800 (PST)
Received: by mail-qc0-f177.google.com with SMTP id i8so15224013qcq.8 for <urn-nid@apps.ietf.org>; Tue, 04 Feb 2014 22:32:56 -0800 (PST)
X-Received: by 10.224.79.19 with SMTP id n19mr26957667qak.99.1391581976083; Tue, 04 Feb 2014 22:32:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.72.65 with HTTP; Tue, 4 Feb 2014 22:32:36 -0800 (PST)
From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Tue, 4 Feb 2014 22:32:36 -0800
Message-ID: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com>
Subject: Application for a formal URN NID ("EIDR")
To: urn-nid@apps.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 05 Feb 2014 08:16:03 -0800
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, 05 Feb 2014 06:34:01 -0000

Good morning/evening,

Per IETF RFC 3406, please find at the link below an application for a
formal URN NID ("EIDR").

http://www.ietf.org/id/draft-pal-eidr-urn-00.txt

Very much Looking forward to your comments and feedback. Let me know
if you need additional information.

Best,

-- Pierre [on behalf of MovieLabs (http://movielabs.com)]

From ted.ietf@gmail.com  Wed Feb  5 11:14:20 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 B3A3B1A00FA for <urn-nid@ietfa.amsl.com>; Wed,  5 Feb 2014 11:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=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 IE5wnFENT_zb for <urn-nid@ietfa.amsl.com>; Wed,  5 Feb 2014 11:14:18 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 344CE1A00EB for <urn-nid@apps.ietf.org>; Wed,  5 Feb 2014 11:14:18 -0800 (PST)
Received: by mail-ig0-f172.google.com with SMTP id k19so13922787igc.5 for <urn-nid@apps.ietf.org>; Wed, 05 Feb 2014 11:14:16 -0800 (PST)
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=+yU+sVRTKnGIlQLmO43xC5tbM9pQvA8Seru48WeyCeE=; b=iVuMWj77X4CDU0Xym9SPJd8NHYZlllmRjVsiDiUkexso6Tg6R+Vu+Dw0yZXVUBwKBH kxhLSI+zbRuage6uPBXpBs8lZMz+VQynuGAfRu8jEXJcTuJlU7hoJ2VSmQdfh6H+sKYp oKLa6+XuaVxTEqmVxXc4bPnv0HI1AxXKHz4RtFAuP6fKgXwMRptq7CjkGlyo0AToS4L6 jAb1VoB+2SOyz0l9+zK91u7UgNr17JwaWI22Lb6t43aO8xDuIMraeL78XaCL7qbnxuO2 keC8Nupm+/ATrEfjmuYReuifrigBX2Ezhy7ulesTEzVgEZomoOHp4JLbWBwnRJ3Stt6+ Z8Ow==
MIME-Version: 1.0
X-Received: by 10.42.228.65 with SMTP id jd1mr2491733icb.62.1391627656241; Wed, 05 Feb 2014 11:14:16 -0800 (PST)
Received: by 10.43.164.201 with HTTP; Wed, 5 Feb 2014 11:14:16 -0800 (PST)
In-Reply-To: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com>
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com>
Date: Wed, 5 Feb 2014 11:14:16 -0800
Message-ID: <CA+9kkMD-fYNwxiK9iwC1itiBgmNtxmhMHKoNX=xY7eWVLVEOTg@mail.gmail.com>
Subject: Re: Application for a formal URN NID ("EIDR")
From: Ted Hardie <ted.ietf@gmail.com>
To: Pierre-Anthony Lemieux <pal@sandflow.com>
Content-Type: multipart/alternative; boundary=001a1132e4cc1c274a04f1ad9067
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: Wed, 05 Feb 2014 19:14:20 -0000

--001a1132e4cc1c274a04f1ad9067
Content-Type: text/plain; charset=ISO-8859-1

Thanks for sending your draft for review.  A few quick points:

The draft currently says:

EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX

This would seem to imply that any DOI prefix may be
encountered and that this NID could be used with any
registered DOI.  IF that were the intent, I would

suggest registering the namespace "DOI" instead.  I
understand that the DOI folks have consciously chosen not
to do that(cf: http://www.doi.org/factsheets/DOIIdentifierSpecs.html),

though, so I suspect your intent is to limit this to a subset
of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
If not, how will the appropriate subset be identified?

This comes up again here:

When DOI-PREFIX is equal to "10.5240", the syntax of DOI-SUFFIX is
further constrained according to [SMPTERP2079] as follows:

           DOI-SUFFIX   = EIDR-SUFFIX
           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK
           DIGIT        = %x30-39
           HEXDIG       = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
           ALPHA        = %x41-5A / %x61-7A
           CHECK        = DIGIT / ALPHA

I don't think this says quite what you intend.  I think what you

intend is to say is that the overall syntax is roughly either:

urn:eidr:10.5240:EIDR-SUFFIX

or

urn:eidr:DOI-PREFIX-which-is-not-10.5240:DOI-SUFFIX

If the use of the URN is only for 10.5240, then you can just
drop the second syntax.  If it is for a set of DOI prefixes,
none of which but 10.5240 is intended to have this restriction,

then I believe you want to say, roughly:

EIDR-NSS = EIDR-PREFIX ":" EIDR-SUFFIX


where EIDR-SUFFIX has a choice pattern:

EIDR-SUFFIX: SMPTERP2079-SUFFIX | DOI-SUFFIX

And the list of DOI prefixes suitable for EIDR-PREFIX is
set you register as such. The syntax of the prefix can still

match the general DOI prefix.

Later, the document says:

Rules for Lexical Equivalence:

      Two EIDR-NSS are equivalent if and only if they are equal.  EIDR-
      NSS are case-insensitive.

"equal" here doesn't have a precise meaning.  I'd suggest that

you say something like "are lexically equivalent based on
a case insensitive string match"

regards,

Ted Hardie



On Tue, Feb 4, 2014 at 10:32 PM, Pierre-Anthony Lemieux <pal@sandflow.com>wrote:

> Good morning/evening,
>
> Per IETF RFC 3406, please find at the link below an application for a
> formal URN NID ("EIDR").
>
> http://www.ietf.org/id/draft-pal-eidr-urn-00.txt
>
> Very much Looking forward to your comments and feedback. Let me know
> if you need additional information.
>
> Best,
>
> -- Pierre [on behalf of MovieLabs (http://movielabs.com)]
>

--001a1132e4cc1c274a04f1ad9067
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif">Thanks for sending your draft for review.=A0 A few quick points:<br>=
<br></div><div class=3D"gmail_default" style=3D"font-family:georgia,serif">=
The draft currently says:<br>
<br><pre>EIDR-NSS =3D DOI-PREFIX &quot;:&quot; DOI-SUFFIX<br><br></pre><pre=
>This would seem to imply that any DOI prefix may be <br>encountered and th=
at this NID could be used with any <br>registered DOI.  IF that were the in=
tent, I would<br>
</pre><pre>suggest registering the namespace &quot;DOI&quot; instead.  I<br=
>understand that the DOI folks have consciously chosen not<br>to do that(cf=
: <a href=3D"http://www.doi.org/factsheets/DOIIdentifierSpecs.html">http://=
www.doi.org/factsheets/DOIIdentifierSpecs.html</a>),<br>
</pre><pre>though, so I suspect your intent is to limit this to a subset<br=
>of DOIs.  Is that correct?  Is it essentially limited to 10.5240?<br>If no=
t, how will the appropriate subset be identified?  <br><br></pre><pre>This =
comes up again here:<br>
<br>When DOI-PREFIX is equal to &quot;10.5240&quot;, the syntax of DOI-SUFF=
IX is<br>further constrained according to [SMPTERP2079] as follows:

           DOI-SUFFIX   =3D EIDR-SUFFIX
           EIDR-SUFFIX  =3D 5*5(4*4HEXDIG &quot;-&quot;) CHECK
           DIGIT        =3D %x30-39
           HEXDIG       =3D DIGIT / &quot;A&quot; / &quot;B&quot; / &quot;C=
&quot; / &quot;D&quot; / &quot;E&quot; / &quot;F&quot;
           ALPHA        =3D %x41-5A / %x61-7A
           CHECK        =3D DIGIT / ALPHA<br><br></pre><pre>I don&#39;t thi=
nk this says quite what you intend.  I think what you<br></pre><pre>intend =
is to say is that the overall syntax is roughly either:<br><br></pre><pre>
urn:eidr:10.5240:EIDR-SUFFIX<br></pre><pre>or<br><br></pre><pre>urn:eidr:DO=
I-PREFIX-which-is-not-10.5240:DOI-SUFFIX<br><br></pre><pre>If the use of th=
e URN is only for 10.5240, then you can just<br>drop the second syntax.  If=
 it is for a set of DOI prefixes,<br>
none of which but 10.5240 is intended to have this restriction,<br></pre><p=
re>then I believe you want to say, roughly:<br><br>EIDR-NSS =3D EIDR-PREFIX=
 &quot;:&quot; EIDR-SUFFIX<br><br><br></pre><pre>where EIDR-SUFFIX has a ch=
oice pattern:<br>
</pre><pre>EIDR-SUFFIX: SMPTERP2079-SUFFIX | DOI-SUFFIX<br></pre><pre>And t=
he list of DOI prefixes suitable for EIDR-PREFIX is <br>set you register as=
 such. The syntax of the prefix can still<br></pre><pre>match the general D=
OI prefix.<br>
<br></pre><pre>Later, the document says:<br><br>Rules for Lexical Equivalen=
ce:

      Two EIDR-NSS are equivalent if and only if they are equal.  EIDR-
      NSS are case-insensitive.<br><br></pre><pre>&quot;equal&quot; here do=
esn&#39;t have a precise meaning.  I&#39;d suggest that<br></pre><pre>you s=
ay something like &quot;are lexically equivalent based on<br>a case insensi=
tive string match&quot;<br>
<br></pre><pre>regards,<br><br>Ted Hardie<br></pre></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Feb 4, 2014 at =
10:32 PM, Pierre-Anthony Lemieux <span dir=3D"ltr">&lt;<a href=3D"mailto:pa=
l@sandflow.com" target=3D"_blank">pal@sandflow.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">Good morning/evening,<br>
<br>
Per IETF RFC 3406, please find at the link below an application for a<br>
formal URN NID (&quot;EIDR&quot;).<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-pal-eidr-urn-00.txt" target=3D"_bla=
nk">http://www.ietf.org/id/draft-pal-eidr-urn-00.txt</a><br>
<br>
Very much Looking forward to your comments and feedback. Let me know<br>
if you need additional information.<br>
<br>
Best,<br>
<br>
-- Pierre [on behalf of MovieLabs (<a href=3D"http://movielabs.com" target=
=3D"_blank">http://movielabs.com</a>)]<br>
</blockquote></div><br></div>

--001a1132e4cc1c274a04f1ad9067--

From worley@shell01.TheWorld.com  Thu Feb  6 11:21:30 2014
Return-Path: <worley@shell01.TheWorld.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 7A6981A044C for <urn-nid@ietfa.amsl.com>; Thu,  6 Feb 2014 11:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.254
X-Spam-Level: 
X-Spam-Status: No, score=-1.254 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 1W05UvZnWjde for <urn-nid@ietfa.amsl.com>; Thu,  6 Feb 2014 11:21:28 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id A54C01A0466 for <urn-nid@apps.ietf.org>; Thu,  6 Feb 2014 11:21:27 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s16JKIC7012526; Thu, 6 Feb 2014 14:20:21 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s16JG1dE4397647; Thu, 6 Feb 2014 14:16:01 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s16JG0J64392388; Thu, 6 Feb 2014 14:16:00 -0500 (EST)
Date: Thu, 6 Feb 2014 14:16:00 -0500 (EST)
Message-Id: <201402061916.s16JG0J64392388@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Pierre-Anthony Lemieux <pal@sandflow.com>
In-reply-to: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com> (pal@sandflow.com)
Subject: Re: Application for a formal URN NID ("EIDR")
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com>
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 <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: Thu, 06 Feb 2014 19:21:30 -0000

If there's a difference between EIDR and DOI, you ought to make that
clear.  The two terms are used throughout the document and I vaguely
assumed that they are the same.  Actually, the underlying problem is
that you write the document assuming that the reader is thoroughly
familiar with EIDR's, DOI's, and the like.  Start with enough tutorial
so that someone who has never heard of either before (me) will have a
clear understanding of what is going on.

> From: Ted Hardie <ted.ietf@gmail.com>
> 
> EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX
> 
> This would seem to imply that any DOI prefix may be
> encountered and that this NID could be used with any
> registered DOI.  IF that were the intent, I would
> suggest registering the namespace "DOI" instead.  I
> understand that the DOI folks have consciously chosen not
> to do that(cf: http://www.doi.org/factsheets/DOIIdentifierSpecs.html),
> though, so I suspect your intent is to limit this to a subset
> of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
> If not, how will the appropriate subset be identified?

If the NID is to provide an encoding for all DOI names, then it should
be named "doi".  But if the DOI people have decided that it is not a
good thing to provide a NID for all DOI names, then:

- the NID should be "eidr"

- the syntax should not give a DOI-PREFIX, because that will *always*
  be "10.5240", and there's no point including a long invariant string
  in the syntax

Fundamentally, you need to determine if the DOI people are
fundamentally against mapping DOI names into URNs, or whether they
just don't want to put in the work (and you are actually doing the job
for them).

Also, if you are thinking of providing a NID that can encompass all
DOIs, you have to worry about character sets.  According to Wikipedia,
"Most legal Unicode characters are allowed in these strings", whereas
the %-encoding system can only represent ASCII characters.

>       where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix,
>       respectively, translated into canonical NSS format according to
>       [RFC2141].  DOI Name syntax is specified in [ISO26234].

What you mean to say is something like:  A DOI name consists of a
prefix and a suffix, which are character strings [a fact the reader
didn't know before].  They are translated into the DOI-PREFIX and
DOI-SUFFIX by replacing all characters which are not XXX with
corresponding %-escapes.  (See RFC 2141 section 2.2.)

Exactly what the set XXX is needs to be specified with some care.
Section 2.2 specifies that all characters that may not appear in URNs
*at all* must be escaped.  But of course, ":" may appear in URNs and
by that specification need not be escaped.  OTOH, if ":" appears in a
prefix or suffix, you very well want it escaped.  I'm pretty sure that
you want XXX to be <pchar> as defined in RFC 3986 (the infamous
"Uniform Resource Identifier (URI): Generic Syntax").

Also, you are depending on the fact that EIDR suffixes consist of
ASCII characters, which can be represented by %-escapes (whereas DOI
suffixes can contain Unicode characters, which can't).

NIDs are case-insensitive (RFC 2141 section 5), but usually are
presented in lower case.

>           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK

You can just say

           EIDR-SUFFIX  = 5(4HEXDIG "-") CHECK

>    Identifier persistence considerations:
> 
>       As a DOI Name, the persistence of EIDR-NSS is guaranteed by the
>       ISO 26324 Registration Authority.  A DOI Name remains valid
>       indefinitely.

It would be clearer if you said something like

       The ISO 26324 Registration Authority assigns DOI Names to
       works(?).  A DOI Name remains valid indefinitely.  As a
       consequence, the URN derived from a DOI Name remains valid
       indefinitely.

Similar editing of the other items in this section would be helpful.

I can't quite put my finger on what seems to be the problem with the
writing.  I *think* the problem is that the text is written from the
point of view of someone who is thoroughly familiar with DOIs/EIDRs,
to the point where it never really has to be said what they are *for*
or how they work, whereas the correct way to write these sections is
from the point of view of someone who is familiar with URNs but has
never heard of a DOI before.  "We are talking about URNs that look
like this: ...  These URNs are used to specify DOIs, which are used in
XXX industry to designate YYYs.  DOIs are assigned to YYYs by ZZZ."

In the above paragraph, the sentence starts with "As a DOI Name...",
which is actually trying to leverage that the reader *already
understands* how DOI Names work.

>       As a DOI Name, the resolution of EIDR-NSS is handled by the ISO
>       26324 Registration Authority.
> 
>       The ISO 26324 Registration Authority operates a web service that
>       allows an EIDR-NSS to be resolved by issuing an HTTP GET request
>       to the following URI:
> 
>                "http://doi.org/" DOI-PREFIX "/" DOI-SUFFIX

As written, this doesn't specify anything, because you can apply that
process to any alleged EIDR.  In order to make this meaningful, you
have to specify what the format of the HTTP *response* is and the
significance of the elements of the response.  (Presumably there is an
ISO standard you can reference here.)

Dale

From pal@sandflow.com  Thu Feb  6 18:08:19 2014
Return-Path: <pal@sandflow.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 5A6B81A05A0 for <urn-nid@ietfa.amsl.com>; Thu,  6 Feb 2014 18:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 raQiCJtha9-F for <urn-nid@ietfa.amsl.com>; Thu,  6 Feb 2014 18:08:16 -0800 (PST)
Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) by ietfa.amsl.com (Postfix) with ESMTP id A87A71A059A for <urn-nid@apps.ietf.org>; Thu,  6 Feb 2014 18:08:16 -0800 (PST)
Received: by mail-qc0-f178.google.com with SMTP id m20so4761361qcx.37 for <urn-nid@apps.ietf.org>; Thu, 06 Feb 2014 18:08:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=DRwq0WG6nJZPHg+FpS0iYxH9Hqm3MopEdAiIsDGdvAM=; b=NunrUWOc+EaV8HtKr2dI0yP+PTw4UzjGSLtbhcI0rhBcvXoY6FJYYgVc58v67qHR58 OSBkZqYJ4uUP4qdmTgc2gRV19oLyTYLMUA3WP1LXmV9bGv12tIs5szx1DJzS02/EevPs kV1ib3gbT+I0BvHb9aYclKbF0/tjIAgCmVSSSPYbWgCdG9usYemaWBbM6vffMSERgohh pnN6GJxxePAJYKd7Vq99+Bvrp5APJTbinyseC9Tt+ZDG58QHuaH/LavLcc4Fu6BvDOS+ zNMvVZ79fKl01oL+3B7uY9GMR0mmHE08ds5xEQF2hWiTCDv6CdxyV1UUOKwh1Y8Nfjh4 Ljew==
X-Gm-Message-State: ALoCoQk9H6U0dtC+XLo73d636AExe8DBmBW4FGc6nW1VmCkYsbOs3JTcLAjp8VNa5UXcr5ztNp+F
X-Received: by 10.140.105.35 with SMTP id b32mr16607342qgf.36.1391738895287; Thu, 06 Feb 2014 18:08:15 -0800 (PST)
Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by mx.google.com with ESMTPSA id k107sm5844265qgk.5.2014.02.06.18.08.14 for <urn-nid@apps.ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Feb 2014 18:08:14 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id ii20so4257726qab.32 for <urn-nid@apps.ietf.org>; Thu, 06 Feb 2014 18:08:14 -0800 (PST)
X-Received: by 10.140.18.142 with SMTP id 14mr16335828qgf.105.1391738894421; Thu, 06 Feb 2014 18:08:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.72.65 with HTTP; Thu, 6 Feb 2014 18:07:54 -0800 (PST)
In-Reply-To: <201402061916.s16JG0J64392388@shell01.TheWorld.com>
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com> <201402061916.s16JG0J64392388@shell01.TheWorld.com>
From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Thu, 6 Feb 2014 18:07:54 -0800
Message-ID: <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
Subject: Re: Application for a formal URN NID ("EIDR")
To: "Dale R. Worley" <worley@ariadne.com>, ted.ietf@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
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: Fri, 07 Feb 2014 02:08:19 -0000

Hi Ted and Dale,

Thanks for the detailed comments, which I am in the process of
addressing. In the meantime, some additional background and
clarification on the request.

The requested EIDR NID is not intended to accommodate any and all DOI
Names, but specifically DOI Names allocated by EIDR organization, i.e.
DOI Names with a prefix assigned to EIDR organization. This means that
(a) EIDR organization essentially controls the syntax of the EIDR
Identifiers, e.g. add check codes and constrain it to the ASCII set,
and (b) the NID is specifically intended for audiovisual works. The
fact that EIDR Identifiers are valid DOI Names ensures persistence,
uniqueness and an open resolution infrastructure.

Currently, EIDR Identifiers use the 10.5240 prefix for audiovisual
works. The idea is to leave the door open for additional prefixes (and
corresponding suffixes) to be defined in the future (with EIDR NID
specification being updated accordingly). In all cases, these prefixes
and suffixes would be defined and controlled by EIDR organization.

So, if an implementation receives an EIDR-NSS with an unknown prefix,
it can still accept it, treating it as an opaque (case insensitive)
identifier (with the option of resolving it as generic DOI Name.) If
the prefix is known, additional processing can occur, e.g. error
detection in the case of the 10.5240 prefix.

Does this makes sense? I assume it is acceptable to reply cc'ing the
reflector. If not, I am happy to chat offline.

Best,

-- Pierre

On Thu, Feb 6, 2014 at 11:16 AM, Dale R. Worley <worley@ariadne.com> wrote:
> If there's a difference between EIDR and DOI, you ought to make that
> clear.  The two terms are used throughout the document and I vaguely
> assumed that they are the same.  Actually, the underlying problem is
> that you write the document assuming that the reader is thoroughly
> familiar with EIDR's, DOI's, and the like.  Start with enough tutorial
> so that someone who has never heard of either before (me) will have a
> clear understanding of what is going on.
>
>> From: Ted Hardie <ted.ietf@gmail.com>
>>
>> EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX
>>
>> This would seem to imply that any DOI prefix may be
>> encountered and that this NID could be used with any
>> registered DOI.  IF that were the intent, I would
>> suggest registering the namespace "DOI" instead.  I
>> understand that the DOI folks have consciously chosen not
>> to do that(cf: http://www.doi.org/factsheets/DOIIdentifierSpecs.html),
>> though, so I suspect your intent is to limit this to a subset
>> of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
>> If not, how will the appropriate subset be identified?
>
> If the NID is to provide an encoding for all DOI names, then it should
> be named "doi".  But if the DOI people have decided that it is not a
> good thing to provide a NID for all DOI names, then:
>
> - the NID should be "eidr"
>
> - the syntax should not give a DOI-PREFIX, because that will *always*
>   be "10.5240", and there's no point including a long invariant string
>   in the syntax
>
> Fundamentally, you need to determine if the DOI people are
> fundamentally against mapping DOI names into URNs, or whether they
> just don't want to put in the work (and you are actually doing the job
> for them).
>
> Also, if you are thinking of providing a NID that can encompass all
> DOIs, you have to worry about character sets.  According to Wikipedia,
> "Most legal Unicode characters are allowed in these strings", whereas
> the %-encoding system can only represent ASCII characters.
>
>>       where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix,
>>       respectively, translated into canonical NSS format according to
>>       [RFC2141].  DOI Name syntax is specified in [ISO26234].
>
> What you mean to say is something like:  A DOI name consists of a
> prefix and a suffix, which are character strings [a fact the reader
> didn't know before].  They are translated into the DOI-PREFIX and
> DOI-SUFFIX by replacing all characters which are not XXX with
> corresponding %-escapes.  (See RFC 2141 section 2.2.)
>
> Exactly what the set XXX is needs to be specified with some care.
> Section 2.2 specifies that all characters that may not appear in URNs
> *at all* must be escaped.  But of course, ":" may appear in URNs and
> by that specification need not be escaped.  OTOH, if ":" appears in a
> prefix or suffix, you very well want it escaped.  I'm pretty sure that
> you want XXX to be <pchar> as defined in RFC 3986 (the infamous
> "Uniform Resource Identifier (URI): Generic Syntax").
>
> Also, you are depending on the fact that EIDR suffixes consist of
> ASCII characters, which can be represented by %-escapes (whereas DOI
> suffixes can contain Unicode characters, which can't).
>
> NIDs are case-insensitive (RFC 2141 section 5), but usually are
> presented in lower case.
>
>>           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK
>
> You can just say
>
>            EIDR-SUFFIX  = 5(4HEXDIG "-") CHECK
>
>>    Identifier persistence considerations:
>>
>>       As a DOI Name, the persistence of EIDR-NSS is guaranteed by the
>>       ISO 26324 Registration Authority.  A DOI Name remains valid
>>       indefinitely.
>
> It would be clearer if you said something like
>
>        The ISO 26324 Registration Authority assigns DOI Names to
>        works(?).  A DOI Name remains valid indefinitely.  As a
>        consequence, the URN derived from a DOI Name remains valid
>        indefinitely.
>
> Similar editing of the other items in this section would be helpful.
>
> I can't quite put my finger on what seems to be the problem with the
> writing.  I *think* the problem is that the text is written from the
> point of view of someone who is thoroughly familiar with DOIs/EIDRs,
> to the point where it never really has to be said what they are *for*
> or how they work, whereas the correct way to write these sections is
> from the point of view of someone who is familiar with URNs but has
> never heard of a DOI before.  "We are talking about URNs that look
> like this: ...  These URNs are used to specify DOIs, which are used in
> XXX industry to designate YYYs.  DOIs are assigned to YYYs by ZZZ."
>
> In the above paragraph, the sentence starts with "As a DOI Name...",
> which is actually trying to leverage that the reader *already
> understands* how DOI Names work.
>
>>       As a DOI Name, the resolution of EIDR-NSS is handled by the ISO
>>       26324 Registration Authority.
>>
>>       The ISO 26324 Registration Authority operates a web service that
>>       allows an EIDR-NSS to be resolved by issuing an HTTP GET request
>>       to the following URI:
>>
>>                "http://doi.org/" DOI-PREFIX "/" DOI-SUFFIX
>
> As written, this doesn't specify anything, because you can apply that
> process to any alleged EIDR.  In order to make this meaningful, you
> have to specify what the format of the HTTP *response* is and the
> significance of the elements of the response.  (Presumably there is an
> ISO standard you can reference here.)
>
> Dale

From worley@shell01.TheWorld.com  Fri Feb  7 08:45:12 2014
Return-Path: <worley@shell01.TheWorld.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 B308F1AC7ED for <urn-nid@ietfa.amsl.com>; Fri,  7 Feb 2014 08:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 ktmgYejbBacU for <urn-nid@ietfa.amsl.com>; Fri,  7 Feb 2014 08:45:11 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id C8BAC1A0143 for <urn-nid@apps.ietf.org>; Fri,  7 Feb 2014 08:45:07 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s17GigdN023952; Fri, 7 Feb 2014 11:44:44 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s17GieRS4399126; Fri, 7 Feb 2014 11:44:40 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s17GicOQ4457148; Fri, 7 Feb 2014 11:44:38 -0500 (EST)
Date: Fri, 7 Feb 2014 11:44:38 -0500 (EST)
Message-Id: <201402071644.s17GicOQ4457148@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Pierre-Anthony Lemieux <pal@sandflow.com>
In-reply-to: <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com> (pal@sandflow.com)
Subject: Re: Application for a formal URN NID ("EIDR")
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com> <201402061916.s16JG0J64392388@shell01.TheWorld.com> <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
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 <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: Fri, 07 Feb 2014 16:45:12 -0000

> From: Pierre-Anthony Lemieux <pal@sandflow.com>

> The requested EIDR NID is not intended to accommodate any and all DOI
> Names, but specifically DOI Names allocated by EIDR organization, i.e.
> DOI Names with a prefix assigned to EIDR organization. [...]
> Currently, EIDR Identifiers use the 10.5240 prefix for audiovisual
> works. The idea is to leave the door open for additional prefixes (and
> corresponding suffixes) to be defined in the future (with EIDR NID
> specification being updated accordingly). In all cases, these prefixes
> and suffixes would be defined and controlled by EIDR organization.

Interesting...  That is what the draft *says* now that I read it again
but it didn't come through the first time I read it.  I think it would
be easier to understand if you start with

           URN-EIDR = "URN:EIDR:" EIDR-NSS
           EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX

      where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix,
      respectively, translated into canonical NSS format according to
      [RFC2141].  DOI Name syntax is specified in [ISO26234].

      NOTE: The canonical string representation of an EIDR Identifier
      uses "/" instead of ":" as the delimiter between DOI-PREFIX and
      DOI-SUFFIX. ":" is used here since "/" is a reserved character.

Then say that the prefix must be one that is allocated to EIDR
organization, and that currently only '10.5240' is allocated, though
others might be allocated in the future.  Then continue,

      When DOI-PREFIX is equal to "10.5240", the syntax of DOI-SUFFIX is
      further constrained according to [SMPTERP2079] as follows:

Othewise the transition into "When DOI-PREFIX is equal to
"10.5240"..." is mysterious -- What is special about that value?  Why
is there a special syntax constraint on suffixes for that single
prefix?

You still need to worry about the character encoding issues regarding
possible additional prefixes, as the ISO standard doesn't restrict
possible future EIDR prefixes from including Unicode characters that
can't be represented with %-escapes.

Dale

From ted.ietf@gmail.com  Fri Feb  7 10:31:40 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 1AFB11ACCF2 for <urn-nid@ietfa.amsl.com>; Fri,  7 Feb 2014 10:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=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 rlRlhpyrskA9 for <urn-nid@ietfa.amsl.com>; Fri,  7 Feb 2014 10:31:35 -0800 (PST)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id B01821A03E1 for <urn-nid@apps.ietf.org>; Fri,  7 Feb 2014 10:31:35 -0800 (PST)
Received: by mail-ie0-f179.google.com with SMTP id ar20so1885915iec.38 for <urn-nid@apps.ietf.org>; Fri, 07 Feb 2014 10:31:35 -0800 (PST)
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=riVsvZWAIm2O7EUqiSWtjzom+8pKLKGK1pW22n2KCn4=; b=qdGEBzCKj8vK8rOFFp5wYgCL3nDtZ4AwdqoyjiRaAxJs+iLIhJspWx9cu3gDDaflw5 V1XWALFqL6RlI03LaMt82CS2gEXDJzL5HIjlfdKHiSBsI3k7lXyEh/ERRUWW7INN4L4a yhxAdAn7BbW3vSGabY6rcbprrTkjBMeEUzAUtgsQki3AseGmzenKDaLSqu8F1VMDUhYD E9jt5fyHxwOgzEGehrof3V3NPakp5qZL0jO/r97O+DGeOO4Se7fQ5QHB5bTD7KrSmU0M G+l3twz8lC8gPCki35E9rOXVO06RhGs/NNKYKyq+LusWeDNAd843zXuQdtxKcpXAm1Yf V3rg==
MIME-Version: 1.0
X-Received: by 10.42.228.65 with SMTP id jd1mr1769909icb.62.1391797895409; Fri, 07 Feb 2014 10:31:35 -0800 (PST)
Received: by 10.43.164.201 with HTTP; Fri, 7 Feb 2014 10:31:35 -0800 (PST)
In-Reply-To: <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com> <201402061916.s16JG0J64392388@shell01.TheWorld.com> <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
Date: Fri, 7 Feb 2014 10:31:35 -0800
Message-ID: <CA+9kkMAroDRk0DKvVMGoLgu2H7yw6zNYFuZxaHCAzRtUwpsOuQ@mail.gmail.com>
Subject: Re: Application for a formal URN NID ("EIDR")
From: Ted Hardie <ted.ietf@gmail.com>
To: Pierre-Anthony Lemieux <pal@sandflow.com>
Content-Type: multipart/alternative; boundary=001a1132e4cc27b4e404f1d533da
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: Fri, 07 Feb 2014 18:31:40 -0000

--001a1132e4cc27b4e404f1d533da
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 6, 2014 at 6:07 PM, Pierre-Anthony Lemieux <pal@sandflow.com>wrote:

> Hi Ted and Dale,
>
> Thanks for the detailed comments, which I am in the process of
> addressing. In the meantime, some additional background and
> clarification on the request.
>
> The requested EIDR NID is not intended to accommodate any and all DOI
> Names, but specifically DOI Names allocated by EIDR organization, i.e.
> DOI Names with a prefix assigned to EIDR organization. This means that
> (a) EIDR organization essentially controls the syntax of the EIDR
> Identifiers, e.g. add check codes and constrain it to the ASCII set,
> and (b) the NID is specifically intended for audiovisual works. The
> fact that EIDR Identifiers are valid DOI Names ensures persistence,
> uniqueness and an open resolution infrastructure.
>
> Currently, EIDR Identifiers use the 10.5240 prefix for audiovisual
> works. The idea is to leave the door open for additional prefixes (and
> corresponding suffixes) to be defined in the future (with EIDR NID
> specification being updated accordingly). In all cases, these prefixes
> and suffixes would be defined and controlled by EIDR organization.
>
> I think you might update the draft to discuss that these are intended to
be
a subset of DOIs, then, just to remove any confusion.

Would you anticipate that later EIDR suffixes would retain the syntax
of the current 10.5240-based identifiers?  If so, this would be relatively
simple.  If not, it may be simpler to register one namespace now, basedon
10.5240 and its syntax, and then register later NIDs for other prefix/suffix
combinations in future.

regards,

Ted Hardie





> So, if an implementation receives an EIDR-NSS with an unknown prefix,
> it can still accept it, treating it as an opaque (case insensitive)
> identifier (with the option of resolving it as generic DOI Name.) If
> the prefix is known, additional processing can occur, e.g. error
> detection in the case of the 10.5240 prefix.
>
> Does this makes sense? I assume it is acceptable to reply cc'ing the
> reflector. If not, I am happy to chat offline.
>
> Best,
>
> -- Pierre
>
> On Thu, Feb 6, 2014 at 11:16 AM, Dale R. Worley <worley@ariadne.com>
> wrote:
> > If there's a difference between EIDR and DOI, you ought to make that
> > clear.  The two terms are used throughout the document and I vaguely
> > assumed that they are the same.  Actually, the underlying problem is
> > that you write the document assuming that the reader is thoroughly
> > familiar with EIDR's, DOI's, and the like.  Start with enough tutorial
> > so that someone who has never heard of either before (me) will have a
> > clear understanding of what is going on.
> >
> >> From: Ted Hardie <ted.ietf@gmail.com>
> >>
> >> EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX
> >>
> >> This would seem to imply that any DOI prefix may be
> >> encountered and that this NID could be used with any
> >> registered DOI.  IF that were the intent, I would
> >> suggest registering the namespace "DOI" instead.  I
> >> understand that the DOI folks have consciously chosen not
> >> to do that(cf: http://www.doi.org/factsheets/DOIIdentifierSpecs.html),
> >> though, so I suspect your intent is to limit this to a subset
> >> of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
> >> If not, how will the appropriate subset be identified?
> >
> > If the NID is to provide an encoding for all DOI names, then it should
> > be named "doi".  But if the DOI people have decided that it is not a
> > good thing to provide a NID for all DOI names, then:
> >
> > - the NID should be "eidr"
> >
> > - the syntax should not give a DOI-PREFIX, because that will *always*
> >   be "10.5240", and there's no point including a long invariant string
> >   in the syntax
> >
> > Fundamentally, you need to determine if the DOI people are
> > fundamentally against mapping DOI names into URNs, or whether they
> > just don't want to put in the work (and you are actually doing the job
> > for them).
> >
> > Also, if you are thinking of providing a NID that can encompass all
> > DOIs, you have to worry about character sets.  According to Wikipedia,
> > "Most legal Unicode characters are allowed in these strings", whereas
> > the %-encoding system can only represent ASCII characters.
> >
> >>       where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix,
> >>       respectively, translated into canonical NSS format according to
> >>       [RFC2141].  DOI Name syntax is specified in [ISO26234].
> >
> > What you mean to say is something like:  A DOI name consists of a
> > prefix and a suffix, which are character strings [a fact the reader
> > didn't know before].  They are translated into the DOI-PREFIX and
> > DOI-SUFFIX by replacing all characters which are not XXX with
> > corresponding %-escapes.  (See RFC 2141 section 2.2.)
> >
> > Exactly what the set XXX is needs to be specified with some care.
> > Section 2.2 specifies that all characters that may not appear in URNs
> > *at all* must be escaped.  But of course, ":" may appear in URNs and
> > by that specification need not be escaped.  OTOH, if ":" appears in a
> > prefix or suffix, you very well want it escaped.  I'm pretty sure that
> > you want XXX to be <pchar> as defined in RFC 3986 (the infamous
> > "Uniform Resource Identifier (URI): Generic Syntax").
> >
> > Also, you are depending on the fact that EIDR suffixes consist of
> > ASCII characters, which can be represented by %-escapes (whereas DOI
> > suffixes can contain Unicode characters, which can't).
> >
> > NIDs are case-insensitive (RFC 2141 section 5), but usually are
> > presented in lower case.
> >
> >>           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK
> >
> > You can just say
> >
> >            EIDR-SUFFIX  = 5(4HEXDIG "-") CHECK
> >
> >>    Identifier persistence considerations:
> >>
> >>       As a DOI Name, the persistence of EIDR-NSS is guaranteed by the
> >>       ISO 26324 Registration Authority.  A DOI Name remains valid
> >>       indefinitely.
> >
> > It would be clearer if you said something like
> >
> >        The ISO 26324 Registration Authority assigns DOI Names to
> >        works(?).  A DOI Name remains valid indefinitely.  As a
> >        consequence, the URN derived from a DOI Name remains valid
> >        indefinitely.
> >
> > Similar editing of the other items in this section would be helpful.
> >
> > I can't quite put my finger on what seems to be the problem with the
> > writing.  I *think* the problem is that the text is written from the
> > point of view of someone who is thoroughly familiar with DOIs/EIDRs,
> > to the point where it never really has to be said what they are *for*
> > or how they work, whereas the correct way to write these sections is
> > from the point of view of someone who is familiar with URNs but has
> > never heard of a DOI before.  "We are talking about URNs that look
> > like this: ...  These URNs are used to specify DOIs, which are used in
> > XXX industry to designate YYYs.  DOIs are assigned to YYYs by ZZZ."
> >
> > In the above paragraph, the sentence starts with "As a DOI Name...",
> > which is actually trying to leverage that the reader *already
> > understands* how DOI Names work.
> >
> >>       As a DOI Name, the resolution of EIDR-NSS is handled by the ISO
> >>       26324 Registration Authority.
> >>
> >>       The ISO 26324 Registration Authority operates a web service that
> >>       allows an EIDR-NSS to be resolved by issuing an HTTP GET request
> >>       to the following URI:
> >>
> >>                "http://doi.org/" DOI-PREFIX "/" DOI-SUFFIX
> >
> > As written, this doesn't specify anything, because you can apply that
> > process to any alleged EIDR.  In order to make this meaningful, you
> > have to specify what the format of the HTTP *response* is and the
> > significance of the elements of the response.  (Presumably there is an
> > ISO standard you can reference here.)
> >
> > Dale
>

--001a1132e4cc27b4e404f1d533da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Thu, Feb 6, 2014 at 6:07 PM,=
 Pierre-Anthony Lemieux <span dir=3D"ltr">&lt;<a href=3D"mailto:pal@sandflo=
w.com" target=3D"_blank">pal@sandflow.com</a>&gt;</span> wrote:<br><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Ted and Dale,<br>
<br>
Thanks for the detailed comments, which I am in the process of<br>
addressing. In the meantime, some additional background and<br>
clarification on the request.<br>
<br>
The requested EIDR NID is not intended to accommodate any and all DOI<br>
Names, but specifically DOI Names allocated by EIDR organization, i.e.<br>
DOI Names with a prefix assigned to EIDR organization. This means that<br>
(a) EIDR organization essentially controls the syntax of the EIDR<br>
Identifiers, e.g. add check codes and constrain it to the ASCII set,<br>
and (b) the NID is specifically intended for audiovisual works. The<br>
fact that EIDR Identifiers are valid DOI Names ensures persistence,<br>
uniqueness and an open resolution infrastructure.<br>
<br>
Currently, EIDR Identifiers use the 10.5240 prefix for audiovisual<br>
works. The idea is to leave the door open for additional prefixes (and<br>
corresponding suffixes) to be defined in the future (with EIDR NID<br>
specification being updated accordingly). In all cases, these prefixes<br>
and suffixes would be defined and controlled by EIDR organization.<br>
<br></blockquote><div><div class=3D"gmail_default" style=3D"font-family:geo=
rgia,serif">I think you might update the draft to discuss that these are in=
tended to be<br>a subset of DOIs, then, just to remove any confusion.<br>
<br></div><div class=3D"gmail_default" style=3D"font-family:georgia,serif">=
Would you anticipate that later EIDR suffixes would retain the syntax<br>of=
 the current 10.5240-based identifiers?=A0 If so, this would be relatively<=
br>
simple.=A0 If not, it may be simpler to register one namespace now, basedon=
<br></div><div class=3D"gmail_default" style=3D"font-family:georgia,serif">=
10.5240 and its syntax, and then register later NIDs for other prefix/suffi=
x<br>
combinations in future.<br><br>regards,<br><br></div><div class=3D"gmail_de=
fault" style=3D"font-family:georgia,serif">Ted Hardie<br></div><br><br><br>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">

So, if an implementation receives an EIDR-NSS with an unknown prefix,<br>
it can still accept it, treating it as an opaque (case insensitive)<br>
identifier (with the option of resolving it as generic DOI Name.) If<br>
the prefix is known, additional processing can occur, e.g. error<br>
detection in the case of the 10.5240 prefix.<br>
<br>
Does this makes sense? I assume it is acceptable to reply cc&#39;ing the<br=
>
reflector. If not, I am happy to chat offline.<br>
<br>
Best,<br>
<br>
-- Pierre<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Thu, Feb 6, 2014 at 11:16 AM, Dale R. Worley &lt;<a href=3D"mailto:worle=
y@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br>
&gt; If there&#39;s a difference between EIDR and DOI, you ought to make th=
at<br>
&gt; clear. =A0The two terms are used throughout the document and I vaguely=
<br>
&gt; assumed that they are the same. =A0Actually, the underlying problem is=
<br>
&gt; that you write the document assuming that the reader is thoroughly<br>
&gt; familiar with EIDR&#39;s, DOI&#39;s, and the like. =A0Start with enoug=
h tutorial<br>
&gt; so that someone who has never heard of either before (me) will have a<=
br>
&gt; clear understanding of what is going on.<br>
&gt;<br>
&gt;&gt; From: Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gmail.com">ted.iet=
f@gmail.com</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; EIDR-NSS =3D DOI-PREFIX &quot;:&quot; DOI-SUFFIX<br>
&gt;&gt;<br>
&gt;&gt; This would seem to imply that any DOI prefix may be<br>
&gt;&gt; encountered and that this NID could be used with any<br>
&gt;&gt; registered DOI. =A0IF that were the intent, I would<br>
&gt;&gt; suggest registering the namespace &quot;DOI&quot; instead. =A0I<br=
>
&gt;&gt; understand that the DOI folks have consciously chosen not<br>
&gt;&gt; to do that(cf: <a href=3D"http://www.doi.org/factsheets/DOIIdentif=
ierSpecs.html" target=3D"_blank">http://www.doi.org/factsheets/DOIIdentifie=
rSpecs.html</a>),<br>
&gt;&gt; though, so I suspect your intent is to limit this to a subset<br>
&gt;&gt; of DOIs. =A0Is that correct? =A0Is it essentially limited to 10.52=
40?<br>
&gt;&gt; If not, how will the appropriate subset be identified?<br>
&gt;<br>
&gt; If the NID is to provide an encoding for all DOI names, then it should=
<br>
&gt; be named &quot;doi&quot;. =A0But if the DOI people have decided that i=
t is not a<br>
&gt; good thing to provide a NID for all DOI names, then:<br>
&gt;<br>
&gt; - the NID should be &quot;eidr&quot;<br>
&gt;<br>
&gt; - the syntax should not give a DOI-PREFIX, because that will *always*<=
br>
&gt; =A0 be &quot;10.5240&quot;, and there&#39;s no point including a long =
invariant string<br>
&gt; =A0 in the syntax<br>
&gt;<br>
&gt; Fundamentally, you need to determine if the DOI people are<br>
&gt; fundamentally against mapping DOI names into URNs, or whether they<br>
&gt; just don&#39;t want to put in the work (and you are actually doing the=
 job<br>
&gt; for them).<br>
&gt;<br>
&gt; Also, if you are thinking of providing a NID that can encompass all<br=
>
&gt; DOIs, you have to worry about character sets. =A0According to Wikipedi=
a,<br>
&gt; &quot;Most legal Unicode characters are allowed in these strings&quot;=
, whereas<br>
&gt; the %-encoding system can only represent ASCII characters.<br>
&gt;<br>
&gt;&gt; =A0 =A0 =A0 where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix an=
d suffix,<br>
&gt;&gt; =A0 =A0 =A0 respectively, translated into canonical NSS format acc=
ording to<br>
&gt;&gt; =A0 =A0 =A0 [RFC2141]. =A0DOI Name syntax is specified in [ISO2623=
4].<br>
&gt;<br>
&gt; What you mean to say is something like: =A0A DOI name consists of a<br=
>
&gt; prefix and a suffix, which are character strings [a fact the reader<br=
>
&gt; didn&#39;t know before]. =A0They are translated into the DOI-PREFIX an=
d<br>
&gt; DOI-SUFFIX by replacing all characters which are not XXX with<br>
&gt; corresponding %-escapes. =A0(See RFC 2141 section 2.2.)<br>
&gt;<br>
&gt; Exactly what the set XXX is needs to be specified with some care.<br>
&gt; Section 2.2 specifies that all characters that may not appear in URNs<=
br>
&gt; *at all* must be escaped. =A0But of course, &quot;:&quot; may appear i=
n URNs and<br>
&gt; by that specification need not be escaped. =A0OTOH, if &quot;:&quot; a=
ppears in a<br>
&gt; prefix or suffix, you very well want it escaped. =A0I&#39;m pretty sur=
e that<br>
&gt; you want XXX to be &lt;pchar&gt; as defined in RFC 3986 (the infamous<=
br>
&gt; &quot;Uniform Resource Identifier (URI): Generic Syntax&quot;).<br>
&gt;<br>
&gt; Also, you are depending on the fact that EIDR suffixes consist of<br>
&gt; ASCII characters, which can be represented by %-escapes (whereas DOI<b=
r>
&gt; suffixes can contain Unicode characters, which can&#39;t).<br>
&gt;<br>
&gt; NIDs are case-insensitive (RFC 2141 section 5), but usually are<br>
&gt; presented in lower case.<br>
&gt;<br>
&gt;&gt; =A0 =A0 =A0 =A0 =A0 EIDR-SUFFIX =A0=3D 5*5(4*4HEXDIG &quot;-&quot;=
) CHECK<br>
&gt;<br>
&gt; You can just say<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0EIDR-SUFFIX =A0=3D 5(4HEXDIG &quot;-&quot;) CHE=
CK<br>
&gt;<br>
&gt;&gt; =A0 =A0Identifier persistence considerations:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 As a DOI Name, the persistence of EIDR-NSS is guarante=
ed by the<br>
&gt;&gt; =A0 =A0 =A0 ISO 26324 Registration Authority. =A0A DOI Name remain=
s valid<br>
&gt;&gt; =A0 =A0 =A0 indefinitely.<br>
&gt;<br>
&gt; It would be clearer if you said something like<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0The ISO 26324 Registration Authority assigns DOI Names =
to<br>
&gt; =A0 =A0 =A0 =A0works(?). =A0A DOI Name remains valid indefinitely. =A0=
As a<br>
&gt; =A0 =A0 =A0 =A0consequence, the URN derived from a DOI Name remains va=
lid<br>
&gt; =A0 =A0 =A0 =A0indefinitely.<br>
&gt;<br>
&gt; Similar editing of the other items in this section would be helpful.<b=
r>
&gt;<br>
&gt; I can&#39;t quite put my finger on what seems to be the problem with t=
he<br>
&gt; writing. =A0I *think* the problem is that the text is written from the=
<br>
&gt; point of view of someone who is thoroughly familiar with DOIs/EIDRs,<b=
r>
&gt; to the point where it never really has to be said what they are *for*<=
br>
&gt; or how they work, whereas the correct way to write these sections is<b=
r>
&gt; from the point of view of someone who is familiar with URNs but has<br=
>
&gt; never heard of a DOI before. =A0&quot;We are talking about URNs that l=
ook<br>
&gt; like this: ... =A0These URNs are used to specify DOIs, which are used =
in<br>
&gt; XXX industry to designate YYYs. =A0DOIs are assigned to YYYs by ZZZ.&q=
uot;<br>
&gt;<br>
&gt; In the above paragraph, the sentence starts with &quot;As a DOI Name..=
.&quot;,<br>
&gt; which is actually trying to leverage that the reader *already<br>
&gt; understands* how DOI Names work.<br>
&gt;<br>
&gt;&gt; =A0 =A0 =A0 As a DOI Name, the resolution of EIDR-NSS is handled b=
y the ISO<br>
&gt;&gt; =A0 =A0 =A0 26324 Registration Authority.<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 The ISO 26324 Registration Authority operates a web se=
rvice that<br>
&gt;&gt; =A0 =A0 =A0 allows an EIDR-NSS to be resolved by issuing an HTTP G=
ET request<br>
&gt;&gt; =A0 =A0 =A0 to the following URI:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;<a href=3D"http://doi.org/" t=
arget=3D"_blank">http://doi.org/</a>&quot; DOI-PREFIX &quot;/&quot; DOI-SUF=
FIX<br>
&gt;<br>
&gt; As written, this doesn&#39;t specify anything, because you can apply t=
hat<br>
&gt; process to any alleged EIDR. =A0In order to make this meaningful, you<=
br>
&gt; have to specify what the format of the HTTP *response* is and the<br>
&gt; significance of the elements of the response. =A0(Presumably there is =
an<br>
&gt; ISO standard you can reference here.)<br>
&gt;<br>
&gt; Dale<br>
</div></div></blockquote></div><br></div></div>

--001a1132e4cc27b4e404f1d533da--

From Phillip.Maness@dts.com  Fri Feb 14 14:34:59 2014
Return-Path: <Phillip.Maness@dts.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 90E991A01D4 for <urn-nid@ietfa.amsl.com>; Fri, 14 Feb 2014 14:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.618
X-Spam-Level: 
X-Spam-Status: No, score=-0.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 dRq-FMmVUXBV for <urn-nid@ietfa.amsl.com>; Fri, 14 Feb 2014 14:34:55 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 55C101A0168 for <urn-nid@apps.ietf.org>; Fri, 14 Feb 2014 14:34:55 -0800 (PST)
Received: from BL2PR01CA010.prod.exchangelabs.com (10.141.66.50) by BLUPR01MB131.prod.exchangelabs.com (10.242.201.23) with Microsoft SMTP Server (TLS) id 15.0.878.16; Fri, 14 Feb 2014 22:34:51 +0000
Received: from BY2FFO11FD013.protection.gbl (2a01:111:f400:7c0c::121) by BL2PR01CA010.outlook.office365.com (2a01:111:e400:c1b::50) with Microsoft SMTP Server (TLS) id 15.0.878.16 via Frontend Transport; Fri, 14 Feb 2014 22:34:51 +0000
Received: from LAX-EXCA01.dts.local (207.178.146.195) by BY2FFO11FD013.mail.protection.outlook.com (10.1.14.75) with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Fri, 14 Feb 2014 22:34:50 +0000
Received: from LAX-EXMB02.dts.local ([fe80::b50e:9af7:de19:4aa9]) by LAX-EXCA01.dts.local ([fe80::5efe:10.10.10.122%11]) with mapi id 14.03.0174.001; Fri, 14 Feb 2014 14:34:47 -0800
From: Phillip Maness <Phillip.Maness@dts.com>
To: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>
Subject: draft RFC to describe a URN for DTS audio
Thread-Topic: draft RFC to describe a URN for DTS audio
Thread-Index: Ac8pziu7+AEftNL9SJaiWkH4O+prOw==
Date: Fri, 14 Feb 2014 22:34:45 +0000
Message-ID: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.10.10.112]
Content-Type: multipart/mixed; boundary="_004_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:207.178.146.195; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(43234003)(38284003)(189002)(199002)(85714005)(81686001)(19300405004)(81342001)(2656002)(71186001)(512954002)(81816001)(86362001)(56816005)(90146001)(92566001)(33656001)(94946001)(92726001)(83072002)(65816001)(93136001)(80022001)(93516002)(85852003)(63696002)(79102001)(77096001)(20776003)(6806004)(74706001)(74366001)(83322001)(19580405001)(4396001)(80976001)(85306002)(19580395003)(69226001)(49866001)(87266001)(76176001)(76786001)(76796001)(47976001)(55846006)(15843345004)(47446002)(568964001)(74662001)(31966008)(74502001)(47736001)(15974865002)(59766001)(50986001)(74876001)(77982001)(15202345003)(94316002)(51856001)(95666001)(87936001)(81542001)(16236675002)(56776001)(15975445006)(84326002)(53806001)(95416001)(76482001)(44976005)(54356001)(46102001)(54316002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR01MB131; H:LAX-EXCA01.dts.local; CLIP:207.178.146.195; FPR:DE1F61E8.AC9606DA.29E769B3.C4E1C9C0.201FB; PTR:.; MX:1; A:1; LANG:en; 
X-Forefront-PRVS: 01221E3973
X-OriginatorOrg: dts.com
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/eWMIrG0aceCReoUPoIB2zxvkUmc
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: Fri, 14 Feb 2014 22:36:51 -0000

--_004_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_
Content-Type: multipart/alternative;
	boundary="_000_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_"

--_000_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Sir or Madam,
Attached is a draft RFC describing the use of a namespace for DTS audio.
I have also submitted this as a draft RFC on https://datatracker.ietf.org/s=
ubmit/
Please contact me at phillip.maness@dts.com<mailto:phillip.maness@dts.com> =
with any suggestions or editorial input to improve the draft RFC.
Best regards,
Phil Maness

Phillip Maness
Director, Corporate Strategy and Development
DTS, Inc
5220 Las Virgenes Rd
Calabasas, CA 91302
+1(818)436-1361 (office)
+1(818)519-1978 (mobile)
www.dts.com<http://www.dts.com/>


________________________________

Notice:
This message and any included attachments are intended only for the use of =
the addressee, and may contain information that is privileged or confidenti=
al. If you are not the intended recipient, you are hereby notified that any=
 dissemination, distribution or copying of this communication is strictly p=
rohibited. If you have received this communication in error, please destroy=
 the original message and any copies or printouts hereof.

--_000_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-name:"Heading 1\,H1\,h1\,Heading U\,H11\,\0152\00A9_o\201A\00B5=
 1\,?c_o??E 1\,Titre 1\,\0152\,\0152\00A9";
	mso-style-priority:9;
	mso-style-link:"Heading 1 Char\,H1 Char\,h1 Char\,Heading U Char\,H11 Char=
\,\0152\00A9_o\201A\00B5 1 Char\,?c_o??E 1 Char\,Titre 1 Char\,\0152 Char\,=
\0152\00A9 Char";
	margin-top:24.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.3in;
	margin-bottom:.0001pt;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo6;
	font-size:14.0pt;
	font-family:"Cambria","serif";
	color:#365F91;}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	margin-top:10.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.4in;
	margin-bottom:.0001pt;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l0 level2 lfo6;
	font-size:13.0pt;
	font-family:"Cambria","serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-indent:-.5in;
	page-break-after:avoid;
	mso-list:l0 level3 lfo6;
	font-size:12.0pt;
	font-family:"Cambria","serif";}
h5
	{mso-style-name:"Heading 5\,H5\,H51\,h5\,Titre 5";
	mso-style-priority:9;
	mso-style-link:"Heading 5 Char\,H5 Char\,H51 Char\,h5 Char\,Titre 5 Char";
	margin-top:15.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.7in;
	margin-bottom:.0001pt;
	text-indent:-.7in;
	page-break-after:avoid;
	mso-list:l0 level5 lfo6;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:#365F91;
	letter-spacing:.5pt;
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-name:"List Paragraph\,Reference List";
	mso-style-priority:34;
	margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-name:"List Paragraph\,Reference ListCxSpFirst";
	mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-name:"List Paragraph\,Reference ListCxSpMiddle";
	mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-name:"List Paragraph\,Reference ListCxSpLast";
	mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.StyleHeading1Before0ptAfter12pt, li.StyleHeading1Before0ptAfter12pt, div.=
StyleHeading1Before0ptAfter12pt
	{mso-style-name:"Style Heading 1 + Before\:  0 pt After\:  12 pt";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-before:always;
	page-break-after:avoid;
	mso-list:l0 level1 lfo6;
	font-size:14.0pt;
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char\,H1 Char\,h1 Char\,Heading U Char\,H11 Cha=
r\,\0152\00A9_o\201A\00B5 1 Char\,?c_o??E 1 Char\,Titre 1 Char\,\0152 Char\=
,\0152\00A9 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1\,H1\,h1\,Heading U\,H11\,\0152\00A9_o\201A\00B5 =
1\,?c_o??E 1\,Titre 1\,\0152\,\0152\00A9";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-family:"Cambria","serif";
	font-weight:bold;}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Cambria","serif";
	font-weight:bold;}
span.Heading5Char
	{mso-style-name:"Heading 5 Char\,H5 Char\,H51 Char\,h5 Char\,Titre 5 Char"=
;
	mso-style-priority:9;
	mso-style-link:"Heading 5\,H5\,H51\,h5\,Titre 5";
	font-family:"Calibri","sans-serif";
	color:#365F91;
	letter-spacing:.5pt;}
span.EmailStyle23
	{mso-style-type:personal-compose;
	font-family:"Times New Roman","serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
.MsoPapDefault
	{mso-style-type:export-only;
	margin-top:3.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1136407231;
	mso-list-template-ids:1838824418;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-style-link:"Heading 5";
	mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l1
	{mso-list-id:1336222248;
	mso-list-template-ids:-1076734090;}
@list l1:level1
	{mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l1:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l1:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l1:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l1:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">Dear Sir or Madam,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">Attached is a draft RFC describing the use of a names=
pace for DTS audio.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">I have also submitted this as a draft RFC on
<a href=3D"https://datatracker.ietf.org/submit/">https://datatracker.ietf.o=
rg/submit/</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">Please contact me at
<a href=3D"mailto:phillip.maness@dts.com">phillip.maness@dts.com</a> with a=
ny suggestions or editorial input to improve the draft RFC.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">Best regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">Phil Maness
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"mso-element:para-border-div;border:none;border-top:solid wind=
owtext 1.0pt;padding:1.0pt 0in 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">Phillip Maness<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">Director, Corporate Strategy and Development<o:p></o:p></spa=
n></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">DTS, Inc<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">5220 Las Virgenes Rd<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">Calabasas, CA 91302<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">&#43;1(818)436-1361 (office)<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;">&#43;1(818)519-1978 (mobile)<o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin-top:0in;border:none;padding:0in"><i>=
<span style=3D"font-size:9.0pt;font-family:&quot;Times New Roman&quot;,&quo=
t;serif&quot;"><a href=3D"http://www.dts.com/">www.dts.com</a><o:p></o:p></=
span></i></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Courier New" color=3D"Black" size=3D"3"><br>
Notice:<br>
This message and any included attachments are intended only for the use of =
the addressee, and may contain information that is privileged or confidenti=
al. If you are not the intended recipient, you are hereby notified that any=
 dissemination, distribution or
 copying of this communication is strictly prohibited. If you have received=
 this communication in error, please destroy the original message and any c=
opies or printouts hereof.<br>
</font>
</body>
</html>

--_000_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_--

--_004_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_
Content-Type: text/plain; name="draft-pmaness-dts-urn-00.txt"
Content-Description: draft-pmaness-dts-urn-00.txt
Content-Disposition: attachment; filename="draft-pmaness-dts-urn-00.txt";
	size=10085; creation-date="Fri, 14 Feb 2014 21:37:26 GMT";
	modification-date="Fri, 14 Feb 2014 21:37:26 GMT"
Content-Transfer-Encoding: base64

TmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBQLiBNYW5lc3MKSW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBEVFMsIEluYy4KSW50ZW5kZWQgc3RhdHVzOiBJbmZvcm1hdGlv
bmFsICAgICAgICAgICAgICAgICAgICAgICAgRmVicnVhcnkgMTQsIDIwMTQKRXhwaXJlczogQXVn
dXN0IDIwMTQKCgoKICAgICAgICAgICAgICAgICAgICAgICAgIERUUyBOYW1lc3BhY2UgSWRlbnRp
ZmllcgogICAgICAgICAgICAgICAgICAgICAgIGRyYWZ0LXBtYW5lc3MtZHRzLXVybi0wMC50eHQK
CgpTdGF0dXMgb2YgdGhpcyBNZW1vCgogICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRl
ZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFu
ZCBCQ1AgNzkuCgogICBUaGlzIGRvY3VtZW50IG1heSBjb250YWluIG1hdGVyaWFsIGZyb20gSUVU
RiBEb2N1bWVudHMgb3IgSUVURgogICBDb250cmlidXRpb25zIHB1Ymxpc2hlZCBvciBtYWRlIHB1
YmxpY2x5IGF2YWlsYWJsZSBiZWZvcmUgTm92ZW1iZXIKICAgMTAsIDIwMDguIFRoZSBwZXJzb24o
cykgY29udHJvbGxpbmcgdGhlIGNvcHlyaWdodCBpbiBzb21lIG9mIHRoaXMKICAgbWF0ZXJpYWwg
bWF5IG5vdCBoYXZlIGdyYW50ZWQgdGhlIElFVEYgVHJ1c3QgdGhlIHJpZ2h0IHRvIGFsbG93CiAg
IG1vZGlmaWNhdGlvbnMgb2Ygc3VjaCBtYXRlcmlhbCBvdXRzaWRlIHRoZSBJRVRGIFN0YW5kYXJk
cyBQcm9jZXNzLgogICBXaXRob3V0IG9idGFpbmluZyBhbiBhZGVxdWF0ZSBsaWNlbnNlIGZyb20g
dGhlIHBlcnNvbihzKSBjb250cm9sbGluZwogICB0aGUgY29weXJpZ2h0IGluIHN1Y2ggbWF0ZXJp
YWxzLCB0aGlzIGRvY3VtZW50IG1heSBub3QgYmUgbW9kaWZpZWQKICAgb3V0c2lkZSB0aGUgSUVU
RiBTdGFuZGFyZHMgUHJvY2VzcywgYW5kIGRlcml2YXRpdmUgd29ya3Mgb2YgaXQgbWF5CiAgIG5v
dCBiZSBjcmVhdGVkIG91dHNpZGUgdGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3MsIGV4Y2VwdCB0
byBmb3JtYXQKICAgaXQgZm9yIHB1YmxpY2F0aW9uIGFzIGFuIFJGQyBvciB0byB0cmFuc2xhdGUg
aXQgaW50byBsYW5ndWFnZXMgb3RoZXIKICAgdGhhbiBFbmdsaXNoLgoKICAgSW50ZXJuZXQtRHJh
ZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcKICAg
VGFzayBGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5v
dGUgdGhhdAogICBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3Vt
ZW50cyBhcyBJbnRlcm5ldC0KICAgRHJhZnRzLgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFm
dCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXgKICAgbW9udGhzIGFuZCBtYXkg
YmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMKICAg
YXQgYW55IHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMg
YXMKICAgcmVmZXJlbmNlIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3
b3JrIGluIHByb2dyZXNzLiIKCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRz
IGNhbiBiZSBhY2Nlc3NlZCBhdAogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3Ry
YWN0cy50eHQKCiAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3Rvcmll
cyBjYW4gYmUgYWNjZXNzZWQgYXQKICAgaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbAoK
ICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBBdWd1c3QgMTQsIDIwMTQuCgoK
CgoKCk1hbmVzcyAgICAgICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTQsIDIwMTQgICAgICAg
ICAgICAgICAgIFtQYWdlIDFdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICBEVFMgTmFtZXNwYWNl
IElkZW50aWZpZXIgICAgICAgICAgIEZlYnJ1YXJ5IDIwMTQKCgpDb3B5cmlnaHQgTm90aWNlCgog
ICBDb3B5cmlnaHQgKGMpIDIwMTQgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmll
ZCBhcyB0aGUKICAgZG9jdW1lbnQgYXV0aG9ycy4gQWxsIHJpZ2h0cyByZXNlcnZlZC4KCiAgIFRo
aXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVn
YWwKICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0cDovL3Ry
dXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YKICAg
cHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVu
dHMKICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmlj
dGlvbnMgd2l0aAogICByZXNwZWN0IHRvIHRoaXMgZG9jdW1lbnQuCgpBYnN0cmFjdAoKICAgVGhp
cyBkb2N1bWVudCBkZXNjcmliZXMgdGhlIE5hbWVzcGFjZSBJZGVudGlmaWVyIChOSUQpIGZvciBV
bmlmb3JtCiAgIFJlc291cmNlIE5hbWVzcGFjZSAoVVJOKSByZXNvdXJjZXMgdG8gYmUgdXNlZCBm
b3IgRFRTIGF1ZGlvIHJlbGF0ZWQKICAgbWV0YWRhdGEgYW5kIHNpZ25hbGluZyBwYXJhbWV0ZXJz
LgoKQ29tbWVudHMgUmVxdWVzdGVkCgogICBDb21tZW50cyBhcmUgc29saWNpdGVkIGFuZCBzaG91
bGQgYmUgYWRkcmVzc2VkIHRvCiAgIHBoaWxsaXAubWFuZXNzQGR0cy5jb20uCgpUYWJsZSBvZiBD
b250ZW50cwoKCiAgIDEuIEludHJvZHVjdGlvbi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLjIKICAgMi4gU3BlY2lmaWNhdGlvbnMgVGVtcGxhdGUuLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMwogICAzLiBFeGFtcGxlLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi41CiAgIDQu
IE5hbWVzcGFjZSBDb25zaWRlcmF0aW9ucy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLjUKICAgNS4gQ29tbXVuaXR5IENvbnNpZGVyYXRpb25zLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uNQogICA2LiBJQU5BIENvbnNpZGVyYXRpb25zLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi42CiAgIDcuIFJlZmVyZW5jZXMuLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjYKICAgICAg
Ny4xLiBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uNgogICA4LiBBY2tub3dsZWRnbWVudHMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi42CgoxLiBJbnRyb2R1Y3Rpb24KCiAgIFRoZSBEVFMgYXVkaW8g
Zm9ybWF0cyBhcmUgdXNlZCBpbiBhIHdpZGUgdmFyaWV0eSBvZiBlbnRlcnRhaW5tZW50CiAgIG1l
ZGlhIGZvcm1hdHMuCgogICBEVFMgYXVkaW8gZW1lcmdlZCBpbiBwaHlzaWNhbCBtZWRpYSwgb3Jp
Z2luYXRpbmcgd2l0aCBMYXNlciBEaXNjIGluCiAgIDE5OTYgYW5kIGlzIGEgd2lkZWx5IHVzZWQg
YXVkaW8gZm9ybWF0IHVzZWQgaW4gQmx1LXJheSBkaXNjcyB0b2RheS4KICAgVGhlIG5leHQgZ2Vu
ZXJhdGlvbiBvZiBlbnRlcnRhaW5tZW50IG1lZGlhIGZvcm1hdHMgaXMgbm93IGVtZXJnaW5nCiAg
IGluIHRoZSBmb3JtIG9mIGRvd25sb2FkYWJsZSBmaWxlcyBhbmQgc3RyZWFtZWQgbWVkaWEsIGlu
Y2x1ZGluZyB0aGUKICAgRGlnaXRhbCBFbnRlcnRhaW5tZW50IENvbnRlbnQgRWNvc3lzdGVtIChV
bHRyYVZpb2xldCkgYW5kIG90aGVyCiAgIGRpZ2l0YWwgZGVsaXZlcnkgZWNvc3lzdGVtcyBjdXJy
ZW50bHkgaW4gZGV2ZWxvcG1lbnQuCgoKTWFuZXNzICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1
Z3VzdCAxNCwgMjAxNCAgICAgICAgICAgICAgICAgW1BhZ2UgMl0KDApJbnRlcm5ldC1EcmFmdCAg
ICAgICAgIERUUyBOYW1lc3BhY2UgSWRlbnRpZmllciAgICAgICAgICAgRmVicnVhcnkgMjAxNAoK
CiAgIERUUyBhdWRpbyBmb3JtYXRzIGFyZSBzdXBwb3J0ZWQgaW4gbWFueSBicm9hZGNhc3Qgc3Rh
bmRhcmRzLAogICBpbmNsdWRpbmcgRFZCLCBBVFNDLCBTQ1RFLCBPSVBGLCBIYmJUViBhbmQgdGhl
IEtvcmVhbiBUVEEKICAgc3BlY2lmaWNhdGlvbnMgYW5kIGFyZSBkZWZpbmVkIGZvciBib3RoIE9U
VCBhbmQgYnJvYWRjYXN0IGRlbGl2ZXJ5CiAgIGluIG1hbnkgb2YgdGhlc2Ugc3BlY2lmaWNhdGlv
bnMuCgoyLiBTcGVjaWZpY2F0aW9ucyBUZW1wbGF0ZQoKICAgTmFtZXNwYWNlIElEOgoKICAgICAg
ICAgImR0cyIKCiAgIFJlZ2lzdHJhdGlvbiBpbmZvcm1hdGlvbjoKCiAgICAgIFJlZ2lzdHJhdGlv
biBWZXJzaW9uIE51bWJlcjogMQoKICAgICAgUmVnaXN0cmF0aW9uIERhdGU6IDIwMTQtMDItMTQK
CiAgIERlY2xhcmVkIHJlZ2lzdHJhbnQgb2YgdGhlIG5hbWVzcGFjZToKCiAgICAgIE5hbWU6ICAg
ICAgIERUUywgSW5jLgoKICAgICAgQWRkcmVzczogICAgNTIyMCBMYXMgVmlyZ2VuZXMgUmQKCiAg
ICAgICAgICAgICAgICAgIENhbGFiYXNhcywgQ2FsaWZvcm5pYSwgOTEzMDEsIFVTQQoKICAgICAg
Q29udGFjdDogICAgUGhpbGxpcCBNYW5lc3MKCiAgICAgICAgICAgICAgICAgIFBob25lOiArMSA4
MTggNDM2IDEzNjEKCiAgICAgICAgICAgICAgICAgIEVtYWlsOiBQaGlsbGlwLm1hbmVzc0BkdHMu
Y29tCgogICBEZWNsYXJhdGlvbiBvZiBzdHJ1Y3R1cmU6CgogICAgICBUaGUgTmFtZXNwYWNlIFNw
ZWNpZmljIFN0cmluZyAoTlNTKSBvZiBhbGwgVVJOcyBhc3NpZ25lZCBieQoKICAgICAgRFRTLCBJ
bmMuIHdpbGwgaGF2ZSB0aGUgZm9sbG93aW5nIGhpZXJhcmNoaWNhbCBzdHJ1Y3R1cmU6CgogICAg
ICAgICB1cm46ZHRzOntjYXRlZ29yeX06e3N0cmluZ30KCiAgICAgIHdoZXJlIHRoZSAiY2F0ZWdv
cnkiIGlzIGEgVVMtQVNDSUkgc3RyaW5nIHRoYXQgY29uZm9ybXMgdG8gVVJOCiAgICAgIHN5bnRh
eCByZXF1aXJlbWVudHMgKFtSRkMyMTQxXSksIGFuZCAie3N0cmluZ30iIGlzIGEgc3RyaW5nIHRo
YXQKICAgICAgY29uZmlybXMgdG8gVVJOIHN5bnRheCByZXF1aXJlbWVudHMgKFtSRkMyMTQxXSku
CgogICBSZWxldmFudCBhbmNpbGxhcnkgZG9jdW1lbnRhdGlvbjoKCiAgICAgIG5vbmUKCgoKTWFu
ZXNzICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAxNCwgMjAxNCAgICAgICAgICAgICAg
ICAgW1BhZ2UgM10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgIERUUyBOYW1lc3BhY2UgSWRlbnRp
ZmllciAgICAgICAgICAgRmVicnVhcnkgMjAxNAoKCiAgIElkZW50aWZpZXIgdW5pcXVlbmVzcyBj
b25zaWRlcmF0aW9uczoKCiAgICAgIERUUywgSW5jLiBzaGFsbCBlc3RhYmxpc2ggdW5pcXVlIGlk
ZW50aWZpZXJzIGFzIGFwcHJvcHJpYXRlLgogICAgICBVbmlxdWVuZXNzIGlzIGd1YXJhbnRlZWQg
YXMgbG9uZyBhcyB0aGUgYXNzaWduZWQgIntjYXRlZ29yeX0iIGlzCiAgICAgIG5ldmVyIHJlYXNz
aWduZWQgZm9yIG90aGVyIGNhdGVnb3JpZXMuICBEVFMsIEluYy4gaXMgcmVzcG9uc2libGUKICAg
ICAgZm9yIHRoaXMuCgogICBJZGVudGlmaWVyIHBlcnNpc3RlbmNlIGNvbnNpZGVyYXRpb25zOgoK
ICAgICAgRFRTLCBJbmMuIGlzIGNvbW1pdHRlZCB0byBtYWludGFpbmluZyB0aGUgYWNjZXNzaWJp
bGl0eSBhbmQKICAgICAgcGVyc2lzdGVuY2Ugb2YgYWxsIHJlc291cmNlcyB0aGF0IGFyZSBvZmZp
Y2lhbGx5IGFzc2lnbmVkIFVSTnMgYnkKICAgICAgdGhpcyBvcmdhbml6YXRpb24uICBQZXJzaXN0
ZW5jZSBvZiBpZGVudGlmaWVycyBpcyBkZXBlbmRlbnQgdXBvbgogICAgICBzdWl0YWJsZSBkZWxl
Z2F0aW9uIGF0IHRoZSBsZXZlbCBvZiAiY2F0ZWdvcnkicywgYW5kIHBlcnNpc3RlbmNlCiAgICAg
IG9mIGNhdGVnb3J5IGFzc2lnbm1lbnQuCgogICBQcm9jZXNzIG9mIGlkZW50aWZpZXIgYXNzaWdu
bWVudDoKCiAgICAgIEFsbCB0aGUgYXNzaWdubWVudHMgb2YgaWRlbnRpZmllcnMgYXJlIGZ1bGx5
IGNvbnRyb2xsZWQgYW5kCiAgICAgIG1hbmFnZWQgYnkgRFRTLCBJbmMuCgogICBQcm9jZXNzIG9m
IGlkZW50aWZpZXIgcmVzb2x1dGlvbjoKCiAgICAgIFRoZSBuYW1lc3BhY2UgaXMgbm90IGxpc3Rl
ZCB3aXRoIGFuIFJEUzsgdGhpcyBpcyBub3QgcmVsZXZhbnQuCgogICBSdWxlcyBmb3IgTGV4aWNh
bCBFcXVpdmFsZW5jZToKCiAgICAgIFRoZSAie2NhdGVnb3J5fSIgaXMgY2FzZS1pbnNlbnNpdGl2
ZS4gIFRodXMsIHRoZSBwb3J0aW9uIG9mIHRoZQogICAgICBVUk46CgogICAgICAgICB1cm46ZHRz
OntjYXRlZ29yeX06CgogICAgICBpcyBjYXNlLWluc2Vuc2l0aXZlIGZvciBtYXRjaGVzLiAgVGhl
IHJlbWFpbmRlciBvZiB0aGUgaWRlbnRpZmllcgogICAgICBzaGFsbCBiZSBjb25zaWRlcmVkIGNh
c2Utc2Vuc2l0aXZlOyBoZW5jZSwgVVJOcyBhcmUgb25seQogICAgICBsZXhpY2FsbHkgZXF1aXZh
bGVudCBpZiB0aGV5IGFyZSBhbHNvIGxleGljYWxseSBpZGVudGljYWwgaW4gdGhlCiAgICAgIHJl
bWFpbmluZyB7c3RyaW5nfSBmaWVsZC4KCiAgIENvbmZvcm1hbmNlIHdpdGggVVJOIFN5bnRheDoK
CiAgICAgIE5vIHNwZWNpYWwgY29uc2lkZXJhdGlvbnMuCgogICBWYWxpZGF0aW9uIG1lY2hhbmlz
bToKCiAgICAgIFZhbGlkYXRpb24gc2hhbGwgYmUgZG9uZSBieSBhIHN5bnRheCBncmFtbWFyIGNv
cnJlc3BvbmRpbmcgdG8KICAgICAgZWFjaCAie2NhdGVnb3J5fSIuCgogICBTY29wZToKCgoKTWFu
ZXNzICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAxNCwgMjAxNCAgICAgICAgICAgICAg
ICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgIERUUyBOYW1lc3BhY2UgSWRlbnRp
ZmllciAgICAgICAgICAgRmVicnVhcnkgMjAxNAoKCiAgICAgIEdsb2JhbC4KCjMuIEV4YW1wbGUK
CiAgIFRoZSBmb2xsb3dpbmcgZXhhbXBsZXMgcmVwcmVzZW50IGh5cG90aGV0aWNhbCBVUk5zIHRo
YXQgY291bGQgYmUKICAgYXNzaWduZWQgYnkgRFRTLCBJbmMuCgogICAgIHVybjpkdHM6ZGFzaDpN
UERwYXJhbWV0ZXI6MjAxNAoKICAgICB1cm46ZHRzOm1ldGFkYXRhLWV4YW1wbGU6bWV0YXBhcmFt
ZXRlcjoyMDE0CgogICAgIHVybjpkdHM6cHJvZmlsZS1leGFtcGxlOnByb2ZpbGVwYXJhbWV0ZXI6
MjAxNQoKNC4gTmFtZXNwYWNlIENvbnNpZGVyYXRpb25zCgogICAgIFRoZSBvYmplY3RpdmUgb2Yg
dGhpcyBuYW1lc3BhY2UgcmVnaXN0cmF0aW9uIGlzIHRvIGZhY2lsaXRhdGUKICAgICBjb25zaXN0
ZW50IGltcGxlbWVudGF0aW9uIG9mIERUUyBhY3Jvc3MgYWxsIG5ldHdvcmtlZCBlY29zeXN0ZW1z
LgoKNS4gQ29tbXVuaXR5IENvbnNpZGVyYXRpb25zCgogICAgIFRoZSBuYW1lcyBpbiB0aGlzIG5h
bWVzcGFjZSBhcmUgdG8gYmUgdXNlZCBpbiBhbnkgcHVibGljCiAgICAgaW1wbGVtZW50YXRpb25z
IGFwcGx5aW5nIERUUyBzcGVjaWZpY2F0aW9ucyBvciBpbiB0aGUgdHJhbnNtaXNzaW9uCiAgICAg
b2YgRFRTIGJpdHN0cmVhbXMgc28gYW55Ym9keSBjYW4gYmVuZWZpdCBmcm9tIHRoZSBvZmZpY2lh
bGx5CiAgICAgYXNzaWduZWQgbmFtZXNwYWNlLgoKICAgICBQb3RlbnRpYWwgYmVuZWZpY2lhcnkg
Y29tbXVuaXRpZXMgaW5jbHVkZToKCiAgYSkgSW1wbGVtZW50ZXJzIG9mIHRoZSBNUEVHIERBU0gg
c3BlY2lmaWNhdGlvbnMgdXNpbmcgRFRTIGF1ZGlvLgoKICAgICBSZXNvdXJjZXMgdGhhdCBjb21w
bHkgd2l0aCB0aGUgTVBFRyBEQVNIIHNwZWNpZmljYXRpb25zIChpbmNsdWRpbmcKICAgICBEQVNI
IHNjaGVtYXMsIGluc3RhbmNlIGRvY3VtZW50cyB0aGF0IGNvbXBseSB3aXRoIERBU0ggc2NoZW1h
cywKICAgICBhbmQgREFTSCBkZWZhdWx0IENsYXNzaWZpY2F0aW9uIFNjaGVtZXMpIG1heSwgYnkg
bWVhbnMgb2YgdGhlCiAgICAgcmVnaXN0ZXJlZCBuYW1lc3BhY2UsIGJlY29tZSBleHBvc2VkIHRv
IHRoZSBnZW5lcmFsIEludGVybmV0IGFuZAogICAgIGdhaW4gZnJvbSB0aGUgaW50ZXJvcGVyYWJp
bGl0eSBiZW5lZml0cyBvZiB0aGUgSW50ZXJuZXQgYXQgbGFyZ2UuCgogIGIpIEltcGxlbWVudGVy
cyBvZiBvdGhlciBzcGVjaWZpY2F0aW9ucyB0aGF0IGluY29ycG9yYXRlIGNvbXBvbmVudHMKICAg
ICBvZiB0aGUgRFRTIHNwZWNpZmljYXRpb25zLgoKICAgICBVUk5zIHVzZWQgdG8gaWRlbnRpZnkg
RFRTIGNvbXBvbmVudHMgbWF5IGJlIHVzZWQgdG8gZW5hYmxlIHRoZWlyCiAgICAgaW5jbHVzaW9u
IGluLCBhbmQgZW5oYW5jZW1lbnQgb2YsIG90aGVyIHNwZWNpZmljYXRpb25zIHdoaWxlCiAgICAg
bWFpbnRhaW5pbmcsIHRvIGEgY2VydGFpbiBkZWdyZWUsIGludGVyb3BlcmFiaWxpdHkgd2l0aCB0
aGUgRFRTCiAgICAgaW1wbGVtZW50ZXJzIGNvbW11bml0eS4KCiAgYykgSW1wbGVtZW50ZXJzIG9m
IG90aGVyIHNlbWFudGljYWxseSByZWxhdGVkIHNwZWNpZmljYXRpb25zIHRoYXQgZG8KICAgICBu
b3QgZGlyZWN0bHkgaW5jb3Jwb3JhdGUgY29tcG9uZW50cyBvZiB0aGUgRFRTIHNwZWNpZmljYXRp
b25zLgoKCgoKTWFuZXNzICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAxNCwgMjAxNCAg
ICAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgIERUUyBOYW1l
c3BhY2UgSWRlbnRpZmllciAgICAgICAgICAgRmVicnVhcnkgMjAxNAoKCiAgICAgVVJOcyB1c2Vk
IHRvIGlkZW50aWZ5IGNvbXBvbmVudHMgb2YgdGhlIERUUyBzcGVjaWZpY2F0aW9ucywgc3VjaAog
ICAgIGFzIGlkZW50aWZpZXJzIG9mIHRlcm1zIHdpdGhpbiBkZWZhdWx0IENsYXNzaWZpY2F0aW9u
IFNjaGVtZXMsIG1heQogICAgIGVuYWJsZSBpbnRlcm9wZXJhdGlvbiB3aXRoIG90aGVyIHNlbWFu
dGljYWxseSBkZXRlcm1pbmVkCiAgICAgc3BlY2lmaWNhdGlvbnMgKGluY2x1ZGluZyBwcmVzZW50
IGFuZCBmdXR1cmUgbWV0YWRhdGEvcmVzb3VyY2UKICAgICBkZXNjcmlwdGlvbiBhbmQgb250b2xv
Z3kgc3BlY2lmaWNhdGlvbnMpIG9mIHJlbGV2YW5jZSB0byBhdWRpbwogICAgIGNvZGVjIGltcGxl
bWVudGF0aW9uICBjb21tdW5pdGllcyAoc2VlIGEpIGFuZCBiKSBhYm92ZSkuRm9ybWFsCiAgICAg
U3ludGF4Cgo2LiBJQU5BIENvbnNpZGVyYXRpb25zCgogICBUaGUgZG9jdW1lbnQgaW5jbHVkZXMg
YSBVUk4gTklEIHJlZ2lzdHJhdGlvbiB0aGF0IGlzIHRvIGJlIGVudGVyZWQKICAgaW50byB0aGUg
SUFOQSByZWdpc3RyeSBvZiBVUk4gTklEcy4KCjcuIFJlZmVyZW5jZXMKCjcuMS4gSW5mb3JtYXRp
dmUgUmVmZXJlbmNlcwoKICAgWzFdICAgW1JGQzMzMDZdICAgRGFpZ2xlLCBMLiwgIlVuaWZvcm0g
UmVzb3VyY2UgTmFtZXMgKFVSTikKICAgICAgICAgTmFtZXNwYWNlIERlZmluaXRpb24gTWVjaGFu
aXNtcyIsIFJGQyAzMzA2LCBPY3RvYmVyIDIwMDIuCgo4LiBBY2tub3dsZWRnbWVudHMKCiAgIFRo
aXMgZG9jdW1lbnQgd2FzIHByZXBhcmVkIHVzaW5nIDItV29yZC12Mi4wLnRlbXBsYXRlLmRvdC4K
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpNYW5lc3MgICAgICAgICAgICAgICAgIEV4cGlyZXMg
QXVndXN0IDE0LCAyMDE0ICAgICAgICAgICAgICAgICBbUGFnZSA2XQoMCkludGVybmV0LURyYWZ0
ICAgICAgICAgRFRTIE5hbWVzcGFjZSBJZGVudGlmaWVyICAgICAgICAgICBGZWJydWFyeSAyMDE0
CgoKQXV0aG9ycycgQWRkcmVzc2VzCgogICBQaGlsbGlwIE1hbmVzcwogICBEVFMsIEluYy4KICAg
NTIyMCBMYXMgVmlyZ2VuZXMgUmQuLCBDYWxhYmFzYXMgQ0EgOTEzMDEsIFVTQQoKICAgUGhvbmU6
ICsxICg4MTgpIDUxOS0xOTc4CiAgIEVtYWlsOiBQaGlsbGlwLm1hbmVzc0BkdHMuY29tCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKTWFuZXNzICAgICAgICAgICAgICAg
ICBFeHBpcmVzIEF1Z3VzdCAxNCwgMjAxNCAgICAgICAgICAgICAgICAgW1BhZ2UgN10KDAo=

--_004_520A56052CF01E42B1C128F990FBE681A46AFD52LAXEXMB02dtsloc_--


From nobody Mon Feb 17 14:51:25 2014
Return-Path: <worley@shell01.TheWorld.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 63CEE1A0537 for <urn-nid@ietfa.amsl.com>; Mon, 17 Feb 2014 14:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 ug2htaySaTcp for <urn-nid@ietfa.amsl.com>; Mon, 17 Feb 2014 14:51:10 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 083D51A041C for <urn-nid@apps.ietf.org>; Mon, 17 Feb 2014 14:51:09 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1HMo8Z0006242; Mon, 17 Feb 2014 17:50:11 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1HMjnvr5224842; Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1HMjnBU5200650; Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Date: Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Message-Id: <201402172245.s1HMjnBU5200650@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Phillip Maness <Phillip.Maness@dts.com>
In-reply-to: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> (Phillip.Maness@dts.com)
Subject: Re: draft RFC to describe a URN for DTS audio
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local>
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/cWomaDeNYAD21vHODSxtO2WuO2M
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 <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, 17 Feb 2014 22:51:14 -0000

What are the objects that these URNs name?  As far as I can tell, the
draft does not specify that.

It appears from the two examples that the objects are intended to be
parameters which are attributes of particular DTS audio encodings.  In
that case, it would seem that there will only be a small number (maybe
tens or hundreds) of these URNs that are valid.  If so, it may save
effort to have IETF allocate a sub-namespace,
"urn:ietf:params:dts:..." into which DTS can assign paramater URNs.
(See https://www.iana.org/assignments/params/params.xml and RFC 3553.)

Dale


From nobody Tue Feb 18 18:40:02 2014
Return-Path: <Phillip.Maness@dts.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 2CE9B1A0534 for <urn-nid@ietfa.amsl.com>; Tue, 18 Feb 2014 18:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 jWSDx1epTDcl for <urn-nid@ietfa.amsl.com>; Tue, 18 Feb 2014 18:39:56 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0190.outbound.protection.outlook.com [207.46.163.190]) by ietfa.amsl.com (Postfix) with ESMTP id 4303E1A043D for <urn-nid@apps.ietf.org>; Tue, 18 Feb 2014 18:39:56 -0800 (PST)
Received: from BLUPR01CA004.prod.exchangelabs.com (10.255.223.162) by BLUPR01MB469.prod.exchangelabs.com (10.141.81.16) with Microsoft SMTP Server (TLS) id 15.0.878.16; Wed, 19 Feb 2014 02:39:51 +0000
Received: from BN1BFFO11FD050.protection.gbl (2a01:111:f400:7c10::1:180) by BLUPR01CA004.outlook.office365.com (2a01:111:e400:841::34) with Microsoft SMTP Server (TLS) id 15.0.883.10 via Frontend Transport; Wed, 19 Feb 2014 02:39:51 +0000
Received: from LAX-EXCA02.dts.local (207.178.146.195) by BN1BFFO11FD050.mail.protection.outlook.com (10.58.145.5) with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Wed, 19 Feb 2014 02:39:51 +0000
Received: from LAX-EXMB02.dts.local ([fe80::b50e:9af7:de19:4aa9]) by LAX-EXCA02.dts.local ([fe80::5efe:10.10.10.123%11]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 18:39:50 -0800
From: Phillip Maness <Phillip.Maness@dts.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: RE: draft RFC to describe a URN for DTS audio
Thread-Topic: draft RFC to describe a URN for DTS audio
Thread-Index: AQHPLDLBHwS6EV29SE6B2sonNGQO6Jq7PYBA
Date: Wed, 19 Feb 2014 02:39:48 +0000
Message-ID: <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local>
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> <201402172245.s1HMjnBU5200650@shell01.TheWorld.com>
In-Reply-To: <201402172245.s1HMjnBU5200650@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.10.10.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:207.178.146.195; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(13464003)(199002)(189002)(85714005)(377454003)(80022001)(81342001)(83072002)(2656002)(56816005)(80976001)(92726001)(33656001)(85852003)(63696002)(46406003)(94946001)(93136001)(79102001)(65816001)(83322001)(77096001)(44976005)(20776003)(19580405001)(19580395003)(90146001)(74706001)(47976001)(47736001)(49866001)(50986001)(6806004)(69226001)(74502001)(47446002)(76786001)(87266001)(55846006)(54316002)(53806001)(51856001)(15975445006)(77982001)(46102001)(59766001)(93516002)(81686001)(81816001)(86362001)(74366001)(74662001)(31966008)(85306002)(92566001)(76796001)(4396001)(74876001)(94316002)(81542001)(47776003)(95666001)(87936001)(95416001)(50466002)(56776001)(23726002)(76482001)(54356001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR01MB469; H:LAX-EXCA02.dts.local; CLIP:207.178.146.195; FPR:CE9FF1ED.AE3A97A6.29F3394A.84F4D1CD.20440; PTR:.; A:1; MX:1; LANG:en; 
X-Forefront-PRVS: 012792EC17
X-OriginatorOrg: dts.com
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/RJU0-4n9oydR8sImYLl4i7GxFeM
Cc: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>, "Mark R. Johnson" <Mark.Johnson@dts.com>
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, 19 Feb 2014 02:40:00 -0000

Hi Dale,
Historically, many 100's of millions of products containing DTS technologie=
s over many 1000's of SKUs and hundreds of manufacturers have shipped world=
wide. We have an extensive footprint in physical media, but we know that di=
gital media and cloud services are quickly displacing this. We have publicl=
y stated that this is our vision and where we are focusing our efforts.

Sorry, I have to be intentionally vague from this point on. We have a numbe=
r of business activities in process so we have to consider customers, partn=
ers and competitors (and, of course, the financial community, as we are a p=
ublicly traded company). The nature of these disclosures in publications su=
ch as an RFC can be (intentionally or unintentionally) indicative, (or perc=
eived as being indicative), of future business.

I will say that our prospects are considerably more extensive than audio pa=
rameters. Audio parameters were used as examples as they are fairly obvious=
 to the current nature of our business. We have the potential for many thou=
sands of references over multiple categories under the dts namespace.

While I can't put any more color to this in writing, I would be happy to sc=
hedule a phone conversation with myself and our VP of Streaming and Media S=
olutions to give you a better idea of how we plan to utilize this namespace=
. When would be a good time to schedule a call? Fridays are generally good =
for us.

Best Regards,
Phil Maness


-----Original Message-----
From: Dale R. Worley [mailto:worley@ariadne.com]
Sent: Monday, February 17, 2014 2:46 PM
To: Phillip Maness
Cc: urn-nid@apps.ietf.org
Subject: Re: draft RFC to describe a URN for DTS audio

What are the objects that these URNs name?  As far as I can tell, the draft=
 does not specify that.

It appears from the two examples that the objects are intended to be parame=
ters which are attributes of particular DTS audio encodings.  In that case,=
 it would seem that there will only be a small number (maybe tens or hundre=
ds) of these URNs that are valid.  If so, it may save effort to have IETF a=
llocate a sub-namespace, "urn:ietf:params:dts:..." into which DTS can assig=
n paramater URNs.
(See https://www.iana.org/assignments/params/params.xml and RFC 3553.)

Dale

________________________________

Notice:
This message and any included attachments are intended only for the use of =
the addressee, and may contain information that is privileged or confidenti=
al. If you are not the intended recipient, you are hereby notified that any=
 dissemination, distribution or copying of this communication is strictly p=
rohibited. If you have received this communication in error, please destroy=
 the original message and any copies or printouts hereof.


From nobody Thu Feb 20 10:51:12 2014
Return-Path: <worley@shell01.TheWorld.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 CF2A51A0256 for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 10:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level: 
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 6YN1Gnoo6Jvm for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 10:51:08 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF771A01DD for <urn-nid@apps.ietf.org>; Thu, 20 Feb 2014 10:51:08 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1KIoDpQ010263; Thu, 20 Feb 2014 13:50:15 -0500
Received: from shell01.TheWorld.com (localhost [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1KIefP05390028; Thu, 20 Feb 2014 13:40:41 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1KIeelE5399376; Thu, 20 Feb 2014 13:40:40 -0500 (EST)
Date: Thu, 20 Feb 2014 13:40:40 -0500 (EST)
Message-Id: <201402201840.s1KIeelE5399376@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Phillip Maness <Phillip.Maness@dts.com>
In-reply-to: <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local> (Phillip.Maness@dts.com)
Subject: Re: draft RFC to describe a URN for DTS audio
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> <201402172245.s1HMjnBU5200650@shell01.TheWorld.com> <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local>
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/-ryOuFz8PYgsL2XWRcgKPXavzk8
Cc: urn-nid@apps.ietf.org, Mark.Johnson@dts.com
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: Thu, 20 Feb 2014 18:51:11 -0000

> From: Phillip Maness <Phillip.Maness@dts.com>
> 
> Sorry, I have to be intentionally vague from this point on. We have
> a number of business activities in process so we have to consider
> customers, partners and competitors (and, of course, the financial
> community, as we are a publicly traded company). The nature of these
> disclosures in publications such as an RFC can be (intentionally or
> unintentionally) indicative, (or perceived as being indicative), of
> future business.

My first impulse was to say, "I doubt you're going to get much
traction with a proposal for a system of names if you're not going to
admit *what* they are naming."  But that is incorrect, as lots of
organizations have obtained URN NIDs for such generic use.

You may have some difficulty in that DTS is a business, and has no
purported public benefit purpose.  In my quick look at the NID
registrations that are essentially delegations to organizations, all
of the organizations are governments or industry consortia which have
public benefit purposes.  Granting a delegation to DTS would be
setting a precedent for delegation to a business (a straightforward
for-profit entity).  Certainly the question will be raised, "Will it
be possible to use one of these URNs in a context that does not cause
money to flow to DTS Inc."?

(I will note that there are several mechanisms by which DTS could
obtain an Object ID delegation, and there is no question that
businesses may do so.  Since all Object IDs correspond to URNs
(urn:oid:...), DTS can immediately obtain a URN delegation in that
manner.)

Comparing draft-pmaness-dts-urn-00 and the NID registrations for
"3gpp" (RFC 5279), "cablelabs" (RFC 6289), and "cgi" (RFC 5138), the
organizational delegation registrations seem to favor declarations
like "The registration tables and information will be published and
maintained by 3GPP on its web site."  I don't know if such a promise
of public information is critical to getting the NID approved, but it
would certainly help.

The whole of section 1 seems to be true but not actually relevant to
the namespace, as the proposed namespace doesn't seem to be
intrinsically tied to DTS audio formats (that just happens to be
everything that DTS Inc. is involved in right now).  I don't know what
would be a good replacement, but the truth seems to be "DTS has a lot
of irons in the fire, and we think that it would be useful if we could
assign URNs.  Though we have a lot of good ideas, we aren't entirely
certain what we would use them for yet."

In regard to the syntax, you need to specify that "category" may not
contain ":"; otherwise a URN can't be unambiguously parsed into
"category" and "string" components.

Dale


From nobody Thu Feb 20 17:10:02 2014
Return-Path: <pal@sandflow.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 A96D61A0396 for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 17:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.732
X-Spam-Level: 
X-Spam-Status: No, score=0.732 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, T_FILL_THIS_FORM_SHORT=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 T_2oXZnIjQHO for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 17:09:55 -0800 (PST)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2A51A038B for <urn-nid@apps.ietf.org>; Thu, 20 Feb 2014 17:09:55 -0800 (PST)
Received: by mail-qc0-f181.google.com with SMTP id c9so4290595qcz.26 for <urn-nid@apps.ietf.org>; Thu, 20 Feb 2014 17:09:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=A6UjZGs/v1+xFVDuTRr2WNeTsF5qOjnezJukwWClqg4=; b=lF5gvyXb56s8vd/TBGNZ0mj+PuCLBiFdzVRLz8PdJuh6e0goZYwSDlk0gvbPpMskkZ VMD4MSNXmvUPXsprM/h+Vb4Uk6gNtMRNXZBFJhV/m76loMkEQxe2iO1ZPThjw8/sB1wE 0X+9zepGyTWUeH00mk8BjoVT57AoTOdLdH/hiFBvJaNa+kbi4COZjoK4IjIVjfT7+d/F Zo0zptkYeKMbfapr+bFxqLWH0vfn8ds1BpG51jY4TL4iXUDq60tjBbwXLRvqF8H5/XWk J3ob4AKBvOUIbQL26X71lDwSmtuloC0Ox2MYPCbbOu8QzxpFPBnfXFgzlrX5/XUyMOS3 ZUeQ==
X-Gm-Message-State: ALoCoQlrEytPbU+Pry1yNBukfz3uLvQT3wmfwkeIcWak8yFenMNqgdOcLHVQyHsM98aSvggwKmR7
X-Received: by 10.224.67.69 with SMTP id q5mr5961076qai.39.1392944991514; Thu, 20 Feb 2014 17:09:51 -0800 (PST)
Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) by mx.google.com with ESMTPSA id k107sm10169913qgk.5.2014.02.20.17.09.47 for <urn-nid@apps.ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 17:09:47 -0800 (PST)
Received: by mail-qc0-f180.google.com with SMTP id i17so4718305qcy.39 for <urn-nid@apps.ietf.org>; Thu, 20 Feb 2014 17:09:47 -0800 (PST)
X-Received: by 10.224.122.20 with SMTP id j20mr6088087qar.82.1392944987202; Thu, 20 Feb 2014 17:09:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.41.133 with HTTP; Thu, 20 Feb 2014 17:09:26 -0800 (PST)
In-Reply-To: <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
References: <CAF_7JxASOJEKwZ_XAohHwqVjaDz5zqqbG349dCNiQHRh+nnHxw@mail.gmail.com> <201402061916.s16JG0J64392388@shell01.TheWorld.com> <CAF_7JxAsn7StRvXf8B+dPpu8a97XACH+DAf8ftZN6OVFkJmXkg@mail.gmail.com>
From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Thu, 20 Feb 2014 17:09:26 -0800
Message-ID: <CAF_7JxB046x5zZOsjV+VocasxXyVDjJqgdcN7h3mmXxizmu53A@mail.gmail.com>
Subject: Re: Application for a formal URN NID ("EIDR")
To: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>
Content-Type: multipart/mixed; boundary=089e0149c18627b9ea04f2e0473e
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/0k6uzsXdp_pzqtfzoUThI5CK2Tc
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: Fri, 21 Feb 2014 01:10:00 -0000

--089e0149c18627b9ea04f2e0473e
Content-Type: text/plain; charset=ISO-8859-1

Good morning/evening,

Please find attached a revised application for the formal "EIDR" URN
NID. The revised application is intended to address the comments
received on the list.

Some highlights:

- the introduction was expanded to provide more details on DOI Names,
EIDR Identifiers and their relationship.
- the EIDR-URN syntax was refactored to focus on EIDR Identifiers, and
not DOI Names in general.
- the EIDR Identifier prefix and suffix character sets are now
explicitly specified to remove potential ambiguities in mapping them
to the URN character set
- the HTTP response to a resolution request to the ISO 26324
Registration Authority is now specified

I plan to update the I-D when the submission window reopens.

Thanks again to the commenters.

Best,

-- Pierre

On Thu, Feb 6, 2014 at 6:07 PM, Pierre-Anthony Lemieux <pal@sandflow.com> wrote:
> Hi Ted and Dale,
>
> Thanks for the detailed comments, which I am in the process of
> addressing. In the meantime, some additional background and
> clarification on the request.
>
> The requested EIDR NID is not intended to accommodate any and all DOI
> Names, but specifically DOI Names allocated by EIDR organization, i.e.
> DOI Names with a prefix assigned to EIDR organization. This means that
> (a) EIDR organization essentially controls the syntax of the EIDR
> Identifiers, e.g. add check codes and constrain it to the ASCII set,
> and (b) the NID is specifically intended for audiovisual works. The
> fact that EIDR Identifiers are valid DOI Names ensures persistence,
> uniqueness and an open resolution infrastructure.
>
> Currently, EIDR Identifiers use the 10.5240 prefix for audiovisual
> works. The idea is to leave the door open for additional prefixes (and
> corresponding suffixes) to be defined in the future (with EIDR NID
> specification being updated accordingly). In all cases, these prefixes
> and suffixes would be defined and controlled by EIDR organization.
>
> So, if an implementation receives an EIDR-NSS with an unknown prefix,
> it can still accept it, treating it as an opaque (case insensitive)
> identifier (with the option of resolving it as generic DOI Name.) If
> the prefix is known, additional processing can occur, e.g. error
> detection in the case of the 10.5240 prefix.
>
> Does this makes sense? I assume it is acceptable to reply cc'ing the
> reflector. If not, I am happy to chat offline.
>
> Best,
>
> -- Pierre
>
> On Thu, Feb 6, 2014 at 11:16 AM, Dale R. Worley <worley@ariadne.com> wrote:
>> If there's a difference between EIDR and DOI, you ought to make that
>> clear.  The two terms are used throughout the document and I vaguely
>> assumed that they are the same.  Actually, the underlying problem is
>> that you write the document assuming that the reader is thoroughly
>> familiar with EIDR's, DOI's, and the like.  Start with enough tutorial
>> so that someone who has never heard of either before (me) will have a
>> clear understanding of what is going on.
>>
>>> From: Ted Hardie <ted.ietf@gmail.com>
>>>
>>> EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX
>>>
>>> This would seem to imply that any DOI prefix may be
>>> encountered and that this NID could be used with any
>>> registered DOI.  IF that were the intent, I would
>>> suggest registering the namespace "DOI" instead.  I
>>> understand that the DOI folks have consciously chosen not
>>> to do that(cf: http://www.doi.org/factsheets/DOIIdentifierSpecs.html),
>>> though, so I suspect your intent is to limit this to a subset
>>> of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
>>> If not, how will the appropriate subset be identified?
>>
>> If the NID is to provide an encoding for all DOI names, then it should
>> be named "doi".  But if the DOI people have decided that it is not a
>> good thing to provide a NID for all DOI names, then:
>>
>> - the NID should be "eidr"
>>
>> - the syntax should not give a DOI-PREFIX, because that will *always*
>>   be "10.5240", and there's no point including a long invariant string
>>   in the syntax
>>
>> Fundamentally, you need to determine if the DOI people are
>> fundamentally against mapping DOI names into URNs, or whether they
>> just don't want to put in the work (and you are actually doing the job
>> for them).
>>
>> Also, if you are thinking of providing a NID that can encompass all
>> DOIs, you have to worry about character sets.  According to Wikipedia,
>> "Most legal Unicode characters are allowed in these strings", whereas
>> the %-encoding system can only represent ASCII characters.
>>
>>>       where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix,
>>>       respectively, translated into canonical NSS format according to
>>>       [RFC2141].  DOI Name syntax is specified in [ISO26234].
>>
>> What you mean to say is something like:  A DOI name consists of a
>> prefix and a suffix, which are character strings [a fact the reader
>> didn't know before].  They are translated into the DOI-PREFIX and
>> DOI-SUFFIX by replacing all characters which are not XXX with
>> corresponding %-escapes.  (See RFC 2141 section 2.2.)
>>
>> Exactly what the set XXX is needs to be specified with some care.
>> Section 2.2 specifies that all characters that may not appear in URNs
>> *at all* must be escaped.  But of course, ":" may appear in URNs and
>> by that specification need not be escaped.  OTOH, if ":" appears in a
>> prefix or suffix, you very well want it escaped.  I'm pretty sure that
>> you want XXX to be <pchar> as defined in RFC 3986 (the infamous
>> "Uniform Resource Identifier (URI): Generic Syntax").
>>
>> Also, you are depending on the fact that EIDR suffixes consist of
>> ASCII characters, which can be represented by %-escapes (whereas DOI
>> suffixes can contain Unicode characters, which can't).
>>
>> NIDs are case-insensitive (RFC 2141 section 5), but usually are
>> presented in lower case.
>>
>>>           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK
>>
>> You can just say
>>
>>            EIDR-SUFFIX  = 5(4HEXDIG "-") CHECK
>>
>>>    Identifier persistence considerations:
>>>
>>>       As a DOI Name, the persistence of EIDR-NSS is guaranteed by the
>>>       ISO 26324 Registration Authority.  A DOI Name remains valid
>>>       indefinitely.
>>
>> It would be clearer if you said something like
>>
>>        The ISO 26324 Registration Authority assigns DOI Names to
>>        works(?).  A DOI Name remains valid indefinitely.  As a
>>        consequence, the URN derived from a DOI Name remains valid
>>        indefinitely.
>>
>> Similar editing of the other items in this section would be helpful.
>>
>> I can't quite put my finger on what seems to be the problem with the
>> writing.  I *think* the problem is that the text is written from the
>> point of view of someone who is thoroughly familiar with DOIs/EIDRs,
>> to the point where it never really has to be said what they are *for*
>> or how they work, whereas the correct way to write these sections is
>> from the point of view of someone who is familiar with URNs but has
>> never heard of a DOI before.  "We are talking about URNs that look
>> like this: ...  These URNs are used to specify DOIs, which are used in
>> XXX industry to designate YYYs.  DOIs are assigned to YYYs by ZZZ."
>>
>> In the above paragraph, the sentence starts with "As a DOI Name...",
>> which is actually trying to leverage that the reader *already
>> understands* how DOI Names work.
>>
>>>       As a DOI Name, the resolution of EIDR-NSS is handled by the ISO
>>>       26324 Registration Authority.
>>>
>>>       The ISO 26324 Registration Authority operates a web service that
>>>       allows an EIDR-NSS to be resolved by issuing an HTTP GET request
>>>       to the following URI:
>>>
>>>                "http://doi.org/" DOI-PREFIX "/" DOI-SUFFIX
>>
>> As written, this doesn't specify anything, because you can apply that
>> process to any alleged EIDR.  In order to make this meaningful, you
>> have to specify what the format of the HTTP *response* is and the
>> significance of the elements of the response.  (Presumably there is an
>> ISO standard you can reference here.)
>>
>> Dale

--089e0149c18627b9ea04f2e0473e
Content-Type: text/plain; charset=US-ASCII; name="EIDR-URN-app-20140220.txt"
Content-Disposition: attachment; filename="EIDR-URN-app-20140220.txt"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_hrwrczwk0

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqIE5PVCBBTiBJLUQgKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqCgoKCk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgUC4gTGVtaWV1eApJbnRlcm5ldC1EcmFmdCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgU2FuZGZsb3cgQ29uc3VsdGluZyBMTEMKRXhwaXJl
czogWFhYWFhYWFhYWFhYWFhYICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFhYWFhYWFhY
WFhYWFhYWFhYCgoKICAgRW50ZXJ0YWlubWVudCBJZGVudGlmaWVyIFJlZ2lzdHJ5IChFSURSKSBV
Uk4gTmFtZXNwYWNlIERlZmluaXRpb24KICAgICAgICAgICAgICAgICAgICAgICAgIGRyYWZ0LXBh
bC1laWRyLXVybi0weAoKQWJzdHJhY3QKCiAgIEVudGVydGFpbm1lbnQgSWRlbnRpZmllciBSZWdp
c3RyeSAoRUlEUikgSWRlbnRpZmllcnMgYXJlIHVzZWQgZm9yIHRoZQogICBnbG9iYWwgdW5pcXVl
IGlkZW50aWZpY2F0aW9uIG9mIG1vdGlvbiBwaWN0dXJlIGFuZCB0ZWxldmlzaW9uCiAgIGNvbnRl
bnQuICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIGZvcm1hbCBVbmlmb3JtIFJlc291cmNlIE5h
bWUKICAgKFVSTikgTmFtZXNwYWNlIElkZW50aWZpZXIgKE5JRCkgZm9yIEVJRFIgSWRlbnRpZmll
cnMuCgpTdGF0dXMgb2YgVGhpcyBNZW1vCgogICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1p
dHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4
IGFuZCBCQ1AgNzkuCgogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9m
IHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwogICBUYXNrIEZvcmNlIChJRVRGKS4gIE5vdGUgdGhh
dCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQogICB3b3JraW5nIGRvY3VtZW50cyBh
cyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LQogICBEcmFm
dHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly4KCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0g
b2Ygc2l4IG1vbnRocwogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0
ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0
ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQogICBtYXRlcmlhbCBvciB0byBj
aXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iCgogICBUaGlzIEludGVy
bmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIFhYWFhYWFhYWFhYWFhYWC4KCkNvcHlyaWdodCBOb3Rp
Y2UKCiAgIENvcHlyaWdodCAoYykgMjAxNCBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVu
dGlmaWVkIGFzIHRoZQogICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4K
CiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0
J3MgTGVnYWwKICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0
cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUg
b2YKICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2Ug
ZG9jdW1lbnRzCiAgIGNhcmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQg
cmVzdHJpY3Rpb25zIHdpdGggcmVzcGVjdAogICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21w
b25lbnRzIGV4dHJhY3RlZCBmcm9tIHRoaXMgZG9jdW1lbnQgbXVzdAogICBpbmNsdWRlIFNpbXBs
aWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LmUgb2YKICAg
dGhlIFRydXN0IExlZ2FsIFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0IHdhcnJh
bnR5IGFzCiAgIGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS4KCgoKCgpM
ZW1pZXV4ICAgICAgICAgICAgICAgICAgRXhwaXJlcyBYWFhYWFhYWFhYWFhYWFggICAgICAgICAg
ICAgICAgW1BhZ2UgMV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgRUlEUiBVUk4gTmFtZXNwYWNl
IERlZmluaXRpb24gICAgICAgIFhYWFhYWFhYWFhYWFgKCgoxLiAgSW50cm9kdWN0aW9uCgogICBU
aGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIGZvcm1hbCBVbmlmb3JtIFJlc291cmNlIE5hbWUgKFVS
TikKICAgTmFtZXNwYWNlIElkZW50aWZpZXIgKE5JRCkgZm9yIEVJRFIgSWRlbnRpZmllcnMuCgog
ICBFSURSIElkZW50aWZpZXJzIGFyZSBjZW50cmFsbHkgcmVnaXN0ZXJlZCwgZ2xvYmFsbHkgdW5p
cXVlCiAgIGlkZW50aWZpZXJzIGZvciBhdWRpb3Zpc3VhbCB3b3JrcyBhbmQgdGhlaXIgdmFyaWFu
dHMsIHByaW1hcmlseSBmaWxtCiAgIGFuZCB0ZWxldmlzaW9uLiAgQSB1bmlxdWUgc2V0IG9mIG1l
dGFkYXRhIHBhcmFtZXRlcnMgZGVzY3JpYmluZyB0aGUKICAgYXNzb2NpYXRlZCB3b3JrIGlzIGJv
dW5kIHRvIHRoZSBFSURSIElkZW50aWZpZXIgYXQgdGltZSBvZgogICByZWdpc3RyYXRpb24uCgog
ICBFSURSIElkZW50aWZpZXJzIGFyZSBhIHNwZWNpYWwga2luZCBvZiBET0kgTmFtZXMgYWxsb2Nh
dGVkIGJ5IEVJRFIKICAgQXNzb2NpYXRpb24gc3BlY2lmaWNhbGx5IGZvciBhdWRpb3Zpc3VhbCB3
b3Jrcy4gIFRoZSBEaWdpdGFsIE9iamVjdAogICBJZGVudGlmaWVyIChET0kpIHN5c3RlbSBwcm92
aWRlcyBhbiBpbmZyYXN0cnVjdHVyZSBmb3IgcGVyc2lzdGVudAogICB1bmlxdWUgaWRlbnRpZmlj
YXRpb24gb2Ygb2JqZWN0cyBvZiBhbnkgdHlwZSwgYW5kIGlzIHNwZWNpZmllZCBpbgogICBbSVNP
MjYyMzRdLiAgQSBET0kgbmFtZSBpcyB0aGUgaWRlbnRpZmllciB0aGF0IGlzIHBlcm1hbmVudGx5
CiAgIGFzc2lnbmVkIHRvIGFuIG9iamVjdC4gIFRoZSB1c2Ugb2YgRE9JIE5hbWVzIGVuc3VyZXMg
cGVyc2lzdGVuY2UsCiAgIGdsb2JhbCB1bmlxdWVuZXNzIGFuZCBhbiBvcGVuIHJlc29sdXRpb24g
aW5mcmFzdHJ1Y3R1cmUuCgogICBBcyBhIERPSSBOYW1lLCBhbiBFSURSIElkZW50aWZpZXIgaGFz
IHR3byBjb21wb25lbnRzOiBhIHByZWZpeAogICBhc3NpZ25lZCBleGNsdXNpdmVseSB0byBFSURS
IEFzc29jaWF0aW9uIGJ5IHRoZSBET0kgUmVnaXN0cmF0aW9uCiAgIEF1dGhvcml0eSBhbmQgYSBz
dWZmaXggZGVmaW5lZCBieSBFSURSIEFzc29jaWF0aW9uLiAgQ3VycmVudGx5LCBFSURSCiAgIElk
ZW50aWZpZXJzIHVzZSB0aGUgcHJlZml4ICIxMC41MjQwIiwgYnV0IGFkZGl0aW9uYWwgcHJlZml4
ZXMgbWlnaHQKICAgYmUgaW50cm9kdWNlZCBpbiB0aGUgZnV0dXJlLgoKICAgVGhlIGZvbGxvd2lu
ZyBpcyBhbiBleGFtcGxlIG9mIGFuIEVJRFIgSWRlbnRpZmllciBpbiBpdHMgY2Fub25pY2FsCiAg
IHJlcHJlc2VudGF0aW9uOgoKICAgICAgICAgICAxMC41MjQwLzY4REQtMzQxRS0wM0VFLTRCQjgt
MTc2MS1RCgogICB3aGVyZSAiMTAuNTI0MCIgaXMgdGhlIHByZWZpeCBhbmQgIjY4REQtMzQxRS0w
M0VFLTRCQjgtMTc2MS1RIiBpcyB0aGUKICAgc3VmZml4LiAgVGhlIGNhbm9uaWNhbCBVUk4gcmVw
cmVzZW50YXRpb24gb2YgdGhlIHNhbWUgRUlEUiBJZGVudGlmaWVyCiAgIGlzOgoKICAgICAgICAg
ICB1cm46ZWlkcjoxMC41MjQwOjY4REQtMzQxRS0wM0VFLTRCQjgtMTc2MS1RCgogICBOb3RlIHRo
YXQgIjoiIGlzIHVzZWQgYXMgc2VwYXJhdG9yIGJldHdlZW4gcHJlZml4IGFuZCBzdWZmaXggc2lu
Y2UgIi8KICAgIiBpcyBhIFVSTiByZXNlcnZlZCBjaGFyYWN0ZXIuCgogICBbRUlEUi1PVkVSVklF
V10gYW5kIFtFSURSLUlOVFJPXSBwcm92aWRlIGFkZGl0aW9uYWwgYmFja2dyb3VuZAogICBpbmZv
cm1hdGlvbi4KCjIuICBVUk4gTmFtZXNwYWNlIERlZmluaXRpb24gVGVtcGxhdGUKCiAgIFRoZSBm
b2xsb3dpbmcgdGVtcGxhdGUgaXMgcHJvdmlkZWQgaW4gYWNjb3JkYW5jZSB3aXRoIFtSRkMzNDA2
XS4KCiAgIE5hbWVzcGFjZSBJRDoKCgoKCkxlbWlldXggICAgICAgICAgICAgICAgICBFeHBpcmVz
IFhYWFhYWFhYWFhYWFhYWCAgICAgICAgICAgICAgICBbUGFnZSAyXQoMCkludGVybmV0LURyYWZ0
ICAgICAgICBFSURSIFVSTiBOYW1lc3BhY2UgRGVmaW5pdGlvbiAgICAgICAgWFhYWFhYWFhYWFhY
WAoKCiAgICAgIEVJRFIKCiAgIFJlZ2lzdHJhdGlvbiBJbmZvcm1hdGlvbjoKCiAgICAgIFZlcnNp
b24gMQoKICAgICAgMjAxNC0wMi0wNAoKICAgRGVjbGFyZWQgcmVnaXN0cmFudCBvZiB0aGUgbmFt
ZXNwYWNlOgoKICAgICAgTmFtZToKCiAgICAgICAgIEVudGVydGFpbm1lbnQgSWRlbnRpZmllciBS
ZWdpc3RyeSBBc3NvY2lhdGlvbgoKICAgICAgQWRkcmVzczoKCiAgICAgICAgIDE1MTUgQ29yZGls
bGVyYXMgUm9hZC4KICAgICAgICAgUmVkd29vZCBDaXR5LCBDQSA5NDA2MgogICAgICAgICBVU0EK
CiAgICAgIENvbnRhY3Q6CgogICAgICAgICBSaWNoYXJkIEtyb29uCiAgICAgICAgIEUtbWFpbDog
cmtyb29uQGVpZHIub3JnCgogICBEZWNsYXJhdGlvbiBvZiBzeW50YWN0aWMgc3RydWN0dXJlOgoK
ICAgICAgQW4gRUlEUiBJZGVudGlmaWVyIGlzIGEgc3BlY2lhbCBraW5kIG9mIERPSSBOYW1lIChz
ZWUgW0lTTzI2MjM0XSkKICAgICAgYW5kLCBhcyBzdWNoLCBjb25zaXN0cyBvZiB0d28gY29tcG9u
ZW50czogYSBwcmVmaXggZGVub3RlZCBFSURSLQogICAgICBQUkVGSVggYW5kIGEgc3VmZml4IGRl
bm90ZWQgRUlEUi1TVUZGSVguICBUaGUgVVJOIHJlcHJlc2VudGF0aW9uCiAgICAgIFVSTi1FSURS
IG9mIGFuIEVJRFIgSWRlbnRpZmllciBjb25mb3JtcyB0byB0aGUgc3ludGF4IChleHByZXNzZWQK
ICAgICAgdXNpbmcgW1JGQzUyMzRdKToKCiAgICAgICAgICAgVVJOLUVJRFIgPSAidXJuOmVpZHI6
IiBFSURSLU5TUwogICAgICAgICAgIEVJRFItTlNTID0gRUlEUi1QUkVGSVggIjoiIEVJRFItU1VG
RklYCiAgICAgICAgICAgRUlEUi1QUkVGSVggPSAxKkVJRFItQ0hBUlMKICAgICAgICAgICBFSURS
LVNVRkZJWCA9IDEqRUlEUi1DSEFSUwogICAgICAgICAgIEVJRFItQ0hBUlMgPSBBTFBIQSAvIERJ
R0lUIC8gIi0iIC8gIi4iIC8gIl8iCgoKICAgICAgVGhlIG9ubHkgdmFsdWUgb2YgRUlEUi1QUkVG
SVggY3VycmVudGx5IGluIHVzZSBpcyAiMTAuNTI0MCIuCiAgICAgIEFkZGl0aW9uYWwgcHJlZml4
IHZhbHVlcyBjb25mb3JtaW5nIHRvIHRoZSBFSURSLVBSRUZJWCBzeW50YXgKICAgICAgbWlnaHQg
YmUgaW50cm9kdWNlZCBieSBFSURSIG9yZ2FuaXphdGlvbiBpbiB0aGUgZnV0dXJlLiAgRWFjaCBv
ZgogICAgICB0aGVzZSBhZGRpdGlvbmFsIHByZWZpeCB2YWx1ZXMgd2lsbCBpbiBhbGwgY2FzZXMg
YmUgYXNzb2NpYXRlZAogICAgICB3aXRoIHN1ZmZpeCB2YWx1ZXMgdGhhdCBjb25mb3JtIHRvIGEg
c3Vic2V0IG9mIHRoZSBFSURSLVNVRkZJWAogICAgICBzeW50YXguICBUaGVzZSBhZGRpdGlvbmFs
IHByZWZpeGVzIGFuZCB0aGVpciBjb3JyZXNwb25kaW5nCiAgICAgIHN1ZmZpeGVzIHdpbGwgYmUg
ZG9jdW1lbnRlZCBpbiBmdXR1cmUgcmV2aXNpb25zIHRvIHRoaXMKICAgICAgcmVnaXN0cmF0aW9u
LgoKCgpMZW1pZXV4ICAgICAgICAgICAgICAgICAgRXhwaXJlcyBYWFhYWFhYWFhYWFhYWFggICAg
ICAgICAgICAgICAgW1BhZ2UgM10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgRUlEUiBVUk4gTmFt
ZXNwYWNlIERlZmluaXRpb24gICAgICAgIFhYWFhYWFhYWFhYWFgKCgogICAgICBBbiBpbXBsZW1l
bnRhdGlvbiBjYW4gcHJvY2VzcyBhbiBFSURSLU5TUyB3aXRoIGFuIHVua25vd24gcHJlZml4CiAg
ICAgIGFzIGFuIG9wYXF1ZSBzdHJpbmcgcGVyIHRoZSBTZWN0aW9uICJydWxlcyBvZiBsZXhpY2Fs
CiAgICAgIGVxdWl2YWxlbmNlIiwgYW5kIHJlc29sdmUgaXQgYXMgYSBnZW5lcmljIERPSSBOYW1l
IHBlciB0aGUKICAgICAgU2VjdGlvbiAicHJvY2VzcyBmb3IgaWRlbnRpZmllciByZXNvbHV0aW9u
Ii4KCiAgICAgIFdoZW4gRUlEUi1QUkVGSVggaXMgZXF1YWwgdG8gIjEwLjUyNDAiLCB0aGUgc3lu
dGF4IG9mIEVJRFItU1VGRklYCiAgICAgIGlzIGZ1cnRoZXIgY29uc3RyYWluZWQgYWNjb3JkaW5n
IHRvIHRoZSB0byBSUDIwNzktU1VGRklYIHN5bnRheAogICAgICBzcGVjaWZpZWQgaW4gW1NNUFRF
UlAyMDc5XToKCiAgICAgICAgICAgUlAyMDc5LVNVRkZJWCA9IDUoNEhFWERJRyAiLSIpIENIRUNL
CiAgICAgICAgICAgQ0hFQ0sgICAgICAgICA9IERJR0lUIC8gQUxQSEEKCiAgICAgIHdoZXJlIENI
RUNLIGlzIHRoZSBNb2QgMzcsMzYgY2hlY2sgY2hhcmFjdGVyIGFzIHNwZWNpZmllZCBpbgogICAg
ICBbSVNPNzA2NF0sIGNvbXB1dGVkIG92ZXIgdGhlIDIwIGhleGFkZWNpbWFsIGRpZ2l0cyBIRVhE
SUcgb2YKICAgICAgUlAyMDc5LVNVRkZJWC4KCiAgICAgIEVYQU1QTEU6IHVybjplaWRyOjEwLjUy
NDA6NjhERC0zNDFFLTAzRUUtNEJCOC0xNzYxLVEKCiAgIFJlbGV2YW50IGFuY2lsbGFyeSBkb2N1
bWVudGF0aW9uOgoKICAgICAgW0lTTzI2MjM0XSBzcGVjaWZpZXMgRE9JIE5hbWUgc3ludGF4IGFu
ZCByZWdpc3RyYXRpb24uCgogICAgICBbU01QVEVSUDIwNzldIHNwZWNpZmllcyB0aGUgc3ludGF4
IG9mIEVJRFIgSWRlbnRpZmllciB3aXRoIHRoZQogICAgICBwcmVmaXggIjEwLjUyNDAiLgoKICAg
SWRlbnRpZmllciB1bmlxdWVuZXNzIGNvbnNpZGVyYXRpb25zOgoKICAgICAgQW4gRUlEUiBJZGVu
dGlmaWVyIGlzIGEgRE9JIE5hbWUuICBUaGUgSVNPIDI2MzI0IFJlZ2lzdHJhdGlvbgogICAgICBB
dXRob3JpdHkgZW5zdXJlcyB0aGF0IERPSSBOYW1lIHVuaXF1ZW5lc3MsIHRoZXJlZm9yZSB0aGUg
VVJOLUVJRFIKICAgICAgZGVyaXZlZCBmcm9tIGFuIEVJRFIgSWRlbnRpZmllciBpcyBndWFyYW50
ZWVkIHVuaXF1ZSBhbmQgbmV2ZXIKICAgICAgcmVhc3NpZ25lZC4KCiAgICAgIEZ1cnRoZXJtb3Jl
LCBhbiBFSURSIElkZW50aWZpZXIgaXMgYXNzb2NpYXRlZCB3aXRoIGEgc2luZ2xlIFVSTi0KICAg
ICAgRUlEUi4KCiAgIElkZW50aWZpZXIgcGVyc2lzdGVuY2UgY29uc2lkZXJhdGlvbnM6CgogICAg
ICBBbiBFSURSIElkZW50aWZpZXIgaXMgYSBET0kgTmFtZS4gIFRoZSBJU08gMjYzMjQgUmVnaXN0
cmF0aW9uCiAgICAgIEF1dGhvcml0eSBlbnN1cmVzIHRoYXQgYSBET0kgTmFtZSByZW1haW5zIHZh
bGlkIGluZGVmaW5pdGVseSwKICAgICAgdGhlcmVmb3JlIHRoZSBVUk4tRUlEUiBkZXJpdmVkIGZy
b20gYW4gRUlEUiBJZGVudGlmaWVyIHJlbWFpbnMKICAgICAgdmFsaWQgaW5kZWZpbml0ZWx5LgoK
ICAgUHJvY2VzcyBvZiBpZGVudGlmaWVyIGFzc2lnbm1lbnQ6CgogICAgICBUaGUgRUlEUiBBc3Nv
Y2lhdGlvbiByZWdpc3RlcnMgZWFjaCBFSURSIElkZW50aWZpZXIgd2l0aCB0aGUgSVNPCiAgICAg
IDI2MzI0IFJlZ2lzdHJhdGlvbiBBdXRob3JpdHkuCgoKCgoKTGVtaWV1eCAgICAgICAgICAgICAg
ICAgIEV4cGlyZXMgWFhYWFhYWFhYWFhYWFhYICAgICAgICAgICAgICAgIFtQYWdlIDRdCgwKSW50
ZXJuZXQtRHJhZnQgICAgICAgIEVJRFIgVVJOIE5hbWVzcGFjZSBEZWZpbml0aW9uICAgICAgICBY
WFhYWFhYWFhYWFhYCgoKICAgICAgRW50aXRpZXMgaW52b2x2ZWQgaW4gdGhlIG1vdGlvbiBwaWN0
dXJlIGFuZCB0ZWxldmlzaW9uIGluZHVzdHJ5LAogICAgICBlaXRoZXIgZGlyZWN0bHkgaW4gdGhl
IHByb2R1Y3Rpb24gb2YgY29udGVudCBvciBpbiBpdHMKICAgICAgZGlzdHJpYnV0aW9uIGFuZCBy
ZWxhdGVkIHNlcnZpY2VzLCBhcmUgZWxpZ2libGUgdG8gYXBwbHkgZm9yCiAgICAgIHJlZ2lzdHJh
bnQgc3RhdHVzLiAgUmVnaXN0cmFudHMgcGF5IGFuIGFubnVhbCBtZW1iZXJzaGlwIGZlZSB0aGF0
CiAgICAgIGRlcGVuZHMgb24gdGhlIHNpemUgb2YgdGhlIGNvbXBhbnkuCgogICBQcm9jZXNzIGZv
ciBpZGVudGlmaWVyIHJlc29sdXRpb246CgogICAgICBBcyBhIERPSSBOYW1lLCB0aGUgcmVzb2x1
dGlvbiBvZiB0aGUgRUlEUiBJZGVudGlmaWVyIGFzc29jaWF0ZWQKICAgICAgd2l0aCBhbiBFSURS
LU5TUyBpcyBoYW5kbGVkIGJ5IHRoZSBJU08gMjYzMjQgUmVnaXN0cmF0aW9uCiAgICAgIEF1dGhv
cml0eS4KCiAgICAgIFRoZSBJU08gMjYzMjQgUmVnaXN0cmF0aW9uIEF1dGhvcml0eSBvcGVyYXRl
cyBhIHdlYiBzZXJ2aWNlIHRoYXQKICAgICAgYWxsb3dzIHRoZSBFSURSIElkZW50aWZpZXIgYXNz
b2NpYXRlZCB3aXRoIGFuIEVJRFItTlNTIHRvIGJlCiAgICAgIHJlc29sdmVkIGJ5IGlzc3Vpbmcg
YW4gSFRUUCBHRVQgcmVxdWVzdCB0byB0aGUgZm9sbG93aW5nIFVSSSAoc2VlCiAgICAgIFtSRkMy
NjE2XSk6CgogICAgICAgICAgICAgICAiaHR0cDovL2RvaS5vcmcvIiBFSURSLVBSRUZJWCAiLyIg
RUlEUi1TVUZGSVgKCiAgICAgIElmIHRoZSBFSURSIElkZW50aWZpZXIgZXhpc3RzLCB0aGVuIGFu
IFhNTCBTY2hlbWEgaW5zdGFuY2UKICAgICAgZG9jdW1lbnQgKHNlZSBbWE1MU2NoZW1hXSkgY29u
dGFpbmluZyBtZXRhZGF0YSBhc3NvY2lhdGVkIHdpdGggdGhlCiAgICAgIEVJRFIgSWRlbnRpZmll
ciBpcyByZXR1cm5lZCwgb3RoZXJ3aXNlIHRoZSBIVFRQIHN0YXR1cyBjb2RlICI0MDQKICAgICAg
Tm90IEZvdW5kIiBpcyByZXR1cm5lZC4KCiAgICAgIEVYQU1QTEU6IGh0dHA6Ly9kb2kub3JnLzEw
LjUyNDAvNjhERC0zNDFFLTAzRUUtNEJCOC0xNzYxLVEKCiAgIFJ1bGVzIGZvciBMZXhpY2FsIEVx
dWl2YWxlbmNlOgoKICAgICAgTGV4aWNhbCBlcXVpdmFsZW5jZSBvZiBFSURSLVVSTiBpcyBkZWZp
bmVkIGJ5IGNhc2UtaW5zZW5zaXRpdmUKICAgICAgc3RyaW5nIG1hdGNoLgoKICAgQ29uZm9ybWFu
Y2Ugd2l0aCBVUk4gU3ludGF4OgoKICAgICAgQXMgc3BlY2lmaWVkIGFib3ZlLCB0aGUgc3ludGF4
IG9mIEVJRFItVVJOIGlzIGEgc3Vic2V0IG9mIHRoZSBVUk4KICAgICAgc3ludGF4IHNwZWNpZmll
ZCBpbiBbUkZDMjE0MV0uCgogICBWYWxpZGF0aW9uIG1lY2hhbmlzbToKCiAgICAgIFRoZSB2YWxp
ZGl0eSBvZiBhbiBFSURSLU5TUyBjYW4gb25seSBiZSBndWFyYW50ZWVkIGJ5IGNvbXBsZXRpbmcK
ICAgICAgdGhlIHJlc29sdXRpb24gcHJvY2Vzcy4KCiAgICAgIEZvciBFSURSLU5TUyB3aXRoIGFu
IEVJRFItUFJFRklYIGVxdWFsIHRvICIxMC41MjQwIiwgdGhlIENIRUNLCiAgICAgIHZhbHVlIGNh
biBiZSB1c2VkIGZvciBpbnRlZ3JpdHkgY2hlY2tpbmcsIGFzIHNwZWNpZmllZCBhYm92ZS4KCiAg
IFNjb3BlOgoKICAgICAgRUlEUiBJZGVudGlmaWVycyBhcmUgY2VudHJhbGx5IHJlZ2lzdGVyZWQs
IGdsb2JhbGx5IHVuaXF1ZQogICAgICBpZGVudGlmaWVycyBmb3IgdXNlIHdpdGggYXVkaW92aXN1
YWwgd29ya3Mgd29ybGR3aWRlLgoKCgpMZW1pZXV4ICAgICAgICAgICAgICAgICAgRXhwaXJlcyBY
WFhYWFhYWFhYWFhYWFggICAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFmdCAg
ICAgICAgRUlEUiBVUk4gTmFtZXNwYWNlIERlZmluaXRpb24gICAgICAgIFhYWFhYWFhYWFhYWFgK
CgozLiAgTmFtZXNwYWNlIENvbnNpZGVyYXRpb25zCgogICBFSURSIElkZW50aWZpZXJzIGFyZSBp
bnRlbmRlZCBmb3IgdXNlIGluIEludGVybmV0IGFwcGxpY2F0aW9ucywgd2hlcmUKICAgVVJOcyBh
cmUgcm91dGluZWx5IHVzZWQgdG8gaWRlbnRpZnkgYXVkaW92aXN1YWwgcmVzb3VyY2VzLiAgVGhl
cmUgaXMKICAgbm8gZGlyZWN0IG1hcHBpbmcgZnJvbSBFSURSIElkZW50aWZpZXJzIHRvIGV4aXN0
aW5nIFVSTiBuYW1lcHNhY2VzLgoKNC4gIENvbW11bml0eSBDb25zaWRlcmF0aW9ucwoKICAgVGhl
IHByaW1hcnkgcmVnaXN0cmFudHMgb2YgRUlEUiBJZGVudGlmaWVycyBhcmUgcHJvZHVjZXJzIGFu
ZAogICBkaXN0cmlidXRvcnMgb2YgYXVkaW92aXN1YWwgd29ya3MsIG1ldGFkYXRhIGFnZ3JlZ2F0
b3JzLCBhbmQKICAgYXVkaW92aXN1YWwgYXJjaGl2ZXMuICBBbnkgYm9uYSBmaWRlIG1lbWJlciBv
ZiB0aGUgZWNvc3lzdGVtIGNhbgogICBiZWNvbWUgYW4gRUlEUiBtZW1iZXIgYW5kIHJlZ2lzdGVy
IGFueSB3b3JrLiAgRUlEUiBpZGVudGlmaWVycyBjYW4gYmUKICAgdXNlZCBieSBhbnlvbmUgdG8g
dW5hbWJpZ3VvdXNseSBpZGVudGlmeSBhbiBhdWRpb3Zpc3VhbCBhc3NldCBhbmQKICAgcmV0cmll
dmUgdW5kZXJseWluZyBtZXRhZGF0YS4gIFRoZSBwcmltYXJ5IGJlbmVmaXRzIG9mIGl0cyB1c2Ug
YXJlCiAgIGFzc29jaWF0ZWQgd2l0aCB3b3JrcyBpbiB3aWRlIGRpc3RyaWJ1dGlvbiwgbWFuYWdl
bWVudCBvZiBsb25nIG9yCiAgIGNvbXBsZXggZGlzdHJpYnV0aW9uIGNoYWlucywgYW5kIGFnZ3Jl
Z2F0aW9uIG9mIGluZm9ybWF0aW9uIGZyb20KICAgbXVsdGlwbGUgc291cmNlcy4KCjUuICBJQU5B
IENvbnNpZGVyYXRpb25zCgogICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBVUk4gTklEIHJlZ2lz
dHJhdGlvbiB0aGF0IGlzIHRvIGJlIGVudGVyZWQKICAgaW50byB0aGUgSUFOQSByZWdpc3RyeSBv
ZiBVUk4gTklEcy4gIEl0IHNwZWNpZmljYWxseSByZXF1ZXN0cyB0aGUKICAgRUlEUiBOSUQuCgo2
LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMKCiAgIFRoaXMgZG9jdW1lbnQgb25seSBzcGVjaWZp
ZXMgdGhlIHN5bnRheCBvZiB0aGUgRUlEUi1VUk4gbmFtZXNwYWNlLAogICBhbmQgaXMgdGhlcmVm
b3JlIHNlY3VyaXR5LW5ldXRyYWwuICBUaGUgZGV0YWlscyBhc3NpZ25tZW50IGFuZAogICByZXNv
bHV0aW9uIHByb2Nlc3NlcyBhcmUgZGVmaW5lZCBleHRlcm5hbCB0byB0aGlzIGRvY3VtZW50IGJ5
IHRoZQogICBFSURSIEFzc29jaWF0aW9uIGFuZCB0aGUgSVNPIDI2MzI0IFJlZ2lzdHJhdGlvbiBB
dXRob3JpdHksIGFuZCB0aHVzCiAgIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQu
Cgo3LiAgUmVmZXJlbmNlcwoKNy4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtSRkMyMTQx
XSAgTW9hdHMsIFIuLCAiVVJOIFN5bnRheCIsIFJGQyAyMTQxLCBNYXkgMTk5Ny4KCiAgIFtSRkM1
MjM0XSAgQ3JvY2tlciwgRC4gYW5kIFAuIE92ZXJlbGwsICJBdWdtZW50ZWQgQk5GIGZvciBTeW50
YXgKICAgICAgICAgICAgICBTcGVjaWZpY2F0aW9uczogQUJORiIsIFNURCA2OCwgUkZDIDUyMzQs
IEphbnVhcnkgMjAwOC4KCiAgIFtJU08yNjIzNF0KICAgICAgICAgICAgICBJbnRlcm5hdGlvbmFs
IE9yZ2FuaXphdGlvbiBmb3IgU3RhbmRhcmRpemF0aW9uLAogICAgICAgICAgICAgICJJbmZvcm1h
dGlvbiBhbmQgZG9jdW1lbnRhdGlvbiAtIERpZ2l0YWwgb2JqZWN0IGlkZW50aWZpZXIKICAgICAg
ICAgICAgICBzeXN0ZW0iLCBJU08gU3RhbmRhcmQgMjYzMjQsIDIwMTIuCgoKCgoKCkxlbWlldXgg
ICAgICAgICAgICAgICAgICBFeHBpcmVzIFhYWFhYWFhYWFhYWFhYWCAgICAgICAgICAgICAgICBb
UGFnZSA2XQoMCkludGVybmV0LURyYWZ0ICAgICAgICBFSURSIFVSTiBOYW1lc3BhY2UgRGVmaW5p
dGlvbiAgICAgICAgWFhYWFhYWFhYWFhYWAoKCiAgIFtJU083MDY0XSAgSW50ZXJuYXRpb25hbCBP
cmdhbml6YXRpb24gZm9yIFN0YW5kYXJkaXphdGlvbiwKICAgICAgICAgICAgICAiSW5mb3JtYXRp
b24gdGVjaG5vbG9neSAtIFNlY3VyaXR5IHRlY2huaXF1ZXMgLSBDaGVjawogICAgICAgICAgICAg
IGNoYXJhY3RlciBzeXN0ZW1zIiwgSVNPIFN0YW5kYXJkIDcwNjQsIDIwMDMuCgogICBbU01QVEVS
UDIwNzldCiAgICAgICAgICAgICAgU29jaWV0eSBvZiBNb3Rpb24gUGljdHVyZSBhbmQgVGVsZXZp
c2lvbiBFbmdpbmVlcnMsCiAgICAgICAgICAgICAgIkRpZ2l0YWwgT2JqZWN0IElkZW50aWZpZXIg
KERPSSkgTmFtZSBhbmQgRW50ZXJ0YWlubWVudCBJRAogICAgICAgICAgICAgIFJlZ2lzdHJ5IChF
SURSKSBJZGVudGlmaWVyIFJlcHJlc2VudGF0aW9ucyIsIFNNUFRFIFJQCiAgICAgICAgICAgICAg
MjA3OSwgMjAxNC4KCjcuMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtYTUxTY2hlbWFd
CiAgICAgICAgICAgICAgSG9sc3RlZ2UsIE0uIGFuZCBBLiBWZWRhbXV0aHUsICJXM0MgWE1MIFNj
aGVtYSBEZWZpbml0aW9uCiAgICAgICAgICAgICAgTGFuZ3VhZ2UgKFhTRCk6IENvbXBvbmVudCBE
ZXNpZ25hdG9ycyIsIFdvcmxkIFdpZGUgV2ViCiAgICAgICAgICAgICAgQ29uc29ydGl1bSBDUiBD
Ui14bWxzY2hlbWEtcmVmLTIwMTAwMTE5LCBKYW51YXJ5IDIwMTAsCiAgICAgICAgICAgICAgPGh0
dHA6Ly93d3cudzMub3JnL1RSLzIwMTAvQ1IteG1sc2NoZW1hLXJlZi0yMDEwMDExOT4uCgogICBb
UkZDMjYxNl0gIEZpZWxkaW5nLCBSLiwgR2V0dHlzLCBKLiwgTW9ndWwsIEouLCBGcnlzdHlrLCBI
LiwKICAgICAgICAgICAgICBNYXNpbnRlciwgTC4sIExlYWNoLCBQLiwgYW5kIFQuIEJlcm5lcnMt
TGVlLCAiSHlwZXJ0ZXh0CiAgICAgICAgICAgICAgVHJhbnNmZXIgUHJvdG9jb2wgLS0gSFRUUC8x
LjEiLCBSRkMgMjYxNiwgSnVuZSAxOTk5LgoKICAgW1JGQzM0MDZdICBEYWlnbGUsIEwuLCB2YW4g
R3VsaWssIEQuLCBJYW5uZWxsYSwgUi4sIGFuZCBQLiBGYWx0c3Ryb20sCiAgICAgICAgICAgICAg
IlVuaWZvcm0gUmVzb3VyY2UgTmFtZXMgKFVSTikgTmFtZXNwYWNlIERlZmluaXRpb24KICAgICAg
ICAgICAgICBNZWNoYW5pc21zIiwgQkNQIDY2LCBSRkMgMzQwNiwgT2N0b2JlciAyMDAyLgoKICAg
W0VJRFItT1ZFUlZJRVddCiAgICAgICAgICAgICAgRW50ZXJ0YWlubWVudCBJZGVudGlmaWVyIFJl
Z2lzdHJ5IEFzc29jaWF0aW9uLCAiRUlEUgogICAgICAgICAgICAgIE92ZXJ2aWV3IiwgTm92ZW1i
ZXIgMjAxMywgPGh0dHA6Ly9laWRyLm9yZy9kb2N1bWVudHMvCiAgICAgICAgICAgICAgMjAxMy0x
MS0wMV9FSURSX092ZXJ2aWV3X0ZJTkFMLnBkZj4uCgogICBbRUlEUi1JTlRST10KICAgICAgICAg
ICAgICBFbnRlcnRhaW5tZW50IElkZW50aWZpZXIgUmVnaXN0cnkgQXNzb2NpYXRpb24sICJFSURS
OiBJRAogICAgICAgICAgICAgIEZvcm1hdCBWZXIuIDEuMSIsIEF1Z3VzdCAyMDEzLAogICAgICAg
ICAgICAgIDxodHRwOi8vZWlkci5vcmcvZG9jdW1lbnRzL0VJRFJfSURfRm9ybWF0X3YxLjEucGRm
Pi4KCkF1dGhvcidzIEFkZHJlc3MKCiAgIFBpZXJyZS1BbnRob255IExlbWlldXgKICAgU2FuZGZs
b3cgQ29uc3VsdGluZyBMTEMKCiAgIEVtYWlsOiBwYWxAc2FuZGZsb3cuY29tCgoKCgoKCgoKCkxl
bWlldXggICAgICAgICAgICAgICAgICBFeHBpcmVzIFhYWFhYWFhYWFhYWFhYWCAgICAgICAgICAg
ICAgICBbUGFnZSA3XQo=
--089e0149c18627b9ea04f2e0473e--


From nobody Thu Feb 20 18:13:04 2014
Return-Path: <Phillip.Maness@dts.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 CD83E1A03BD for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 18:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, 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 gmXulhsPK4ZY for <urn-nid@ietfa.amsl.com>; Thu, 20 Feb 2014 18:12:59 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF941A03C4 for <urn-nid@apps.ietf.org>; Thu, 20 Feb 2014 18:12:56 -0800 (PST)
Received: from BY2PR01CA002.prod.exchangelabs.com (10.255.247.32) by BY2PR01MB121.prod.exchangelabs.com (10.242.38.152) with Microsoft SMTP Server (TLS) id 15.0.883.10; Fri, 21 Feb 2014 02:12:51 +0000
Received: from BN1AFFO11FD035.protection.gbl (2a01:111:f400:7c10::100) by BY2PR01CA002.outlook.office365.com (2a01:111:e400:2c16::32) with Microsoft SMTP Server (TLS) id 15.0.883.10 via Frontend Transport; Fri, 21 Feb 2014 02:12:51 +0000
Received: from LAX-EXCA02.dts.local (207.178.146.195) by BN1AFFO11FD035.mail.protection.outlook.com (10.58.52.159) with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Fri, 21 Feb 2014 02:12:51 +0000
Received: from LAX-EXMB02.dts.local ([fe80::b50e:9af7:de19:4aa9]) by LAX-EXCA02.dts.local ([fe80::5efe:10.10.10.123%11]) with mapi id 14.03.0174.001; Thu, 20 Feb 2014 18:12:50 -0800
From: Phillip Maness <Phillip.Maness@dts.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: RE: draft RFC to describe a URN for DTS audio
Thread-Topic: draft RFC to describe a URN for DTS audio
Thread-Index: AQHPLDLBHwS6EV29SE6B2sonNGQO6Jq+gVnCgAAAptA=
Date: Fri, 21 Feb 2014 02:12:48 +0000
Message-ID: <520A56052CF01E42B1C128F990FBE681A46B8845@LAX-EXMB02.dts.local>
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> <201402172245.s1HMjnBU5200650@shell01.TheWorld.com> <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local> <201402201840.s1KIeelE5399376@shell01.TheWorld.com>
In-Reply-To: <201402201840.s1KIeelE5399376@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.10.10.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:207.178.146.195; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(377454003)(85714005)(13464003)(51914003)(189002)(199002)(51704005)(87266001)(69226001)(54316002)(44976005)(56776001)(83322001)(19580405001)(76482001)(19580395003)(561944002)(86362001)(94316002)(85306002)(95416001)(92566001)(94946001)(50466002)(81342001)(87936001)(33656001)(47736001)(50986001)(47976001)(4396001)(2656002)(95666003)(49866001)(81542001)(47446002)(74502001)(31966008)(55846006)(51856001)(74662001)(93136001)(93516002)(46102001)(80976001)(53806001)(54356001)(77096001)(74366001)(77982001)(59766001)(79102001)(81816001)(47776003)(63696002)(81686001)(20776003)(76796001)(76786001)(6806004)(92726001)(65816001)(46406003)(90146001)(56816005)(80022001)(74706001)(85852003)(74876001)(83072002)(23726002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR01MB121; H:LAX-EXCA02.dts.local; CLIP:207.178.146.195; FPR:CE2FF3E5.AEFAD3E1.F2D39BBB.46EDF94C.20609; PTR:.; MX:1; A:1; LANG:en; 
X-Forefront-PRVS: 01294F875B
X-OriginatorOrg: dts.com
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/iDGUKcMbha-6crGlKQV4G-mhtlY
Cc: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>, "Mark R. Johnson" <Mark.Johnson@dts.com>
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: Fri, 21 Feb 2014 02:13:02 -0000

Hi Dale,

Thanks for the additional insight, this is some very helpful dialog.

The primary use of this urn would by those providing services to devices th=
at contain our technologies (products made by many different CE manufacture=
rs), or devices connected to devices that contain our technology.

We don't derive revenue from service providers. Our revenues come from the =
device manufacturers who license our technologies. We also permit (in the c=
ase of audio codecs), devices to "pass-through" to downstream decoder at no=
 cost. In this case, a device (such as a streaming service box or dongle) c=
an advertise "inherited" features of a device downstream (e.g. an A/V recei=
ver attached via. HDMI).

Our objective is to enable our customers, (or rather the consumers who purc=
hase their products), the ability to derive greater benefit from the availa=
bility of our technology. This benefits us by making our technology more us=
eful, but it also benefits our customers by expanding the use of features a=
lready available in their products, and benefits the consumer (their custom=
er) by providing them a better entertainment experience.

So DTS' benefit is indirectly related to the use of the URN. I wouldn't go =
so far as to say that we will never directly benefit (financially) from the=
 use of an assigned namespace, but I can't envision such a use case at this=
 time.

I think this is consistent with how the industry consortia you cited use th=
eir namespace to benefit their members (for profit companies) to directly d=
eriving benefit by selling services.

I'm sure my explanation above could be better worded, but is this usage bet=
ter in line with the philosophy of ietf? Does this explanation help you? Wo=
uld it be beneficial to add this usage explanation in section 5?

Thanks and best regards,
Phil Maness

-----Original Message-----
From: Dale R. Worley [mailto:worley@ariadne.com]
Sent: Thursday, February 20, 2014 10:41 AM
To: Phillip Maness
Cc: urn-nid@apps.ietf.org; Mark R. Johnson
Subject: Re: draft RFC to describe a URN for DTS audio

> From: Phillip Maness <Phillip.Maness@dts.com>
>
> Sorry, I have to be intentionally vague from this point on. We have a
> number of business activities in process so we have to consider
> customers, partners and competitors (and, of course, the financial
> community, as we are a publicly traded company). The nature of these
> disclosures in publications such as an RFC can be (intentionally or
> unintentionally) indicative, (or perceived as being indicative), of
> future business.

My first impulse was to say, "I doubt you're going to get much traction wit=
h a proposal for a system of names if you're not going to admit *what* they=
 are naming."  But that is incorrect, as lots of organizations have obtaine=
d URN NIDs for such generic use.

You may have some difficulty in that DTS is a business, and has no purporte=
d public benefit purpose.  In my quick look at the NID registrations that a=
re essentially delegations to organizations, all of the organizations are g=
overnments or industry consortia which have public benefit purposes.  Grant=
ing a delegation to DTS would be setting a precedent for delegation to a bu=
siness (a straightforward for-profit entity).  Certainly the question will =
be raised, "Will it be possible to use one of these URNs in a context that =
does not cause money to flow to DTS Inc."?

(I will note that there are several mechanisms by which DTS could obtain an=
 Object ID delegation, and there is no question that businesses may do so. =
 Since all Object IDs correspond to URNs (urn:oid:...), DTS can immediately=
 obtain a URN delegation in that
manner.)

Comparing draft-pmaness-dts-urn-00 and the NID registrations for "3gpp" (RF=
C 5279), "cablelabs" (RFC 6289), and "cgi" (RFC 5138), the organizational d=
elegation registrations seem to favor declarations like "The registration t=
ables and information will be published and maintained by 3GPP on its web s=
ite."  I don't know if such a promise of public information is critical to =
getting the NID approved, but it would certainly help.

The whole of section 1 seems to be true but not actually relevant to the na=
mespace, as the proposed namespace doesn't seem to be intrinsically tied to=
 DTS audio formats (that just happens to be everything that DTS Inc. is inv=
olved in right now).  I don't know what would be a good replacement, but th=
e truth seems to be "DTS has a lot of irons in the fire, and we think that =
it would be useful if we could assign URNs.  Though we have a lot of good i=
deas, we aren't entirely certain what we would use them for yet."

In regard to the syntax, you need to specify that "category" may not contai=
n ":"; otherwise a URN can't be unambiguously parsed into "category" and "s=
tring" components.

Dale

________________________________

Notice:
This message and any included attachments are intended only for the use of =
the addressee, and may contain information that is privileged or confidenti=
al. If you are not the intended recipient, you are hereby notified that any=
 dissemination, distribution or copying of this communication is strictly p=
rohibited. If you have received this communication in error, please destroy=
 the original message and any copies or printouts hereof.


From nobody Fri Feb 21 19:33:13 2014
Return-Path: <worley@shell01.TheWorld.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 B2CEF1A0381 for <urn-nid@ietfa.amsl.com>; Fri, 21 Feb 2014 19:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 8WsN8-6kFegh for <urn-nid@ietfa.amsl.com>; Fri, 21 Feb 2014 19:33:09 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 025B41A02BD for <urn-nid@apps.ietf.org>; Fri, 21 Feb 2014 19:33:08 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1M3WU3d001971; Fri, 21 Feb 2014 22:32:32 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1M3WNTZ5488615; Fri, 21 Feb 2014 22:32:23 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1M3WKC35420938; Fri, 21 Feb 2014 22:32:20 -0500 (EST)
Date: Fri, 21 Feb 2014 22:32:20 -0500 (EST)
Message-Id: <201402220332.s1M3WKC35420938@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Phillip Maness <Phillip.Maness@dts.com>
In-reply-to: <520A56052CF01E42B1C128F990FBE681A46B8845@LAX-EXMB02.dts.local>
Subject: Re: draft RFC to describe a URN for DTS audio
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> <201402172245.s1HMjnBU5200650@shell01.TheWorld.com> <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local> <201402201840.s1KIeelE5399376@shell01.TheWorld.com> <520A56052CF01E42B1C128F990FBE681A46B8845@LAX-EXMB02.dts.local>
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/KIjCGboCgL5hbouduVHBBCUSRZ0
Cc: urn-nid@apps.ietf.org, Mark.Johnson@dts.com
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: Sat, 22 Feb 2014 03:33:11 -0000

Thanks for your recent thoughts.  Here are some more of my thoughts.
They are not organized into a particular proposal, but I think may
provide a guide to obtaining useful results.

I am having some difficulty orienting myself as to how to look at your
proposal.  One issue is that your proposal is (or at least appears to
be) completely commercial.  I don't think that is intrinsically bad,
but it is *different* from other namespace proposals.  And I think
that other people will see your proposal as *different* for the same
reason.

Backing up, I see that you would like a "formal" URN namespace, one
with a nice name, and not a "urn-<number>" name.  (RFC 3406)  That
makes sense to me.  But that does mean that the IESG will have to
approve the proposal as an RFC.  So there's a question of whether the
IESG will raise the questions that I am discussing.

I see a number of issues deriving from DTS's purely commercial status:

- There is an intention of commercial benefit, and less of a position
  of public benefit.

I don't see this as important, since many namespace assignments are
delegations to industry consortia.  The consortia are usually
non-profit, but their members are definitely businesses.

- Because the registrant is a business, it would be desirable if the
  delegation was done under a policy that was explicitly even-handed
  toward all businesses that might want a delegation.

- There are a *lot* of potential business registrants, leading to the
  possibility of "NID pollution", filling the registry with names to
  the point that new names that are meaningful would be difficult to
  assign.

- Businesses will likely desire an NID based on the business' name,
  making it harder to resolve conflicts regarding desired NIDs.

It seems to me that a good way to address these issues is to create a
single NID whose sub-NIDs are delegated to businesses.

At this point, let me use the term "enterprise" instead of "business".
"Enterprise" is used as a generic term for organizations in RFC 2578
and the IANA registry of "private enterprise numbers"
(https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers).

I can see at least three ways to handle all enterprises in a
systematic way:

- urn:enterprise:<enterprise-number>:<NSS>

This technique uses the existing private enterprise numbers to
identify the enterprise.

- urn:enterprise:<identifier>:<NSS>

This technique would create a new registry, from which enterprises
would allocate identifiers on a first-come basis.  The syntax of
<identifier> would probably be the same as <NID> in RFC 2141.

- urn:enterprise:<domain-name>:<NSS>

This technique uses the enterprise's domain name.  (There are a bunch
of details that are needed to make domain names permanent.  See
draft-ietf-salud-alert-info-urns-11 for how to do it.)

Using my consulting company (Ariadne Internet Services) as an example,
these techniques would produce:

- urn:enterprise:14490:nss

- urn:enterprise:ariadne:nss

- urn:enterprise:ariadne.com:nss, or
  urn:enterprise:ariadne.com(2012-01-01):nss

Perhaps this concept has been discussed in the URN working group and
they have already come to a decision.

Dale


From nobody Mon Feb 24 11:53:36 2014
Return-Path: <worley@shell01.TheWorld.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 E613C1A01AB for <urn-nid@ietfa.amsl.com>; Mon, 24 Feb 2014 11:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.098
X-Spam-Level: ****
X-Spam-Status: No, score=4.098 tagged_above=-999 required=5 tests=[BAYES_95=3,  MISSING_SUBJECT=1.799, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 iLGnGyi0wqrh for <urn-nid@ietfa.amsl.com>; Mon, 24 Feb 2014 11:53:28 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4D11A0198 for <urn-nid@apps.ietf.org>; Mon, 24 Feb 2014 11:53:28 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1OJq4CN013510; Mon, 24 Feb 2014 14:52:06 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1OJhrW45671068; Mon, 24 Feb 2014 14:43:53 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1OJhoGO5625537; Mon, 24 Feb 2014 14:43:50 -0500 (EST)
Date: Mon, 24 Feb 2014 14:43:50 -0500 (EST)
Message-Id: <201402241943.s1OJhoGO5625537@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: urn-nid@apps.ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/5Iv25BrxpK60dd4XiPX65EYHiww
Cc: Phillip Maness <Phillip.Maness@dts.com>, Mark.Johnson@dts.com
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, 24 Feb 2014 19:53:30 -0000

This is an idea that appeared in a previous message to urn-nid.  I
want to extract it and present it as a stand-alone message so I can
get more feedback on the idea.

The question is, "What do we do if an enterprise (business or other
organization) wants to have a NID of its own?"

("Enterprise" is used as a generic term for organizations in RFC 2578
and the IANA registry of "private enterprise numbers"
(https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers).)

I feel that this raises several questions which I have not seen
involved in other NID definitions:

- Because the registrant is a single enterprise, it would be desirable
  if the delegation was done under a policy that was explicitly
  even-handed toward all enterprises that might want a delegation.

- There are a *lot* of potential enterprise registrants, leading to
  the possibility of "NID pollution", filling the registry with names
  to the point that new names that are meaningful would be difficult
  to assign.

- Enterprises will likely desire an NID based on the enterprise's
  name, making it harder to resolve conflicts regarding desired NIDs.

It seems to me that a good way to address these issues is to create a
single NID whose sub-NIDs are delegated to enterprises.

I can see at least three ways to handle all enterprises in a
systematic way:

- urn:enterprise:<enterprise-number>:<NSS>

This technique uses the existing private enterprise numbers to
identify the enterprise.

- urn:enterprise:<identifier>:<NSS>

This technique would create a new registry, from which enterprises
would allocate identifiers on a first-come basis.  The syntax of
<identifier> would probably be the same as <NID> in RFC 2141.

- urn:enterprise:<domain-name>:<NSS>

This technique uses the enterprise's domain name.  (There are a bunch
of details that are needed to make domain names permanent.  See
draft-ietf-salud-alert-info-urns-11 for how to do it.)

Using my consulting company (Ariadne Internet Services) as an example
enterprise, these techniques would produce the following examples,
assuming that the overall NID was "enterprise", using the different
formats:

- urn:enterprise:14490:nss

- urn:enterprise:ariadne:nss

- urn:enterprise:ariadne.com:nss, or
  urn:enterprise:ariadne.com(2012-01-01):nss

If we wanted to be terse, we could assign the NID "e", giving these
examples:

- urn:e:14490:nss

- urn:e:ariadne:nss

- urn:e:ariadne.com:nss, or
  urn:e:ariadne.com(2012-01-01):nss

Perhaps this concept has been discussed in the URN working group and
they have already come to a decision.

Dale

