IETF Logo Mail Archive

Re: [Gen-art] Review: draft-bbf-bbf-urn-02

Jari Arkko <jari.arkko@piuha.net> Thu, 01 December 2016 13:40 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F21B1294A6; Thu, 1 Dec 2016 05:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] autolearn=ham autolearn_force=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 zjBID_yVUMsk; Thu, 1 Dec 2016 05:40:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id A43D3129713; Thu, 1 Dec 2016 05:40:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 055F42CCAE; Thu, 1 Dec 2016 15:40:25 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKWoHtQWAMpc; Thu, 1 Dec 2016 15:40:24 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5C3B42CC95; Thu, 1 Dec 2016 15:40:24 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_84EC0454-CB0E-4ABF-A6E0-1A3AFD7B7864"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <56f433c2-fd24-bebb-c63d-88c9b7802b0d@joelhalpern.com>
Date: Thu, 01 Dec 2016 15:40:24 +0200
Message-Id: <8DFA7CF0-C60D-4325-92A3-14CFBC5AB790@piuha.net>
References: <69fcc020-96bf-63e5-d32b-ebb4dc222e59@nostrum.com> <a8d23000-2861-dc58-c6c5-582afe1b7971@nostrum.com> <aa837e61-0a74-d9dd-e688-d9d8481c06b8@joelhalpern.com> <56f433c2-fd24-bebb-c63d-88c9b7802b0d@joelhalpern.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oG-xi7E5E-MLPl5Cqbqqt7KFBXc>
Cc: General Area Review Team <gen-art@ietf.org>, draft-bbf-bbf-urn@ietf.org
Subject: Re: [Gen-art] Review: draft-bbf-bbf-urn-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2016 13:40:31 -0000

Thanks for the review & the edits.

jari

On 24 Nov 2016, at 02:24, Joel Halpern <jmh@joelhalpern.com> wrote:

> The new version addresses my concerns and is ready for publication as an informational RFC.
> 
> Yours,
> Joel M. Halpern
> 
> On 10/14/16 4:51 PM, Joel M. Halpern wrote:
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>> 
>> For more information, please see the FAQ at
>> 
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> 
>> Document: draft-bbf-bbf-urn-02
>>    Uniform Resource Name (URN) Namespaces for Broadband Forum
>> Reviewer: Joel M. Halpern
>> Review Date: 14-October-2016
>> IETF LC End Date: 4-November-2016
>> IESG Telechat date: N/A
>> 
>> Summary: This document is almost ready for publication as an
>> Informational RFC.
>> 
>> Major issues:
>>    RFC 3406 states that the namespace considerations section should
>> indicate why a new namespace is needed.  While this is pretty obvious,
>> the text does not actually say anything in that section to explain it.
>>    In particular, I would expect that section to explain why 3 NIDs are
>> needed rather than just 1.
>> 
>> 
>> Minor issues:
>>    The template in RFC 3406 indicates the the section in each NID on
>> the Process of identifier assignment should "detail the mechanism and or
>> authorities for assigning URNs to resources."  The draft simply says
>> that the BBF will provide procedures.  Do those procedures exist?  If
>> not, there seems to be a minor problem.  If they do exist, it would seem
>> sensible to include a pointer to the place where the BBF publicly
>> documents those procedures, so that people using this information who
>> might want to register something can understand what the rules and
>> expectations are. (I realize that the RFC 6289 example this is based on
>> did not include such a pointer, which is why I am making this a minor
>> comment instead of a major one.)
>> 
>> Nits/editorial comments:
>> 
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

v2.23.0 | Report a Bug | By Email