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

Fernando Gont <fernando@gont.com.ar> Sun, 01 March 2020 01:54 UTC

Return-Path: <fernando@gont.com.ar>
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 CCBDA3A1796; Sat, 29 Feb 2020 17:54:25 -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 7eHlmhjvd-Rk; Sat, 29 Feb 2020 17:54:24 -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 E379F3A136D; Sat, 29 Feb 2020 17:54:23 -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 8E027802F7; Sun, 1 Mar 2020 02:54:16 +0100 (CET)
To: Joseph Touch <touch@strayalpha.com>, Robert Raszuk <robert@raszuk.net>
Cc: Internet Area <int-area@ietf.org>, IETF <ietf@ietf.org>, architecture-discuss@iab.org, Internet Architecture Board <iab@iab.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> <69bd06b8-7eee-dfbc-5476-bba0f71ae915@si6networks.com> <3c307da7e8f52b7a29037a1084daf254@strayalpha.com> <a24a3621-99f6-755d-c679-2061b9a67adf@si6networks.com> <CAOj+MMGJ11CBCov=-jfZUtROJPwhQB3A=+0gMBhzZgxoF_9N1A@mail.gmail.com> <A83D4788-AD7B-490C-B74E-2548A1345C47@strayalpha.com> <CAOj+MMHfKMGa7w9pkqg=2RC4XeuYk7+iHt949B3kUtc+vCeB1Q@mail.gmail.com> <E85CB286-E396-45AF-A7E3-5600B66297CD@strayalpha.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <040673a8-0e63-6603-9fae-5fea164f4379@gont.com.ar>
Date: Sat, 29 Feb 2020 22:46:03 -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: <E85CB286-E396-45AF-A7E3-5600B66297CD@strayalpha.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/sc9gGCj1HN2wyXBCSFB2jz6dZeU>
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 01:54:27 -0000

On 28/2/20 22:55, Joseph Touch wrote:
> 
> 
>> On Feb 28, 2020, at 12:18 AM, Robert Raszuk <robert@raszuk.net 
>> <mailto:robert@raszuk.net>> wrote:
>>
>> >  I don’t care about what you WANT to do; I care whether it breaks 
>> what everyone else expects.
>>
>> I see many folks on this colorful thread simply forgot what networks 
>> are for. To deliver packets in the most robust and resilient way to 
>> end user applications. 
> 
> They’re for delivering packets, agreed.
> 
> I did look at the protocols involved here; the ingress does add headers 
> but doesn’t appear to handle fragmentation.
> 
> That’s a non-starter if you want your packets to traverse a network 
> because people WILL hand you 1280-byte packets, so what will you do?

FWIW, we have been insisting on this point (and others) since they first 
tried to push EH insertion in draft-ietf-6man-segment-routing-header.

THey removed it from *that* document, but they keep trying to push 
similar ideas in other documents.

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1