Re: [Techspec] Additional comment on draft-mankin-pub-req-08

John C Klensin <john-ietf@jck.com> Mon, 12 June 2006 18:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FprLf-0000ZC-16; Mon, 12 Jun 2006 14:41:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FprLe-0000Z4-5C; Mon, 12 Jun 2006 14:41:14 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FprLc-0005gy-RE; Mon, 12 Jun 2006 14:41:14 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1FprLc-000PDq-Dz; Mon, 12 Jun 2006 14:41:12 -0400
Date: Mon, 12 Jun 2006 14:41:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Elwyn Davies <elwynd@googlemail.com>, techspec@ietf.org
Subject: Re: [Techspec] Additional comment on draft-mankin-pub-req-08
Message-ID: <6BA11EBC3FD1D3F28CD6570A@p3.JCK.COM>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: iesg@ietf.org
X-BeenThere: techspec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" <techspec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/techspec>
List-Post: <mailto:techspec@ietf.org>
List-Help: <mailto:techspec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=subscribe>
Errors-To: techspec-bounces@ietf.org

(resending a slightly modified version from the correct address
-- sorry)

--On Monday, 12 June, 2006 18:19 +0100 Elwyn Davies
<elwynd@googlemail.com> wrote:

> I appreciate that the last call is strictly over, but one
> extra point came to mind when considering
> draft-iab-rfc-editor-00.
> 
> The requirements in draft-mankin split into two parts:
> - Those that are specific to the IETF document 'stream' -
> most;y the 'front end' of the process
> - Those that apply mainly to the back end of the process and
> are relevant to any documents that are published by the RFC
> Editor
> 
> For convenience when specifying requirements for IAB and IRTF
> documents etc it would be helpful if the two types of
> requirements were split into separate sections for easier
> cross referencing.

Elwyn,

This is, of course, one of the meta-problems with the document
that several of us have tried to point out in different ways.
The community has been repeatedly assured that it applies _only_
to the IETF document stream.  If that is true, then the material
you describe as "generic" is advisory at best.  At worst, it
needs separate evaluation via other processes.

If it is not true, then the document needs an entirely different
type of review and the IESG may not be an appropriate body to
manage that review.

Of course, those comments don't make your suggestion about
reorganizing the document and clearly identifying applicability
any less useful.

       john


_______________________________________________
Techspec mailing list
Techspec@ietf.org
https://www1.ietf.org/mailman/listinfo/techspec