RFC 7117, "Multicast in Virtual Private LAN Service (VPLS)", February 2014

Errata ID: 7977
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Igor Malyushkin
Date Reported: 2024-06-09
Verifier Name: Gunter Van de Velde
Date Verified: 2025-02-10

Section 4.2 says:

Furthermore, if the local PE uses RSVP-TE P2MP LSP for sending
(multicast) traffic, originated by VPLS sites connected to the PE, to
the sites attached to other PEs, then the local PE MUST use the
Originating Router’s IP Address information carried in the Intra-AS
A-D route to add the PE, that originated the route, as a leaf node to
the LSP. This MUST be done irrespective of whether or not the
received Intra-AS A-D route carries the PMSI Tunnel attribute.

It should say:

Furthermore, if the local PE uses RSVP-TE P2MP LSP for sending
(multicast) traffic, originated by VPLS sites connected to the PE, to
the sites attached to other PEs, then the local PE MUST use the
BGP Next-Hop IP Address carried in the Intra-AS
A-D route to add the PE, that originated the route, as a leaf node to
the LSP. This MUST be done irrespective of whether or not the
received Intra-AS A-D route carries the PMSI Tunnel attribute.

Notes:

There is no such field as the Origination Router's IP Address in any VPLS A-D routes (RFC4761, RFC6074). For Intra-AS cases the BGP NH IP address can be used for the leaf tracking.

Report New Errata