IETF Logo Mail Archive

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

Joel Halpern <jmh@joelhalpern.com> Thu, 24 November 2016 00:24 UTC

Return-Path: <jmh@joelhalpern.com>
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 8C7E0129412; Wed, 23 Nov 2016 16:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 WDWrtvS7rubc; Wed, 23 Nov 2016 16:24:47 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CEEA1295D6; Wed, 23 Nov 2016 16:24:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 3D2B6247571; Wed, 23 Nov 2016 16:24:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1479947087; bh=ks9oaxb8yLC/VaZDsRiPdtfJ76kuWAH3+n2dNyoZTsI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=i3S7b8uU8dRIWB7RLDBaj1+yqzi9hPNEc8nLdhVGV1G2jqTRvJ9ZubryAjyTRcG7L bdv2alfhsmIuaYaltWCQSltP6yzKdLPUHloTQeUS1jrUTIXf4T3+sG5cWBhnThDKI3 op6JCBQKTyjKnOuXuO0QVVwvGfCR7qalJW8wuIO4=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id B53D2240304; Wed, 23 Nov 2016 16:24:46 -0800 (PST)
To: "A. Jean Mahoney" <mahoney@nostrum.com>, General Area Review Team <gen-art@ietf.org>, draft-bbf-bbf-urn@ietf.org
References: <69fcc020-96bf-63e5-d32b-ebb4dc222e59@nostrum.com> <a8d23000-2861-dc58-c6c5-582afe1b7971@nostrum.com> <aa837e61-0a74-d9dd-e688-d9d8481c06b8@joelhalpern.com>
From: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <56f433c2-fd24-bebb-c63d-88c9b7802b0d@joelhalpern.com>
Date: Wed, 23 Nov 2016 19:24:46 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <aa837e61-0a74-d9dd-e688-d9d8481c06b8@joelhalpern.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/I-eOIg3b6kkOfi-Isc0_ryEE6CQ>
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, 24 Nov 2016 00:24:48 -0000

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
>

v2.23.0 | Report a Bug | By Email