PCEP Extensions for MPLS Source Routing-based SFC
draft-xu-pce-sr-sfc-04

Document Type Active Internet-Draft (individual)
Last updated 2016-12-29
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
PCE Working Group                                                  X. Xu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                  J. You
Expires: July 2, 2017
                                                            S. Sivabalan
                                                                   Cisco
                                                                 H. Shah
                                                                   Ciena
                                                            L. Contreras
                                                          Telefonica I+D
                                                              D. Bernier
                                                             Bell Canada
                                                       December 29, 2016

           PCEP Extensions for MPLS Source Routing-based SFC
                         draft-xu-pce-sr-sfc-04

Abstract

   Source Packet Routing in Networking (SPRING) WG is developing an MPLS
   source routing mechanism.  This MPLS source routing mechanism can be
   leveraged to realize the service path layer functionality of the
   service function chaining (i.e., steering the selected traffic
   through a particular service function path) by encoding the service
   function path information as an MPLS label stack.  This document
   describes extensions to the Path Computation Element Protocol (PCEP)
   that allow a PCE to compute and instantiate service function paths in
   the MPLS source routing based service function chaining context.  The
   extensions specified in this document are applicable to both the
   stateless PCE model and the stateful PCE model.

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

Xu, et al.                Expires July 2, 2017                  [Page 1]
Internet-Draft                                             December 2016

   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 July 2, 2017.

Copyright Notice

   Copyright (c) 2016 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  PCEP Message Extensions for MPLS Source Routing-based SFC . .   4
     3.1.  PCReq Message . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  PCRep Message . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  PCUpd Message . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  PCRpt Message . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Object Formats  . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  OPEN Object . . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  SR-SFC PCE Capability TLV . . . . . . . . . . . . . .   6
     4.2.  RP/SRP Object . . . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Include Route Object  . . . . . . . . . . . . . . . . . .   7
     4.4.  SR-SFC-ERO Object . . . . . . . . . . . . . . . . . . . .   7
       4.4.1.  SR-SFC-ERO Subobject  . . . . . . . . . . . . . . . .   7
       4.4.2.  NSI Associated with SID . . . . . . . . . . . . . . .   9
       4.4.3.  SR-SFC-ERO Processing . . . . . . . . . . . . . . . .   9
Show full document text