<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.saum-nvo3-mtu-propagation-over-evpn-overlays" target="https://datatracker.ietf.org/doc/html/draft-saum-nvo3-mtu-propagation-over-evpn-overlays-09">
   <front>
      <title>MTU propagation over EVPN Overlays</title>
      <author initials="D." surname="Dikshit" fullname="Saumya Dikshit">
         <organization>Aruba Networks, HPE</organization>
      </author>
      <author initials="V." surname="Joshi" fullname="Vinayak Joshi">
         <organization>Oracle India Pvt Ltd</organization>
      </author>
      <author initials="A. S." surname="Nayak" fullname="A Sujeet Nayak">
         <organization>Cisco</organization>
      </author>
      <date month="January" day="27" year="2026" />
      <abstract>
	 <t>   Path MTU Discovery between end-host-devices/Virtual-Machines/servers/
   workloads connected over an EVPN-Overlay Network in
   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
   networking elements, including underlay routers/switches,
   constituting 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 &quot;accurate MTU&quot; learnings.

   This document also leverages the icmp multipart message extension,
   mentioned in [RFC4884] to carry the original packet in the icmp PDU.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-saum-nvo3-mtu-propagation-over-evpn-overlays-09" />
   
</reference>
