IPv6 Packet Truncation
draft-leddy-6man-truncate-04

Document Type Active Internet-Draft (individual)
Last updated 2018-06-29
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)
6man                                                            J. Leddy
Internet-Draft                                                   Comcast
Intended status: Standards Track                               R. Bonica
Expires: December 31, 2018                              Juniper Networks
                                                           June 29, 2018

                         IPv6 Packet Truncation
                      draft-leddy-6man-truncate-04

Abstract

   This document defines IPv6 packet truncation procedures.  When an
   IPv6 source node originates a packet, it can mark the packet as being
   eligible for truncation and forward it towards its destination.  If
   an intermediate node cannot forward the packet because of an MTU
   issue, it truncates the packet, marks it as being truncated, and,
   again, forwards it towards its destination.  When the destination
   node receives the packet, it detects that it has been truncated and
   sends an ICMP message to the source node.  The ICMP message contains
   MTU information that the source node uses to update its Path MTU
   estimate.

   The above-mentioned procedures enhance Path MTU Discovery (PMTUD) by
   eliminating its reliance on the network's ability to deliver ICMP
   messages from an intermediate node to the source node.  However, the
   above-mentioned procedures require the network to deliver ICMP
   messages from the destination node to the source node.

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 https://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 December 31, 2018.

Leddy & Bonica          Expires December 31, 2018               [Page 1]
Internet-Draft           IPv6 Packet Truncation                June 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   5
   4.  Reference Topology  . . . . . . . . . . . . . . . . . . . . .   5
   5.  New IPv6 Destination Options  . . . . . . . . . . . . . . . .   6
     5.1.  The IPv6 Truncation Eligible Option . . . . . . . . . . .   6
     5.2.  The IPv6 Truncated Packet Option  . . . . . . . . . . . .   7
   6.  PMTU Signaling Procedures . . . . . . . . . . . . . . . . . .   8
   7.  Truncation Considerations . . . . . . . . . . . . . . . . . .   9
   8.  Destination Node Considerations . . . . . . . . . . . . . . .  10
   9.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .  10
   10. Optimizations . . . . . . . . . . . . . . . . . . . . . . . .  11
   11. Upper-Layer Considerations  . . . . . . . . . . . . . . . . .  11
   12. Encapsulating Security Payload Considerations . . . . . . . .  11
   13. Extension Header Considerations . . . . . . . . . . . . . . .  12
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   16. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   17. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     17.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     17.2.  Informative References . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   An Internet path connects a source node to a destination node.  A
   path can contain links and intermediate nodes (e.g., routers).

   Each link is constrained by the number of bytes that it can convey in
   a single IP packet.  This constraint is called the link Maximum
   Transmission Unit (MTU).  IPv6 [RFC8200] requires every link to have
Show full document text