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

Fernando Gont <fgont@si6networks.com> Sun, 01 March 2020 02:49 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122D83A1852; Sat, 29 Feb 2020 18:49:49 -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 MeWutKo7mxME; Sat, 29 Feb 2020 18:49:47 -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 685873A184F; Sat, 29 Feb 2020 18:49:47 -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 AFE3F80C7D; Sun, 1 Mar 2020 03:49:43 +0100 (CET)
To: Robert Raszuk <robert@raszuk.net>, Joe Touch <touch@strayalpha.com>
Cc: Internet Architecture Board <iab@iab.org>, architecture-discuss@iab.org, Internet Area <int-area@ietf.org>, IETF <ietf@ietf.org>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <CALx6S36wN7VEi_rxLC1ETcTvkGaPhs20KhQrGWAGGTrCL5OT+g@mail.gmail.com> <d41a94f5ede994b9e14605871f9f7140@strayalpha.com> <CAOj+MMFo=7G6ygCNEkwNXzzzdbYh7Aw6SzcjL_Atg6RGyDJdjA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <02d51d11-c3da-3e1e-fe1f-ca88fc48e734@si6networks.com>
Date: Sat, 29 Feb 2020 23:49:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAOj+MMFo=7G6ygCNEkwNXzzzdbYh7Aw6SzcjL_Atg6RGyDJdjA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/y8CQ6o71-y_E7ahC-IPtd3DoWJc>
Subject: Re: [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2020 02:49:49 -0000

On 27/2/20 20:04, Robert Raszuk wrote:
> Joe, all,
> 
> Just to clarify something Fernando purposely missed in his call for action: >
> All operations on the packets discussed in SPRING WG are happening NOT 
> on the original (end to end) packet header. They are all defined to 
> happen within new imposed outer encapsulated header (IPv6 in IPv6 to be 
> precise).

Nobody ever claimed something different.

But I tell you what: the outer packets are IPv6 packets. Hence, when you 
add/remove extension headers en-route to destination, you are violating 
RFC8200.

Please repeat with me: IPv6 does not allow the insertion/removal of 
extension header while the packets are en-route to the final destination.

I wished this conversation could go back to a honest one.

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