Segment Routing Policy for Traffic Engineering
draft-filsfils-spring-segment-routing-policy-03

Document Type Active Internet-Draft (individual)
Last updated 2017-10-30
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                                        C. Filsfils
Internet-Draft                                              S. Sivabalan
Intended status: Standards Track                                 K. Raza
Expires: May 3, 2018                                            J. Liste
                                                                 F. Clad
                                                     Cisco Systems, Inc.
                                                                S. Hegde
                                                  Juniper Networks, Inc.
                                                                D. Yoyer
                                                            Bell Canada.
                                                                  S. Lin
                                                             A. Bogdanov
                                                            Google, Inc.
                                                            M. Horneffer
                                                        Deutsche Telekom
                                                            D. Steinberg
                                                    Steinberg Consulting
                                                             B. Decraene
                                                            S. Litkowski
                                                Orange Business Services
                                                        October 30, 2017

             Segment Routing Policy for Traffic Engineering
          draft-filsfils-spring-segment-routing-policy-03.txt

Abstract

   Segment Routing (SR) allows a headend node to steer a packet flow
   along any path.  Intermediate per-flow states are eliminated thanks
   to source routing.  The headend node steers a flow into an SR Policy.
   The header of a packet steered in an SR Policy is augmented with the
   ordered list of segments associated with that SR Policy.  This
   document details the concepts of SR Policy and steering into an SR
   Policy.

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 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

Filsfils, et al.           Expires May 3, 2018                  [Page 1]
Internet-Draft                  SR Policy                   October 2017

   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 May 3, 2018.

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  SR Traffic Engineering Architecture . . . . . . . . . . . . .   4
   3.  SR Policy . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  SR Policy Active Path Selection Examples  . . . . . . . . . .   8
   5.  Segment-list  . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Explicit Null . . . . . . . . . . . . . . . . . . . . . .  10
   6.  SR Policy Multi-Domain Database . . . . . . . . . . . . . . .  11
   7.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  W-ECMP  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.2.  Path Validation . . . . . . . . . . . . . . . . . . . . .  12
     7.3.  Fast Convergence  . . . . . . . . . . . . . . . . . . . .  12
   8.  Binding SID . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.2.  Allocation  . . . . . . . . . . . . . . . . . . . . . . .  14
       8.2.1.  Dynamic BSID Allocation . . . . . . . . . . . . . . .  14
Show full document text