The Use Cases for Using PCE as the Central Controller(PCECC) of LSPs
draft-ietf-teas-pcecc-use-cases-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (teas WG)
|
|
Last updated |
|
2017-03-02
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
TEAS Working Group Quintin Zhao
Internet-Draft Robin Li
Intended status: Experimental Boris Khasanov
Expires: September 1, 2017 Huawei Technologies
King Ke
Tencent Holdings Ltd.
Luyuan Fang
Microsoft
Chao Zhou
Cisco Systems
Boris Zhang
Telus Communications
Artem Rachitskiy
Mobile TeleSystems JLLC
Anton Gulida
LLC "Lifetech"
March 1, 2017
The Use Cases for Using PCE as the Central Controller(PCECC) of LSPs
draft-ietf-teas-pcecc-use-cases-00
Abstract
In certain networks deployment scenarios, service providers would
like to keep all the existing MPLS functionalities in both MPLS and
GMPLS network while reducing existing complexity.In this document,
we propose to use the PCE as a central controller so that LSP can be
calculated/signaled/initiated/downloaded/managed through a
centralized PCE server to each network devices along the LSP path
while leveraging the existing PCE technologies as much as possible.
This draft describes the use cases for using the PCE as the central
controller where LSPs are calculated/setup/initiated/downloaded/
maintained through extending the current PCE architectures and
extending the PCEP.
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 [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/.
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."
Zhao, et al. Expires September 1, 2017 [Page 1]
Internet-Draft Use Cases for PCECC March 2017
This Internet-Draft will expire on September 1, 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
1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Using the PCE as the Central Controller (PCECC) Approach 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. PCEP Requirements . . . . . . . . . . . . . . . . . . . . . . 7
4. Use Cases of PCECC for Label Resource Reservations . . . . . 8
5. Using PCECC for SR without the IGP Extension . . . . . . . . 9
5.1. Use Cases of PCECC for SR Best Effort(BE) Path . . . . . 10
5.2. Use Cases of PCECC for SR Traffic Engineering (TE) Path . 11
6. Use Cases of PCECC for TE LSP . . . . . . . . . . . . . . . . 12
7. Use Cases of PCECC for Multicast LSPs . . . . . . . . . . . . 14
7.1. Using PCECC for P2MP/MP2MP LSPs' Setup . . . . . . . . . 14
7.2. Use Cases of PCECC for the Resiliency of P2MP/MP2MP LSPs 15
7.2.1. PCECC for the End-to-End Protection of the P2MP/MP2MP
Show full document text