[apps-discuss] AppsDir review of draft-housley-ltans-oids-00

Carsten Bormann <cabo@tzi.org> Thu, 25 July 2013 09:46 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DBB21F9A94; Thu, 25 Jul 2013 02:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 557gTtDcIqz3; Thu, 25 Jul 2013 02:46:00 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCAA21F9ABA; Thu, 25 Jul 2013 02:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r6P9jun6020348; Thu, 25 Jul 2013 11:45:56 +0200 (CEST)
Received: from [192.168.217.105] (p54894526.dip0.t-ipconnect.de [84.137.69.38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0049023C; Thu, 25 Jul 2013 11:45:55 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Carsten Bormann <cabo@tzi.org>
Date: Thu, 25 Jul 2013 11:45:55 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <226664B3-428E-46F1-A3A4-EC743F28C4F2@tzi.org>
To: "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>, draft-housley-ltans-oids.all@tools.ietf.org
X-Mailer: Apple Mail (2.1508)
Cc: The IESG <iesg@ietf.org>
Subject: [apps-discuss] AppsDir review of draft-housley-ltans-oids-00
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2013 09:46:06 -0000

I have been selected as the Applications Area Directorate reviewer for
this draft (for background on appsdir, please see
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate).

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-housley-ltans-oids-00

Title: Object Identifier Registry for the
              Long-Term Archive and Notary Services (LTANS) Working Group

Reviewer: Carsten Bormann
Review Date: 2013-07-25
IESG Telechat Date: 2013-08-15
IETF Last Call Expires: 2013-07-31

* Summary: The document is almost ready for publication, but may need
the addition of some guidance for the IANA expert review.

The document nicely and accessibly summarizes the status of
ASN.1 OIDs assigned for LTANS and establishes IANA registration
policies for some arcs.

* Major:

As with all registries that specify Expert Review:
Is there any guidance for the designated expert?
I.e., what is the objective for the review?
What will be the grounds for acceptance or rejection of a registration?
(Such guidance is likely obvious to those closely involved with the work.
It is not obvious to someone newly approaching this document and
considering whether the registry is the right one to use.)

* Minor

One OID is described as obsolete, which is fine.  The ones designated
for LTAP are not described as obsolete, but it is not clear what the
disposition of this protocol is.  (It may not be the purview of this
document to make statements about this, but if the answer is obvious,
it should be given.)
(This is confounded by referencing a long dead I-D as "work in
progress" -- is it indeed in progress?  Again, maybe not for this
document to fix this longstanding issue about I-D citations.)

* Nits

Add period at end of section 1.
6: "it raise no new"