[IPv6]Éric Vyncke's Discuss on draft-ietf-6man-eh-limits-19: (with DISCUSS and COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Fri, 11 April 2025 16:15 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 03B4F1AC62D2; Fri, 11 Apr 2025 09:15:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174438813986.996873.14080673571345851328@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Fri, 11 Apr 2025 09:15:39 -0700
Message-ID-Hash: EEXURWS5XWDCXVY7KWBCZV2LXKQPIEAI
X-Message-ID-Hash: EEXURWS5XWDCXVY7KWBCZV2LXKQPIEAI
X-MailFrom: noreply@ietf.org
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: draft-ietf-6man-eh-limits@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, suresh.krishnan@gmail.com, jeanmichel.combes@orange.com, jounikor@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [IPv6]É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/8a7CkOXbZOK1pbXxApiR4GFcP-8>
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>

É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.

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.