PCEP Extensions for MPSL-TE LSP Path Protection with stateful PCE
draft-ananthakrishnan-pce-stateful-path-protection-04

Document Type Active Internet-Draft (individual)
Last updated 2017-09-26
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                                     H. Ananthakrishnan
Internet-Draft                                             Packet Design
Intended status: Standards Track                            S. Sivabalan
Expires: March 30, 2018                                            Cisco
                                                                C. Barth
                                                                R. Torvi
                                                        Juniper Networks
                                                                I. Minei
                                                             Google, Inc
                                                               E. Crabbe
                                                  Individual Contributor
                                                                D. Dhody
                                                     Huawei Technologies
                                                      September 26, 2017

   PCEP Extensions for MPSL-TE LSP Path Protection with stateful PCE
         draft-ananthakrishnan-pce-stateful-path-protection-04

Abstract

   A stateful Path Computation Element (PCE) is capable of computing as
   well as controlling via Path Computation Element Protocol (PCEP)
   Multiprotocol Label Switching Traffic Engineering Label Switched
   Paths (MPLS LSP).  Furthermore, it is also possible for a stateful
   PCE to create, maintain, and delete LSPs.  This document describes
   PCEP extension to associate two or more LSPs to provide end-to-end
   path protection.

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
   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 March 30, 2018.

Ananthakrishnan, et al.  Expires March 30, 2018                 [Page 1]
Internet-Draft      Stateful PCE LSP Path Protection      September 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Path Protection Association Type  . . . . . . . . . . . .   5
     3.2.  Path Protection Association TLV . . . . . . . . . . . . .   6
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  PCC Initiated LSPs  . . . . . . . . . . . . . . . . . . .   7
     4.2.  PCE Initiated LSPs  . . . . . . . . . . . . . . . . . . .   7
     4.3.  State Synchronization . . . . . . . . . . . . . . . . . .   8
     4.4.  Session Termination . . . . . . . . . . . . . . . . . . .   8
     4.5.  Error Handling  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Other considerations  . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Association Type  . . . . . . . . . . . . . . . . . . . .   9
     6.2.  PPAG TLV  . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.3.  PCEP Errors . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Manageability Considerations  . . . . . . . . . . . . . . . .  11
     8.1.  Control of Function and Policy  . . . . . . . . . . . . .  11
     8.2.  Information and Data Models . . . . . . . . . . . . . . .  11
     8.3.  Liveness Detection and Monitoring . . . . . . . . . . . .  11
     8.4.  Verify Correct Operations . . . . . . . . . . . . . . . .  11
     8.5.  Requirements On Other Protocols . . . . . . . . . . . . .  11
     8.6.  Impact On Network Operations  . . . . . . . . . . . . . .  11
Show full document text