Attribution Option for Extension Header Insertion
draft-herbert-6man-eh-attrib-02

Document Type Active Internet-Draft (individual)
Author Tom Herbert 
Last updated 2020-08-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                                         T. Herbert
Internet-Draft                                                     Intel
Intended status: Experimental                            August 24, 2020
Expires: February 25, 2021

           Attribution Option for Extension Header Insertion
                    draft-herbert-6man-eh-attrib-02

Abstract

   This document defines an "attribution option" that provides
   attribution for IPv6 extension headers, Hop-by-Hop options, or
   Destination options that are inserted by intermediate nodes in the
   delivery path of a packet.  The purpose of this option is twofold:
   first it identifies the extension headers or options that have been
   inserted, secondly it attributes the inserted extension headers or
   options to the node responsible for inserting them.

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 25, 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
   (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

Herbert                 Expires February 25, 2021               [Page 1]
Internet-Draft             Attribution Option                August 2020

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Motivation for extension header insertion . . . . . . . .   3
     1.2.  Problems with extension header and options insertion  . .   4
     1.3.  Inserting Hop-by-Hop options  . . . . . . . . . . . . . .   5
     1.4.  Inserting Destination options . . . . . . . . . . . . . .   5
     1.5.  Inserting extension headers . . . . . . . . . . . . . . .   5
     1.6.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     1.7.  Requirements Language . . . . . . . . . . . . . . . . . .   6
   2.  Attribution Option  . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  Attribution Option with short identifier  . . . . . .   7
       2.1.2.  Attribution Option with IPv6 address identifier . . .   8
     2.2.  Model . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Insertion . . . . . . . . . . . . . . . . . . . . . . . .  10
       3.1.1.  Insertion procedure . . . . . . . . . . . . . . . . .  10
       3.1.2.  Errors during insertion . . . . . . . . . . . . . . .  11
     3.2.  Removal of inserted extension headers and options . . . .  12
       3.2.1.  Removal procedure . . . . . . . . . . . . . . . . . .  12
       3.2.2.  Errors during removal . . . . . . . . . . . . . . . .  13
     3.3.  Domain edge filtering . . . . . . . . . . . . . . . . . .  13
     3.4.  ICMP processing . . . . . . . . . . . . . . . . . . . . .  14
     3.5.  Processing AH . . . . . . . . . . . . . . . . . . . . . .  15
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Extension header insertion has been proposed as a mechanism to
   annotate packets for transit across controlled, or limited domains
   ([I-D.voyer-6man-extension-header-insertion],
   [I-D.ietf-ippm-ioam-ipv6-options]).  These annotations are in the
   form of inserted Hop-by-Hop or Destination options, or other inserted
   extension headers such Segment Routing Header.  Presumably, before a
   packet egresses a controlled domain, any inserted extension headers
Show full document text