IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Mon, 26 February 2007 06:51 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLZhX-0006y0-VF; Mon, 26 Feb 2007 01:51:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLZhV-0006ua-Ag for ietf@ietf.org; Mon, 26 Feb 2007 01:51:09 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLZhU-0005wt-1M for ietf@ietf.org; Mon, 26 Feb 2007 01:51:09 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 26 Feb 2007 07:51:07 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1Q6p7Co000967; Mon, 26 Feb 2007 07:51:07 +0100
Received: from elear-mac.cisco.com (ams3-vpn-dhcp549.cisco.com [10.61.66.37]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l1Q6p6C8012599; Mon, 26 Feb 2007 07:51:06 +0100 (MET)
Message-ID: <45E28359.1070501@cisco.com>
Date: Mon, 26 Feb 2007 07:51:05 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0b2 (Macintosh/20070116)
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <E1HI5XU-0007M1-72@stiedprstage1.ietf.org> <001401c75775$1dbd8be0$0601a8c0@pc6> <tsl649rtg95.fsf@cz.mit.edu>
In-Reply-To: <tsl649rtg95.fsf@cz.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

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@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email