IETF Logo Mail Archive

Re: My notes on draft-carpenter-newtrk-questions-00.txt

Eric Rosen <erosen@cisco.com> Wed, 12 July 2006 18:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0jXf-0007YK-Hv; Wed, 12 Jul 2006 14:34:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0jWt-0006wg-3u for ietf@ietf.org; Wed, 12 Jul 2006 14:33:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0jRu-0001FM-GX for ietf@ietf.org; Wed, 12 Jul 2006 14:28:39 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 12 Jul 2006 11:28:38 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,236,1149490800"; d="scan'208"; a="31995037:sNHT21472828"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6CIScoT024344; Wed, 12 Jul 2006 14:28:38 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6CISb7t026542; Wed, 12 Jul 2006 14:28:38 -0400 (EDT)
Message-Id: <200607121828.k6CISb7t026542@rtp-core-1.cisco.com>
To: Spencer Dawkins <spencer@mcsr-labs.org>
In-reply-to: Your message of Wed, 12 Jul 2006 00:16:35 -0400. <0e6d01c6a5a8$17a0c9e0$d31adb84@china.huawei.com>
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset="US-ASCII"
Date: Wed, 12 Jul 2006 14:28:37 -0400
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=854; t=1152728918; x=1153592918; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=erosen@cisco.com; z=From:Eric=20Rosen=20<erosen@cisco.com> |Subject:Re=3A=20My=20notes=20on=20draft-carpenter-newtrk-questions-00.txt=20 |To:=22Spencer=20Dawkins=22=20<spencer@mcsr-labs.org>; X=v=3Dcisco.com=3B=20h=3DWkgyhnjwUKvH/laIf3VmqVzhYw0=3D; b=KbC0jRWsdJZMrzr0E5wbxCXHBNNr5tpHlbhm6qaFvoF7bQH/ZVqLDIqRN62Gz7fSkSYtaknK Re28YxrIxEI0+52nbchjwjqtDpl663TpiHaQr9HiaJ2g5HwJWTlmj4u/;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=erosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ietf@ietf.org
Subject: Re: My notes on draft-carpenter-newtrk-questions-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.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

The focus on document relationships rather than on simplifying the standards
track is  what (well, is one  of the things)  that sent newtrk off  into the
weeds. 

Frankly, I don't  care if someone on a desert island  cannot figure out from
the RFCs alone how  to implement some protocol.  I just don't  see that as a
problem we have to solve.   Anyway, implementing a protocol requires so much
more knowledge than can be obtained  from the RFCs that no amount of messing
with the document strategy is going to have any impact on the ability of our
castaway to become a successful implementer. 

> it's worth revisiting  the whole ISD/SRD thing with one  new ground rule -
> no more work for IESG in steady state

Let  me suggest a  second new  ground rule:  no more  work for  the document
authors, document editors, or the WG chairs. 

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

v2.23.0 | Report a Bug | By Email