Re: Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)

S Moonesamy <sm+ietf@elandsys.com> Fri, 28 February 2020 03:25 UTC

Return-Path: <sm@elandsys.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 0EC713A0DA7 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 19:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 r6_bos25wvnq for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 19:25:37 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id CB6453A0D99 for <ietf@ietf.org>; Thu, 27 Feb 2020 19:25:32 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.182.47]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 01S3P7KA025185 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2020 19:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1582860328; x=1582946728; i=@elandsys.com; bh=0PK0NXiT2S/b89ODbKZhvTGzrHnlhUZ5DIFAAnXSBkw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tdGUKmB5RlFVqIUYvI1zDb90x38Pwk7dZfFN5vl0vFtuplbzm674WxP5/eyk7oSv8 p9okyxHFDB9xkZNT7jn0DXLkzdk2hK9MleddCm2VXZ5D1A/X8EpmJkdMDs4D9Sv12K EG8SumNqahGgj5xBsY+SijPsoNVt+Axl4CE98Kk0=
Message-Id: <6.2.5.6.2.20200227173633.0ef5ba98@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Feb 2020 19:20:53 -0800
To: Fernando Gont <fgont@si6networks.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
Cc: Suresh Krishnan <suresh@kaloom.com>, jinmei@wide.ad.jp
In-Reply-To: <e90c70d8-12b0-b3c7-384b-fd9e5fc39a11@si6networks.com>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <6.2.5.6.2.20200227151910.1077c270@elandnews.com> <e90c70d8-12b0-b3c7-384b-fd9e5fc39a11@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xLOan4Ee7Ooemnd7paVtkofglhA>
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: Fri, 28 Feb 2020 03:25:39 -0000

Hi Fernando,
At 04:26 PM 27-02-2020, Fernando Gont wrote:
>Seriously?

Yes.  It is up to the vendor to assess whether it is sound 
engineering or a financially-viable decision.

>I did, one or too months ago. Also cc'ed the architecture-dicuss list.

One of the persons discussing on the thread is an IAB member.

>Would change the consensus from what to what?
>
>Appendix B of RFC8200 clearly says:
>    o  Clarified that extension headers (except for the Hop-by-Hop
>       Options header) are not processed, inserted, or deleted by any
>       node along a packet's delivery path.
>
>Is the errata I filed anything different from such intent?

The consensus is on the text in the first part (Section 4) at 
https://www.rfc-editor.org/errata/eid5933  The recommendation is to 
replace the original two paragraphs with four paragraphs.  If the 
above is what appendix B states, the clarification (re. erratum) is not needed.

For what it is worth, there was an email which is allegedly from an 
Area Director.  One of the points in that email is about "a misuse of 
the Errata process".

Regards,
S. Moonesamy