Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
Brian E Carpenter <brc@zurich.ibm.com> Sun, 25 February 2007 10:22 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLGWM-0000vx-2m; Sun, 25 Feb 2007 05:22:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLGWK-0000tQ-El for ietf@ietf.org; Sun, 25 Feb 2007 05:22:20 -0500
Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLGWI-0002Cb-Sr for ietf@ietf.org; Sun, 25 Feb 2007 05:22:20 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.8/8.13.8) with ESMTP id l1PAM4pY027060 for <ietf@ietf.org>; Sun, 25 Feb 2007 10:22:04 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.2) with ESMTP id l1PAM4H91994846 for <ietf@ietf.org>; Sun, 25 Feb 2007 11:22:04 +0100
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l1PAM3xu010244 for <ietf@ietf.org>; Sun, 25 Feb 2007 11:22:03 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l1PAM324010237; Sun, 25 Feb 2007 11:22:03 +0100
Received: from [9.4.210.81] ([9.4.210.81]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA329176; Sun, 25 Feb 2007 11:21:59 +0100
Message-ID: <45E16346.9060104@zurich.ibm.com>
Date: Sun, 25 Feb 2007 11:21:58 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <E1HI5XU-0007M1-72@stiedprstage1.ietf.org> <001401c75775$1dbd8be0$0601a8c0@pc6> <tsl649rtg95.fsf@cz.mit.edu> <5B03ECFB5535D3618C3C2785@[192.168.1.110]>
In-Reply-To: <5B03ECFB5535D3618C3C2785@[192.168.1.110]>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf <ietf@ietf.org>
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
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 believe that if we follow the authors' suggestion to proceed rapidly, Tom's concern could be met by a simple informational note summarizing how to deal with downrefs in practice. Such a note could be input to an eventual combined document after some experience, as John suggests. Brian On 2007-02-25 00:00, John C Klensin wrote: > > > --On Saturday, February 24, 2007 4:09 PM -0500 Sam Hartman > <hartmans-ietf@mit.edu> wrote: > >>>>>>> "Tom" == Tom Petch <sisyphus@dial.pipex.com> writes: >> >> Tom> I have no problem with the underlying idea, in so far >> as I Tom> understand it, but I do not agree that this I-D >> is the best Tom> way to achieve it. >> >> Tom> I think that my problem is well illustrated by a >> sentence in Tom> the Abstract ' This document replaces the >> "hold on normative Tom> reference" rule will be replaced >> by a "note downward Tom> normative reference and move on" >> approach. ' As may be Tom> apparent, this brief - three >> pages plus boilerplate - I-D, Tom> aimed at BCP status, >> only partly updates or replaces BCP97 Tom> (also three >> pages plus boilerplate) so we will in future have Tom> to >> conflate two documents to understand what is on offer. >> >> My strong preference as an individual is to approve this >> document as is. I think there's a good split between RFC 3967 >> and this document. RFC 3967 will cover informational >> documents; this document will cover standards track. >> >> I'm not in principle opposed to having one document but I am >> opposed to the delay it would introduce. > > Tom, > > This is very much up to the IESG, but my personal opinion is that we are > better off putting this draft through as is and then coming back and > revisiting the situation in a year or so, once we have gotten some > experience with the combination. My guess -- harking back to the > original "process experiment" theory -- is that some tuning is going to > be needed and that there is no point in tangling 3967 up with the tuning > process. That assumption is particularly important because Sam's > observation of 3967 for informational (and experimental) documents and > this for standards-track is what I'm expecting too... but it is an > assumption. One can imagine the community responding to a downref under > this procedure for a particular document by saying "just too dangerous > to do it that way; let's use the 3967 procedure in that case". We > might be willing to eliminate that possibility once we have some more > experience, but I'd think it would be dangerous to do so right now. So, > for the present, we have this procedure for standards-track documents > when it seems appropriate and 3967 for everything else. > > In a year or two, if anyone cares, we can fold the two together on the > basis of actual experience (or fold both into the long-avoided 2026bis). > > john > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ 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