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

Alia Atlas <akatlas@gmail.com> Mon, 12 December 2016 00:48 UTC

Return-Path: <akatlas@gmail.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 596751294B3 for <ietf@ietfa.amsl.com>; Sun, 11 Dec 2016 16:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 G_OOInf1s-pv for <ietf@ietfa.amsl.com>; Sun, 11 Dec 2016 16:48:16 -0800 (PST)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F53A129458 for <ietf@ietf.org>; Sun, 11 Dec 2016 16:48:16 -0800 (PST)
Received: by mail-qt0-x233.google.com with SMTP id c47so63336936qtc.2 for <ietf@ietf.org>; Sun, 11 Dec 2016 16:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6KqUYXbPmx6nGhU4uUsUhUE74v7IhTgot+e85oVN4Vo=; b=kN6OXzGc1+vsRHidHutaDluBpKEfH51/1fq+VmcunhkZzCYPrNFCrZC9w+ws2QIhzt 5bNKQ+APFbendMPNsbg6Xs6tmHsUEwMUL0NMuagavCoo8qxy2hy545k3cgnQgvjEQwLU tVspq8xkJxv4D7k5yDGoG0C889Tbk1ZlD1qzZIf6ECBE9R6JiWo0EBi+m1kf9yMdvz4x hjpQiAAHUz4JETvlT5fZDB58cSQQmyZBdw/npC7NnAm2WwqfJP0CLHNMob53Lm6rGCFN npfF36k+7E6zOhEXsWaKV0U7PxVmyoh6VaQrvUrckLS8aXNEn0AuUhE5dQVap1AHO2gn a+cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6KqUYXbPmx6nGhU4uUsUhUE74v7IhTgot+e85oVN4Vo=; b=ZdLsR1uDc+aIwU16uoh6gW3tj1E/P5epWYWBNB3GPLHaotYkJVjrGjay7HElnnuidN 7Jf/P5BSI7AWn/hxSrM8QjZrl8t6kMAl3j/gNJKXg4+/zngPmdic5MCCpladDHxnJfVF pjGZbTwz0UbnmjLpRREc+o2pM7q13gtPN1bWACVp3EdoYxUv7wVCWEyUfYDB/Fz6mzSz 6EdUkYXxYaSE6Ms1r6RZcCQjSyFKyRWUPVDAcrAHYQkq5Y64g8MyFVgZgdNQ4+SJI+Hr kvRE8qFFQwHKrrU9Ywwu8QAUqcKvBe7QQbxOY0Fon0v//2noeWaoJuadzQYr/iRRBCtw MK8g==
X-Gm-Message-State: AKaTC01Pd54f5NJlrf9cq8WTTlQb+QS1xcN4VSu3TQeOVuK1qKVJll1344JIjgT0+OchMToz68d6kfBx377dIA==
X-Received: by 10.237.38.37 with SMTP id z34mr89482597qtc.73.1481503695166; Sun, 11 Dec 2016 16:48:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.45.14 with HTTP; Sun, 11 Dec 2016 16:48:14 -0800 (PST)
In-Reply-To: <092718de-7c66-351f-29f2-bc8914864218@gmail.com>
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> <5B38298D-078F-4EFF-B25C-81B61714307F@sobco.com> <092718de-7c66-351f-29f2-bc8914864218@gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Sun, 11 Dec 2016 19:48:14 -0500
Message-ID: <CAG4d1re41BQeCFAYSR7J32_Wbx8ok7dyxi1zDULYC8Riq05GUw@mail.gmail.com>
Subject: Re: I-D Action: draft-wilde-updating-rfcs-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c122a387c15c405436b7546
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uaRERXYtI8ptc8bJqLBHuAbWu_0>
Cc: dret@ca.com, IETF discussion list <ietf@ietf.org>, Erik Wilde <erik.wilde@dret.net>
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: Mon, 12 Dec 2016 00:48:18 -0000

On Sun, Dec 11, 2016 at 7:39 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 12/12/2016 10:23, Scott O. Bradner wrote:
> > see, for example, https://datatracker.ietf.org/doc/draft-ietf-newtrk-
> repurposing-isd/
>
> And while we're reviewing ancient history, let me say that the new IESG in
> 2005,
> with me as the new Chair, did spend hours discussing that draft and
> failing to
> reach a useful consensus. But not because we thought there was no problem.
> As I've
> said more than once, there is a problem, for any protocol that is
> complicated enough
> to need several interlocking RFCs to define it. As those various
> components require
> updating, we grow a dependency tree. The "Updates" tag on the more recent
> RFCs is a
> very coarse way of expressing the dependencies.
>

Off-topic for the draft and updates questions, but in response....

A place where we could work on capturing the relationships of how various
RFCs and drafts
in a WG relate to each other and what the WG is focusing on is the IETF
WG's wiki.  Done well,
one could have references to it from other sites (e.g. Wikipedia) to help
folks coming newly
to the IETF or trying to learn about the related protocols and how they
plug together.
With this information written down - even informally and with just the WG
chairs or AD reviewing it,
I think it would be useful.

I've been encouraging some of my WG Chairs to think about this and see if
they can find
volunteers to do one for their WG.   Once it is written, I think that
updating it periodically wouldn't
be too challenging and having something that describes technology in
something other than
a difference architecture would be helpful.    I've seen some enthusiasm
and agreement, but
no text so far.

Regards,


Requiring the updating RFC to be clear about why and how it is updating
> other RFCs
> is IMHO a good idea. However, I don't think that a mandatory section in
> the updating
> RFC is the right way to ensure this. It would just become a box-ticking
> exercise.
>
> Regards
>     Brian
>
> >
> > Scott (network WG chair)
> >
> >
> >> On Dec 11, 2016, at 2:22 PM, John C Klensin <john-ietf@jck.com> wrote:
> >>
> >> Erik,
> >>
> >> Sorry for the delay in responding. Let me try a very high-level
> >> summary of the implications of what I, at least, consider the
> >> most important history of the problem you are trying to bite off
> >> a piece of (others will have other histories).  First, it isn't
> >> easy.  Even if one just ignores the various flavors of
> >> Informational documents, the right documentation rules for
> >> single-stage processes (e.g., BCPs) are inevitably different
> >> from those for two (and previously three)-stage technical
> >> standards track ones.  That problem is further complicated by
> >> the fact that we use BCPs, and occasionally technical standards,
> >> for what are really procedural or policy statement documents.
> >> Second, there is a complexity tradeoff.  Today, for normative
> >> documents, we have BCP documents and 2 1/2 levels of standards
> >> track  one (depending on what one thinks Experimental is).
> >>
> >> The issues of updating and categories are also inevitably
> >> complicated by the nearly-orthogonal one of interrelated and
> >> interdependent documents, some developed at different times and
> >> by different groups and often with non-obvious overlaps.
> >>
> >> We tried to take all of this on some years ago in a WG called
> >> "NEWTRK".  It was not successful.  In particular (and trying to
> >> state this as neutrally as I can manage), the WG concluded that
> >> we needed a new type of Standards Track document that would talk
> >> about status and relationships among documents, rather than
> >> being one or more technical specification itself.  At least some
> >> of what you seem to be proposing would go into those
> >> standards-description documents and not the technical
> >> specifications themselves.  In addition, at least some of us
> >> believe that the relevant documents would be living documents
> >> with change histories rather than the inherently-static (at
> >> least per-document) RFC series.
> >>
> >> WIthout revisiting the argument and various opinions about
> >> motivations, the IESG concluded that the idea was just too
> >> complicated and/or inappropriate and the idea when nowhere.  In
> >> retrospect, they might have been right.  Or not.  Either way,
> >> the experience left many of us reluctant to start nibbling at
> >> the issues again unless there was a comprehensive plan that the
> >> IETF was willing to sing off on.
> >>
> >> However, I do believe that it is unrealistic to believe one can
> >> take on inter-document relationships without at least reviewing
> >> the issues that the NEWTRK WG examined and the options it
> >> considered.
> >>
> >> best,
> >>    john
> >>
> >>
> >>
> >> --On Wednesday, December 07, 2016 21:52 -0800 Erik Wilde
> >> <erik.wilde@dret.net> wrote:
> >>
> >>> hello john.
> >>>
> >>> On 2016-09-15 09:37, John C Klensin wrote:
> >>>> Independent of where it is discussed (as
> >>>> long as it is on a public list), this I-D would be, at least
> >>>> IMO, a much more satisfactory basis for discussion if it
> >>>> demonstrated more convincingly that the author was aware of
> >>>> those earlier discussions and had considered them, rather than
> >>>> assuming (or appearing to assume) that no one had thought
> >>>> about these topics.
> >>>
> >>> it was not my intention to ignore or belittle previous
> >>> discussions. it just occurred to me as a frequent reader of
> >>> RFCs that there is a large variation in quality how updates
> >>> are documented. the idea was that some simple documentation
> >>> guidelines might help to improve that, without necessarily
> >>> being hard definitions on what exactly updates are, and how
> >>> exactly they have to be documented.
> >>>
> >>> i'd be more than happy to include these earlier discussions,
> >>> but i am afraid if that involves going through a long list of
> >>> mail archives, this simply is beyond the time commitment i can
> >>> reasonably make. i'd be more than happy to have somebody
> >>> co-authoring and filling in those gaps, but that of course
> >>> assumes that somebody else would be willing to put in the
> >>> effort of writing up this history.
> >>>
> >>> thanks and cheers,
> >>>
> >>> dret.
> >>
> >>
> >>
> >>
> >
> >
>
>