1 / 6

draft-sd-l2vpn-evpn-overlay-03.txt

draft-sd-l2vpn-evpn-overlay-03.txt. Sajassi (Cisco ) – Editor J . Drake (Juniper ) – Editor IETF 90, July 2014 Toronto. Co-authors/Contributors. Nabil Bitar (Verizon) Aldrin Isaac (Bloomberg) James Uttaro (ATT) Wim Hendrix (ALU)

dallon
Télécharger la présentation

draft-sd-l2vpn-evpn-overlay-03.txt

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-sd-l2vpn-evpn-overlay-03.txt Sajassi(Cisco)– Editor J. Drake (Juniper)– Editor IETF 90, July 2014 Toronto

  2. Co-authors/Contributors • Nabil Bitar (Verizon) • Aldrin Isaac (Bloomberg) • James Uttaro (ATT) • Wim Hendrix (ALU) • YakovRekhter, R. Shekhar, B. Schliesser (Juniper) • S. Salam, K. Patel, D. Rao, S. Thoria, D Cai, S. Sinha (Cisco) • L. Yong (Huawei)

  3. History • draft-sajassi-l2vpn-evpn-overlay-00 presented at IETF 85 • Was merged with draft-drake-nvo3-evpn-control-plane-00 • Merged draft-sd-l2vpn-evpn-overlay-01 was presented at IETF-86 • Good feedback from WG at IETF-86 and comments were incorporated into next rev • draft-sd-l2vpn-evpn-overlay-02 was presented at IETF-88 • Comments were incorporated into this rev (rev03)

  4. Industry Adoption • Several vendors have already implemented this draft: Cisco, Juniper, ALU • Several service providers support this draft

  5. Changes from Rev02 • No major changes • Added terminology section • Misc. editorial changes • Removed old section 8 • Expanded on section 5.1.2.1 (Auto Derivation of RT)

  6. Next Step • It is overdue for a WG call 

More Related