Re: [IPv6] Fwd: New Version Notification for draft-ietf-6man-eh-limits-05.txt

Technically, this looks good.

With my IETF Process Wonk hat on, I very much doubt that a BCP is
allowed to formally update a standards track document. I suggest
discussing that with immediately the AD to avoid much wider debate
during IETF Last Call and IESG review. Alternatively, simply
remove Updates: 8200.  I am not convinced that the draft does truly
*update* RFC8200. There is this:

> 3.  Requirements
> 
>    This section lists the normative requirements related to sending and
>    processing extension headers.  The requirements in this section
>    update the processing requirements specified in Section 4 of
>    [RFC8200]; in particular, requirements for how many Hop-by-Hop
>    options an intermediate node must process are updated.

but I don't see where section 4 of RFC8200 states how many HbH options
a node *must* process. So I think that this BCP does *not* in fact
update RFC8200. A more accurate phrase would be:
"The requirements in this section augment the processing requirements ..."
If agreed, that would resolve my Process Wonk dilemma.

Regards
    Brian

On 26-Sep-23 11:17, Tom Herbert wrote:
> Hi,
> 
> I posted a new version of the Extension Header Limits draft. The
> primary change is to make intended status BCP per feedback. There are
> also some other edits.
> 
> Thanks,
> Tom
> 
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Mon, Sep 25, 2023 at 3:15 PM
> Subject: New Version Notification for draft-ietf-6man-eh-limits-05.txt
> To: Tom Herbert <tom@herbertland.com>
> 
> 
> A new version of Internet-Draft draft-ietf-6man-eh-limits-05.txt has been
> successfully submitted by Tom Herbert and posted to the
> IETF repository.
> 
> Name:     draft-ietf-6man-eh-limits
> Revision: 05
> Title:    Limits on Sending and Processing IPv6 Extension Headers
> Date:     2023-09-25
> Group:    6man
> Pages:    21
> URL:      https://www.ietf.org/archive/id/draft-ietf-6man-eh-limits-05.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-6man-eh-limits/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-6man-eh-limits
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-6man-eh-limits-05
> 
> Abstract:
> 
>     This specification defines various limits that may be applied to
>     receiving, sending, and otherwise processing packets that contain
>     IPv6 extension headers.  The need for such limits is pragmatic to
>     facilitate interoperability amongst hosts and routers in the presence
>     of extension headers and thereby increasing the feasibility of
>     deployment of extension headers.  The limits described herein
>     establish the minimum baseline of support for use of extension
>     headers in the Internet.  If it is known that all communicating
>     parties for a particular communication, including end hosts and any
>     intermediate nodes in the path, are capable of supporting more than
>     the baseline then these default limits may be freely exceeded.  When
>     published, this specification updates [RFC8200] and [RFC8504].
> 
> 
> 
> The IETF Secretariat
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------