IPv6 Authentication Header with Segment Routing Header Processing
draft-herbert-ipv6-srh-ah-00

Document Type Active Internet-Draft (individual)
Last updated 2019-05-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
INTERNET-DRAFT                                                T. Herbert
Intended Status: Standard                                     Quantonium
Expires: November 2019                                                  
                                                                        
                                                            May 27, 2019

   IPv6 Authentication Header with Segment Routing Header Processing
                      draft-herbert-ipv6-srh-ah-00

Abstract

   This specification describes processing of the IPv6 Authentication
   Header when the IPv6 Segment Routing Header is present in the same
   packet. Specifically, the handling of mutable fields in the Segment
   Routing Header for the purposes of computing or verifying the
   packet's authenticating value is specified.

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
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
 

T. Herbert             Expires November 28, 2019                [Page 1]
INTERNET DRAFT        draft-herbert-ipv6-srh-ah-00          May 27, 2019

   (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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Handling mutable fields in AH  . . . . . . . . . . . . . . .  3
     1.2 Mutable fields in Segment Routing Header . . . . . . . . . .  3
   2  Handling mutable SRH fields for ICV calculation . . . . . . . .  4
   3  Security Considerations . . . . . . . . . . . . . . . . . . . .  5
   4  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  5
   5  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.1  Normative References  . . . . . . . . . . . . . . . . . . .  5
     5.2  Informative References  . . . . . . . . . . . . . . . . . .  5
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  5

 

T. Herbert             Expires November 28, 2019                [Page 2]
INTERNET DRAFT        draft-herbert-ipv6-srh-ah-00          May 27, 2019

1  Introduction

   This specification describes processing of the IPv6 Authentication
   Header (AH) [RFC4302] when the IPv6 Segment Routing Header (SRH)
   [SRH] is present in the same packet. AH is used to authenticate the
   preceding IPv6 header and extension headers in a packet.
   Authentication is performed by computing an Integrity Check Value
   (ICV) over the covered headers and comparing the computed value to
   that contained in the ICV field of the AH header. Both the sender and
   receiver (the final destination in the case that a routing header is
   present) MUST independently and deterministically perform the same
   computation over the same data.

1.1 Handling mutable fields in AH

   Certain fields may be modified during transit (i.e. mutable fields).
   To ensure that the sender and receiver both produce the same result
   in ICV computation for mutable fields, Section 5.3.3.1 of [RFC4302]
   specifies:

      * If a field is mutable and its value at the (IPsec) receiver is
        not predictable, then the value of the field is set to zero for
        purposes of the ICV computation.

      * If a field is mutable and its value at the (IPsec) receiver is
        predictable, then the predicted value is inserted into the field
        for purposes of the ICV computation.

1.2 Mutable fields in Segment Routing Header

   Per [RFC8200] and [SRH], there are three instances of mutable fields
Show full document text