[IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6man-eh-limits-19: (with DISCUSS and COMMENT)
Tom Herbert <tom@herbertland.com> Wed, 16 April 2025 00:17 UTC
Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@mail2.ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A71881CA49BA for <ipv6@mail2.ietf.org>; Tue, 15 Apr 2025 17:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PMHZgX9IleT for <ipv6@mail2.ietf.org>; Tue, 15 Apr 2025 17:17:27 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 105591CA4993 for <ipv6@ietf.org>; Tue, 15 Apr 2025 17:17:26 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5e673822f76so10737563a12.2 for <ipv6@ietf.org>; Tue, 15 Apr 2025 17:17:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1744762646; x=1745367446; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pfRwS85QacBjWE1FVkMG+vZ3bUYjP3zpFzXzzXDTwH0=; b=QhUC+PBWKGfZfP+DkgrXdwKBelDxARjJXPV9C1EH5kmp+slhorCihb10dqJj6OLuBy +9SXSHldmMjKBBMYI/V9pLG+6EtA0kGSJKOCC3HVuv/UA7yM0n/P2pmQ3fdyIZ4niC5j Wyv+xBaShYKHjh4VK2V5vTiiDuKnAlfz0ctZyqz1tmFAhw+fFj8tysuyv2VZhtd+POsN LigbBlIvzTqbJ1GcOH4A4sldq7mYOmyUsMfOTuZce3PZ/YKndoQSrQvG0jglFtJhUhOi iIhu2CPlLI4OUjxmEZTevRxd7Mr1TQ1gNwgofH1rS4j9s/tnhhUro4z7TCX02owW0AR0 43PQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744762646; x=1745367446; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pfRwS85QacBjWE1FVkMG+vZ3bUYjP3zpFzXzzXDTwH0=; b=AVj4+1G79zDR5kZhQdjmug5sDs+vnAPkCWEKLwNJT6WOzT5JrKP6NQcqvCtrCjFtuM u54Y9VEon9BOnMvfs2z59c16CjDJ9AHg5ym77bwSQZRKDUcEYfBuFze61zirB/fWWbBW kVASexO88C062ygDfswAlPFsyMVDLFrTQ1Fb9PuTqQzgmR9B87GmDcPwkQ8+dBFJi/i/ 9abCR1Qop55oPSBfmTvf40HF/Xzf5oAeQqdY3+XK/HLAfAknTArCcFK5ZQVSHMXbKeRh qK80r3GXFMjRN2euJyQAXijcy/AX/yzK7YI4ogz2c2q9+LEyZ4zr7pPWgdCgxVL/E6BJ V4Vw==
X-Forwarded-Encrypted: i=1; AJvYcCUqfyvQnHB3WsqUXJ/umcszv4E/Kl+sq7in9ePFs/67nJadOh1mv5fLd5dtItwd7znK3aFT@ietf.org
X-Gm-Message-State: AOJu0YxFWbiKTlRxXmFWBHSur1tzG5CXQbbBF3P2QnhuHJ8OexTPsupM EvBGUnOtuoLL3HfBLT0zP7LLv3Hh0owaxdPW7bRhZ1K5X4O31YAYu5sI/2i4PUMraQrWnp3zdJo SlV1c9spUPbB+mFsLMgRaEG8kkfsBGIz0tmOq
X-Gm-Gg: ASbGncuaDSHfMH4aVF0JULnWs2tJZ+KHUiyZIaLrDkQUCx6mmeE+TnBvMnYYNhTHbH6 Axzjd54vpIkxr9z1lKtxDQZIQFEq9QVBRj2uF6dOuRrTdA4wZ+rh8SBuw6GY8gXjX8DhvtMxm9x 6WiFZyFuBEPxXM8XbdRodDmRW4tWqYv2zSwrBPK1Z3Rr0vUxoRhgWsWNk=
X-Google-Smtp-Source: AGHT+IFMLyN6CTY4iIkvpgJuTmhrMk9S9y6lSbXyl7a7dU8CostubpA9n7qR7UK5DWQb+w1IUq+vlIA8f3WNo7FDKrE=
X-Received: by 2002:a05:6402:27c7:b0:5dc:c531:e5c0 with SMTP id 4fb4d7f45d1cf-5f49a28c7f6mr955196a12.27.1744762645760; Tue, 15 Apr 2025 17:17:25 -0700 (PDT)
MIME-Version: 1.0
References: <174438813986.996873.14080673571345851328@dt-datatracker-64c5c9b5f9-hz6qg> <CALx6S36Fe_HpPvNqEabhvvxY2ykPJWGMAQiom+yKJPYObuW0QA@mail.gmail.com> <PH0PR11MB49665883D60CE205C0255566A9B22@PH0PR11MB4966.namprd11.prod.outlook.com> <CALx6S37kY01pppvSc5RAG0r32u+Z3vaYt-fwCeNYwvPcnTsRkw@mail.gmail.com> <PAXPR07MB7773C7A6C10D19FB17632FAED6B22@PAXPR07MB7773.eurprd07.prod.outlook.com>
In-Reply-To: <PAXPR07MB7773C7A6C10D19FB17632FAED6B22@PAXPR07MB7773.eurprd07.prod.outlook.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 15 Apr 2025 17:17:13 -0700
X-Gm-Features: ATxdqUHb8bVxaN-omgzctyvFscad9F_Bby0IxFRAMKvlGs0RpYEzvGto56aaOy0
Message-ID: <CALx6S35Rn-sC=USeCN4vUQT2k3GTKM0quzfaPNMszepaeHE4Hg@mail.gmail.com>
To: Tim Chown <Tim.Chown=40jisc.ac.uk@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b7e7300632da35b7"
Message-ID-Hash: NH2K43ZCIPOYJIAL27SDWZEPBMOZUMTA
X-Message-ID-Hash: NH2K43ZCIPOYJIAL27SDWZEPBMOZUMTA
X-MailFrom: tom@herbertland.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, "draft-ietf-6man-eh-limits@ietf.org" <draft-ietf-6man-eh-limits@ietf.org>, 6man Chairs <6man-chairs@ietf.org>, 6man <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, "jeanmichel.combes@orange.com" <jeanmichel.combes@orange.com>, "jounikor@gmail.com" <jounikor@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6man-eh-limits-19: (with DISCUSS and COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iSVlABCaiiMg46Yu9-gLe1AMZHg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>
On Tue, Apr 15, 2025, 1:34 PM Tim Chown <Tim.Chown= 40jisc.ac.uk@dmarc.ietf.org> wrote: > Hi, > > > > On 15/04/2025, 18:31, "Tom Herbert" <tom=40herbertland.com@dmarc.ietf.org> > wrote: > > > > On Tue, Apr 15, 2025 at 6:56 AM Eric Vyncke (evyncke) <evyncke@cisco.com> > wrote: > > > > Hello, > > > > > > > > While I agree that the EH state of the global Internet in 2025 could be > better, I would not qualify this state as ossified as things can / should > improve *except* if router vendors follow the I-D recommendations (mainly > the length of extension header chain) as I firmly believe that the draft > limit will become a de facto standard (i.e., min and max header length set > to 64), hence my main DISCUSS. > > Eric, > > Even if that were true, it would be far greater than the de facto > limit deployed today which is 0 bytes of EH! > > > > > > > > > Rather than putting limits, the draft should have been in V6OPS for > recommendation for applications using EH, as a complement to RFC 9098 > “Operational Implications of IPv6 Packets with Extension Headers” > > I don't believe this is an operational sort of thing. For instance, > suppose an application wishes to send an extension headers. Given that > we know Extension Headers have difficulty making it through the > Internet, the developer would like to know how many bytes of EH they > can send with a high probability of delivery. As of today, there is no > guidance for that, and the result is hardly any deployment of > extension headers. > > Consider from RFC 9673: > > "A Source MAY, based on local configuration, allow only one Hop-by-Hop > option to be included in a packet, or it could allow more than one > Hop-by-Hop option but limit their size to increase the likelihood of > successful transfer across a network path." > > So that recommends that a source may limit the size of Hop-by-Hop > options, but it doesn't offer any specific recommendations. Also, this > doesn't have any recommendations for the header chain length as a > whole, packets are often dropped because the header chain pushes the > transport layer header too deep in the packet so that routers that > require to see it can't and just drop (RFC9098 Section 8.1). WIthout > any guidance, the application developer is in the dark. The only > recourse we have is to fallback to the least common denominator and > not use extension headers. > > > > > > > > > I know that both of us (and others as well) want to keep the potential > use of EH open, but we respectfully disagree on the means. > > What is the alternative you're suggesting? > > > > The problem in my eyes is this document is going well beyond the > relatively cautious wording in RFC 8504, wording which we’ll need to review > with 8504-bis. I’d rather see that text perhaps a little firmer but without > the heavy handed approach of this draft. > > > > I like RFC 9673, it’s more pragmatic. Whereas this document will > effectively set a (small) hard limit on EH size forever, which I object to. > I’d encourage Eric, Gunter and others who object to push back on it. > Tim, I think you might be misreading the draft :-). There are no hard limits. At best, we are making recommendations for the minimal level of support. I think Eric's concern is that if we specify minimum level of support then people will infer that's also the maximum. I get the argument, but if we don't set some expectations then people will decide themselves what the minimum they need to support is, which as we've seen with EH is zero. Tom > > Tim > > > > Thanks, > Tom > > > > > > > > > Regards > > > > > > > > -éric > > > > > > > > From: Tom Herbert <tom@herbertland.com> > > Date: Friday, 11 April 2025 at 18:58 > > To: Eric Vyncke (evyncke) <evyncke@cisco.com> > > Cc: The IESG <iesg@ietf.org>, draft-ietf-6man-eh-limits@ietf.org < > draft-ietf-6man-eh-limits@ietf.org>, 6man-chairs@ietf.org < > 6man-chairs@ietf.org>, ipv6@ietf.org <ipv6@ietf.org>, > suresh.krishnan@gmail.com <suresh.krishnan@gmail.com>, > jeanmichel.combes@orange.com <jeanmichel.combes@orange.com>, > jounikor@gmail.com <jounikor@gmail.com> > > Subject: Re: Éric Vyncke's Discuss on draft-ietf-6man-eh-limits-19: > (with DISCUSS and COMMENT) > > > > On Fri, Apr 11, 2025 at 9:15 AM Éric Vyncke via Datatracker > > <noreply@ietf.org> wrote: > > > > > > Éric Vyncke has entered the following ballot position for > > > draft-ietf-6man-eh-limits-19: Discuss > > > > > > When responding, please keep the subject line intact and reply to all > > > email addresses included in the To and CC lines. (Feel free to cut this > > > introductory paragraph, however.) > > > > > > > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > > > for more information about how to handle DISCUSS and COMMENT positions. > > > > > > > > > The document, along with other ballot positions, can be found here: > > > https://datatracker.ietf.org/doc/draft-ietf-6man-eh-limits/ > > > > > > > > > > > > ---------------------------------------------------------------------- > > > DISCUSS: > > > ---------------------------------------------------------------------- > > > > > > > > > # Éric Vyncke, INT AD, comments for draft-ietf-6man-eh-limits-19 > > > CC @evyncke > > > > > > Thank you for the work put into this document, as explained below I > think that > > > the author wants to facilitate the use of extension headers, but I am > deeply > > > concerned about having a reverse effect and actually leading to an IPv6 > > > ossification. > > > > Eric, > > > > IMO, IPv6 is already ossified. Not by the protocol definition, but by > > real deployment. A main impediment to the deployment of extensions is > > the fact they *aren't* limited. Processing an arbitrary number of > > extension headers or EH options isn't feasible. Frankly, it never was. > > Very quickly router vendors saw this and made their own limits in the > > absence of any guidance. But this is not just a router issue, it's > > pretty obvious that hosts also need to limit receive processing to > > prevent DoS attack. For instance, no receiver will support, or should > > blindly support, a packet with 700 Destination Options or HBH > > options-- the only use case for this is DoS attack. On the other hand, > > we really need wide support for something greater than zero or the > > whole EH mechanism is pointless. This is where guidance is needed that > > provides a reasonable limit greater than zero and less than 700. And > > once we convey guidance on receiver limits, it makes sense to provide > > corresponding sender limits. > > > > So the whole point of the draft is instead of letting everyone come up > > with their own adhoc limits, we give clear guidance for the *minimum* > > level of support. If people want to exceed the minimums that's great. > > Also, most of this draft is actually documenting existing limits that > > are already fully deployed. Limits for routers are mostly based on the > > size of their parsing buffer, host side limits are in place to prevent > > DoS attack (the default configuration in Linux applies the limits in > > the draft for several years). > > > > Tom > > > > > > > > Please find below one blocking DISCUSS points (easy to address), some > > > non-blocking COMMENT points (but replies would be appreciated even if > only for > > > my own education), and some nits. > > > > > > Special thanks to Suresh Krishnan for the shepherd's *incomplete > (Q3-5)* > > > write-up including the WG consensus and the detailed justification of > the > > > intended status. > > > > > > Other thanks to Jean-Michel Combes, the Internet directorate reviewer > (at my > > > request): > > > > https://datatracker.ietf.org/doc/review-ietf-6man-eh-limits-19-intdir-telechat-combes-2025-04-03/ > > > (and I have read the email discussion) > > > > > > Other thanks to Jouni Korhonen , the IoT directorate reviewer (at my > request): > > > > https://datatracker.ietf.org/doc/review-ietf-6man-eh-limits-19-iotdir-telechat-korhonen-2025-04-09/ > > > (and I expect to read a reply soon) > > > > > > I hope that this review helps to improve the document, > > > > > > Regards, > > > > > > -éric > > > > > > ## DISCUSS (blocking) > > > > > > As noted in https://www.ietf.org/blog/handling-iesg-ballot-positions/, > a > > > DISCUSS ballot is just a request to have a discussion on the following > topics: > > > > > > ### Race to the bottom > > > > > > Even if I can only laud the intention of the author and of the 6MAN > WG, I am > > > deeply concerned that: > > > > > > 1) short-term: this is wishful thinking, i.e., it won't change the > existing > > > networks (being the global Internet or private/enterprise networks) 2) > > > long-term: if ever this I-D is published, it will most probably end up > in call > > > for tender or other BCP, i.e., vendors will limit themselves to the > different > > > limits written in this document and not try to go beyond, leading to an > > > ossification of the Internet and preventing creative use of extension > headers. > > > > > > The limits are based on studies done in 2022 and 2023 over the public > Internet, > > > this raises two problems: 1) the document should probably restrict its > > > applicability to the public Internet (I find the disclaimers "unless > it is > > > known to work" rather repetitive and too vague) 2) limiting the future > of the > > > Internet based on studies of 2022/2023 (i.e., going over routers dating > > > possibly back to 2017... and being unaware whether it is an operator > policy or > > > a router HW limitation) is too restrictive. 64 bytes for the extension > header > > > chain is really limiting. > > > > > > About 2), I do not know any other RFC limiting the feature set of an > existing > > > deployed protocol. > > > > > > I am afraid that I cannot see how the above points can be addressed. > > > > > > ### Conflict with RFC 8504 > > > > > > Section 5.3 of RFC 8504 (a BCP) uses a lot of "MAY" about the same > limits as in > > > this document. I.e., how can this informational I-D modify a BCP "MAY" > into a > > > "SHOULD" ? This is confusing at least. A way forward would be to use a > normal > > > "should" w/o BCP14 weight. > > > > > > ### Section 2 > > > > > > As the intended status is informational, please do not use "defined" in > > > `defined in this document` but perhaps "suggested". > > > > > > ### Section 3 > > > > > > `all intermediate nodes in a Routing Header in the case of a > Destination > > > Options header before the Routing Header,` is really unclear (or at > least I > > > cannot parse it). Suggest removing "in a Routing Header". > > > > > > AFAIK, all IPv6 nodes are able to skip the IPsec AH, so `the IPsec > header > > > obfuscates following headers so that they are unreadable by nodes in > the path` > > > is wrong and should rather be specific to ESP. > > > > > > `A source host should follow the recommendations in Section 4.1 of > [RFC8200] > > > for extension header ordering`, isn't this obvious ? There is little > point to > > > repeat what is written in RFC 8200 (this is only a source of confusion > IMHO). > > > > > > ### Section 4 > > > > > > `expands the requirements to be applicable to intermediate nodes,` > another > > > conflict with RFC 8504. > > > > > > > > > ---------------------------------------------------------------------- > > > COMMENT: > > > ---------------------------------------------------------------------- > > > > > > > > > ## COMMENTS (non-blocking) > > > > > > ### Section 1.1 > > > > > > RFC 9000 (QUIC) does not really the IPv6 extension headers length as > this > > > length is linked to the IPv6 MTU. The current text tries somehow to > explain it, > > > but it does not seem like the EH limit is done on purpose by QUIC, > this is more > > > a side effect than an explicit limit. > > > > > > ### Section 1.3 > > > > > > As the terminology is mostly the one use by RFC 8200, let's add a > reference to > > > RFC 8200. > > > > > > ### Section 2 > > > > > > This section goes over a simple overview as it also describes > behaviours and > > > rationale, the title should probably be changed. > > > > > > Please start a new paragraph starting with `For a router, the action > to` else > > > the text is confusing. > > > > > > Should there be text about layer-4 ACL for routers ? (it is briefly > touched in > > > section 5 but probably deserved some text in this section as well) > > > > > > `This document defines limits to optionally enforce` but as the text is > > > informational and contains a lot of "SHOULD", does "optionally" make > sense ? > > > I.e., everything could be seen as optional. > > > > > > ### Section 3 > > > > > > As the section is `Host limits for sending extension headers`, does it > not > > > apply to routers and intermediate nodes ? > > > > > > I think that final node can be configured to ignored hop-by-hop > options per RFC > > > 8200, so, the text `will ignore options that exceed their limit in the > case of > > > routers` should not restrict to routers only. > > > > > > ### Section 4 > > > > > > s/As *described* in [RFC8504] a destination host /As *specified* in > [RFC8504] a > > > destination host / as RFC 8504 is a BCP. > > > > > > `allows a receiving node to send an ICMP error [RFC8883] if a limit > has been > > > exceeded.` I do not see why this I-D 'allows' because RFC 8883 (by the > same > > > author :-) ) is standard track, so of course nodes are allowed to send > this > > > ICMP. Same for `it MAY send an ICMP Parameter Problem message` and in > other > > > places. > > > > > > ### Section 5 > > > > > > To be honest, the first paragraph is probably the only part of the I-D > that > > > appears OK and valuable... ``` > > > A router may establish limits for processing packets with received > > > extension headers. If a limit is exceeded, routers SHOULD still > > > forward the packet and SHOULD NOT drop packets because a limit is > > > exceeded. > > > ``` > > > > > > and later > > > > > > ``` > > > * If a router needs to parse the upper layer protocol, for instance > > > to deduce the transport layer port numbers, it MUST be able to > > > correctly forward a packet containing eight or fewer extension > > > headers that precede the transport layer header. > > > ``` > > > > > > and a few other paragraph in this section including the order of > extension > > > headers. > > > > > > ### Appendix A.2 > > > > > > Who is the "we" in `We can extrapolate` ? Is it the author ? The 6MAN > WG ? The > > > IETF Community ? Please be accurate here. > > > > > > `At the time of writing,` does not age well... please use the date of > APNIC & > > > Ana Custura's papers. > > > > > > ### Section 7 > > > > > > Shameless plug: I would have expected to have RFC 9099 listed as well. > > > > > > > > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > List Info: https://mailman3.ietf.org/mailman3/lists/ipv6@ietf.org/ > -------------------------------------------------------------------- >
- [IPv6]Éric Vyncke's Discuss on draft-ietf-6man-eh… Éric Vyncke via Datatracker
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tom Herbert
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Eric Vyncke (evyncke)
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tom Herbert
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tim Chown
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tom Herbert
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tim Chown
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Sebastian Moeller
- [IPv6]Re: Éric Vyncke's Discuss on draft-ietf-6ma… Tim Chown