Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
"Tom.Petch" <sisyphus@dial.pipex.com> Fri, 23 February 2007 19:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKfkz-0005HC-Od; Fri, 23 Feb 2007 14:07:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKfky-000578-6p for ietf@ietf.org; Fri, 23 Feb 2007 14:07:00 -0500
Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKfkv-0003FH-Oz for ietf@ietf.org; Fri, 23 Feb 2007 14:07:00 -0500
Received: from pc6 (1Cust159.tnt16.lnd4.gbr.da.uu.net [62.188.145.159]) by galaxy.systems.pipex.net (Postfix) with SMTP id 10A2DE000521 for <ietf@ietf.org>; Fri, 23 Feb 2007 19:06:41 +0000 (GMT)
Message-ID: <001401c75775$1dbd8be0$0601a8c0@pc6>
From: "Tom.Petch" <sisyphus@dial.pipex.com>
To: ietf <ietf@ietf.org>
References: <E1HI5XU-0007M1-72@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 18:14:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "Tom.Petch" <sisyphus@dial.pipex.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
I have no problem with the underlying idea, in so far as I understand it, but I do not agree that this I-D is the best way to achieve it. I think that my problem is well illustrated by a sentence in the Abstract ' This document replaces the "hold on normative reference" rule will be replaced by a "note downward normative reference and move on" approach. ' As may be apparent, this brief - three pages plus boilerplate - I-D, aimed at BCP status, only partly updates or replaces BCP97 (also three pages plus boilerplate) so we will in future have to conflate two documents to understand what is on offer. How much simpler it would be for all wishing to use this process if we had just one coherent document, perhaps as long as four pages, covering the whole procedure, perhaps highlighting (for the benefit of those who in future remember that things were once different) what was original BCP97 and what revised BCP97. Tom Petch ----- Original Message ----- From: "The IESG" <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> Sent: Friday, February 16, 2007 5:02 PM Subject: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP > The IESG has received a request from an individual submitter to consider > the following document: > > - 'Handling Normative References for Standards Track Documents ' > <draft-klensin-norm-ref-03.txt> as a BCP > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2007-03-16. Exceptionally, > comments may be sent to iesg@ietf.org instead. In either case, please > retain the beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-klensin-norm-ref-03.txt > > > IESG discussion can be tracked via > https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14549&rf c_flag=0 > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: Last Call: draft-klensin-norm-ref (Handling N… Hollenbeck, Scott
- Re: Last Call: draft-klensin-norm-ref (Handling N… Tom.Petch
- Re: Last Call: draft-klensin-norm-ref (Handling N… Sam Hartman
- Re: Last Call: draft-klensin-norm-ref (Handling N… John C Klensin
- Re: Last Call: draft-klensin-norm-ref (Handling N… Brian E Carpenter
- Re: Last Call: draft-klensin-norm-ref (Handling N… Bill Fenner
- Re: Last Call: draft-klensin-norm-ref (Handling N… Eliot Lear
- Re: Last Call: draft-klensin-norm-ref (Handling N… Brian E Carpenter
- Re: Last Call: draft-klensin-norm-ref (Handling N… Sam Hartman
- Re: Last Call: draft-klensin-norm-ref (Handling N… Tom.Petch
- Re: Last Call: draft-klensin-norm-ref (Handling N… Sam Hartman
- Re: Last Call: draft-klensin-norm-ref (Handling N… John C Klensin
- Re: Last Call: draft-klensin-norm-ref (Handling N… Tom.Petch
- Re: Last Call: draft-klensin-norm-ref (Handling N… Eric Rosen
- Re: Last Call: draft-klensin-norm-ref (Handling N… Jeffrey Hutzelman
- Re: Last Call: draft-klensin-norm-ref (Handling N… Frank Ellermann