MTU propagation over EVPN Overlays
draft-nvo3-mtu-propagation-over-evpn-overlays-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Saumya Dikshit , Vinayak Joshi , A Sujeet Nayak | ||
Last updated | 2021-08-03 | ||
Replaces | draft-saum-nvo3-pmtud-over-vxlan | ||
Replaced by | draft-saum-nvo3-mtu-propagation-over-evpn-overlays | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-saum-nvo3-mtu-propagation-over-evpn-overlays | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Path MTU Discovery between end-host-devices/Virtual-Machines/servers/ workloads connected over an EVPN-Overlay Network in an Datacenter/Campus/enterprise deployment, is a problem, yet to be resolved in the standards forums. It needs a converged solution to ensure optimal usage of network and computational resources of the underlay routers/switches forming the basis of the overlay network. This documents takes leads from the guidelines presented in [RFC4459]. The overlay connectivity can pan across various sites (geographically seperated or collocated) for realizing a Datacenter Interconnect or intersite VPNs between campus sites (buildings, branch offices etc). This literature intends to solve problem of icmp error propagation from an underlay routing/switching device to an end-host (hooked to EVPN overlay), thus facilitating "accurate MTU" learnings. This document also leverages the icmp multipart message extension, mentioned in [RFC4884] to carry the original packet in the icmp PDU.
Authors
Saumya Dikshit
Vinayak Joshi
A Sujeet Nayak
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)