PMTUD Over Vxlan
draft-saum-nvo3-pmtud-over-vxlan-04

Document Type Active Internet-Draft (individual)
Last updated 2016-12-12
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NVO3                                                          S. Dikshit
Internet-Draft                                           A. Sujeet Nayak
Intended status: Standards Track                           Cisco Systems
Expires: June 15, 2017                                 December 12, 2016

                            PMTUD Over Vxlan
                  draft-saum-nvo3-pmtud-over-vxlan-04

Abstract

   Path MTU Discovery between hosts/VM/servers/end-points connected over
   a Data-Center/Service-Provider Overlay Network, is still an
   unattended problem.  It needs a converged solution to ensure optimal
   usage of network and computational resources for all hooked end-point
   devices.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 15, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dikshit & Sujeet Nayak    Expires June 15, 2017                 [Page 1]
Internet-Draft              PMTUD Over Vxlan               December 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Solution Requirements . . . . . . . . . . . . . . . . . .   3
   3.  Problem Description . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  IPv6 PMTUD Issues . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Inaccurate MTU relayed to end hosts . . . . . . . . .   5
       3.1.2.  Packet_Too_Big not-relayed to host  . . . . . . . . .   6
   4.  Solution(s) . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Discovery of end-to-end Path MTU  . . . . . . . . . . . .   6
       4.1.1.  ICMP extensions, PMTUD on Vxlan . . . . . . . . . . .   7
       4.1.2.  Packet Path Processing  . . . . . . . . . . . . . . .   7
       4.1.3.  ICMP(v6) Error Translation  . . . . . . . . . . . . .  15
   5.  Multicast and Anycast       Considerations  . . . . . . . . .  25
   6.  Ecmp Considerations . . . . . . . . . . . . . . . . . . . . .  25
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  25
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  25
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  26
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  26
     10.2.  Informative References . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  27

1.  Introduction

   There is an operational disconnect between underlay network
   provisioned as the core network, and the overlay network which
   intends to connect islands of customer deployments.  The deployments
   can range from cloud based services to storage applications or
   web(over the top) servers hosted over virtual machines or any other
   end devices like blade servers.  Overlay network are provisioned as
   tunnels leveraging Vxlan (and associated ones like gpe, geneve, gue),
   NVGRE, MPLS and other overlay encapsulations.

   The end hosts in a typical datacenter deployment are connected to
   devices termed as ToR (top of rack devices).  These are the
   networking devices which encapsulate the packet in an Overlay
   construct and relays it over Data center core network.  Although a
   ToR device MAY NOT always be a gateway for an overlay.

   IPv6/IPv4 enabled hosts/end-points, triggering PMTUD, may not get the
Show full document text