Re: [tsvwg] [Errata Held for Document Update] RFC3168 (4754)

Mirja Kuehlewind <ietf@kuehlewind.net> Wed, 04 March 2020 10:06 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A3D3A0B4E; Wed, 4 Mar 2020 02:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 AsbJ-qa9CvAx; Wed, 4 Mar 2020 02:06:21 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 95BAD3A0B50; Wed, 4 Mar 2020 02:06:21 -0800 (PST)
Received: from p200300dee7239a0084809b28d0f22131.dip0.t-ipconnect.de ([2003:de:e723:9a00:8480:9b28:d0f2:2131]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1j9Quu-0005n6-MU; Wed, 04 Mar 2020 11:06:16 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <20200304095833.277C3F4071F@rfc-editor.org>
Date: Wed, 4 Mar 2020 11:06:15 +0100
Cc: Bob Briscoe <ietf@bobbriscoe.net>, kk@teraoptic.com, black_david@emc.com, IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <10D606C7-7291-422A-B2A3-1A4B4FA17332@kuehlewind.net>
References: <20200304095833.277C3F4071F@rfc-editor.org>
To: tsvwg@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1583316381;8925a12a;
X-HE-SMSGID: 1j9Quu-0005n6-MU
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/luhprr2yL4Ocvmkcm_wB3gbU87A>
Subject: Re: [tsvwg] [Errata Held for Document Update] RFC3168 (4754)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 10:06:27 -0000

Hi tsvwg,

I just moved this errata to “Held for Document Update” as there are multiple points in this errata which go beyond just being an errata.

However there is also errata 4997 which only address the missing update:

https://www.rfc-editor.org/errata/eid4997

Should this errata be verified and the update tag added?

Mirja



> On 4. Mar 2020, at 10:58, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been held for document update 
> for RFC3168, "The Addition of Explicit Congestion Notification (ECN) to IP". 
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid4754
> 
> --------------------------------------
> Status: Held for Document Update
> Type: Editorial
> 
> Reported by: Bob Briscoe <ietf@bobbriscoe.net>
> Date Reported: 2016-07-31
> Held by: Mirja Kühlewind (IESG)
> 
> Section: Header block
> 
> Original Text
> -------------
> Updates: 2474, 2401, 2003, 793
> 
> 
> Corrected Text
> --------------
> Updates: 2474, 2401, 2003, 2473, 793
> 
> Notes
> -----
> RFC 3168 updates RFC 2473 but does not indicate this in its header block.
> 
> Specifically, Section 9 of RFC 3168 defined processing of the ECN field for Encapsulated Packets, which updated section 6.4 of RFC 2473, where the creation of the "IPv6 Tunnel Packet Traffic Class" was specified. RFC3168 also updated the decapsulation behaviour of the ECN field in an IPv6 tunnel header, which had not been specified in RFC2473.
> 
> Note 1: As well as tagging RFC3168 with this erratum, RFC2473 needs to be tagged (in the RFC index and associated tools outputs) to indicate that it is updated by RFC3168.
> 
> Note 2: Originally, the "Updates:" header of RFC3168 did not contain "2003", which was added as a result of Errata ID 2660.
> 
> Note 3: The first sentence of section 9.1 in RFC3168 should also be modified as follows:
> Original text:
>   The encapsulation of IP packet headers in tunnels is used in many
>   places, including IPsec and IP in IP [RFC2003].
> Corrected text:
>   The encapsulation of IP packet headers in tunnels is used in many
>   places, including IPsec and IP in IP [RFC2003, 2473].
> Comment: 
>   Nowadays RFC2473 would be a normative reference, but RFC3168 pre-dated the categorisation of references into normative and informative.
> 
> Note 4: Section 9 of RFC3168 has since been updated by RFC6040. Nonetheless, that is already correctly identified in RFC6040.
> 
> This reported errata has be moved to "Held for Document Update". While the reported problem is correct and needs to be addressed, it is not just an errata but a larger oversight at publication time.
> 
> --------------------------------------
> RFC3168 (draft-ietf-tsvwg-ecn-04)
> --------------------------------------
> Title               : The Addition of Explicit Congestion Notification (ECN) to IP
> Publication Date    : September 2001
> Author(s)           : K. Ramakrishnan, S. Floyd, D. Black
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
> 
>