RE: "Status of I-D Submission: draft-evain-ebu-urn-01.txt" - Request for publication as 'informational'

"Evain, Jean-Pierre" <evain@ebu.ch> Fri, 18 January 2008 10:55 UTC

Return-path: <urn-nid-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFosm-0001VV-6D; Fri, 18 Jan 2008 05:55:32 -0500
Received: from urn-nid by megatron.ietf.org with local (Exim 4.43) id 1JFosk-0001VK-Po for urn-nid-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 05:55:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFosj-0001VA-F6 for urn-nid@apps.ietf.org; Fri, 18 Jan 2008 05:55:29 -0500
Received: from mailgate2.ebu.ch ([193.43.93.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFosg-0004gs-BC for urn-nid@apps.ietf.org; Fri, 18 Jan 2008 05:55:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C859C0.87C212D8"
Date: Fri, 18 Jan 2008 11:54:42 +0100
Message-ID: <9BB211A65FCBFD43B95F67BA2485759D072A0D11@gnvasmail1a.gva.ebu.ch>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: "Status of I-D Submission: draft-evain-ebu-urn-01.txt" - Request for publication as 'informational'
Thread-Index: AchTZ6y3CsZt9r/tTBO+CJSKFVIagwGWJjKQ
From: "Evain, Jean-Pierre" <evain@ebu.ch>
To: Leslie Daigle <leslie@thinkingcat.com>
X-OriginalArrivalTime: 18 Jan 2008 10:54:42.0754 (UTC) FILETIME=[87D51220:01C859C0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3d702b63698072ba67a75ce9e0fc9e
Cc: Lisa Dusseault <lisa@osafoundation.org>, urn-nid@apps.ietf.org
Subject: RE: "Status of I-D Submission: draft-evain-ebu-urn-01.txt" - Request for publication as 'informational'
X-BeenThere: urn-nid@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:urn-nid@apps.ietf.org>
List-Help: <mailto:urn-nid-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@apps.ietf.org?subject=subscribe>
Errors-To: urn-nid-bounces@apps.ietf.org

Dear Leslie,

Thanks for the comments.  Does the attached document address your concerns?
If not, please do not hesitate to let me know.

Best regards,

Jean-Pierre



-----Original Message-----
From: Leslie Daigle [mailto:leslie@thinkingcat.com] 
Sent: mercredi, 9. janvier 2008 19:23
To: Evain, Jean-Pierre
Cc: urn-nid@apps.ietf.org; Lisa Dusseault
Subject: Re: "Status of I-D Submission: draft-evain-ebu-urn-01.txt" -
Request for publication as 'informational'



Hi,

Sorry, I thought I had sent this some time ago, but it seems
not to have gone out.   Looking back in my archive, I think
I confused myself because of structural similarities
to the DVB document (which had the same issue, noted
below).   Consider these now comments on the
-02 document.

The Namespace Considerations should have sentences that explain why no
existing URN namespace is adequate, and a new formal NID should be assigned.
Per RFC3406, the specific requirement of this section is:

"  [...] a "Namespace Considerations" section, which
    outlines the perceived need for a new namespace (i.e., where existing
    namespaces fall short of the proposer's requirements).
"

The current document does not make a clear statement as
to why a new namespace is needed.

Check out the first para in that section of the updated
DVB document draft-adolf-dvb-urn (-03 as of this moment).


Also, this document shares an issue that was flagged in
the DVB document in last call.  Your document says:

"   Identifier uniqueness considerations:

       The EBU will establish unique identifiers as appropriate.

       Uniqueness is guaranteed as long as the assigned string is never
       reassigned.
"

The second sentence is tautologically true.  If what you
mean is that you will ensure an assignment process such
that they don't get reassigned, you must say that.

Similarly,

"   Identifier persistence considerations:

       The European Broadcasting Union (EBU) is committed to maintaining
       the accessibility and persistence of all resources that are
       officially assigned URNs by the organization.  Persistence of
       identifiers is dependent upon suitable delegation at the level of
       "{category}"s, and persistence of category assignment."

If the intention is to ensure that {category}s are suitably delegated and
persistent, through EBU control of assignment, you should say that.

Thanks,
Leslie.


Evain, Jean-Pierre wrote:
> Dear urn-nid editor,
>  
> please find attached the draft-evain-ebu-urn-01.txt  for which I have
> requested publication as 'informational.
>  
> Draft ID
> reference: http://www.ietf.org/internet-drafts/draft-evain-ebu-urn-01.txt.
>  
> Thanks in advance,
>  
> Best regards,
>  
> Jean-Pierre Evain
> 
> ----------------------------------------------------------------------
> --
> 
> * ************************************************** This email and 
> any
> files transmitted with it are confidential and intended solely for the 
> use of the individual or entity to whom they are addressed. If you have 
> received this email in error, please notify the system manager. This 
> footnote also confirms that this email message has been swept by the 
> mailgateway ************************************************** *
> 

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------