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

John Leslie <john@jlc.net> Wed, 12 July 2006 19:17 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0kCz-0006Iq-Iq; Wed, 12 Jul 2006 15:17:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0kCy-0006Ig-5P for ietf@ietf.org; Wed, 12 Jul 2006 15:17:16 -0400
Received: from mailhost.jlc.net ([199.201.159.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0kCv-00043w-UN for ietf@ietf.org; Wed, 12 Jul 2006 15:17:16 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104) id 06771E041F; Wed, 12 Jul 2006 15:17:12 -0400 (EDT)
Date: Wed, 12 Jul 2006 15:17:11 -0400
From: John Leslie <john@jlc.net>
To: Eric Rosen <erosen@cisco.com>
Message-ID: <20060712191711.GC20260@verdi>
References: <0e6d01c6a5a8$17a0c9e0$d31adb84@china.huawei.com> <200607121828.k6CISb7t026542@rtp-core-1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200607121828.k6CISb7t026542@rtp-core-1.cisco.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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
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

Eric Rosen <erosen@cisco.com> wrote:
> 
> The focus on document relationships rather than on simplifying the standards
> track is what... sent newtrk off into the weeds. 

   Wandering in the weeds isn't always wrong.

   (We did make serious attempts to "simplify the standards track", BTW.)
`
> 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.

   Thanks for expressing that opinion.

   (Unfortunately, it's not obvious how to find common ground between it
and other expressed opinions that too many folks are guessing wrong about
which documents to follow.)

> 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. 

   If our castaway lacks Internet access, IMHO, s/he should give up!

   OTOH, if we can help him/her learn where to look on the Internet, it
seems like a win/win.

>> 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. 

   Hmmm...

   At first blush, that seems extreme...

   Nonetheless, I could easily agree that we shouldn't _require_ more
work by any of these before we can demonstrate a benefit.

--
John Leslie <john@jlc.net>

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