ICMPv6 errors for discarding packets due to processing limits
draft-ietf-6man-icmp-limits-08

Document Type Active Internet-Draft (6man WG)
Last updated 2020-04-27 (latest revision 2020-03-18)
Replaces draft-herbert-6man-icmp-limits
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Bob Hinden
Shepherd write-up Show (last changed 2019-09-30)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to Bob Hinden <bob.hinden@gmail.com>, Erik Kline <ek.ietf@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                         T. Herbert
Internet-Draft                                                     Intel
Intended status: Standards Track                          March 18, 2020
Expires: September 19, 2020

     ICMPv6 errors for discarding packets due to processing limits
                     draft-ietf-6man-icmp-limits-08

Abstract

   Network nodes may discard packets if they are unable to process
   protocol headers of packets due to processing constraints or limits.
   When such packets are dropped, the sender receives no indication so
   it cannot take action to address the cause of discarded packets.
   This specification defines several new ICMPv6 errors that can be sent
   by a node that discards packets because it is unable to process the
   protocol headers.  A node that receives such an ICMPv6 error may use
   the information to diagnose packet loss and may modify what it sends
   in future packets to avoid subsequent packet discards.

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 September 19, 2020.

Copyright Notice

   Copyright (c) 2020 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

Herbert                Expires September 19, 2020               [Page 1]
Internet-Draft                ICMPv6 limits                   March 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Extension header limits . . . . . . . . . . . . . . . . .   3
     1.2.  Aggregate header limits . . . . . . . . . . . . . . . . .   4
     1.3.  Nonconformant packet discard  . . . . . . . . . . . . . .   4
     1.4.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  ICMPv6 errors for extension header limits . . . . . . . . . .   5
     2.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Unrecognized Next Header type encountered by intermediate
           node (code TBA1)  . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Extension header too big (code TBA2)  . . . . . . . . . .   6
     2.4.  Extension header chain too long (code TBA3) . . . . . . .   6
     2.5.  Too many extension headers (code TBA4)  . . . . . . . . .   6
     2.6.  Too many options in extension header (code TBA5)  . . . .   7
     2.7.  Option too big (code TBA6)  . . . . . . . . . . . . . . .   7
   3.  ICMPv6 error for aggregate header limits  . . . . . . . . . .   7
     3.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Priority of reporting . . . . . . . . . . . . . . . . . .  10
     4.2.  Host response . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Applicability and use cases . . . . . . . . . . . . . . . . .  11
     5.1.  Reliability of ICMP . . . . . . . . . . . . . . . . . . .  12
     5.2.  Processing limits . . . . . . . . . . . . . . . . . . . .  12
       5.2.1.  Long headers and header chains  . . . . . . . . . . .  12
       5.2.2.  At end hosts  . . . . . . . . . . . . . . . . . . . .  12
       5.2.3.  At intermediate nodes . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Parameter Problem codes . . . . . . . . . . . . . . . . .  13
     7.2.  Destination Unreachable codes . . . . . . . . . . . . . .  14
     7.3.  ICMP Extension Object Classes and Class Sub-types . . . .  14
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
Show full document text