Errata #5933 for RFC8200

Fernando Gont <fgont@si6networks.com> Thu, 27 February 2020 20:07 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A563D3A0AD6 for <ipv6@ietfa.amsl.com>; Thu, 27 Feb 2020 12:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 YySLtOpsFO0V for <ipv6@ietfa.amsl.com>; Thu, 27 Feb 2020 12:07:53 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDBB3A0AD3 for <6man@ietf.org>; Thu, 27 Feb 2020 12:07:53 -0800 (PST)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id BC3E780B59; Thu, 27 Feb 2020 21:07:48 +0100 (CET)
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: "6man@ietf.org" <6man@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: Errata #5933 for RFC8200
Message-ID: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com>
Date: Thu, 27 Feb 2020 17:07:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gyXIf_HwPPtByru7xqagekCVzEw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 20:07:56 -0000

Suresh,

Two months ago I filled an errata on RFC8200 regarding the processing of 
IPv6 extension headers. The errata is available here: 
https://www.rfc-editor.org/errata/eid5933

While I believe that folks with a knowledge of Internet Protocols would 
be able to interpret what is in RFC8200, given recent discussions on the 
topic, and upon a re-read of the text, I believe a clarification is 
warranted, such that we allow all sorts of curious interpretations of 
the text.

I send a heads-up on the 6man mailing list 
(https://mailarchive.ietf.org/arch/msg/ipv6/6MPs25WvSMD6vVT0ekaMYjAwM6c/), 
and the proposed text received the review of at least Brian Carpenter, 
Ron Bonica, and Mark Smith. Their reviews are available on such thread.

In the light that some folks seem to be pretending to leverage "the lack 
of clarify" in RFC8200 (an Internet Standard) to violate it, I'd 
appreciate that the reported errata be processed.

Processing the aforementioned errata is key to many of the discussions 
this and other WGs are having.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492