RFC 6514 - BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs

Overview

Positive

what Ze has

Neutral

measures that are neither good news nor bad

Negative

what Ze owes

The 8 shares marked as a part above are the whole of the 133 gated MUSTs: they add to 100%. Proven by a recorded break is a share of TAGGED UNITS, a different population, so it is not one of them.

At a glance

Enrolment

Not enrolled (out-of-scope, the requirements ARE extracted and the owner decided not to offer the feature for now, so the absence is a scope decision rather than a conformance gap): BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs. OUT OF SCOPE by owner decision, 2026-09-01, marked for future development. The extraction is COMPLETE: the source text is at rfc/full/rfc6514.txt and this summary declares all 201 requirements, 133 of them MUST-level, so a later decision to build MVPN starts from the obligations rather than from nothing. What Ze has today is NLRI plumbing and nothing the RFC is about: the Section 4 route-type split (splitMVPN, internal/core/bgp/nlri/nlrisplit/mvpn.go), an NLRI codec, a config route parser for three of the seven route types, and opaque Adj-RIB-In storage. Exactly one MUST-level requirement is met and it is met vacuously -- RFC6514-9.1.1-10 says the Leaf Information Required flag "MUST be set to zero and MUST be ignored on receipt", and Ze ignores it by never parsing a PMSI byte, because knownAttrParsers leaves attribute code 22 nil. Absent entirely: the PMSI Tunnel attribute, the PE Distinguisher Labels attribute (code 27 has no constant), the Source AS and VRF Route Import extended communities, auto-discovery, the C-multicast route exchange, S-PMSI routes, inter-AS and ASBR operation, upstream multicast hop selection (SAFI 129 is unregistered), and every protocol the document leans on -- PIM, mLDP, RSVP-TE P2MP and MSDP. No {gap} annotation is written for any of it: a gap is an ISSUE and this is a DECISION (ai/rules/rfc-compliance.md), and 132 gap rows would record a feature nobody chose to build as 132 conformance failures.

What the public ledger says

Status: Future

Coverage

No test and no annotation (133): RFC6514-4.5-1, RFC6514-4.5-2, RFC6514-5-1, RFC6514-5-2, RFC6514-5-3, RFC6514-5-4, RFC6514-5-7, RFC6514-5-8, RFC6514-6-1, RFC6514-6-2, RFC6514-6-3, RFC6514-7-1, RFC6514-7-2, RFC6514-7-4, RFC6514-7-5, RFC6514-8-1, RFC6514-8-3, RFC6514-8-4, RFC6514-9.1.1-1, RFC6514-9.1.1-2, RFC6514-9.1.1-4, RFC6514-9.1.1-5, RFC6514-9.1.1-6, RFC6514-9.1.1-7, RFC6514-9.1.1-8, RFC6514-9.1.1-9, RFC6514-9.1.1-10, RFC6514-9.1.1-11, RFC6514-9.1.1-12, RFC6514-9.1.1-14, RFC6514-9.1.2-2, RFC6514-9.2-1, RFC6514-9.2-3, RFC6514-9.2-4, RFC6514-9.2-5, RFC6514-9.2-6, RFC6514-9.2-9, RFC6514-9.2-11, RFC6514-9.2-14, RFC6514-9.2.1-1, RFC6514-9.2.1-3, RFC6514-9.2.3.2-1, RFC6514-9.2.3.2-2, RFC6514-9.2.3.2-3, RFC6514-9.2.3.2-5, RFC6514-9.2.3.2-6, RFC6514-9.2.3.2-7, RFC6514-9.2.3.2.1-1, RFC6514-9.2.3.2.1-2, RFC6514-9.2.3.2.1-3, RFC6514-9.2.3.2.1-4, RFC6514-9.2.3.2.1-5, RFC6514-9.2.3.2.1-6, RFC6514-9.2.3.2.1-7, RFC6514-9.2.3.3-2, RFC6514-9.2.3.4-1, RFC6514-9.2.3.4-2, RFC6514-9.2.3.4-3, RFC6514-9.2.3.4-5, RFC6514-9.2.3.4.1-1, RFC6514-9.2.3.4.1-2, RFC6514-9.2.3.4.1-3, RFC6514-9.2.3.4.1-4, RFC6514-9.2.3.4.1-5, RFC6514-9.2.3.4.1-6, RFC6514-9.2.3.4.1-7, RFC6514-10-2, RFC6514-10-4, RFC6514-10-6, RFC6514-10-7, RFC6514-11.1.1.1-1, RFC6514-11.1.1.1-2, RFC6514-11.1.1.2-1, RFC6514-11.1.1.2-2, RFC6514-11.1.3-1, RFC6514-11.1.4-1, RFC6514-11.1.4-2, RFC6514-11.1.4-3, RFC6514-11.2-1, RFC6514-11.2-2, RFC6514-11.3.1.1-1, RFC6514-11.3.1.1-3, RFC6514-11.3.1.2-1, RFC6514-12.1-1, RFC6514-12.1-2, RFC6514-12.1-3, RFC6514-12.1-4, RFC6514-12.1-5, RFC6514-12.1-6, RFC6514-12.1-7, RFC6514-12.1-8, RFC6514-12.1-12, RFC6514-12.1-13, RFC6514-12.1-14, RFC6514-12.1-16, RFC6514-12.1-18, RFC6514-12.1-19, RFC6514-12.1-20, RFC6514-12.1-21, RFC6514-12.1-22, RFC6514-12.2.1-3, RFC6514-12.2.1-4, RFC6514-12.3-1, RFC6514-13-1, RFC6514-13-2, RFC6514-13.1-1, RFC6514-13.1-2, RFC6514-13.1-3, RFC6514-13.1-4, RFC6514-13.1-6, RFC6514-13.2-1, RFC6514-13.2-2, RFC6514-13.2.1-1, RFC6514-13.2.1-3, RFC6514-13.2.1-4, RFC6514-13.2.1-5, RFC6514-14-1, RFC6514-14-2, RFC6514-14.1-1, RFC6514-14.1-2, RFC6514-14.1-3, RFC6514-14.2-1, RFC6514-14.2-2, RFC6514-14.2-3, RFC6514-14.2-4, RFC6514-14.2-5, RFC6514-14.2-6, RFC6514-14.2-7, RFC6514-14.2-8, RFC6514-14.2-9, RFC6514-17-2, RFC6514-17-3, RFC6514-17-4

Requirements

Gaps and untested MUSTs

Proof state

A tagged unit reads unproven where no discrimination record exists for it: nothing in this tree has been observed to break it, so the claim its tag makes is unproven.

RFC6514-4.5-1

Source Active A-D routes with a Multicast group belonging to the Source Specific Multicast (SSM) range (as defined in [RFC4607], and potentially extended locally on a router) MUST NOT be advertised by a router (§4.5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-4.5-1, so no unit is bound to it.

RFC6514-4.5-2

Source Active A-D routes with a Multicast group belonging to the Source Specific Multicast (SSM) range (as defined in [RFC4607], and potentially extended locally on a router) MUST NOT be advertised by a router and MUST be discarded if received. (§4.5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-4.5-2, so no unit is bound to it.

RFC6514-5-1

When the Tunnel Type is set to Protocol Independent Multicast - Sparse Mode (PIM-SM) tree, the Tunnel Identifier is <Sender Address, P-Multicast Group>. The node that originated the attribute MUST use the address carried in the Sender Address as the source IP address for the IP/GRE (Generic Routing Encapsulation) encapsulation of the MVPN data. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-1, so no unit is bound to it.

RFC6514-5-2

When the Tunnel Type is set to PIM-SSM tree, the Tunnel Identifier is <P-Root Node Address, P-Multicast Group>. The node that originates the attribute MUST use the address carried in the P-Root Node Address as the source IP address for the IP/GRE encapsulation of the MVPN data. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-2, so no unit is bound to it.

RFC6514-5-3

The P-Multicast Group in the Tunnel Identifier of the Tunnel attribute MUST NOT be expected to be the same group for all Intra-AS A-D routes for the same MVPN. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-3, so no unit is bound to it.

RFC6514-5-4

When the Tunnel Type is set to BIDIR-PIM tree, the Tunnel Identifier is <Sender Address, P-Multicast Group>. The node that originated the attribute MUST use the address carried in the Sender Address as the source IP address for the IP/GRE encapsulation of the MVPN data. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-4, so no unit is bound to it.

RFC6514-5-7

An implementation MUST provide debugging facilities to permit issues caused by a malformed PMSI Tunnel attribute to be diagnosed. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-7, so no unit is bound to it.

RFC6514-5-8

An implementation MUST provide debugging facilities to permit issues caused by a malformed PMSI Tunnel attribute to be diagnosed. At a minimum, such facilities MUST include logging an error when such an attribute is detected. (§5)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-5-8, so no unit is bound to it.

RFC6514-6-1

The Global Administrator field of this Community MUST be set to the ASN of the PE. (§6)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-6-1, so no unit is bound to it.

RFC6514-6-2

The Local Administrator field of this Community MUST be set to 0. (§6)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-6-2, so no unit is bound to it.

RFC6514-6-3

A PE that has sites of that MVPN connected to it, and originates a (unicast) route to VPN-IP addresses associated with the destinations within these sites, MUST include in the BGP Update message that carries this route the Source AS Extended Community. (§6)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-6-3, so no unit is bound to it.

RFC6514-7-1

To support MVPN in addition to the import/export Route Target(s) Extended Communities used by the unicast routing, each VRF on a PE MUST have an import Route Target Extended Community, except if it is known a priori that none of the (local) MVPN sites associated with the VRF contain multicast source(s) and/or C-RP; in which case, the VRF need not have this import Route Target. (§7)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-7-1, so no unit is bound to it.

RFC6514-7-2

The Global Administrator field of the C-multicast Import RT MUST be set to an IP address of the PE. (§7)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-7-2, so no unit is bound to it.

RFC6514-7-4

To accomplish this, a PE that originates a (unicast) route to VPN-IP addresses MUST include in the BGP Updates message that carries this route the VRF Route Import Extended Community that has the value of the C-multicast Import RT of the VRF associated with the route (§7)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-7-4, so no unit is bound to it.

RFC6514-7-5

To accomplish this, a PE that originates a (unicast) route to VPN-IP addresses MUST include in the BGP Updates message that carries this route the VRF Route Import Extended Community that has the value of the C-multicast Import RT of the VRF associated with the route, except if it is known a priori (e.g., via provisioning) that none of these addresses could act as multicast sources and/or RP; in which case, the (unicast) route MUST NOT carry the VRF Route Import Extended Community. (§7)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-7-5, so no unit is bound to it.

RFC6514-8-1

Each of the PE addresses in the PE Distinguisher Labels attribute MUST be of the same address family as the "Originating Router's IP Address" of the route that is carrying the attribute. (§8)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-8-1, so no unit is bound to it.

RFC6514-8-3

An implementation MUST provide debugging facilities to permit issues caused by malformed PE Distinguisher Label attribute to be diagnosed. (§8)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-8-3, so no unit is bound to it.

RFC6514-8-4

An implementation MUST provide debugging facilities to permit issues caused by malformed PE Distinguisher Label attribute to be diagnosed. At a minimum, such facilities MUST include logging an error when such an attribute is detected. (§8)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-8-4, so no unit is bound to it.

RFC6514-9.1.1-1

To participate in the MVPN auto-discovery/binding, a PE router that has a given VRF of a given MVPN MUST, except for the cases specified in this section, originate an Intra-AS I-PMSI A-D route and advertises this route in IBGP. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-1, so no unit is bound to it.

RFC6514-9.1.1-2

If the PE that originates the advertisement uses a P-multicast tree for the P-tunnel for the MVPN, the PMSI Tunnel attribute MUST contain the identity of the tree (note that the PE could create the identity of the tree prior to the actual instantiation of the tree). (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-2, so no unit is bound to it.

RFC6514-9.1.1-4

A PE that uses a P-multicast tree for the P-tunnel MAY aggregate two or more MVPNs present on the PE onto the same tree. In this case, in addition to carrying the identity of the tree, the PMSI Tunnel attribute of the Intra-AS I-PMSI A-D route MUST carry an MPLS upstream-assigned label that the PE has bound uniquely to the MVPN associated with this route (as determined by its RTs). (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-4, so no unit is bound to it.

RFC6514-9.1.1-5

If the PE has already advertised Intra-AS I-PMSI A-D routes for two or more MVPNs that it now desires to aggregate, then the PE MUST re-advertise those routes. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-5, so no unit is bound to it.

RFC6514-9.1.1-6

The re-advertised routes MUST be the same as the original ones, except for the PMSI Tunnel attribute and the label carried in that attribute. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-6, so no unit is bound to it.

RFC6514-9.1.1-7

If the PE that originates the advertisement uses ingress replication for the P-tunnel for the MVPN, the route MUST include the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication and Tunnel Identifier set to a routable address of the PE. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-7, so no unit is bound to it.

RFC6514-9.1.1-8

The PMSI Tunnel attribute MUST carry a downstream-assigned MPLS label. This label is used to demultiplex the MVPN traffic received over a unicast tunnel by the PE. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-8, so no unit is bound to it.

RFC6514-9.1.1-9

The Leaf Information Required flag of the PMSI Tunnel attribute MUST be set to zero (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-9, so no unit is bound to it.

RFC6514-9.1.1-10

The Leaf Information Required flag of the PMSI Tunnel attribute MUST be set to zero and MUST be ignored on receipt. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-10, so no unit is bound to it.

RFC6514-9.1.1-11

The Next Hop field of the MP_REACH_NLRI attribute of the route MUST be set to the same IP address as the one carried in the Originating Router's IP Address field. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-11, so no unit is bound to it.

RFC6514-9.1.1-12

That is, by default, the Intra-AS I-PMSI A-D route MUST carry the export Route Target used by the unicast routing. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-12, so no unit is bound to it.

RFC6514-9.1.1-14

Note that if non-segmented inter-AS P-tunnels are being used, then the Intra-AS I-PMSI routes need to be distributed to other ASes and MUST NOT carry the NO_EXPORT Community. (§9.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.1-14, so no unit is bound to it.

RFC6514-9.1.2-2

If the Tunnel Type in the PMSI Tunnel attribute is set to RSVP-TE P2MP LSP, then the PE that originated the route MUST establish an RSVP-TE P2MP LSP with the local PE as a leaf. (§9.1.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.1.2-2, so no unit is bound to it.

RFC6514-9.2-1

An ASBR MUST be configured with a set of (import) Route Targets (RTs) that specifies the set of MVPNs supported by the ASBR. (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-1, so no unit is bound to it.

RFC6514-9.2-3

The ASBR MUST be (auto-)configured with an import Route Target called "ASBR Import RT". (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-3, so no unit is bound to it.

RFC6514-9.2-4

The Global Administrator field of the ASBR Import RT MUST be set to the IP address carried in the Next Hop of all the Inter-AS I-PMSI A-D routes and S-PMSI A-D routes advertised by this ASBR (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-4, so no unit is bound to it.

RFC6514-9.2-5

if the ASBR uses different Next Hops, then the ASBR MUST be (auto-)configured with multiple ASBR Import RTs, one per each such Next Hop (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-5, so no unit is bound to it.

RFC6514-9.2-6

The Local Administrator field of the ASBR Import RT MUST be set to 0. (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-6, so no unit is bound to it.

RFC6514-9.2-9

The ASBR MUST be configured with the tunnel types for the intra-AS segments of the MVPNs supported by the ASBR, as well as (depending on the tunnel type) the information needed to create the PMSI attribute for these tunnel types. (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-9, so no unit is bound to it.

RFC6514-9.2-11

If the ASBR originates an Inter-AS I-PMSI A-D route for a particular MVPN present on some of the PEs within its own AS, the ASBR MUST be (auto-)configured with an RD for that MVPN. (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-11, so no unit is bound to it.

RFC6514-9.2-14

If an ASBR is configured to support a particular MVPN, the ASBR MUST participate in the intra-AS MVPN auto-discovery/binding procedures for that MVPN within the ASBR's own AS, as specified in Section 9.1. (§9.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2-14, so no unit is bound to it.

RFC6514-9.2.1-1

An implementation MUST support the default policy for aggregation of Intra-AS I-PMSI A-D routes into an Inter-AS I-PMSI A-D route. (§9.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.1-1, so no unit is bound to it.

RFC6514-9.2.1-3

Modified policy MUST include rules for constructing RTs carried by the Inter-AS I-PMSI A-D routes originated by the ASBR. (§9.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.1-3, so no unit is bound to it.

RFC6514-9.2.3.2-1

When re-advertising an Inter-AS I-PMSI A-D route, the ASBR MUST set the Next Hop field of the MP_REACH_NLRI attribute to a routable IP address of the ASBR. (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-1, so no unit is bound to it.

RFC6514-9.2.3.2-2

If the ASBR uses ingress replication for the intra-AS segment of the inter-AS tunnel, the re-advertised route MUST carry the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication, but no MPLS labels. (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-2, so no unit is bound to it.

RFC6514-9.2.3.2-3

If the ASBR uses a P-multicast tree for the intra-AS segment of the inter-AS tunnel, the PMSI Tunnel attribute MUST contain the identity of the tree (note that the ASBR could create the identity of the tree prior to the actual instantiation of the tree). (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-3, so no unit is bound to it.

RFC6514-9.2.3.2-5

An ASBR that uses a P-multicast tree as the intra-AS segment of the inter-AS tunnel MAY aggregate two or more MVPNs present on the ASBR onto the same tree. In this case, in addition to the identity of the tree, the PMSI Tunnel attribute of the Inter-AS I- PMSI A-D route MUST carry an MPLS upstream-assigned label that the PE has bound uniquely to the MVPN associated with this route (as determined by its RTs). (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-5, so no unit is bound to it.

RFC6514-9.2.3.2-6

If the ASBR has already advertised Inter-AS I-PMSI A-D routes for two or more MVPNs that it now desires to aggregate, then the ASBR MUST re-advertise those routes. (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-6, so no unit is bound to it.

RFC6514-9.2.3.2-7

The re-advertised routes MUST be the same as the original ones, except for the PMSI Tunnel attribute and the MVPN label. (§9.2.3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2-7, so no unit is bound to it.

RFC6514-9.2.3.2.1-1

In addition, the ASBR MUST send to the EBGP neighbor from whom it received the Inter-AS I-PMSI A-D route, a BGP Update message that carries a Leaf A-D route constructed as follows. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-1, so no unit is bound to it.

RFC6514-9.2.3.2.1-2

The route carries a single MCAST-VPN NLRI with the Route Key field set to the MCAST-VPN NLRI of the Inter-AS I-PMSI A-D route received from that neighbor and the Originating Router's IP address set to the IP address of the ASBR (this MUST be a routable IP address). (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-2, so no unit is bound to it.

RFC6514-9.2.3.2.1-3

The Leaf A-D route MUST include the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication and the Tunnel Identifier set to a routable address of the advertising router. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-3, so no unit is bound to it.

RFC6514-9.2.3.2.1-4

The PMSI Tunnel attribute MUST carry a downstream-assigned MPLS label that is used by the advertising router to demultiplex the MVPN traffic received over a unicast tunnel from the EBGP neighbor. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-4, so no unit is bound to it.

RFC6514-9.2.3.2.1-5

The Next Hop field of the MP_REACH_NLRI attribute of the route MUST be set to the same IP address as the one carried in the Originating Router's IP Address field of the route. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-5, so no unit is bound to it.

RFC6514-9.2.3.2.1-6

To constrain the distribution scope of this route, the route MUST carry the NO_ADVERTISE BGP Community [RFC1997]. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-6, so no unit is bound to it.

RFC6514-9.2.3.2.1-7

The ASBR MUST set up its forwarding state such that packets that arrive on the one-hop ASBR-ASBR LSP, as specified in the PMSI Tunnel attribute of the Leaf A-D route, are transmitted on the intra-AS segment, as specified in the PMSI Tunnel attribute of the Inter-AS I-PMSI A-D route that the ASBR re-advertises in its own AS. (§9.2.3.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.2.1-7, so no unit is bound to it.

RFC6514-9.2.3.3-2

For each of these intra-AS tunnels, if a non-zero MPLS label is carried in the PMSI Tunnel attribute (i.e., aggregation is used), then only packets received on the inner LSP corresponding to that label MUST be forwarded, not the packets received on the outer LSP, as the outer LSP possibly carries the traffic of other VPNs. (§9.2.3.3)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.3-2, so no unit is bound to it.

RFC6514-9.2.3.4-1

If a given Inter-AS I-PMSI A-D route is received via IBGP by a BGP route reflector, the BGP route reflector MUST NOT modify the Next Hop field of the MP_REACH_NLRI attribute when re-advertising the route into IBGP (§9.2.3.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4-1, so no unit is bound to it.

RFC6514-9.2.3.4-2

When propagating the route to the EBGP neighbors, the ASBR MUST set the Next Hop field of the MP_REACH_NLRI attribute to a routable IP address of the ASBR. (§9.2.3.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4-2, so no unit is bound to it.

RFC6514-9.2.3.4-3

If the received Inter-AS I-PMSI A-D route carries the PMSI Tunnel attribute, then the propagated route MUST carry the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication; the attribute carries no MPLS labels. (§9.2.3.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4-3, so no unit is bound to it.

RFC6514-9.2.3.4-5

If the received Inter-AS I-PMSI A-D route carries the PMSI Tunnel attribute with the Tunnel Identifier set to RSVP-TE P2MP LSP, then the ASBR that originated the route MUST establish an RSVP-TE P2MP LSP with the local PE/ASBR as a leaf. (§9.2.3.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4-5, so no unit is bound to it.

RFC6514-9.2.3.4.1-1

If the Leaf Information Required flag in the PMSI Tunnel attribute of the received Inter-AS I-PMSI A-D route is set to 1, then the PE/ASBR MUST originate a new Leaf A-D route as follows. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-1, so no unit is bound to it.

RFC6514-9.2.3.4.1-2

The route carries a single MCAST-VPN NLRI with the Route Key field set to the MCAST-VPN NLRI of the Inter-AS I-PMSI A-D route received from that neighbor and the Originating Router's IP address set to the IP address of the PE/ASBR (this MUST be a routable IP address). (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-2, so no unit is bound to it.

RFC6514-9.2.3.4.1-3

If the received Inter-AS I-PMSI A-D route carries the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication, then the Leaf A-D route MUST carry the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-3, so no unit is bound to it.

RFC6514-9.2.3.4.1-4

The Tunnel Identifier MUST carry a routable address of the PE/ASBR. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-4, so no unit is bound to it.

RFC6514-9.2.3.4.1-5

The PMSI Tunnel attribute MUST carry a downstream-assigned MPLS label that is used to demultiplex the MVPN traffic received over a unicast tunnel by the PE/ASBR. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-5, so no unit is bound to it.

RFC6514-9.2.3.4.1-6

The Next Hop field of the MP_REACH_NLRI attribute of the route MUST be set to the same IP address as the one carried in the Originating Router's IP Address field of the route. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-6, so no unit is bound to it.

RFC6514-9.2.3.4.1-7

To constrain the distribution scope of this route, the route MUST carry the NO_EXPORT Community [RFC1997]. (§9.2.3.4.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-9.2.3.4.1-7, so no unit is bound to it.

RFC6514-10-2

If there is a separate UMH VRF, it MAY have its own import and export Route Targets, different from the ones used by the unicast VRF. These Route Targets MUST be used to control distribution of auto- discovery routes. (§10)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-10-2, so no unit is bound to it.

RFC6514-10-4

If an MVPN site is multihomed to several PEs, then to support non- congruent unicast and multicast connectivity, on each of these PEs, the UMH VRF of the MVPN MUST use its own distinct RD (§10)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-10-4, so no unit is bound to it.

RFC6514-10-6

These routes MUST carry the VRF Route Import Extended Community. (§10)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-10-6, so no unit is bound to it.

RFC6514-10-7

If, for a given MVPN, BGP is used for exchanging C-multicast routes, or if segmented inter-AS tunnels are used, then these routes MUST also carry the Source AS Extended Community. (§10)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-10-7, so no unit is bound to it.

RFC6514-11.1.1.1-1

Whenever (a) a C-PIM instance on a particular PE creates a new (C-S,C-G) state, and (b) the selected upstream PE for C-S (see [MVPN]) is not the local PE, then the local PE MUST originate a C-multicast route of type Source Tree Join. (§11.1.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.1.1-1, so no unit is bound to it.

RFC6514-11.1.1.1-2

Whenever a C-PIM instance on a particular PE deletes a (C-S,C-G) state, the corresponding C-multicast route MUST be withdrawn. (§11.1.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.1.1-2, so no unit is bound to it.

RFC6514-11.1.1.2-1

Whenever (a) a C-PIM instance on a particular PE creates a new (C-*,C-G) state, and (b) the selected upstream PE for the C-RP corresponding to the C-G (see [MVPN]) is not the local PE, then the local PE MUST originate a C-multicast route of type Shared Tree Join. (§11.1.1.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.1.2-1, so no unit is bound to it.

RFC6514-11.1.1.2-2

Whenever a C-PIM instance on a particular PE deletes a (C-*,C-G) state, the corresponding C-multicast route MUST be withdrawn. (§11.1.1.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.1.2-2, so no unit is bound to it.

RFC6514-11.1.3-1

The Next Hop field of the MP_REACH_NLRI attribute MUST be set to a routable IP address of the local PE. (§11.1.3)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.3-1, so no unit is bound to it.

RFC6514-11.1.4-1

In that case, a change in the unicast routing may invalidate prior choices of the UMH route for some C-S. If this happens, the local PE MUST execute the UMH route selection procedures for C-S again. (§11.1.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.4-1, so no unit is bound to it.

RFC6514-11.1.4-2

If the result is that a different UMH route is selected, then for all C-G, any previously originated C-multicast routes for (C-S,C-G) MUST be re-originated. (§11.1.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.4-2, so no unit is bound to it.

RFC6514-11.1.4-3

Similarly, if a unicast routing change results in a change of the UMH route for a C-RP, then for all C-G such that C-RP is the RP associated with C-G, any previously originated C-multicast routes for (C-*,C-G) MUST be re-originated. (§11.1.4)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.1.4-3, so no unit is bound to it.

RFC6514-11.2-1

The ASBR first checks if it already has one or more C-multicast routes that have the same MCAST-VPN NLRI as the newly received route. If such a route(s) already exists, the ASBR keeps the newly received route, but SHALL NOT re-advertise the newly received route. (§11.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.2-1, so no unit is bound to it.

RFC6514-11.2-2

When an ASBR receives a BGP Update message that carries a withdrawal of a previously advertised C-multicast route, the ASBR first checks if it already has at least one other C-multicast route that has the same MCAST-VPN NLRI. If such a route already exists, the ASBR processes the withdrawn route, but SHALL NOT re-advertise the withdrawal. (§11.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.2-2, so no unit is bound to it.

RFC6514-11.3.1.1-1

When, for a said VRF, the last Source Tree Join C-multicast route for (C-S,C-G) is withdrawn, resulting in the situation where the VRF contains no Source Tree Join C-multicast route for (C-S,C-G), the PE MUST remove the I-PMSI/S-PMSI from the outgoing interface list of the (C-S,C-G) state. (§11.3.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.3.1.1-1, so no unit is bound to it.

RFC6514-11.3.1.1-3

If C-G is not in the SSM range for the VRF, then removing the I-PMSI/S-PMSI from the outgoing interface list of the (C-S,C-G) state SHOULD be done after a delay that is controlled by a timer. The value of the timer MUST be configurable. (§11.3.1.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.3.1.1-3, so no unit is bound to it.

RFC6514-11.3.1.2-1

When, for a said VRF, the last Shared Tree Join C-multicast route for (C-*,C-G) is withdrawn, resulting in the situation where the VRF contains no Shared Tree Join C-multicast route for (C-*,C-G), the PE MUST remove the I-PMSI/S-PMSI from the outgoing interface list of the (C-*,C-G) state. (§11.3.1.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-11.3.1.2-1, so no unit is bound to it.

RFC6514-12.1-1

The Multicast Source field MUST contain the source address associated with the C-multicast stream, and the Multicast Source Length field is set appropriately to reflect this. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-1, so no unit is bound to it.

RFC6514-12.1-2

The Multicast Group field MUST contain the group address associated with the C-multicast stream, and the Multicast Group Length field is set appropriately to reflect this. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-2, so no unit is bound to it.

RFC6514-12.1-3

The Originating Router's IP Address field MUST be set to the IP address that the (local) PE places in the Global Administrator field of the VRF Route Import Extended Community of the VPN-IP routes advertised by the PE. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-3, so no unit is bound to it.

RFC6514-12.1-4

The PMSI Tunnel attribute MUST contain the identity of the P-multicast tree (note that the PE could create the identity of the tree prior to the actual instantiation of the tree). (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-4, so no unit is bound to it.

RFC6514-12.1-5

If a PE originates S-PMSI A-D routes with the Leaf Information Required flag in the PMSI Tunnel attribute set to 1, then the PE MUST be (auto-)configured with an import Route Target, which controls acceptance of Leaf A-D routes by the PE. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-5, so no unit is bound to it.

RFC6514-12.1-6

The Global Administrator field of this Route Target MUST be set to the IP address carried in the Next Hop of all the S-PMSI A-D routes advertised by this PE (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-6, so no unit is bound to it.

RFC6514-12.1-7

if the PE uses different Next Hops, then the PE MUST be (auto-)configured with multiple import RTs, one per each such Next Hop (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-7, so no unit is bound to it.

RFC6514-12.1-8

The Local Administrator field of this Route Target MUST be set to 0. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-8, so no unit is bound to it.

RFC6514-12.1-12

If the PE already advertises S-PMSI A-D routes for these S-PMSIs, then aggregation requires the PE to re-advertise these routes. The re-advertised routes MUST be the same as the original ones, except for the PMSI Tunnel attribute. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-12, so no unit is bound to it.

RFC6514-12.1-13

The PMSI Tunnel attribute in the newly advertised/re-advertised routes MUST carry the identity of the P-multicast tree that aggregates the S-PMSIs. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-13, so no unit is bound to it.

RFC6514-12.1-14

If at least some of the S-PMSIs aggregated onto the same P-multicast tree belong to different MVPNs, then all these routes MUST carry an MPLS upstream-assigned label [RFC5331]. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-14, so no unit is bound to it.

RFC6514-12.1-16

If all these aggregated S-PMSIs belong to the same MVPN, and this MVPN uses PIM as its C-multicast routing protocol, then the corresponding S-PMSI A-D routes MAY carry an MPLS upstream-assigned label [RFC5331]. Moreover, in this case, the labels MUST be distinct on a per-MVPN basis and MAY be distinct on a per-route basis. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-16, so no unit is bound to it.

RFC6514-12.1-18

If all these aggregated S-PMSIs belong to the MVPN(s) that uses mLDP as its C-multicast routing protocol, then the corresponding S-PMSI A-D routes MUST carry an MPLS upstream-assigned label [RFC5331] (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-18, so no unit is bound to it.

RFC6514-12.1-19

If all these aggregated S-PMSIs belong to the MVPN(s) that uses mLDP as its C-multicast routing protocol, then the corresponding S-PMSI A-D routes MUST carry an MPLS upstream-assigned label [RFC5331], and these labels MUST be distinct on a per-route (per-mLDP FEC) basis, irrespective of whether the aggregated S-PMSIs belong to the same or different MVPNs. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-19, so no unit is bound to it.

RFC6514-12.1-20

The Next Hop field of the MP_REACH_NLRI attribute of the route MUST be set to the same IP address as the one carried in the Originating Router's IP Address field. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-20, so no unit is bound to it.

RFC6514-12.1-21

In each of the above cases, an implementation MUST allow the set of Route Targets carried by the route to be specified by configuration. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-21, so no unit is bound to it.

RFC6514-12.1-22

In the absence of a configured set of Route Targets, the route MUST carry the default set of Route Targets, as specified above. (§12.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.1-22, so no unit is bound to it.

RFC6514-12.2.1-3

If an ASBR merges a (C-S,C-G) S-PMSI A-D route into an Inter-AS I-PMSI A-D route, the ASBR MUST discard all (C-S,C-G) traffic it receives on the tunnel advertised in the I-PMSI A-D route. (§12.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.2.1-3, so no unit is bound to it.

RFC6514-12.2.1-4

An ASBR that merges an S-PMSI A-D route into an Inter-AS I-PMSI A-D route MUST NOT re-advertise the S-PMSI A-D route. (§12.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.2.1-4, so no unit is bound to it.

RFC6514-12.3-1

In addition to the procedures specified in Section 9.2.3.4.1, the PE MUST set up its forwarding path to receive (C-S,C-G) traffic from the tunnel advertised by the S-PMSI A-D route (the PE MUST switch to the S-PMSI). (§12.3)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-12.3-1, so no unit is bound to it.

RFC6514-13-1

The procedures defined in this section only apply when the C-multicast routing protocol is PIM [RFC4601]; moreover, they only apply for the multicast ASM mode and MUST NOT be applied to multicast group addresses belonging to the SSM range. (§13)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13-1, so no unit is bound to it.

RFC6514-13-2

The procedures also MUST NOT be applied when the C-multicast routing protocol is BIDIR-PIM [RFC5015]. (§13)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13-2, so no unit is bound to it.

RFC6514-13.1-1

When, as a result of receiving a Source Tree Join C-multicast route for (C-S,C-G) from some other PE the local PE adds either the S-PMSI or the I-PMSI to the outgoing interface list of the (C-S,C-G) state (see Section 11.3.1.1), the local PE MUST originate a Source Active A-D route if the PE has not originated such route already. (§13.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.1-1, so no unit is bound to it.

RFC6514-13.1-2

The Multicast Source field MUST be set to C-S. The Multicast Source Length field is set appropriately to reflect this. (§13.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.1-2, so no unit is bound to it.

RFC6514-13.1-3

The Multicast Group field MUST be set to C-G. The Multicast Group Length field is set appropriately to reflect this. (§13.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.1-3, so no unit is bound to it.

RFC6514-13.1-4

The Next Hop field of the MP_REACH_NLRI attribute MUST be set to the IP address that the PE places in the Global Administrator field of the VRF Route Import Extended Community of the VPN-IP routes advertised by the PE from the MVPN's VRF. (§13.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.1-4, so no unit is bound to it.

RFC6514-13.1-6

When, as a result of receiving a withdrawal of the previously advertised Source Tree Join C-multicast route for (C-S,C-G), the PE is going to remove the S-PMSI/I-PMSI from the outgoing interface list of the (C-S,C-G) state. The local PE MUST also withdraw the Source Active A-D route for (C-S,C-G), if such a route has been advertised. (§13.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.1-6, so no unit is bound to it.

RFC6514-13.2-1

When (as a result of receiving PIM messages from one of its CEs) a PE creates in one of its MVPN-TIBs a (new) (C-*,C-G) entry with a non- empty outgoing interface list that contains one or more PE-CE interfaces, the PE MUST check if it has any matching Source Active A-D routes. (§13.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2-1, so no unit is bound to it.

RFC6514-13.2-2

When, as a result of receiving a new Source Active A-D route, a PE updates its VRF with the route, the PE MUST check if the newly received route matches any (C-*,C-G) entries. (§13.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2-2, so no unit is bound to it.

RFC6514-13.2.1-1

If the outgoing interface list (oif) for the found (C-*,C-G) entry in the MVPN-TIB on the PE contains either I-PMSI or S-PMSI, and the PE does not originate the Source Tree Join C-multicast route for (C-S,C-G) (where C-S is address carried in the Multicast Source field and C-G is the address carried in the Multicast Group field of the received Source Active A-D route), then the PE MUST transition the (C-S,C-G,rpt) downstream state machine on I-PMSI/S-PMSI to the Prune state. (§13.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2.1-1, so no unit is bound to it.

RFC6514-13.2.1-3

Transitioning the state machine to the Prune state SHOULD be done after a delay that is controlled by a timer. The value of the timer MUST be configurable. (§13.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2.1-3, so no unit is bound to it.

RFC6514-13.2.1-4

The PE MUST keep the (C-S,C-G,rpt) downstream state machine on I-PMSI/S-PMSI in the Prune state for as long as (a) the outgoing interface list (oif) for the found (C-*,C-G) entry in the MVPN-TIB on the PE contains either I-PMSI or S-PMSI, (b) the PE has at least one Source Active A-D route for (C-S,C-G), and (c) the PE does not originate the Source Tree Join C-multicast route for (C-S,C-G). (§13.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2.1-4, so no unit is bound to it.

RFC6514-13.2.1-5

The PE MUST keep the (C-S,C-G,rpt) downstream state machine on I-PMSI/S-PMSI in the Prune state for as long as (a) the outgoing interface list (oif) for the found (C-*,C-G) entry in the MVPN-TIB on the PE contains either I-PMSI or S-PMSI, (b) the PE has at least one Source Active A-D route for (C-S,C-G), and (c) the PE does not originate the Source Tree Join C-multicast route for (C-S,C-G). Once any of these conditions become no longer valid, the PE MUST transition the (C-S,C-G,rpt) downstream state machine on I-PMSI/S-PMSI to the NoInfo state. (§13.2.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-13.2.1-5, so no unit is bound to it.

RFC6514-14-1

The procedures defined in this section only apply when the C-multicast routing protocol is PIM [RFC4601]; moreover, only apply for the multicast ASM mode, and MUST NOT be applied to multicast group addresses belonging to the SSM range. (§14)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14-1, so no unit is bound to it.

RFC6514-14-2

The procedures also MUST NOT be applied when the C-multicast routing protocol is BIDIR-PIM [RFC5015]. (§14)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14-2, so no unit is bound to it.

RFC6514-14.1-1

The Multicast Source field MUST be set to the source IP address of the multicast data packet carried in the PIM Register message (RP/PIM register case) or of the MSDP Source-Active message (MSDP case). (§14.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.1-1, so no unit is bound to it.

RFC6514-14.1-2

The Multicast Group field MUST be set to the group IP address of the multicast data packet carried in the PIM Register message (RP/PIM register case) or of the MSDP Source-Active message (MSDP case). (§14.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.1-2, so no unit is bound to it.

RFC6514-14.1-3

The Next Hop field of the MP_REACH_NLRI attribute MUST be set to the IP address that the PE places in the Global Administrator field of the VRF Route Import Extended Community of the VPN-IP routes advertised by the PE. (§14.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.1-3, so no unit is bound to it.

RFC6514-14.2-1

When (as a result of receiving PIM messages from one of its CEs) a PE creates, in one of its MVPN-TIBs, a (new) (C-*,C-G) entry with a non- empty outgoing interface list that contains one or more PE-CE interfaces, the PE MUST check if it has any matching Source Active A-D routes. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-1, so no unit is bound to it.

RFC6514-14.2-2

If there is one or more such matching routes, and the best path to C-S carried in the matching route(s) is reachable through some other PE, then for each such route the PE MUST originate a Source Tree Join C-multicast route. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-2, so no unit is bound to it.

RFC6514-14.2-3

If there is one or more such matching routes, and the best path to C-S carried in the matching route(s) is reachable through a CE connected to the PE, then for each such route the PE MUST originate a PIM Join (C-S,C-G) towards the CE. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-3, so no unit is bound to it.

RFC6514-14.2-4

When, as a result of receiving a new Source Active A-D route, a PE updates its VRF with the route, the PE MUST check if the newly received route matches any (C-*,C-G) entries. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-4, so no unit is bound to it.

RFC6514-14.2-5

If there is a matching entry, and the best path to C-S carried in the (A-D) route is reachable through some other PE, the PE MUST originate a Source Tree Join C-multicast route for the (C-S,C-G) carried by the route. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-5, so no unit is bound to it.

RFC6514-14.2-6

If there is a matching entry, and the best path to C-S carried in the (A-D) route is reachable through a CE connected to the PE, the PE MUST originate a PIM Join (C-S,C-G) towards the CE. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-6, so no unit is bound to it.

RFC6514-14.2-7

A PE MUST withdraw a Source Tree Join C-multicast route for (C-S,C-G) if, as a result of having received PIM messages from one of its CEs, the PE creates a Prune (C-S,C-G,rpt) upstream state in one of its MVPN-TIBs but has no (C-S,C-G) Joined state in that MVPN-TIB and had previously advertised the said route. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-7, so no unit is bound to it.

RFC6514-14.2-8

A PE MUST withdraw a Source Tree Join C-multicast route for (C-S,C-G) if the Source Active A-D route that triggered the advertisement of the C-multicast route is withdrawn. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-8, so no unit is bound to it.

RFC6514-14.2-9

When a PE deletes the (C-*,C-G) state (e.g., due to receiving PIM Prune (C-*,C-G) from its CEs), the PE MUST withdraw all the Source Tree Join C-multicast routes for C-G that have been advertised by the PE, except for the routes for which the PE still maintains the corresponding (C-S,C-G) state. (§14.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-14.2-9, so no unit is bound to it.

RFC6514-17-2

A PE router MUST NOT accept, from CEs routes, with MCAST-VPN SAFI. (§17)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-17-2, so no unit is bound to it.

RFC6514-17-3

If BGP is used as a CE-PE routing protocol, then when a PE receives a route from a CE, if this route carries the VRF Route Import Extended Community, the PE MUST remove this Community from the route before turning it into a VPN-IP route. (§17)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-17-3, so no unit is bound to it.

RFC6514-17-4

Routes that a PE advertises to a CE MUST NOT carry the VRF Route Import Extended Community. (§17)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC6514-17-4, so no unit is bound to it.

Extraction sign-off

No extraction sign-off exists for RFC 6514, so no reviewer has walked its text sentence by sentence.

Superseded

No document obsoletes RFC 6514, so its obligations are stated where they were written.