<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.generic-v6ops-tunmtu" target="https://datatracker.ietf.org/doc/html/draft-generic-v6ops-tunmtu-11">
   <front>
      <title>Operational Issues with Tunnel Maximum Transmission Unit (MTU)</title>
      <author initials="F." surname="Templin" fullname="Fred Templin">
         </author>
      <date month="October" day="18" year="2012" />
      <abstract>
	 <t>   The Maximum Transmission Unit (MTU) for popular IP-within-IP tunnels
   is currently recommended to be set to 1500 (or less) minus the length
   of the encapsulation headers when static MTU determination is used.
   This requires the tunnel ingress to either fragment any IP packet
   larger than the MTU or drop the packet and return an ICMP Packet Too
   Big (PTB) message.  Concerns for operational issues with Path MTU
   Discovery (PMTUD) point to the possibility of MTU-related black holes
   when a packet is dropped due to an MTU restriction.  The current
   &quot;Internet cell size&quot; is effectively 1500 bytes (i.e., the minimum MTU
   configured by the vast majority of links in the Internet) and should
   therefore also be the minimum MTU assigned to tunnels, but this has
   proven to be problematic in common operational practice.  This
   document therefore discusses operational issues for IP-within-IP
   tunnel MTUs.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-generic-v6ops-tunmtu-11" />
   
</reference>
