PCEP Extensions for Service Function Chaining (SFC)
draft-wu-pce-traffic-steering-sfc-11

Document Type Active Internet-Draft (individual)
Last updated 2017-03-09
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                                                  Q. Wu
Internet-Draft                                                  D. Dhody
Intended status: Standards Track                                  Huawei
Expires: September 10, 2017                                 M. Boucadair
                                                            C. Jacquenet
                                                                  Orange
                                                             J. Tantsura
                                                           March 9, 2017

          PCEP Extensions for Service Function Chaining (SFC)
                  draft-wu-pce-traffic-steering-sfc-11

Abstract

   This document provides an overview of the usage of Path Computation
   Element (PCE) to dynamically structure service function chains.
   Service Function Chaining (SFC) is a technique that is meant to
   facilitate the dynamic enforcement of differentiated traffic
   forwarding policies within a domain.  Service function chains are
   composed of an ordered set of elementary Service Functions (such as
   firewalls, load balancers) that need to be invoked according to the
   design of a given service.  Corresponding traffic is thus forwarded
   along a Service Function Path (SFP) that can be computed by means of
   PCE.

   This document specifies extensions to the Path Computation Element
   Protocol (PCEP) that allow a stateful PCE to compute and instantiate
   Service Function Paths.

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

   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 10, 2017.

Wu, et al.             Expires September 10, 2017               [Page 1]
Internet-Draft                PCEP for SFC                    March 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.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Service Function Paths and PCE  . . . . . . . . . . . . . . .   4
   4.  Overview of PCEP Operation in SFC-Enabled Networks  . . . . .   6
     4.1.  SFP Instantiation . . . . . . . . . . . . . . . . . . . .   6
     4.2.  SFP Withdrawal  . . . . . . . . . . . . . . . . . . . . .   6
     4.3.  SFP Delegation and Cleanup  . . . . . . . . . . . . . . .   7
     4.4.  SFP State Synchronization . . . . . . . . . . . . . . . .   7
     4.5.  SFP Update and Report . . . . . . . . . . . . . . . . . .   7
   5.  Object Formats  . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  The OPEN Object . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  The LSP Object  . . . . . . . . . . . . . . . . . . . . .   8
       5.2.1.  SFP Identifiers TLV . . . . . . . . . . . . . . . . .   8
   6.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .   9
   7.  SFP Instantiation Signaling and Forwarding Considerations . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Service Function Chaining (SFC) enables the creation of composite
   services that consist of an ordered set of Service Functions (SF)
Show full document text