[bess] [Technical Errata Reported] RFC9135 (9000)

rfc-editor@rfc-editor.org Wed, 10 June 2026 18:19 UTC

Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: james.n.guichard@futurewei.com, martin.vigoureux@nokia.com, jorge.rabadan@nokia.com, gunter.van_de_velde@nokia.com, ketant.ietf@gmail.com, sajassi@gmail.com, jdrake@juniper.net, ssalam@cisco.com, sthoria@cisco.com, zzhang@juniper.net
Date: Wed, 10 Jun 2026 18:19:24 -0000
message-id: <178111556392.19.2521473977084585538@rfc-editor.org>
Message-ID-Hash: 4C7IGFECQQ5CKEFQMAPAL6V6ARKUWW6D
CC: rfc-editor@rfc-editor.org, bess@ietf.org, alexander.vainshtein@rbbn.com
Precedence: list
Subject: [bess] [Technical Errata Reported] RFC9135 (9000)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/2IuwiB3EbTDnKnm4ZwqQgAsp81s>

The following errata report has been submitted for RFC9135,
"Integrated Routing and Bridging in Ethernet VPN (EVPN)"

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

--------------------------------------
Type: Technical
Reported by: Alexander ("Sasha") Vainshtein <alexander.vainshtein@rbbn.com>

Section 5.1 and 5.2 says:

Original Text
-------------
In Section 5.1:
This route MUST be advertised with two Route Targets, one corresponding to the MAC-VRF of the tenant's subnet
and another corresponding to the tenant's IP-VRF.

In Section 5.2:
When a PE (e.g., PE2 in Figure 4 above) receives this EVPN MAC/IP Advertisement route, it performs the following:

The MAC-VRF Route Target and Ethernet Tag, if the latter is non-zero, are used to identify the correct MAC-VRF and bridge table,
and if they are found, the MAC address is imported.
The IP-VRF Route Target is used to identify the correct IP-VRF, and if it is found, the IP address is imported.

Corrected Text
--------------
In Section 5,1:
This route MUST be advertised with two Route Targets, one corresponding to the MAC-VRF of the tenant's subnet and another corresponding to the tenant's IP-VRF.
The Route Targets corresponding to the tenants IP-VRF SHOULD be omitted if the IP address the NLRI of teh route is a link-local IPv6 address.

In Section 5.2:
When a PE (e.g., PE2 in Figure 4 above) receives this EVPN MAC/IP Advertisement route, it performs the following:

The MAC-VRF Route Target and Ethernet Tag, if the latter is non-zero, are used to identify the correct MAC-VRF and bridge table,
and if they are found, the MAC address is imported.
If the IP address in the NLRI of the route is not an IPv6 link-local address, the IP-VRF Route Target is used to identify the correct IP-VRF, and if it is found, the IP address is imported.

Notes
-----
As per Section 2.5.6 of RFC 4291, "Routers must not forward any packets with Link-Local source or destination addresses to other links".

Therefore, these addresses MUST NOT be in the IP-VRF in ingress PE, and there is no need to attach Route Targets of the IP-VRF in the egress PE because they are used solely for identification of the importing IP-VRF in the ingress PE.

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.

--------------------------------------
RFC9135 (draft-ietf-bess-evpn-inter-subnet-forwarding)
--------------------------------------
Title : Integrated Routing and Bridging in Ethernet VPN (EVPN)
Publication Date : October 2021
Author(s) : A. Sajassi, S. Salam, S. Thoria, J. Drake, J. Rabadan
Category : Proposed Standard
Source : bess (rtg)
Stream : IETF
Verifying Party : IESG

[bess] [Technical Errata Reported] RFC9135 (9000) rfc-editor