Operational Implications of IPv6 Packets with Extension Headers
draft-ietf-v6ops-ipv6-ehs-packet-drops-00

Document Type Active Internet-Draft (v6ops WG)
Last updated 2020-07-31
Replaces draft-gont-v6ops-ipv6-ehs-packet-drops
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Operations Working Group (v6ops)                            F. Gont
Internet-Draft                                              SI6 Networks
Intended status: Informational                               N. Hilliard
Expires: February 1, 2021                                           INEX
                                                              G. Doering
                                                             SpaceNet AG
                                                               W. Kumari
                                                                  Google
                                                               G. Huston
                                                                   APNIC
                                                                  W. Liu
                                                     Huawei Technologies
                                                           July 31, 2020

    Operational Implications of IPv6 Packets with Extension Headers
               draft-ietf-v6ops-ipv6-ehs-packet-drops-00

Abstract

   This document summarizes the operational implications of IPv6
   extension headers, and attempts to analyze reasons why packets with
   IPv6 extension headers may be dropped in the public Internet.

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 February 1, 2021.

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

Gont, et al.            Expires February 1, 2021                [Page 1]
Internet-Draft           IPv6 Extension Headers                July 2020

   (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.  Disclaimer  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Previous Work on IPv6 Extension Headers . . . . . . . . . . .   3
   4.  Packet Forwarding Engine Constraints  . . . . . . . . . . . .   5
   5.  Requirement to Process Layer-3/layer-4 information in
       Intermediate Systems  . . . . . . . . . . . . . . . . . . . .   6
     5.1.  ECMP and Hash-based Load-Sharing  . . . . . . . . . . . .   6
     5.2.  Enforcing infrastructure ACLs . . . . . . . . . . . . . .   7
     5.3.  DDoS Management and Customer Requests for Filtering . . .   7
   6.  Operational Implications  . . . . . . . . . . . . . . . . . .   8
     6.1.  Inability to Find Layer-4 Information . . . . . . . . . .   8
     6.2.  Route-Processor Protection  . . . . . . . . . . . . . . .   8
     6.3.  Inability to Perform Fine-grained Filtering . . . . . . .   8
     6.4.  Security Concerns Associated with IPv6 Extension Headers    8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   IPv6 Extension Headers (EHs) allow for the extension of the IPv6
   protocol, and provide support for core functionality such as IPv6
   fragmentation.  However, common implementation limitations suggest
   that EHs present a challenge for IPv6 packet routing equipment and
   middle-boxes, and evidence exists that IPv6 packets with EHs may be
   intentionally dropped in the public Internet in some network
   deployments.

   The authors of this document have been involved in numerous
   discussions about IPv6 extension headers (both within the IETF and in
   other fora), and have noticed that the security and operational
Show full document text