[bess] [Technical Errata Reported] RFC10018 (9139)

rfc-editor@rfc-editor.org Mon, 17 August 2026 20:19 UTC

Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: danvoyerwork@gmail.com, rishabh@arrcus.com, james.n.guichard@futurewei.com, cfilsfil@cisco.com, ketant.ietf@gmail.com, gunter.van_de_velde@nokia.com, hooman.bidgoli@nokia.com, gunter@vandevelde.cc, zzhang@juniper.net, slitkows.ietf@gmail.com
message-id: <178699795523.13.9589770869303200186@rfc-editor.org>
Message-ID-Hash: HKPV3FOX7ZRPNTOZFPFQIBG3NZ6JJO6T
CC: rfc-editor@rfc-editor.org, bess@ietf.org, paitken@ciena.com
Precedence: list
Subject: [bess] [Technical Errata Reported] RFC10018 (9139)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/-FrC-8p8h_aPK2fLHxqPShhaVSY>
Date: Mon, 17 Aug 2026 20:19:15 -0000

The following errata report has been submitted for RFC10018,
"Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress Replication"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9139/

--------------------------------------
Type: Technical
Reported by: Paul Aitken <paitken@ciena.com>

Section 4.1.1.1.1. and 4.2.1. says:

Original Text
-------------
4.1.1.1.1.) "When an SR P2MP P-tunnel is not shared across MVPNs, i.e., there is one-to-one association between an EVI and an SR P2MP P-tunnel, the MPLS Label field is set to zero as per [RFC6514]. In this case, the SR-MPLS Tree-SID of the PTI of the SR P2MP Policy advertised in the P-tunnel is sufficient to identify the MVPN instance for delivering the payload."

4.2.1.) "PE1 will encapsulate the MVPN payload into the MPLS label stack <L1, L2, L3, L10> with L10 as the BoS label."

Corrected Text
--------------
4.1.1.1.1.) "When an SR P2MP P-tunnel is not shared across EVIs, i.e., there is one-to-one association between an EVI and an SR P2MP P-tunnel, the MPLS Label field is set to zero as per [RFC6514]. In this case, the SR-MPLS Tree-SID of the PTI of the SR P2MP Policy advertised in the P-tunnel is sufficient to identify the EVI for delivering the payload."

4.2.1.) "PE1 will encapsulate the EVPN payload into the MPLS label stack <L1, L2, L3, L10> with L10 as the BoS label."

Notes
-----
In section 4.1.1.1.1, two occurrences of "MVPN" appear to be copied from Section 3.2.1.1.

In section 4.2.1, "MVPN payload" should be "EVPN payload" (copied from 3.3.1).

Instructions:
-------------
This erratum is currently posted as "Reported". Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC10018 (draft-ietf-bess-mvpn-evpn-sr-p2mp)
--------------------------------------
Title : Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress Replication
Publication Date : August 2026
Author(s) : R. Parekh, Ed., D. Voyer, Ed., C. Filsfils, H. Bidgoli, Z. Zhang
Category : Proposed Standard
Source : bess (rtg)
Stream : IETF
Verifying Party : IESG

[bess] [Technical Errata Reported] RFC10018 (9139) rfc-editor