1 / 6

Network Overlay Dataplane Requirements

This draft outlines dataplane requirements for Data Center Network Virtualization over L3 tunnels, covering VAP Identification, VN context identification, QoS marking, NVE tunnelling functions, LAG support, ECMP handling, BUM processing, and more. It includes details on VNI Types, L2 VNI, and L3 VNI, with changes and next steps outlined for further development.

tallis
Télécharger la présentation

Network Overlay Dataplane Requirements

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. Network Overlay Dataplane Requirements Draft-nb-nvo3-dataplane-requirements-01

  2. Authors Nabil Bitar Marc Lasserre Florin Balus Thomas Morin

  3. Purpose of the draft • Dataplane requirements for Data Center Network Virtualization over L3 tunnels: • VAP Identification • L2 & L3 VNI types • NVO3 header and tunnel processing • VN context identification • Explicit unique id (e.g. VNID) or locally significant identifier • Optional QoS/Cos marking • NVE tunnelling functions • IP encaps (MUST) & MPLS encaps (MAY) • LAG & ECMP support • DiffServ & ECN marking • BUM handling • External connectivity via GW • Path optimality • Path MTU handling

  4. VNI Types • L2 VNI • Emulated Ethernet multipoint service • MAC address learning via • Dataplane learning • Control/Management plane MAC address population • L3 VNI • Virtualized IP routing & forwarding

  5. Changes in -01 • Addressed comments made on the list and privately • Updated VN context identification (VNID or local reference ID) • Optional multicast support • Optional integrated bridging & routing support • Clarification of DP learning applicability vs CP/Management based provisioning

  6. Next Steps • Make entropy requirement more generic • E.g. “the encapsulation MUST result in sufficient entropy to exercise all paths through several LAG/ECMP hops”

More Related