Found 1 record.

Status: Verified (1)

RFC 9136, "IP Prefix Advertisement in Ethernet VPN (EVPN)", October 2021

Errata ID: 8474
Status: Verified
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Zhaohui (Jeffrey) Zhang
Date Reported: 2025-06-20
Verifier Name: Gunter Van de Velde
Date Verified: 2025-07-07

Section 4.1 says:

   An example of inter-subnet forwarding between subnet SN1, which uses
   a 24-bit IP prefix (written as SN1/24 in the future), and a subnet
   sitting in the WAN is described below.  NVE2, NVE3, DGW1, and DGW2
   are running BGP EVPN.  TS2 and TS3 do not participate in dynamic
   routing protocols, and they only have a static route to forward the
   traffic to the WAN.  SN1/24 is dual-homed to NVE2 and NVE3.

It should say:

   An example of inter-subnet forwarding between subnet SN1, which uses
   a 24-bit IP prefix (hereafter referred to as SN1/24), and a subnet
   sitting in the WAN is described below.  NVE2, NVE3, DGW1, and DGW2
   are running BGP EVPN.  TS2 and TS3 do not participate in dynamic
   routing protocols, and they only have a static route to forward the
   traffic to the WAN.  SN1/24 is dual-homed to NVE2 and NVE3.

Notes:

In the original text, the phrase:

"(written as SN1/24 in the future)"

may be misinterpreted. The intended meaning is that the notation SN1/24, referring to subnet SN1 with a 24-bit IP prefix, will be used throughout the remainder of the document for brevity. However, the wording could be ambiguously perceived as either (a) suggesting that this notation will be adopted in future revisions or drafts, or (b) implying a forward-looking change in nomenclature.

Report New Errata