IETF Logo Mail Archive

[Gen-art] Review: draft-martin-urn-globus-02

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 12 February 2016 00:27 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 938231A6FDF; Thu, 11 Feb 2016 16:27:06 -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
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 EvDCcFAP6Mrx; Thu, 11 Feb 2016 16:27:02 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17BD81A6FB8; Thu, 11 Feb 2016 16:26:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id F1EC21C07A1; Thu, 11 Feb 2016 16:26:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1455236818; bh=eK0FoKBEp+VIjguZYuIFbDSR7kTCO7NnayfalRYmTfg=; h=Subject:To:References:From:Date:In-Reply-To:From; b=BCUsuKjeTOT0In6vb+eK2AaDlfqaFDd86CaXoUp2EdA/s3MnY4lQSEPl7+P+JcxU0 Sd7Wqaty4YMJoYCoV0VSONED4LD/FqeMNX7EBnnLcyUsuqExPiz9nYF6bCqtF27lCY s58uCGITLKse58JARniP5oeeytMmQuJrNJIY8cHE=
X-Virus-Scanned: Debian amavisd-new at b2.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 mailb2.tigertech.net (Postfix) with ESMTPSA id 80A931C059C; Thu, 11 Feb 2016 16:26:58 -0800 (PST)
To: "A. Jean Mahoney" <mahoney@nostrum.com>, General Area Review Team <gen-art@ietf.org>, draft-martin-urn-globus.all@ietf.org
References: <56BD072F.4080905@nostrum.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <56BD269D.1040703@joelhalpern.com>
Date: Thu, 11 Feb 2016 19:26:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56BD072F.4080905@nostrum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/lRmB2qldtLy8r_jEcOgUIdEyGr4>
Subject: [Gen-art] Review: draft-martin-urn-globus-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Feb 2016 00:27:06 -0000

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-martin-urn-globus-02
     A URN Namespace for Globus
Reviewer: Joel M. Halpern
Review Date: 11-Feb-2016
IETF LC End Date: 9-March-2016
IESG Telechat date: 17-March-2016

Summary: This document is nearly ready for publication as an 
informational RFC.

This reviewer assumes that the appropriate message has been or will be 
sent to urn-nid@apps.ietf.org.

Major issues:
     As per the pointer in this document to RFC 3406 section 4.3, this 
document is required to have 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)."  While there is 
a section called Namespace Considerations, what it lists is the 
envisioned usages, not the reasons existing name spaces are insufficient.

Minor issues: N/A

Nits/editorial comments: N/A

v2.23.0 | Report a Bug | By Email