Re: "Status of I-D Submission: draft-evain-ebu-urn-01.txt" - Request for publication as 'informational'
Leslie Daigle <leslie@thinkingcat.com> Fri, 11 January 2008 00:47 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 1JD83D-0002Nj-83; Thu, 10 Jan 2008 19:47:11 -0500
Received: from urn-nid by megatron.ietf.org with local (Exim 4.43) id 1JD83C-0002Jv-J3 for urn-nid-confirm+ok@megatron.ietf.org; Thu, 10 Jan 2008 19:47:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JD83C-0002Jm-9J for urn-nid@apps.ietf.org; Thu, 10 Jan 2008 19:47:10 -0500
Received: from zeke.blacka.com ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD83B-0002Ut-Pq for urn-nid@apps.ietf.org; Thu, 10 Jan 2008 19:47:10 -0500
Received: from beethoven.local ([::ffff:209.183.196.229]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Wed, 09 Jan 2008 13:23:25 -0500 id 015886FC.4785111D.00002E22
Message-ID: <47851114.2070406@thinkingcat.com>
Date: Wed, 09 Jan 2008 13:23:16 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: "Evain, Jean-Pierre" <evain@ebu.ch>
References: <9BB211A65FCBFD43B95F67BA2485759D072A0BC8@gnvasmail1a.gva.ebu.ch>
In-Reply-To: <9BB211A65FCBFD43B95F67BA2485759D072A0BC8@gnvasmail1a.gva.ebu.ch>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
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
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 -------------------------------------------------------------------
- "Status of I-D Submission: draft-evain-ebu-urn-01… Evain, Jean-Pierre
- Re: "Status of I-D Submission: draft-evain-ebu-ur… Leslie Daigle
- RE: "Status of I-D Submission: draft-evain-ebu-ur… Evain, Jean-Pierre
- RE: "Status of I-D Submission: draft-evain-ebu-ur… Evain, Jean-Pierre