[urn] OPS-DIR review of draft-martin-urn-globus-02

Stefan Winter <stefan.winter@restena.lu> Mon, 22 February 2016 07:07 UTC

Return-Path: <stefan.winter@restena.lu>
X-Original-To: expand-draft-martin-urn-globus.all@virtual.ietf.org
Delivered-To: urn@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id B07D51B3622; Sun, 21 Feb 2016 23:07:40 -0800 (PST)
X-Original-To: xfilter-draft-martin-urn-globus.all@ietfa.amsl.com
Delivered-To: xfilter-draft-martin-urn-globus.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC6B1B3620; Sun, 21 Feb 2016 23:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.505
X-Spam-Level:
X-Spam-Status: No, score=-0.505 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.006, WEIRD_PORT=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 C1YjzijlbaoF; Sun, 21 Feb 2016 23:07:38 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [158.64.1.62]) (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 2749C1B361B; Sun, 21 Feb 2016 23:07:38 -0800 (PST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 76C1B43AE1; Mon, 22 Feb 2016 08:07:36 +0100 (CET)
To: ops-dir@ietf.org, draft-martin-urn-globus.all@ietf.org
From: Stefan Winter <stefan.winter@restena.lu>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66; url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66
X-Enigmail-Draft-Status: N1111
Message-ID: <56CAB3B2.1030905@restena.lu>
Date: Mon, 22 Feb 2016 08:07:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="okePRjdPr0krOkWRk5TU98whuggK5I67h"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/aIK7QvhSBBA64opOctZQ39uon1Y>
X-Mailman-Approved-At: Tue, 23 Feb 2016 11:48:42 -0800
Subject: [urn] OPS-DIR review of draft-martin-urn-globus-02
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 07:07:40 -0000

Hello,

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the IESG.
 These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not addressed
in last call may be included in AD reviews during the IESG review.
Document editors and WG chairs should treat these comments just like any
other last call comments.

I believe this document is ready.

It is a well-elaborated registration for a new URN namespace, and
contains few operational issues to consider. All aspects of the
registration are well explained, and the registration of a new namespace
(rather than using existing ones) is justified (Globus should of course
consider using the existing urn:ietf:params:oauth namespace where that
one is sufficient; the examples given in the registration make clear
that the globus namespace is used for things /not/ covered there).

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
2, avenue de l'Université
L-4365 Esch-sur-Alzette

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66