rfc9574v3.txt | rfc9574.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) J. Rabadan, Ed. | Internet Engineering Task Force (IETF) J. Rabadan, Ed. | |||
Request for Comments: 9574 S. Sathappan | Request for Comments: 9574 S. Sathappan | |||
Category: Standards Track Nokia | Category: Standards Track Nokia | |||
ISSN: 2070-1721 W. Lin | ISSN: 2070-1721 W. Lin | |||
Juniper Networks | Juniper Networks | |||
M. Katiyar | M. Katiyar | |||
Versa Networks | Versa Networks | |||
A. Sajassi | A. Sajassi | |||
Cisco Systems | Cisco Systems | |||
April 2024 | May 2024 | |||
Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) | |||
Abstract | Abstract | |||
Network Virtualization Overlay (NVO) networks using Ethernet VPNs | Network Virtualization Overlay (NVO) networks using Ethernet VPNs | |||
(EVPNs) as their control plane may use trees based on ingress | (EVPNs) as their control plane may use trees based on ingress | |||
replication or Protocol Independent Multicast (PIM) to convey the | replication or Protocol Independent Multicast (PIM) to convey the | |||
overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM | overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM | |||
provides an efficient solution that prevents sending multiple copies | provides an efficient solution that prevents sending multiple copies | |||
skipping to change at line 130 ¶ | skipping to change at line 130 ¶ | |||
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 G1 | | |||
| +----PE->+-----+ No State | | IIF +-----+ OIF to G | | | +----PE->+-----+ No State | | IIF +-----+ OIF to G1 | | |||
| | +---2->|Spine|------+ | | +------>Spine|------+ | | | | +---2->|Spine|------+ | | +------>Spine|------+ | | |||
| | | +-3->+-----+ | | | | +-----+ | | | | | | +-3->+-----+ | | | | +-----+ | | | |||
| | | | 2 3 | | |PIM |OIF to G | | | | | | | 2 3 | | |PIM |OIF to G1| | | |||
| | | |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 262 ¶ | skipping to change at line 262 ¶ | |||
that must follow the AR procedures. The AR-IP is also used in the | that must follow the AR procedures. The AR-IP is also used in the | |||
Tunnel Identifier and Next Hop fields of the Replicator-AR route. | Tunnel Identifier and Next Hop fields of the Replicator-AR route. | |||
AR-LEAF: Assisted Replication - LEAF. Refers to an NVE/PE that | AR-LEAF: Assisted Replication - LEAF. Refers to an NVE/PE that | |||
sends all the BM traffic to an AR-REPLICATOR that can replicate | sends all the BM traffic to an AR-REPLICATOR that can replicate | |||
the traffic further on its behalf. An AR-LEAF is typically an | the traffic further on its behalf. An AR-LEAF is typically an | |||
NVE/PE with poor replication performance capabilities. | NVE/PE with poor replication performance capabilities. | |||
AR-REPLICATOR: Assisted Replication - REPLICATOR. Refers to an NVE/ | AR-REPLICATOR: Assisted Replication - REPLICATOR. Refers to an NVE/ | |||
PE that can replicate broadcast or multicast traffic received on | PE that can replicate broadcast or multicast traffic received on | |||
overlay tunnels to other overlay tunnels and local ACs. This | overlay tunnels to other overlay tunnels and local Attachment | |||
document defines the control and data plane procedures that an AR- | Circuits (ACs). This document defines the control and data plane | |||
REPLICATOR needs to follow. | procedures that an AR-REPLICATOR needs to follow. | |||
AR-VNI: Assisted Replication - VNI. Refers to a Virtual eXtensible | AR-VNI: Assisted Replication - VNI. Refers to a Virtual eXtensible | |||
Local Area Network (VXLAN) Network Identifier (VNI) advertised by | Local Area Network (VXLAN) Network Identifier (VNI) advertised by | |||
the AR-REPLICATOR along with the Replicator-AR route. It is used | the AR-REPLICATOR along with the Replicator-AR route. It is used | |||
to identify the incoming packets that must follow the AR | to identify the incoming packets that must follow the AR | |||
procedures ONLY in the single-IP AR-REPLICATOR case (see | procedures ONLY in the single-IP AR-REPLICATOR case (see | |||
Section 8). | Section 8). | |||
Assisted Replication forwarding mode: In the case of an AR-LEAF, | Assisted Replication forwarding mode: In the case of an AR-LEAF, | |||
sending an Attachment Circuit (AC) Broadcast and Multicast (BM) | sending an AC Broadcast and Multicast (BM) packet to a single AR- | |||
packet to a single AR-REPLICATOR with a tunnel destination address | REPLICATOR with a tunnel destination address AR-IP. In the case | |||
AR-IP. In the case of an AR-REPLICATOR, this means sending a BM | of an AR-REPLICATOR, this means sending a BM packet to a selected | |||
packet to a selected number of, or all of, the overlay tunnels | number of, or all of, the overlay tunnels when the packet was | |||
when the packet was previously received from an overlay tunnel. | previously received from an overlay tunnel. | |||
BD: Broadcast Domain, as defined in [RFC7432]. | BD: Broadcast Domain, as defined in [RFC7432]. | |||
BD label: Defined as the MPLS label that identifies the BD and is | BD label: Defined as the MPLS label that identifies the BD and is | |||
advertised in Regular-IR or Replicator-AR routes, when the | advertised in Regular-IR or Replicator-AR routes, when the | |||
encapsulation is MPLS over GRE (MPLSoGRE) or MPLS over UDP | encapsulation is MPLS over GRE (MPLSoGRE) or MPLS over UDP | |||
(MPLSoUDP). | (MPLSoUDP). | |||
BM traffic: Refers to broadcast and multicast frames (excluding | BM traffic: Refers to broadcast and multicast frames (excluding | |||
unknown unicast frames). | unknown unicast frames). | |||
skipping to change at line 1483 ¶ | skipping to change at line 1483 ¶ | |||
[RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R., | [RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R., | |||
Uttaro, J., and W. Henderickx, "A Network Virtualization | Uttaro, J., and W. Henderickx, "A Network Virtualization | |||
Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365, | Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365, | |||
DOI 10.17487/RFC8365, March 2018, | DOI 10.17487/RFC8365, March 2018, | |||
<https://www.rfc-editor.org/info/rfc8365>. | <https://www.rfc-editor.org/info/rfc8365>. | |||
[RFC9572] Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A. | [RFC9572] Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A. | |||
Sajassi, "Updates to EVPN Broadcast, Unknown Unicast, or | Sajassi, "Updates to EVPN Broadcast, Unknown Unicast, or | |||
Multicast (BUM) Procedures", RFC 9572, | Multicast (BUM) Procedures", RFC 9572, | |||
DOI 10.17487/RFC9572, April 2024, | DOI 10.17487/RFC9572, May 2024, | |||
<https://www.rfc-editor.org/info/rfc9572>. | <https://www.rfc-editor.org/info/rfc9572>. | |||
12.2. Informative References | 12.2. Informative References | |||
[RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed., | [RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed., | |||
"Encapsulating MPLS in IP or Generic Routing Encapsulation | "Encapsulating MPLS in IP or Generic Routing Encapsulation | |||
(GRE)", RFC 4023, DOI 10.17487/RFC4023, March 2005, | (GRE)", RFC 4023, DOI 10.17487/RFC4023, March 2005, | |||
<https://www.rfc-editor.org/info/rfc4023>. | <https://www.rfc-editor.org/info/rfc4023>. | |||
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, | [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, | |||
End of changes. 6 change blocks. | ||||
13 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |