Re: Proposed IESG Statement on the use of the “Updates” header

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Tue, 11 September 2018 18:30 UTC

Return-Path: <kathleen.moriarty.ietf@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 049DD1292F1; Tue, 11 Sep 2018 11:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 awnmwIqL5Lqj; Tue, 11 Sep 2018 11:30:39 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 CBA53130D7A; Tue, 11 Sep 2018 11:30:38 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id h138-v6so17393778qke.8; Tue, 11 Sep 2018 11:30:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ie8IDIi25NBFr00TGl+79TPl2iP7r8yn4oO2bAng/kA=; b=HDDZABcyTVoQsnLIsgWIT/4izi/G8XPi0JAVXHG0SnvuT1dGAOyek1x/Gd1H4un/Av 31nvvC68WUa+Jf5/dDjTW5YBdot80un7UeqUaUev6Tfoq5enq8UqveoZmvMhE+xdavyu Ow9RAM/FrEIbaRFarB1yT+c4PYu8SwsX+pTzh85i7Zdj/yZ+T9VokAnfAXcDvs8Uij/K FNKM/HvNi209A57nD+HiRV3eiwMDTmKWL+kTLMgqtv5tv4bLENB/R9f3yC/n8Adblc9x wlRzvPetv5P+InE+zEeTQJYof8cxBlTOETiwYOSrAcIMeCBV6gcaKOzMOZagw1leMp16 N1iQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ie8IDIi25NBFr00TGl+79TPl2iP7r8yn4oO2bAng/kA=; b=s7mw05oo79EXo25Bijq3d2szlqDg4kyPOJw+Wc0x8coFWU7J9mBtJ+2kp0eWqtpQZ/ Gkf8vDa3kgi0Wz3XLdo+0390Yp5ij3VZNf7rJRBbxTUn0joc1Kncr1jj1NOrviMRW84b /62YUK3A3txzuVzWA0HNtRuMFiziHLLbTKulMJ/n0cm9wpFJ+cBjT36EtDw7226EnW0a +WWL90sMMxGJ9L6kfA4xtr6QKbERlsLNWhyaE9ZehFD8OP6Ms19gMkWvKr/flFHHGdId lxiK3NAcCZ60zT8+JMTXF86UxyqTpK6Ri9Ke+UNXCOrxaQTvI+BNQybQ6IGGRzX3MJac Ejuw==
X-Gm-Message-State: APzg51DbGmORHqTs+NnSMAbo3b8Tv+K08gJrS4fVfois7Gjyg/PqHjno Kp9e7IOOmhcWUG2/Rr9QphKQ+OWC
X-Google-Smtp-Source: ANB0VdYtevj9Zf4rXzzALJbKBvevhZmKHu+UWt4PAauaHMEc0CMUTcgnvlSXZJm4VhLIuyAM9GUT6g==
X-Received: by 2002:a37:a456:: with SMTP id n83-v6mr19480219qke.160.1536690637828; Tue, 11 Sep 2018 11:30:37 -0700 (PDT)
Received: from [192.168.1.210] (209-6-121-113.s2671.c3-0.arl-cbr1.sbo-arl.ma.cable.rcncustomer.com. [209.6.121.113]) by smtp.gmail.com with ESMTPSA id k21-v6sm9148420qtj.11.2018.09.11.11.30.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Sep 2018 11:30:37 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: Proposed IESG Statement on the use of the “Updates” header
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (15E216)
In-Reply-To: <9a505c33-3327-a13f-f5ce-4fac360169b1@nostrum.com>
Date: Tue, 11 Sep 2018 14:30:36 -0400
Cc: Ben Campbell <ben@nostrum.com>, ietf@ietf.org, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA3FAF47-2415-44E1-A782-D43FA2C0C624@gmail.com>
References: <59F6DED7-8D39-4206-8268-22AB6A99A876@nostrum.com> <9a505c33-3327-a13f-f5ce-4fac360169b1@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1A9XNAgRiaaN8VinQlwqYODcPVo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 18:30:41 -0000


Sent from my mobile device

> On Sep 11, 2018, at 2:08 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> I can live with this statement, but I don't like it.
> 
> I'm in the camp that prefers the more specific "This changes the code you need to write" camp - I would prefer Update be restricted to the cases where you are changing the protocol defined in the updated document in an essential way. The use of extension points doesn't cross that bar. So, count me as against everything in the second paragraph beyond the first sentence.

+1

Kathleen 

> 
> That said, I again note that I can live with what's proposed.
> 
> RjS
> 
> p.s. I assume you've rehashed previous IESGs discussions of adding a "See Also" relationship?
> 
>> On 9/11/18 10:55 AM, Ben Campbell wrote:
>> Hi Everyone,
>> 
>> There have been several discussions lately about the use and meaning of the “Updates” header in RFCs, and the resulting “Updates”/“Updated by” relationships. The IESG is thinking about making the following statement, and solicits feedback.
>> 
>> Thanks!
>> 
>> Ben.
>> --------------------------------------------
>> 
>> There has been considerable confusion among the IETF community about the formal meaning of the “Updates” / "Updated by" relationship in IETF stream RFCs. The “Updates” header has been historically used for number of reasons of various strength. For example, the “Updates” header may be used to indicate critical normative updates (i.e. bug fixes), optional extensions, and even “additional information”.
>> 
>> The IESG intends these headers to be used to inform readers of an updated RFC that they need to be aware of the RFC that updates it. The headers have no formal meaning beyond that. In particular, the headers do not, by themselves, imply a normative change to the updated RFC, nor do they, by themselves, imply that implementers must implement the updating RFC to continue to comply with the updated one.
>> 
>> The specific reasons that a given RFC updates another should be described in the abstract and body of the new RFC. The level of detail may differ between the abstract and the body; typically an abstract should contain enough detail to help readers decide if they need to read the rest of the RFC. The body should contain enough detail for readers to fully understand the nature of the update.
>> 
>> The importance of including an “Updates” header depends on the nature of the update. Normative updates that do not use a known extension point should always include an “Updates” header. Extensions that do use known extension points do not typically need to include the “Updates” header, but may in cases where it’s important to make the extension known to readers of the original RFC. Other uses of “Updates” may be appropriate when it’s important for readers to know about them; for example a new RFC may expand security or operational considerations in a way that is not normative, but still important.
>> 
>> RFCs that fully replace other RFCs should typically use the “Obsoletes” header rather than the “Updates” header. The “Updates” header should be used to flag updates to published RFCs; it is not appropriate to “Update” an Internet-Draft.
>> 
>> 
>