Search RFCs

RFC Editor

Found 1 record.

Status:Held for Document Update (1)

RFC 6513, "Multicast in MPLS/BGP IP VPNs", February 2012

Note: This RFC has been updated byRFC 7582, RFC 7900, RFC 7988

Errata ID:3658
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Joël Repiquet
Date Reported: 2013-06-17
Held for Document Update by: Stewart Bryant
Date Held: 2013-09-17

Section 5.3.1 says:

   Whenever a C-multicast route is sent, it must also carry the Selected   Upstream Multicast Hop corresponding to the C-root address   (determined by the procedures of Section 5.1).  The Selected Upstream   Multicast Hop must be encoded as part of a Route Target Extended   Community to facilitate the optional use of filters that can prevent   the distribution of the update to BGP speakers other than the   Upstream Multicast Hop.  See Section 10.1.3 of [MVPN-BGP] for the   details.

It should say:

   Whenever a C-multicast route is sent, it must also carry the Selected   Upstream Multicast Hop corresponding to the C-root address   (determined by the procedures of Section 5.1).  The Selected Upstream   Multicast Hop must be encoded as part of a Route Target Extended   Community to facilitate the optional use of filters that can prevent   the distribution of the update to BGP speakers other than the   Upstream Multicast Hop.  See Section 11.1.3 of [MVPN-BGP] for the   details.

Report New Errata