Re: [IPv6] I-D Action: draft-ietf-6man-eh-limits-02.txt

Bob Hinden <bob.hinden@gmail.com> Thu, 02 March 2023 19:06 UTC

Return-Path: <bob.hinden@gmail.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 B7431C13A34A for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2023 11:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bbIeHejYro2j for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2023 11:06:45 -0800 (PST)
Received: from mail-oa1-x2f.google.com (mail-oa1-x2f.google.com [IPv6:2001:4860:4864:20::2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECE94C151520 for <ipv6@ietf.org>; Thu, 2 Mar 2023 11:06:45 -0800 (PST)
Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-17652f24da7so503786fac.4 for <ipv6@ietf.org>; Thu, 02 Mar 2023 11:06:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ciJjyxFnkkqv/pWxpxRrnZYLdw9Uq3z8VdszGMseKG8=; b=JSfp0u0GDMQ53hYYVieqXrOcs6gF+Uo7RUyoM33IxERDB6IuJRzJ0KukjTuG7eP6Bh xjJiJE1HMHvddHBnEmvAEr2Tf/yZNJ9q/xZAKBKCmsZXldwt20dXmKXe6Ja9OaX2an2w QRJyEKnKn9JwWnozr5D8T4Ck0/CB9mfsJLIhyTMZHYp98JvZLn5Tk9pPaEcWXuyclHWA niovG/AzCwifpy7RUUDGrg3iC0S+bLUtPfd6elmnV3l732Zic8U84NJMKCscelRY3rFs kfO65RjczGWWU+8h13dNn5+W3id1Ow7kXA/6hQN9cI6edY5GPFN8m/NsPL56bzv9GQnz 40Lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ciJjyxFnkkqv/pWxpxRrnZYLdw9Uq3z8VdszGMseKG8=; b=KnwayiZinPXy453GJgf6DlePasRTbz/8tycgL6b9dKns2jgI2t+gJ6KD720fS28m6O fpRDfgOP0OGmtSH27dKj8/r0srmdNiDrKyE8zzK29g9Vwd3QEUSqoSXlO0q8sMPo4cxz KMtu5PUnZQzgfJthQE3DN8FRo1rlVrG+yNrsv9iOUhvqnhpMbsLs8zfcDUzWEvDQ7PFn JSoZ6bZ3gAKlaw1K2QTsVHhBdQySXXJ/yQ/XKofQQ7DoHr3ZmtrspBTW5agDrcIswikg JzUEybO1Jw6Im94YtB/tpSReQB3cl3Nv99o9KP6wkhP2jgA2Vjx6Tjm8pqPJpfOhgv97 zIwg==
X-Gm-Message-State: AO0yUKWAhg8f/TtpeyICGLw+1lGAv/qgiwzBG9wDGB0Avyh1W81V0Aob 61hRx/49wqPTu7/uPobyqgI=
X-Google-Smtp-Source: AK7set8HrYeyaLYHCiA+DjW2Ov5ZIkdZQYgC4KurvoDjTk2sH5rgX33hni9ZbqdI+22WWCdg4fC79Q==
X-Received: by 2002:a05:6870:169d:b0:176:263e:996c with SMTP id j29-20020a056870169d00b00176263e996cmr4233394oae.47.1677784005051; Thu, 02 Mar 2023 11:06:45 -0800 (PST)
Received: from smtpclient.apple ([2600:1700:4383:c05f:65c4:9c7e:d4f4:12db]) by smtp.gmail.com with ESMTPSA id h9-20020a4aa289000000b005253a5cc3cfsm6299844ool.29.2023.03.02.11.06.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Mar 2023 11:06:44 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_7D5E4460-9882-42E2-B9CB-A3A81AC662B7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <910EE374-5677-47B3-9339-54EAF27F6F06@employees.org>
Date: Thu, 02 Mar 2023 11:06:43 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>, IPv6 List <ipv6@ietf.org>
Message-Id: <DBE99F3F-EED8-401F-88F5-A7F64E3DE963@gmail.com>
References: <d33ad4199e794493ba45fe94c9c49784@boeing.com> <caae1407-1715-bd69-3e89-cc798ce07417@foobar.org> <54A1539A-E82A-49A1-891E-5BC28CA7D18E@employees.org> <CALx6S37BR1h29u-LjC614-jwnVBaa3=i_fTwhnTMb9m7UcYPcQ@mail.gmail.com> <910EE374-5677-47B3-9339-54EAF27F6F06@employees.org>
To: Ole Troan <otroan=40employees.org@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xTHzVXrAdOocaYcPg2uOv9I_0Vg>
Subject: Re: [IPv6] I-D Action: draft-ietf-6man-eh-limits-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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, 02 Mar 2023 19:06:47 -0000

Ole,

> On Mar 2, 2023, at 7:58 AM, Ole Troan <otroan=40employees.org@dmarc.ietf.org> wrote:
> 
> Tom,
> 
>> It's a classic "chicken and egg problem". Extension headers would on
>> be deployable if there are real use cases, but we can't develop real
>> use cases unless they are deployable.
> 
> There might be an aspect of that, but I don’t think that’s the whole truth.
> It is quite telling that there isn’t a single universally “interesting” extension header.

I continue to think that RFC9268 "IPv6 Minimum Path MTU Hop-by-Hop Option” is both interesting.

Bob


> That’s applicable to intermediate nodes. You could almost generalise it to any node.
> 
>>> As an implementor I am quite unhappy when headers aren’t at fixed and predictable offsets in the packet.
>> 
>> As an implementer I am quite unhappy that some vendors and operators
>> have taken arbitrary liberty to block protocols thereby ossifying the
>> Internet and otherwise make protocol conformance optional for the
>> purposes of their financial gain. The effect is that we need to
>> reverse engineer these implementations and policies to provide
>> workarounds to continue to give end users the best service and the
>> benefits of an evolving Internet.
>> 
>> In any case, the problems and perceptions about extension headers have
>> been well documented. Now the question is: what is IETF going to do
>> about it? This draft and hbh-processing are attempting to address at
>> least part of the problem.
> 
> It’s not like there is a raft of use cases / solutions waiting for extension headers to magically start working.
> I’ve come to the conclusion that it’s just the wrong layer. 3.5 isn’t a layer. ;-)
> Limited domains, sure, there’s some special cases there. Although they could also be resolved by TLVs in tunnel headers.
> 
> But I’m not going to stop anyone who thinks spending effort on EHs is useful.
> 
> Best regards,
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------