IETF Logo Mail Archive

Re: [Int-area] New Version Notification for draft-herbert-ipv4-eh-03.txt

"touch@strayalpha.com" <touch@strayalpha.com> Fri, 22 March 2024 14:45 UTC

Return-Path: <touch@strayalpha.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 7B223C14F70D for <int-area@ietfa.amsl.com>; Fri, 22 Mar 2024 07:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Level:
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_r2B6ff6R0z for <int-area@ietfa.amsl.com>; Fri, 22 Mar 2024 07:45:35 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89F36C1D6206 for <int-area@ietf.org>; Fri, 22 Mar 2024 07:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KYXvlucQuTF0RtqSflneJjJmTNxmUjOk5Bsmj+e2LSo=; b=KhI515UEY2evcc1W/UnTlyNaa8 1VrdbB3gXroWXdXl/uCPZ5rWljy5u0SPpDrB8URNRs7tJ0YWRf07sEwMpEvWX9PyJl/UtRN0F4sr4 Oe8o2yLXyuT+E/4KXomt/9x8oZFjzCKWmrZL2o5i/Qt+MJVySw2VRPJkPuhsuedgn/4GAKQKgpoYe CjryLZFCJ1eHBn7XpFWREntk/zIW4lWa6oLjzRUeDIc9YWouy2Lb8Dl4vBTKOS5GF7GpAShiXSn9J vDigVKt2WtW30Ygh+deMWahVwHLEWUjuA0qRROyYnxKG8zml4+CYleRJymFoKq+8F7orOE9OllXL2 2mY+gSyA==;
Received: from [172.58.209.101] (port=62287 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <touch@strayalpha.com>) id 1rng9B-005rdi-1D; Fri, 22 Mar 2024 10:45:33 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_D47E51D8-F471-4F1B-8DBD-45B2DF8A45F9"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <CALx6S35MpnnE3BpXfQDy9mBNYvDR3_SN+Mt1JxM4yMo-DQ7jTA@mail.gmail.com>
Date: Fri, 22 Mar 2024 07:45:16 -0700
Cc: Toerless Eckert <tte@cs.fau.de>, int-area <int-area@ietf.org>
Message-Id: <4A250FF9-1514-416C-A117-AFC4E7042440@strayalpha.com>
References: <170865175505.14082.3856617737779580933@ietfa.amsl.com> <CALx6S363oh+7rNMaMa0s+9A-xeyLBy+ct-Q_Bx0xQm_di1PPJA@mail.gmail.com> <ZeZjGyxmuapXz5tb@faui48e.informatik.uni-erlangen.de> <CALx6S34OFL7tzabL+RMvB3nkad5k9esCD_dFpMi6DUtUEG-Dmg@mail.gmail.com> <ZedO1u7aheBhZ26N@faui48e.informatik.uni-erlangen.de> <ZfurRK_oNVES2hVz@faui48e.informatik.uni-erlangen.de> <CALx6S36L57vPa5YkiV3khYbFpPPgPUVynWaRVno0BufvXcALeA@mail.gmail.com> <Zfu5GQ7101lMnHGs@faui48e.informatik.uni-erlangen.de> <DCE2D4E2-9C5D-40B7-952F-7424E7FCBAFE@strayalpha.com> <CALx6S37XnjWcpeGZUQWXFyE0jP=XyodmUBBh+69SonLw3ndvaQ@mail.gmail.com> <57C622DE-2C8E-4415-805D-7053309B0D01@strayalpha.com> <CALx6S36Dpn0qC9e0ZGaK-ckbT58hRkeLHDKkNqmmJn0vQ5ONUw@mail.gmail.com> <B1CC8B09-A701-4401-8BEA-C31DE0FD0FD3@strayalpha.com> <CALx6S354xQHqk4y+0dTkTQ524n5vrN01gJe57FBjbV1UuToWLA@mail.gmail.com> <FF84650B-6739-4D12-B390-977627A1296E@strayalpha.com> <CALx6S34ePRxNNqx1TOSon9=QgKvq0wJh7mMFRH7gr2OUjZ_zmw@mail.gmail.com> <E89DABED-3612-4B18-93FF-4FB31A072508@strayalpha.com> <CALx6S34F0FTyUhf8ew0tAuyaLJquRPdiOHVnT0OE7pFAQY+c_Q@mail.gmail.com> <5820339B-C98C-4F1F-93E7-B56106C66C99@strayalpha.com> <CALx6S35MpnnE3BpXfQDy9mBNYvDR3_SN+Mt1JxM4yMo-DQ7jTA@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/5xnptrBMo5RWZ1Ufp2csWsnBB1Y>
Subject: Re: [Int-area] New Version Notification for draft-herbert-ipv4-eh-03.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG 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: Fri, 22 Mar 2024 14:45:39 -0000

On Mar 21, 2024, at 10:58 PM, Tom Herbert <tom@herbertland.com> wrote:
> 
>> Again, I’m not saying it’s not useful. I’m saying it’s just another transport - one with particular properties, but still just a transport.
> 
> Extension headers are not transport protocols per the standard,
> RFC8200 clearly distinguishes extension headers from upper layer
> protocols which can be transport layer protocols.

IPv6 EH = extension headers to IPv6

IMO, IPv6 EH per this draft = just another transport protocol

RFC8200 does not apply to this proposal.

There is NOTHING that can be done for IPv4 to permit legacy endpoints to silently ignore an EH when so desired by the sender. That’s what makes IPv6 EHs different than this (IMO, again) transport protocol.

It’s misleading to call this proposal an EH or having to do with IPv4. 
It doesn’t help the programmer or user by doing so.
It doesn’t imbue the proposed solution with any properties a transport protocol couldn’t have, by design.

I don’t think this is being proposed in the correct IETF area; it belongs in TSVWG.

Joe

v2.23.0 | Report a Bug | By Email