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

Document Type Active Internet-Draft (6man WG)
Last updated 2019-09-30
Replaces draft-herbert-6man-icmp-limits
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Bob Hinden
Shepherd write-up Show (last changed 2019-09-30)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to Bob Hinden <bob.hinden@gmail.com>
INTERNET-DRAFT                                                T. Herbert
Intended Status: Standard                                          Intel
Expires: April 2020                                                     
                                                                        
                                                      September 30, 2019

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

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 be
   able to modify what it sends in future packets to avoid subsequent
   packet discards.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
 

T. Herbert               Expires April 2, 2020                  [Page 1]
INTERNET DRAFT       draft-ietf-6man-icmp-limits-07   September 30, 2019

   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.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1 Extension header limits  . . . . . . . . . . . . . . . . . .  4
     1.2 Aggregate header limits  . . . . . . . . . . . . . . . . . .  5
     1.3 Requirements Language  . . . . . . . . . . . . . . . . . . .  5
   2  ICMPv6 errors for extension header limits . . . . . . . . . . .  6
     2.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     2.2 Unrecognized Next Header type encountered (code 1) . . . . .  7
     2.3 Extension header too big (code TBA)  . . . . . . . . . . . .  7
     2.4 Extension header chain too long (code TBA) . . . . . . . . .  7
     2.5 Too many options in extension header (code TBA)  . . . . . .  7
     2.6 Option too big (code TBA)  . . . . . . . . . . . . . . . . .  8
   3  ICMPv6 error for aggregate header limits  . . . . . . . . . . .  8
     3.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.2 Usage  . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   4  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1 Priority of reporting  . . . . . . . . . . . . . . . . . . . 11
     4.2 Host response  . . . . . . . . . . . . . . . . . . . . . . . 12
   5  Applicability and use cases . . . . . . . . . . . . . . . . . . 12
     5.1 Nonconformant packet discard . . . . . . . . . . . . . . . . 12
     5.2 Reliability of ICMP  . . . . . . . . . . . . . . . . . . . . 13
     5.3 Processing limits  . . . . . . . . . . . . . . . . . . . . . 13
       5.3.1 Long headers and header chains . . . . . . . . . . . . . 13
       5.3.2 At end hosts . . . . . . . . . . . . . . . . . . . . . . 14
       5.3.3 At intermediate nodes  . . . . . . . . . . . . . . . . . 14
   6  Security Considerations . . . . . . . . . . . . . . . . . . . . 14
   7  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
     7.1 Parameter Problem codes  . . . . . . . . . . . . . . . . . . 14
     7.2 Destination Unreachable codes  . . . . . . . . . . . . . . . 15
     7.3 ICMP Extension Object Classes and Class Sub-types  . . . . . 15
Show full document text