rfc9574v2.txt   rfc9574.txt 
skipping to change at line 123 skipping to change at line 123
side of the diagram, NVE1 uses ingress replication to send a BUM side of the diagram, NVE1 uses ingress replication to send a BUM
frame (originated from Tenant System TS1) to the remote nodes frame (originated from Tenant System TS1) to the remote nodes
attached to the BD, i.e., NVE2, NVE3, and PE1. On the right-hand attached to the BD, i.e., NVE2, NVE3, and PE1. On the right-hand
side, the same example is depicted but using a PIM-based tree, i.e., side, the same example is depicted but using a PIM-based tree, i.e.,
(S1,G1), instead of ingress replication. While a single copy of the (S1,G1), instead of ingress replication. While a single copy of the
tunneled BUM frame is generated in the latter approach, all the tunneled BUM frame is generated in the latter approach, all the
routers in the fabric need to keep multicast state, e.g., the spine routers in the fabric need to keep multicast state, e.g., the spine
keeps a PIM routing entry for (S1,G1) with an Incoming Interface keeps a PIM routing entry for (S1,G1) with an Incoming Interface
(IIF) and three Outgoing Interfaces (OIFs). (IIF) and three Outgoing Interfaces (OIFs).
To-WAN To-WAN To WAN To WAN
^ ^ ^ ^
| | | |
+-----+ +-----+ +-----+ +-----+
+----------| PE1 |-----------+ +----------| PE1 |-----------+ +----------| PE1 |-----------+ +----------| PE1 |-----------+
| +--^--+ | | +--^--+ | | +--^--+ | | +--^--+ |
| | IP Fabric | | | IP Fabric | | | IP Fabric | | | IP Fabric |
| PE | | (S1,G1) |OIF to-G | | PE | | (S1,G1) |OIF to G |
| +----PE->+-----+ No State | | IIF +-----+ OIF to-G | | +----PE->+-----+ No State | | IIF +-----+ OIF to G |
| | +---2->|Spine|------+ | | +------>Spine|------+ | | | +---2->|Spine|------+ | | +------>Spine|------+ |
| | | +-3->+-----+ | | | | +-----+ | | | | | +-3->+-----+ | | | | +-----+ | |
| | | | 2 3 | | |PIM |OIF to-G | | | | | | 2 3 | | |PIM |OIF to G | |
| | | |IR | | | | |tree | | | | | | |IR | | | | |tree | | |
|+-----+ +--v--+ +--v--+ | |+-----+ +--v--+ +--v--+ | |+-----+ +--v--+ +--v--+ | |+-----+ +--v--+ +--v--+ |
+| NVE1|---| NVE2|---| NVE3|-+ +| NVE1|---| NVE2|---| NVE3|-+ +| NVE1|---| NVE2|---| NVE3|-+ +| NVE1|---| NVE2|---| NVE3|-+
+--^--+ +-----+ +-----+ +--^--+ +-----+ +-----+ +--^--+ +-----+ +-----+ +--^--+ +-----+ +-----+
| | | | | | | | | | | |
| v v | v v | v v | v v
TS1 TS2 TS3 TS1 TS2 TS3 TS1 TS2 TS3 TS1 TS2 TS3
Figure 1: Ingress Replication vs. PIM-Based Trees in NVO Networks Figure 1: Ingress Replication vs. PIM-Based Trees in NVO Networks
skipping to change at line 515 skipping to change at line 515
the IP address setting in the Next Hop field to create IP the IP address setting in the Next Hop field to create IP
tunnels to the AR-REPLICATOR. tunnels to the AR-REPLICATOR.
- The Next Hop address is referred to as the AR-IP and MUST be - The Next Hop address is referred to as the AR-IP and MUST be
different from the IR-IP for a given PE/NVE, unless the different from the IR-IP for a given PE/NVE, unless the
procedures provided in Section 8 are followed. procedures provided in Section 8 are followed.
* Tunnel Type MUST be set to Assisted Replication Tunnel. * Tunnel Type MUST be set to Assisted Replication Tunnel.
Section 11 provides the allocated type value. Section 11 provides the allocated type value.
* T (AR role type) MUST be set to 01 (AR-REPLICATOR). * T (Assisted Replication type) MUST be set to 01 (AR-
REPLICATOR).
* L (Leaf Information Required) MUST be set to 0 for non- * L (Leaf Information Required) MUST be set to 0 for non-
selective AR and MUST be set to 1 for selective AR. selective AR and MUST be set to 1 for selective AR.
An NVE/PE configured as an AR-REPLICATOR for a BD MUST advertise a An NVE/PE configured as an AR-REPLICATOR for a BD MUST advertise a
Replicator-AR route for the BD and MAY advertise a Regular-IR route. Replicator-AR route for the BD and MAY advertise a Regular-IR route.
The advertisement of the Replicator-AR route will indicate to the AR- The advertisement of the Replicator-AR route will indicate to the AR-
LEAFs which outer IP DA, i.e., which AR-IP, they need to use for IP- LEAFs which outer IP DA, i.e., which AR-IP, they need to use for IP-
encapsulated BM frames that use Assisted Replication forwarding mode. encapsulated BM frames that use Assisted Replication forwarding mode.
The AR-REPLICATOR will forward an IP-encapsulated BM frame in The AR-REPLICATOR will forward an IP-encapsulated BM frame in
skipping to change at line 559 skipping to change at line 560
Next Hop field of the received Replicator-AR route in the Global Next Hop field of the received Replicator-AR route in the Global
Administrator field of the extended community, with the Local Administrator field of the extended community, with the Local
Administrator field of this extended community set to 0, and Administrator field of this extended community set to 0, and
setting the Extended Communities attribute of the Leaf A-D route setting the Extended Communities attribute of the Leaf A-D route
to that extended community. The same IP-address-specific import to that extended community. The same IP-address-specific import
Route Target is auto-configured by the AR-REPLICATOR that sent the Route Target is auto-configured by the AR-REPLICATOR that sent the
Replicator-AR route, in order to control the acceptance of the Replicator-AR route, in order to control the acceptance of the
Leaf A-D routes. Leaf A-D routes.
* The Leaf A-D route MUST include the PMSI Tunnel Attribute with * The Leaf A-D route MUST include the PMSI Tunnel Attribute with
Tunnel Type set to Assisted Replication Tunnel (Section 11), T (AR Tunnel Type set to Assisted Replication Tunnel (Section 11), T
role type) set to AR-LEAF, and Tunnel Identifier set to the IP (Assisted Replication type) set to AR-LEAF, and Tunnel Identifier
address of the advertising AR-LEAF. The PMSI Tunnel Attribute set to the IP address of the advertising AR-LEAF. The PMSI Tunnel
MUST carry a downstream-assigned MPLS label or VNI that is used by Attribute MUST carry a downstream-assigned MPLS label or VNI that
the AR-REPLICATOR to send traffic to the AR-LEAF. is used by the AR-REPLICATOR to send traffic to the AR-LEAF.
Each AR-enabled node understands and processes the T (Assisted Each AR-enabled node understands and processes the T (Assisted
Replication type) field in the PMSI Tunnel Attribute (Flags field) of Replication type) field in the PMSI Tunnel Attribute (Flags field) of
the routes and MUST signal the corresponding type (AR-REPLICATOR or the routes and MUST signal the corresponding type (AR-REPLICATOR or
AR-LEAF type) according to its administrative choice. An NVE/PE AR-LEAF type) according to its administrative choice. An NVE/PE
following this specification is not expected to set the Assisted following this specification is not expected to set the Assisted
Replication Type field to decimal 3 (which is a RESERVED value). If Replication Type field to decimal 3 (which is a RESERVED value). If
a route with the Assisted Replication Type field set to decimal 3 is a route with the Assisted Replication Type field set to decimal 3 is
received by an AR-REPLICATOR or AR-LEAF, the router will process the received by an AR-REPLICATOR or AR-LEAF, the router will process the
route as a Regular-IR route advertised by an RNVE. route as a Regular-IR route advertised by an RNVE.
skipping to change at line 916 skipping to change at line 917
the BM traffic to the RNVEs (if there are any). The same AR roles as the BM traffic to the RNVEs (if there are any). The same AR roles as
those defined in Sections 4 and 5 are used here; however, the those defined in Sections 4 and 5 are used here; however, the
procedures are different. procedures are different.
The selective AR procedures create multiple AR-LEAF-sets in the EVPN The selective AR procedures create multiple AR-LEAF-sets in the EVPN
BD and build single-hop trees among AR-LEAFs of the same set (AR- BD and build single-hop trees among AR-LEAFs of the same set (AR-
LEAF->AR-REPLICATOR->AR-LEAF) and two-hop trees among AR-LEAFs of LEAF->AR-REPLICATOR->AR-LEAF) and two-hop trees among AR-LEAFs of
different sets (AR-LEAF->AR-REPLICATOR->AR-REPLICATOR->AR-LEAF). different sets (AR-LEAF->AR-REPLICATOR->AR-REPLICATOR->AR-LEAF).
Compared to the selective solution, the non-selective AR method Compared to the selective solution, the non-selective AR method
assumes that all the AR-LEAFs of the BD are in the same set and assumes that all the AR-LEAFs of the BD are in the same set and
always creates two-hop trees among AR-LEAFs. While the selective always creates single-hop trees among AR-LEAFs. While the selective
solution is more efficient than the non-selective solution in multi- solution is more efficient than the non-selective solution in multi-
stage IP fabrics, the trade-off is additional signaling and an stage IP fabrics, the trade-off is additional signaling and an
additional outer source IP address lookup. additional outer source IP address lookup.
The following subsections describe the differences in the procedures The following subsections describe the differences in the procedures
for AR-REPLICATORs/LEAFs compared to the non-selective AR solution. for AR-REPLICATORs/LEAFs compared to the non-selective AR solution.
There are no changes applicable to RNVEs. There are no changes applicable to RNVEs.
6.1. Selective AR-REPLICATOR Procedures 6.1. Selective AR-REPLICATOR Procedures
 End of changes. 6 change blocks. 
11 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.48.