IPv6 Segment Routing Header (SRH)
draft-previdi-6man-segment-routing-header-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-03-06
Replaced by draft-ietf-6man-segment-routing-header
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                                    S. Previdi, Ed.
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: September 6, 2014                                      B. Field
                                                                 Comcast
                                                                I. Leung
                                                   Rogers Communications
                                                           March 5, 2014

                   IPv6 Segment Routing Header (SRH)
              draft-previdi-6man-segment-routing-header-00

Abstract

   Segment Routing (SR) allows a node to steer a packet through a
   controlled set of instructions, called segments, by prepending a SR
   header to the packet.  A segment can represent any instruction,
   topological or service-based.  SR allows to enforce a flow through
   any path (topological, or application/service based) while
   maintaining per-flow state only at the ingress node to the SR domain.

   The Segment Routing architecture can be applied to the IPv6 data
   plane with the addition of a new type of Routing Extension Header.
   This draft describes the Segment Routing Extension Header Type and
   how it is used by SR capable nodes.

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 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."

Previdi, et al.         Expires September 6, 2014               [Page 1]
Internet-Draft      IPv6 Segment Routing Header (SRH)         March 2014

   This Internet-Draft will expire on September 6, 2014.

Copyright Notice

   Copyright (c) 2014 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Previdi, et al.         Expires September 6, 2014               [Page 2]
Internet-Draft      IPv6 Segment Routing Header (SRH)         March 2014

Table of Contents

   1.  Structure of this document . . . . . . . . . . . . . . . . . .  4
   2.  Segment Routing Documents  . . . . . . . . . . . . . . . . . .  4
   3.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Data Planes supporting Segment Routing . . . . . . . . . .  5
     3.2.  Illustrative Example . . . . . . . . . . . . . . . . . . .  5
   4.  IPv6 Instantiation of Segment Routing  . . . . . . . . . . . .  6
     4.1.  Segment Routing Extension Header (SRH) . . . . . . . . . .  6
       4.1.1.  SRH and RFC2460 behavior . . . . . . . . . . . . . . .  9
       4.1.2.  SRH Optimization . . . . . . . . . . . . . . . . . . . 10
     4.2.  Segment Identifiers (SIDs) . . . . . . . . . . . . . . . . 10
       4.2.1.  Node-SID . . . . . . . . . . . . . . . . . . . . . . . 10
       4.2.2.  Adjacency-SID  . . . . . . . . . . . . . . . . . . . . 11
   5.  SRH Procedures . . . . . . . . . . . . . . . . . . . . . . . . 11
     5.1.  Segment Routing Operations . . . . . . . . . . . . . . . . 11
     5.2.  Segment Routing Node Functions . . . . . . . . . . . . . . 11
       5.2.1.  Ingress SR Node  . . . . . . . . . . . . . . . . . . . 12
       5.2.2.  Transit Non-SR Capable Node  . . . . . . . . . . . . . 13
       5.2.3.  SR Intra Segment Transit Node  . . . . . . . . . . . . 13
       5.2.4.  SR Segment Endpoint Node . . . . . . . . . . . . . . . 14
     5.3.  FRR Flag Settings  . . . . . . . . . . . . . . . . . . . . 14
   6.  SR-IPv6 Security . . . . . . . . . . . . . . . . . . . . . . . 14
     6.1.  Threat model . . . . . . . . . . . . . . . . . . . . . . . 15
     6.2.  Applicability of RFC 5095 to SRH . . . . . . . . . . . . . 15
Show full document text