Transmission of IPv6 Extension Headers
draft-carpenter-6man-ext-transmit-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-08-13
Replaced by draft-ietf-6man-ext-transmit, rfc7045
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6man                                                        B. Carpenter
Internet-Draft                                         Univ. of Auckland
Updates: 2460, 2780 (if approved)                               S. Jiang
Intended status: Standards Track            Huawei Technologies Co., Ltd
Expires: February 15, 2013                               August 14, 2012

                 Transmission of IPv6 Extension Headers
                  draft-carpenter-6man-ext-transmit-00

Abstract

   Various IPv6 extension headers have been defined since the IPv6
   standard was first published.  This document updates RFC 2460 to
   describe how intermediate nodes should deal with such extension
   headers and with any that are defined in future.  It also specifies
   how extension headers should be registered by IANA, with a
   corresponding minor update to RFC 2780.

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 February 15, 2013.

Copyright Notice

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

Carpenter & Jiang       Expires February 15, 2013               [Page 1]
Internet-Draft     IPv6 Extension Header Transmission        August 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirement to Transmit Extension Headers . . . . . . . . . . . 4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Change log [RFC Editor: Please remove]  . . . . . . . . . . . . 6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7

Carpenter & Jiang       Expires February 15, 2013               [Page 2]
Internet-Draft     IPv6 Extension Header Transmission        August 2012

1.  Introduction

   An initial set of IPv6 extension headers was defined by [RFC2460],
   which also described how they should be handled by intermediate
   nodes, with the exception of the hop-by-hop options header:

   "...extension headers are not examined or processed
   by any node along a packet's delivery path, until the packet reaches
   the node (or each of the set of nodes, in the case of multicast)
   identified in the Destination Address field of the IPv6 header."

   This provision allowed for the addition of new extension headers,
   since it means that forwarding nodes should be completely transparent
   to them.  Thus, new extension headers could be introduced
   progressively, used only by hosts that have been updated to create
   and interpret them.  Several such extension headers have been defined
   since RFC 2460.

   Unfortunately, experience has showed that the network is not
   transparent to these headers.  The main reason for this is that some
   firewalls attempt to inspect the transport payload.  This means that
   they traverse the chain of extension headers, if present, until they
   find the payload.  If they encounter an unknown extension header
   type, some of these firewalls treat the packet as suspect and drop
   it.  It is an established fact that several widely used firewalls do
   not recognise some or all of the extension headers defined since RFC
Show full document text