IETF Logo Mail Archive

Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP

"Bill Fenner" <fenner@gmail.com> Mon, 26 February 2007 05:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLYBM-0000XC-LB; Mon, 26 Feb 2007 00:13:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLYBK-0000WV-TJ for ietf@ietf.org; Mon, 26 Feb 2007 00:13:50 -0500
Received: from wx-out-0506.google.com ([66.249.82.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLYBJ-0001UC-N5 for ietf@ietf.org; Mon, 26 Feb 2007 00:13:50 -0500
Received: by wx-out-0506.google.com with SMTP id h31so1302441wxd for <ietf@ietf.org>; Sun, 25 Feb 2007 21:13:49 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BRDnSp2Ya+ZJlIrKvvgqjItmBUc/zuTFmYAgvdJZK7b/vO9omR5udXO+V3UdW9suDKL3AF4NmLUOmIMS5wJamhMpaxCyKQ9ELHCXpZL5tnPsLaXsJ2CZ72yHKwtE07YJo+sbcgDTagEUw7fWvykBXuySn2bM6FnSQ2HFHTwGZlQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EIMqQNy0/Zf+J562xBMRLJJF1ud8/QFI8pyjSuBYodRYzr9vi8Yq0igEaHvlJtnDNsNsIpdgI+jBPIl80Ek3SX7hu22tACKiVU6s+7iVtXORTG5LmQwOIoyDgEj0FfEcHbRJ5XC5V4WgjNledJGqHa+IP9P+l3IlPQXZdM8jOQE=
Received: by 10.90.84.17 with SMTP id h17mr4340704agb.1172466829412; Sun, 25 Feb 2007 21:13:49 -0800 (PST)
Received: by 10.90.75.9 with HTTP; Sun, 25 Feb 2007 21:13:49 -0800 (PST)
Message-ID: <ed6d469d0702252113x143c985bgb18cdf1cc3785073@mail.gmail.com>
Date: Sun, 25 Feb 2007 21:13:49 -0800
From: Bill Fenner <fenner@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tsl649rtg95.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1HI5XU-0007M1-72@stiedprstage1.ietf.org> <001401c75775$1dbd8be0$0601a8c0@pc6> <tsl649rtg95.fsf@cz.mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 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

On 2/24/07, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> 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 have to admit that when I was reading this document I was confused
by section 4; I thought for a while that the draft-klensin-norm-ref
rules could be applied to informational references, but then the first
paragraph of section 5 says it can't.  It took me a while to
understand that section 4 actually refers to annotating downrefs
approved under the existing rules.

  Bill

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

v2.23.0 | Report a Bug | By Email