Make-Before-Break MPLS-TE LSP restoration and reoptimization procedure using Stateful PCE
draft-tanaka-pce-stateful-pce-mbb-06

Document Type Active Internet-Draft (individual)
Last updated 2018-06-20
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                                              Y. Tanaka
Internet-Draft                                                 Y. Kamite
Intended status: Standards Track                      NTT Communications
Expires: December 22, 2018                                      D. Dhody
                                                              R. Palleti
                                                     Huawei Technologies
                                                           June 20, 2018

 Make-Before-Break MPLS-TE LSP restoration and reoptimization procedure
                           using Stateful PCE
                  draft-tanaka-pce-stateful-pce-mbb-06

Abstract

   Stateful Path Computation Element (PCE) and its corresponding
   protocol extensions provide a mechanism that enables PCE to do
   stateful control of Multiprotocol Label Switching (MPLS) Traffic
   Engineering Label Switched Paths (TE LSP).  Stateful PCE supports
   manipulating of the existing LSP's state and attributes (e.g.,
   bandwidth and path) via delegation and also instantiation of new LSPs
   in the network via PCE Initiation procedures.

   In the current MPLS TE network using Resource ReSerVation Protocol
   (RSVP-TE), LSPs are often controlled by Make-before-break (M-B-B)
   signaling by the headend for the purpose of LSP restoration and
   reoptimization.  In most cases, it is an essential operation to
   reroute LSP traffic without any data disruption.

   This document specifies the procedure of applying stateful PCE's
   control to make-before-break RSVP-TE signaling.  In this document,
   two types of restoration/reoptimization procedures are defined,
   implicit mode and explicit mode.  This document also specifies the
   usage and handling of stateful PCEP (PCE Communication Protocol)
   messages, expected behavior of PCC as RSVP-TE headend and necessary
   extensions of additional PCEP objects.

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

Tanaka, et al.          Expires December 22, 2018               [Page 1]
Internet-Draft           MBB using Stateful PCE                June 2018

   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 December 22, 2018.

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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Make-Before-Break LSP procedures  . . . . . . . . . . . . . .   5
     5.1.  Implicit Make-Before-Break Mode . . . . . . . . . . . . .   6
     5.2.  Explicit Make-Before-Break Mode . . . . . . . . . . . . .   7
       5.2.1.  Initiate Association Group for old LSP  . . . . . . .   8
       5.2.2.  Establish new Trial LSP . . . . . . . . . . . . . . .   9
       5.2.3.  Switchover Data Traffic triggered by a PCUpd message   11
   6.  Protocol extension  . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Association group . . . . . . . . . . . . . . . . . . . .  13
     6.2.  Trial LSP TLV in ASSOCIATION Objects  . . . . . . . . . .  13
     6.3.  Optional TLVs . . . . . . . . . . . . . . . . . . . . . .  14
     6.4.  Error Handling  . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  PCEP TLV Indicators . . . . . . . . . . . . . . . . . . .  15
     8.2.  Association Object Type Indicator . . . . . . . . . . . .  15
   9.  Operational Considerations  . . . . . . . . . . . . . . . . .  15
     9.1.  Operation in multiple PCEs  . . . . . . . . . . . . . . .  15
Show full document text