Segment Routing interworking with RSVP-TE
draft-hu-spring-segment-routing-rsvp-te-interop-00

Document Type Active Internet-Draft (individual)
Last updated 2018-06-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                                              Z. Hu
Internet-Draft                                                    G. Yan
Intended status: Standards Track                                 X. Chen
Expires: January 1, 2019                                          J. Yao
                                                     Huawei Technologies
                                                           June 30, 2018

               Segment Routing interworking with RSVP-TE
           draft-hu-spring-segment-routing-rsvp-te-interop-00

Abstract

   A Segment Routing (SR) node steers a packet through an ordered list
   of instructions, called segments.  A segment can represent any
   instruction, topological or service-based.  Segment Routing (SR) is a
   protocol designed to forward packets on the network based on the
   concept of source routing.  The Segment Routing architecture can be
   directly applied to the MPLS data plane with no change in the
   forwarding plane.  It simplifies the MPLS control protocol,
   simplifies the configuration of the network, and can achieve SDN
   better.

   Resource Reservation Protocol - Traffic Engineering (RSVP-TE) has the
   ability of path planning and resource reservation.  In the process of
   traditional network evolution to Segment Routing, there will
   inevitably be coexistence of RSVP-TE and Segment Routing.  The
   Document describes how to interact with nodes that support Segment
   Routing capabilities and nodes that support RSVP-TE capabilities.

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

Hu, et al.               Expires January 1, 2019                [Page 1]
Internet-Draft  Segment Routing interworking with RSVP-TE      June 2018

   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 January 1, 2019.

Copyright Notice

   Copyright (c) 2018 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  SR to RSVP-TE . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  SR to RSVP-TE . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  SR to RSVP-TE Behavior  . . . . . . . . . . . . . . . . .   5
   3.  RSVP-TE to SR . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  RSVP-TE to SR . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  RSVP-TE to SR Behavior  . . . . . . . . . . . . . . . . .   8
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Segment Routing (SR) described in [I-D.ietf-spring-segment-routing]
   leverages the source routing paradigm.  A Segment Routing (SR) node
   steers a packet through an ordered list of instructions, called
   segments.  A segment can represent any instruction, topological or
   service-based.  Segment Routing can be directly applied to the MPLS
   architecture with no change on the forwarding plane
   [I-D.ietf-spring-segment-routing-mpls].  A segment is encoded as an
   MPLS label.  An ordered list of segments is encoded as a stack of
   labels.  The segment to process is on the top of the stack.  A
Show full document text