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

Brian E Carpenter <> Tue, 26 September 2023 01:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7A08EC151090 for <>; Mon, 25 Sep 2023 18:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Status: No, score=-7.196 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nSA6qaGdMt6O for <>; Mon, 25 Sep 2023 18:41:19 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::22a]) (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 (Postfix) with ESMTPS id C3313C15152E for <>; Mon, 25 Sep 2023 18:41:05 -0700 (PDT)
Received: by with SMTP id 5614622812f47-3ae214a077cso3938214b6e.0 for <>; Mon, 25 Sep 2023 18:41:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1695692464; x=1696297264;; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=618ZITmXXKYBr2/5nFoNcQUCB3EU2P5SJyqlbkfrOZ0=; b=m0MgBz7ThYF/sCJ6/woBJz/bqyxt7iTp5omFk5a0YB7yqqTNdQ1l5Ekr/v++lSUBmJ cY37EZ93Q+XKjDmVZH82QPPYP0S1Lr0xC0W8RyfOjHu1FuECiW8THiLUpppzZcdWv9WU bGb52CnMgJN2KzTVG1mMwBXePcq+QxJmXdgP0wFjX071m7BeJRJoaiknB0O8Ory26sWa sORIBAlTIgmc88FCR7OlRi/kaQo8KR4YittTOMIf+pJp5q9WhKpdflwYr4ga7YwCh1RC 4Fxs4WjjNgsiffOEuDsAW/+xALHpxHvyRgqITwLvtV99p9JprAOA3sqMxeNWvLNhrOIy 5XoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1695692464; x=1696297264; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=618ZITmXXKYBr2/5nFoNcQUCB3EU2P5SJyqlbkfrOZ0=; b=qTA1vcp3AU8+qHlS5w+NCPVfR9DE4DcvGSkFBYzvOZtQ4vYLcJ//7h/IKo73a6ABQJ eLP9qvjinUZzuXGuRsWMAFe5bacEARWXB9YxR8F1UgR9LaYGpD9TFUZcDR3EgJ1M+dR7 CT0u6+F5lja1FP7t8Tw06NUSm6QXEZgOkSIK1PQD5C24rS0MCvoGMBv3R4MU6tFuSoaq 8B6qZiG1gdA1MZVzN1TseSJ12vJ0vjXAPez0J1w2RA2dUbwoTJJFg7h2hWGAlkmmNf5p ySu+kanjC+7sWxd5OJly6CUxKOWN9Ldy+Ao8Yo7hVSEAsAW/11EHppTcnXjEseHFg/Rx PWcg==
X-Gm-Message-State: AOJu0Yz7vZSgwDlqwh1MZeNkMgRNbQI9esR1dJlgtAQffuTaPgj1fiiR /Gj+XviRE3t1iVmX/rF348RX6rvLNHoFgQ==
X-Google-Smtp-Source: AGHT+IHy26CH5biVz3xVsCTriLh27xqAMnGXE8i11/6tG/NZ0hgsGIJsV3NPYiiLkiErCdrsE5VbtQ==
X-Received: by 2002:a05:6808:2094:b0:3ad:f5b3:844c with SMTP id s20-20020a056808209400b003adf5b3844cmr12612851oiw.18.1695692464530; Mon, 25 Sep 2023 18:41:04 -0700 (PDT)
Received: from ?IPV6:2406:e003:110d:5301:8cb6:a2c:7461:4047? ([2406:e003:110d:5301:8cb6:a2c:7461:4047]) by with ESMTPSA id fe18-20020a056a002f1200b0069102aa1918sm8740935pfb.48.2023. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Sep 2023 18:41:04 -0700 (PDT)
Message-ID: <>
Date: Tue, 26 Sep 2023 14:40:59 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Tom Herbert <>, 6man <>
References: <> <>
From: Brian E Carpenter <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <>
Subject: Re: [IPv6] Fwd: New Version Notification for draft-ietf-6man-eh-limits-05.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 26 Sep 2023 01:41:23 -0000

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.


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: <>
> Date: Mon, Sep 25, 2023 at 3:15 PM
> Subject: New Version Notification for draft-ietf-6man-eh-limits-05.txt
> To: Tom Herbert <>
> 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:
> Status:
> HTMLized:
> Diff:
> 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
> Administrative Requests:
> --------------------------------------------------------------------