1 / 5

draft-nr-bess-evpn-mh-split-horizon-00

draft-nr-bess-evpn-mh-split-horizon-00. EVPN Multi-Homing Extensions for Split Horizon Filtering. Jorge Rabadan (Nokia) Kiran Nagaraj (Nokia) Wen Lin (Juniper) Ali Sajassi (Cisco) IETF104, Mar 2019 Prague. In current specifications. EVPN Multi-Homing Split-Horizon mechanisms. EVPN

chadw
Download Presentation

draft-nr-bess-evpn-mh-split-horizon-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-nr-bess-evpn-mh-split-horizon-00 EVPN Multi-HomingExtensionsfor Split HorizonFiltering Jorge Rabadan (Nokia) Kiran Nagaraj(Nokia) WenLin(Juniper) Ali Sajassi (Cisco) IETF104, Mar 2019 Prague

  2. In current specifications EVPN Multi-Homing Split-Horizon mechanisms EVPN NVO ESI Label SHT All-Active and Single-Active Works Inter-AS/domain PE1 PE2 Transp L2 EVI Lx IP1IP2 EVPN MPLS BD1 BD1 ESI L1 NVO Local Bias SHT All-Active only No Inter-AS/domain BUT: less resources, no extra labels, ingress NVE always forward locally PE1 PE2 BUM BUM DESIGNATED FORWARDER (ES-1 AND ES-2) BD1 BD1 BUM DESIGNATED FORWARDER (ES-1 AND ES-2) All-Active ES-2 All-Active ES-1 BUM BUM CE1 CE2 All-Active ES-2 All-Active ES-1 BUM CE1 CE2 RFC8365 Local Bias SH Filtering RFC7432 ESI Label based SH Filtering

  3. For network encapsulations that support both SHTs BGP EVPN extensions Signaling of the Split Horizon Type (SHT) Allows NVE/PEs attached to the same ES to agree on the SHT to be used in the ES. SHT is different than 00 only for tunnels that can support both SHTs Backwards compatibility with RFC8365: inconsistency in the ES reverts to the default SHT ESI Label extended community Advertised with A-D per ES route (type 1) 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=0x06 | Sub-Type=0x01 |Flags (1 octet)| Reserved=0 | +---------------+---------------+-------------------------------+ | Reserved=0 | ESI Label | +---------------------------------------------------------------+ Flags Octet Bits: 0  Single-Active bit 7-6  SHT (Split Horizon Type) SHT bit 7 6 ----------- 0 0  Default SHT. Backwards compatible with [RFC8365] 0 1  Local Bias 1 0  ESI Label based filtering 1 1  reserved for future use NVEs supporting multiple encapsulations A-D per ES routes advertise multiple encapsulations and SHT=00 if at least one of the encaps support only one SHT • A-D per ES routes advertise multiple encapsulations and SHT≠00 if all encaps support both SHTs Different SHT may be signaled for the same ES in different A-D per ES routes for different groups of EVIs

  4. Next steps The Authors would like to request Feedback

  5. Thank you

More Related