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

Document Type Active Internet-Draft (individual)
Last updated 2017-02-18
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                     Cisco Systems, Inc.
Expires: August 22, 2017                                        D. Yoyer
                                                            Bell Canada.
                                                              M. Nanduri
                                                  Microsoft Corporation.
                                                                  S. Lin
                                                             A. Bogdanov
                                                            Google, Inc.
                                                            M. Horneffer
                                                        Deutsche Telekom
                                                                 F. Clad
                                                    Cisco Systems, Inc.,
                                                            D. Steinberg
                                                    Steinberg Consulting
                                                             B. Decraene
                                                             S. Litkosky
                                                Orange Business Services
                                                       February 18, 2017

             Segment Routing Policy for Traffic Engineering
          draft-filsfils-spring-segment-routing-policy-00.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.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute

Filsfils, et al.         Expires August 22, 2017                [Page 1]
Internet-Draft             SR Policy/SR-Policy             February 2017

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

   This Internet-Draft will expire on August 22, 2017.

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
   (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
   2.  SR Traffic Engineering Architecture . . . . . . . . . . . . .   3
   3.  SR Policy . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  SID List  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Explicit Null . . . . . . . . . . . . . . . . . . . . . .   7
   5.  SR Policy Multi-Domain Database . . . . . . . . . . . . . . .   8
   6.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  W-ECMP  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  Path Validation . . . . . . . . . . . . . . . . . . . . .   8
     6.3.  Fast Convergence  . . . . . . . . . . . . . . . . . . . .   9
   7.  Binding SID . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  Allocation  . . . . . . . . . . . . . . . . . . . . . . .  11
Show full document text