RE: I-D Action: draft-wilde-updating-rfcs-00.txt

John C Klensin <john-ietf@jck.com> Thu, 22 December 2016 10:08 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 904231297CA for <ietf@ietfa.amsl.com>; Thu, 22 Dec 2016 02:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5
X-Spam-Level:
X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFhryY86oAhA for <ietf@ietfa.amsl.com>; Thu, 22 Dec 2016 02:08:50 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE977129469 for <ietf@ietf.org>; Thu, 22 Dec 2016 02:08:50 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cK0Ip-000J2B-LR; Thu, 22 Dec 2016 05:08:47 -0500
Date: Thu, 22 Dec 2016 05:08:41 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: RE: I-D Action: draft-wilde-updating-rfcs-00.txt
Message-ID: <BCB3F5280EA709F731908518@PSB>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DA51A6772@GLKXM0003v.GREENLNK.net>
References: <147389550726.29872.13885747896056913688.idtracker@ietfa.amsl.com> <0f129603-20c0-921f-6a67-e5a4c74b3c41@gmail.com> <CAA=duU0NNCeL1EP5iJo9YxDmgdtgXSpa+GO1Xs_i38HMrFxSKQ@mail.gmail.com> <b4ab1536-0eb4-0bb4-d441-79cfd74cfd9c@joelhalpern.com> <66D4FC4D5384B187F1571399@JcK-HP8200> <9a3ff314-e778-b416-182f-0dd687f434ce@dret.net> <378400590145685410530968@JcK-HP8200> <25066.1481576196@obiwan.sandelman.ca> <896.1481578272@obiwan.sandelman.ca> <d527c6cd-bc0c-66b6-e481-2510f747879e@gmail.com> <E186A6708FBC8836D0DC4655@JcK-HP8200> <49012BDE-738C-4755-B5B3-A95A2ED64BE7@sobco.com> <CAKKJt-cWJhLnqXdM80vxBwddJzxKTvrENy=0BXTVMLX_5a1Nvw@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DA51A6772@GLKXM0003v.GREENLNK.net >
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q4vaqoKbWI6SPZt_iWFDRYjvrSM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2016 10:08:51 -0000


--On Thursday, December 22, 2016 09:59 +0000 "Dearlove,
Christopher (UK)" <chris.dearlove@baesystems.com> wrote:

> I've written a few RFCs, and had debates about whether this
> is an update or not (usually resolved as whatever makes the
> IESG happy).
> 
> But as a reader of RFCs I have one simple rule of thumb. If
> I'm reading RFC ABCD, I want to know what other RFCs I need,
> or might need, to read because they modify, or extend, RFC
> ABCD in a manner that matters. For example (and maybe we need
> more examples) if I'm parsing an RFC ABCD message, what new
> options do I need to know about that are in other RFCs?
> Whether that's called update I don't really care, but
> that's my practical need for such a field.

And that is exactly the problem ISDs (and some of the other
changes needed to make them work) were intended to solve.
Paragraphs or sections here and there in documents don't do it,
partially because "you need to go read those two things as well"
may not be reflected in an 'updates' relationship and often are
not.

    john