Re: [urn] The 3406bis template

Peter Saint-Andre <stpeter@stpeter.im> Tue, 13 August 2013 19:39 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C8621F8CB4 for <urn@ietfa.amsl.com>; Tue, 13 Aug 2013 12:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YZjvKmmDVnnK for <urn@ietfa.amsl.com>; Tue, 13 Aug 2013 12:39:05 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A6C5911E81BB for <urn@ietf.org>; Tue, 13 Aug 2013 12:39:05 -0700 (PDT)
Received: from ergon.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 400FB4010C; Tue, 13 Aug 2013 13:42:00 -0600 (MDT)
Message-ID: <520A8B56.1070604@stpeter.im>
Date: Tue, 13 Aug 2013 13:39:02 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <7639E40F70A558B99C1D2367@JcK-HP8200.jck.com>
In-Reply-To: <7639E40F70A558B99C1D2367@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] The 3406bis template
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 13 Aug 2013 19:39:18 -0000

On 8/2/13 6:51 AM, John C Klensin wrote:
> Hi.
> 
> I just looked back through the template in
> draft-ietf-urnbis-rfc3406bis-urn-ns-reg-06 in the light of the
> WG discussion this morning.
> 
> The template description is now over four pages long and some of
> the suggestions made this morning will probably make it longer.
> That is pretty scary; it asks for enough information be copied
> into the template and handed to IANA to probably be seen as a
> barrier to registration in some quarters.  

Agreed: let's make the template as simple as possible, but no simpler.

(Marc Blanchet said he would provide some feedback regarding
simplification, too.)

The template is too long in part because it contains instructions and
examples; those could be moved to the body of 3406bis.

> Recommendations:
> 
> (1) When the "instructions to Expert Reviewer" material is
> added, be clear about what is required and what is merely
> expected.  Then reflect that in the sections of the template
> itself.

Yes.

> (2) Number or otherwise identify the sections of the template to
> make references and cross-references convenient.  That will,
> fwiw, keep this document from running afoul of some
> possibly-pending RFC Editor style rules.
>
> (3) Create an internal table of contents for the template itself.

Right now it is structured in xml2rfc as a huge example. That's easily
fixed and will result in a better table of contents for 3406bis itself
(and enable cross-references as you mention above).

Are you also suggesting that the template contain a mini-ToC?

> (4) Explicitly permit most sections of the template to be
> incorporated by reference to a stable external specification
> (stable by at least the "Specification Required" definition, not
> just the RFC Editor one) or by a mixture of text and such a
> reference.  By explicit about which ones cannot (I think the
> first three sections need to be present in the template itself).

Agreed.

> Let's not make this any harder than it absolutely needs to be.

+1

Do you have suggestions on which sections might productively be removed?

Peter

-- 
Peter Saint-Andre
https://stpeter.im/