Extensions to the Path Computation Element Protocol (PCEP) to Support Resource Sharing-based Path Computation
draft-zhang-pce-resource-sharing-11
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-10-23
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
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 Xian Zhang
Internet Draft Haomian Zheng
Category: Standards track Huawei Technologies
Oscar Gonzales de Dios
Victor Lopez
Telefonica I+D
Yunbin Xu
CAICT
Expires: April 24, 2020 October 24, 2019
Extensions to the Path Computation Element Protocol (PCEP) to Support
Resource Sharing-based Path Computation
draft-zhang-pce-resource-sharing-11
Abstract
Resource sharing in a network means two or more Label Switched Paths
(LSPs) use common pieces of resource along their paths. This can
help save network resources and is useful in scenarios such as LSP
recovery or when two LSPs do not need to be active at the same time.
A Path Computation Element (PCE) is responsible for path computation
with such requirement.
Existing extensions to the Path Computation Element Protocol (PCEP)
allow one path computation request for an LSP to be associated with
other (existing) LSPs through the use of the PCEP Association
Object.
This document extends PCEP in order to support resource-sharing-
based path computation as another use of the Association Object to
enable better efficiency in the computation and in the resultant
paths and network resource usage.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Zhang et al Expires April 2020 [Page 1]
draft-zhang-pce-resource-sharing-11 October 2019
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 24, 2020.
Copyright Notice
Copyright (c) 2019 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 and Motivation .................................. 3
1.1. Requirements Language ................................... 4
2. Motivation ................................................... 5
2.1. Single Domain Use Case .................................. 5
2.2. Multiple Layers/Domains Use Case ........................ 6
2.3. Bulk Path Computation Use Case .......................... 8
3. Extensions to PCEP ........................................... 9
3.1. Association Group and Type .............................. 9
3.2. Resource Sharing TLV ................................... 10
3.3. Processing Rules ....................................... 11
4. Implementation Status ....................................... 12
5. Manageability Considerations ................................ 12
5.1. Control of Function and Policy ......................... 12
5.2. Information and Data Models ............................ 12
5.3. Liveness Detection and Monitoring ...................... 13
5.4. Verify Correct Operations .............................. 13
5.5. Requirements on Other Protocols ........................ 13
Zhang et al Expires April 2020 [Page 2]
Show full document text