IPv6 Segment Routing Header (SRH)
draft-ietf-6man-segment-routing-header-26

Document Type Active Internet-Draft (6man WG)
Last updated 2019-10-31 (latest revision 2019-10-22)
Replaces draft-previdi-6man-segment-routing-header
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Bob Hinden
Shepherd write-up Show (last changed 2019-06-18)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to Robert Hinden <bob.hinden@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Network Working Group                                   C. Filsfils, Ed.
Internet-Draft                                             D. Dukes, Ed.
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: April 24, 2020                                       S. Previdi
                                                                  Huawei
                                                                J. Leddy
                                                              Individual
                                                           S. Matsushima
                                                                Softbank
                                                                D. Voyer
                                                             Bell Canada
                                                        October 22, 2019

                   IPv6 Segment Routing Header (SRH)
               draft-ietf-6man-segment-routing-header-26

Abstract

   Segment Routing can be applied to the IPv6 data plane using a new
   type of Routing Extension Header called the Segment Routing Header.
   This document describes the Segment Routing Header and how it is used
   by Segment Routing capable nodes.

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 April 24, 2020.

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

Filsfils, et al.         Expires April 24, 2020                 [Page 1]
Internet-Draft      IPv6 Segment Routing Header (SRH)       October 2019

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Segment Routing Header  . . . . . . . . . . . . . . . . . . .   4
     2.1.  SRH TLVs  . . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  Padding TLVs  . . . . . . . . . . . . . . . . . . . .   8
       2.1.2.  HMAC TLV  . . . . . . . . . . . . . . . . . . . . . .   9
   3.  SR Nodes  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     3.1.  Source SR Node  . . . . . . . . . . . . . . . . . . . . .  12
     3.2.  Transit Node  . . . . . . . . . . . . . . . . . . . . . .  12
     3.3.  SR Segment Endpoint Node  . . . . . . . . . . . . . . . .  12
   4.  Packet Processing . . . . . . . . . . . . . . . . . . . . . .  13
     4.1.  Source SR Node  . . . . . . . . . . . . . . . . . . . . .  13
       4.1.1.  Reduced SRH . . . . . . . . . . . . . . . . . . . . .  13
     4.2.  Transit Node  . . . . . . . . . . . . . . . . . . . . . .  14
     4.3.  SR Segment Endpoint Node  . . . . . . . . . . . . . . . .  14
       4.3.1.  FIB Entry Is Locally Instantiated SRv6 SID  . . . . .  14
       4.3.2.  FIB Entry Is A Local Interface  . . . . . . . . . . .  16
       4.3.3.  FIB Entry Is A Non-Local Route  . . . . . . . . . . .  17
       4.3.4.  FIB Entry Is A No Match . . . . . . . . . . . . . . .  17
   5.  Intra SR Domain Deployment Model  . . . . . . . . . . . . . .  17
     5.1.  Securing the SR Domain  . . . . . . . . . . . . . . . . .  17
     5.2.  SR Domain as A Single System with Delegation Among
           Components  . . . . . . . . . . . . . . . . . . . . . . .  18
     5.3.  MTU Considerations  . . . . . . . . . . . . . . . . . . .  19
     5.4.  ICMP Error Processing . . . . . . . . . . . . . . . . . .  19
     5.5.  Load Balancing and ECMP . . . . . . . . . . . . . . . . .  19
     5.6.  Other Deployments . . . . . . . . . . . . . . . . . . . .  20
   6.  Illustrations . . . . . . . . . . . . . . . . . . . . . . . .  20
     6.1.  Abstract Representation of an SRH . . . . . . . . . . . .  20
     6.2.  Example Topology  . . . . . . . . . . . . . . . . . . . .  21
Show full document text