Segment Routing with MPLS data plane
draft-ietf-spring-segment-routing-mpls-08

Document Type Active Internet-Draft (spring WG)
Last updated 2017-03-13 (latest revision 2017-03-10)
Replaces draft-filsfils-spring-segment-routing-mpls
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Apr 2016 - Requirements for mod... )
Document shepherd Martin Vigoureux
Shepherd write-up Show (last changed 2017-03-10)
IESG IESG state Publication Requested
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alvaro Retana
Send notices to (None)
Network Working Group                                   C. Filsfils, Ed.
Internet-Draft                                           S. Previdi, Ed.
Intended status: Standards Track                             A. Bashandy
Expires: September 11, 2017                          Cisco Systems, Inc.
                                                             B. Decraene
                                                            S. Litkowski
                                                                  Orange
                                                               R. Shakir
                                                                  Google
                                                          March 10, 2017

                  Segment Routing with MPLS data plane
               draft-ietf-spring-segment-routing-mpls-08

Abstract

   Segment Routing (SR) leverages the source routing paradigm.  A node
   steers a packet through a controlled set of instructions, called
   segments, by prepending the packet with an SR header.  In the MPLS
   dataplane, the SR header is instantiated through a label stack.  A
   segment can represent any instruction, topological or service-based.
   Additional segments can be defined in the future.  SR allows to
   enforce a flow through any topological path and/or service chain
   while maintaining per-flow state only at the ingress node to the SR
   domain.

   Segment Routing can be directly applied to the MPLS architecture with
   no change in the forwarding plane.  This drafts describes how Segment
   Routing operates on top of the MPLS data plane.

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

Filsfils, et al.       Expires September 11, 2017               [Page 1]
Internet-Draft          Segment Routing with MPLS             March 2017

   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 September 11, 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  MPLS Instantiation of Segment Routing . . . . . . . . . . . .   3
   3.  IGP Segments Examples . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Example 1 . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Example 2 . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Example 3 . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Example 4 . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Example 5 . . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   5.  Manageability Considerations  . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Segment Routing architecture [I-D.ietf-spring-segment-routing]
Show full document text