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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Sam Hartman <hartmans-ietf at mit.edu>
Subject: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
From: Eliot Lear <lear at cisco.com>
Date: Mon, 26 Feb 2007 07:51:05 +0100
Authentication-results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim2001 verified; );
Cc: ietf <ietf at ietf.org>
Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=652; t=1172472667; x=1173336667; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20Last=20Call=3A=20draft-klensin-norm-ref=20(Handling=2 0Normative=09References=0A=20for=20Standards=20Track=20Documents)=20to=20B CP |Sender:=20; bh=Zjr7tgbV4WDoVQr/9U7BrJdywjan0FHde8yKfYeAkHw=; b=Wh50icp3EkxK7kfdDvreibKNpf55itxKStTJ/qq73h4xxL/wDbN8o4XonzhBJJLpfrsn+bqT KmsZXMchwhT2TOQxv9kweIVWDoWwT6wjvhnH2JQlq+n7Id0iecIa5geE;
In-reply-to: <tsl649rtg95.fsf@cz.mit.edu>
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <E1HI5XU-0007M1-72@stiedprstage1.ietf.org> <001401c75775$1dbd8be0$0601a8c0@pc6> <tsl649rtg95.fsf@cz.mit.edu>
User-agent: Thunderbird 2.0b2 (Macintosh/20070116)

Sam Hartman wrote:

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.

It's not just one more document. We're working on at least a dozen, starting with RFC 2026, going on to various "IOPs", the boiler plate documents, IESG sponsorship documents, IRTF rules, and more. One has to be an Internet lawyer to understand the system.

Eliot

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

Follow-Ups:
- Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
  - From: Brian E Carpenter

References:
- Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
  - From: Tom.Petch
- Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
  - From: Sam Hartman

Prev by Date: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
Next by Date: new IETF Journal available online
Previous by thread: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
Next by thread: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

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

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.