Enhancement of IPv6 Extension Header
draft-li-6man-enhanced-extension-header-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                              Z. Li
Internet-Draft                                                   S. Peng
Intended status: Standards Track                     Huawei Technologies
Expires: January 9, 2020                                    July 8, 2019

                  Enhancement of IPv6 Extension Header
               draft-li-6man-enhanced-extension-header-00

Abstract

   As SRv6 and the new services such as SFC and IOAM are progressing,
   more and more new requirements are imposed upon the IPv6 extension
   headers, i.e.. Hop-by-hop Options Header, Destination Options Header
   and Routing Header.

   This document defines new IPv6 extension headers and corresponding
   processing procedures considering the interactions among the existing
   IPv6 extension headers, SRH and the newly introduced IPv6 extension
   headers.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 January 9, 2020.

Li & Peng                Expires January 9, 2020                [Page 1]
Internet-Draft      IPv6 Extension Header Enhancement          July 2019

Copyright Notice

   Copyright (c) 2019 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.  New Extension Headers . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Enhanced Hop-by-Hop Options Header  . . . . . . . . . . .   3
     2.2.  IPv6 Metadata Header  . . . . . . . . . . . . . . . . . .   4
   3.  Processing Procedures for Handling IPv6 Metadata Header . . .   6
     3.1.  Processing of IPv6 Metadata Header  . . . . . . . . . . .   6
     3.2.  Interactions between IPv6 Metadata Header and Existing
           IPv6 Extension Headers  . . . . . . . . . . . . . . . . .   7
       3.2.1.  Interactions between IPv6 Metadata Header and
               Authentication Header . . . . . . . . . . . . . . . .   7
       3.2.2.  Interactions between IPv6 Metadata Header and ESP
               header  . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.3.  Interactions between IPv6 Metadata Header and
               Fragment header . . . . . . . . . . . . . . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The basic IPv6 header and the initially defined IPv6 extension
   headers and options are specified in [RFC8200].  SRv6
   [I-D.ietf-spring-srv6-network-programming] introduces a new type of
   Routing Header for IPv6, i.e. SRH
   [I-D.ietf-6man-segment-routing-header].  For supporting the SRv6
   service programming SFC [I-D.xuclad-spring-sr-service-programming],
   SRH TLV is used to carry the Service Metadata [RFC8300].  For the
   SRv6 IOAM [I-D.ali-6man-spring-srv6-oam], the IOAM data fields are
   carried in a pre-allocated SRH TLV, while for the IPv6 IOAM, two
   types of extension headers in IPv6 packets - either Hop-by-Hop

Li & Peng                Expires January 9, 2020                [Page 2]
Internet-Draft      IPv6 Extension Header Enhancement          July 2019

   Options header or Destination options header are proposed to
   encapsulate the IOAM data [I-D.ioametal-ippm-6man-ioam-ipv6-options].

   As SRv6 and the new services such as SFC and iOAM are progressing,
Show full document text