< draft-ietf-pce-hierarchy-extensions-07.txt   draft-ietf-pce-hierarchy-extensions-08.txt >
PCE Working Group F. Zhang PCE Working Group F. Zhang
Internet-Draft Q. Zhao Internet-Draft Q. Zhao
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: June 6, 2019 O. Gonzalez de Dios Expires: June 7, 2019 O. Gonzalez de Dios
Telefonica I+D Telefonica I+D
R. Casellas R. Casellas
CTTC CTTC
D. King D. King
Old Dog Consulting Old Dog Consulting
December 5, 2018 December 6, 2018
Extensions to Path Computation Element Communication Protocol (PCEP) for Extensions to Path Computation Element Communication Protocol (PCEP) for
Hierarchical Path Computation Elements (PCE) Hierarchical Path Computation Elements (PCE)
draft-ietf-pce-hierarchy-extensions-07 draft-ietf-pce-hierarchy-extensions-08
Abstract Abstract
The Hierarchical Path Computation Element (H-PCE) architecture is The Hierarchical Path Computation Element (H-PCE) architecture is
defined in RFC 6805. It provides a mechanism to derive an optimum defined in RFC 6805. It provides a mechanism to derive an optimum
end-to-end path in a multi-domain environment by using a hierarchical end-to-end path in a multi-domain environment by using a hierarchical
relationship between domains to select the optimum sequence of relationship between domains to select the optimum sequence of
domains and optimum paths across those domains. domains and optimum paths across those domains.
This document defines extensions to the Path Computation Element This document defines extensions to the Path Computation Element
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 6, 2019. This Internet-Draft will expire on June 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . .3
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . .4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . .5
1.3. Requirements Language . . . . . . . . . . . . . . . . . . 1.3. Requirements Language . . . . . . . . . . . . . . . . . .5
2. Requirements for H-PCE . . . . . . . . . . . . . . . . . . . 2. Requirements for H-PCE . . . . . . . . . . . . . . . . . . .5
2.1. Path Computation Request . . . . . . . . . . . . . . . . 2.1. Path Computation Request . . . . . . . . . . . . . . . .5
2.1.1. Qualification of PCEP Requests . . . . . . . . . . . 2.1.1. Qualification of PCEP Requests . . . . . . . . . . .6
2.1.2. Multi-domain Objective Functions . . . . . . . . . . 2.1.2. Multi-domain Objective Functions . . . . . . . . . .6
2.1.3. Multi-domain Metrics . . . . . . . . . . . . . . . . 2.1.3. Multi-domain Metrics . . . . . . . . . . . . . . . .6
2.2. Parent PCE Capability Advertisement . . . . . . . . . . . 2.2. Parent PCE Capability Advertisement . . . . . . . . . . .7
2.3. PCE Domain Identification . . . . . . . . . . . . . . . . 2.3. PCE Domain Identification . . . . . . . . . . . . . . . .7
2.4. Domain Diversity . . . . . . . . . . . . . . . . . . . . 2.4. Domain Diversity . . . . . . . . . . . . . . . . . . . .7
3. PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . . 3. PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . .8
3.1. OPEN Object . . . . . . . . . . . . . . . . . . . . . . . 3.1. OPEN Object . . . . . . . . . . . . . . . . . . . . . . .8
3.1.1. H-PCE Capability TLV . . . . . . . . . . . . . . . . 3.1.1. H-PCE Capability TLV . . . . . . . . . . . . . . . .8
3.1.2. Domain-ID TLV . . . . . . . . . . . . . . . . . . . . 3.1.2. Domain-ID TLV . . . . . . . . . . . . . . . . . . . .9
3.2. RP Object . . . . . . . . . . . . . . . . . . . . . . . . 3.2. RP Object . . . . . . . . . . . . . . . . . . . . . . . .10
3.2.1. H-PCE-FLAG TLV . . . . . . . . . . . . . . . . . . . 3.2.1. H-PCE-FLAG TLV . . . . . . . . . . . . . . . . . . .10
3.2.2. Domain-ID TLV . . . . . . . . . . . . . . . . . . . . 3.2.2. Domain-ID TLV . . . . . . . . . . . . . . . . . . . .10
3.3. Objective Functions . . . . . . . . . . . . . . . . . . . 3.3. Objective Functions . . . . . . . . . . . . . . . . . . .11
3.3.1. OF Codes . . . . . . . . . . . . . . . . . . . . . . 3.3.1. OF Codes . . . . . . . . . . . . . . . . . . . . . .11
3.3.2. OF Object . . . . . . . . . . . . . . . . . . . . . . 3.3.2. OF Object . . . . . . . . . . . . . . . . . . . . . .12
3.4. Metric Object . . . . . . . . . . . . . . . . . . . . . . 3.4. Metric Object . . . . . . . . . . . . . . . . . . . . . .13
3.5. SVEC Object . . . . . . . . . . . . . . . . . . . . . . . 3.5. SVEC Object . . . . . . . . . . . . . . . . . . . . . . .14
3.6. PCEP-ERROR object . . . . . . . . . . . . . . . . . . . . 3.6. PCEP-ERROR Object . . . . . . . . . . . . . . . . . . . .14
3.6.1. Hierarchy PCE Error-Type . . . . . . . . . . . . . . 3.6.1. Hierarchy PCE Error-Type . . . . . . . . . . . . . .14
3.7. NO-PATH Object . . . . . . . . . . . . . . . . . . . . . 3.7. NO-PATH Object . . . . . . . . . . . . . . . . . . . . .14
4. H-PCE Procedures . . . . . . . . . . . . . . . . . . . . . . 4. H-PCE Procedures . . . . . . . . . . . . . . . . . . . . . .15
4.1. OPEN Procedure between Child PCE and Parent PCE . . . . . 4.1. OPEN Procedure between Child PCE and Parent PCE . . . . .15
4.2. Procedure to Obtain Domain Sequence . . . . . . . . . . . 4.2. Procedure to Obtain Domain Sequence . . . . . . . . . . .16
5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 5. Error Handling . . . . . . . . . . . . . . . . . . . . . . .16
6. Manageability Considerations . . . . . . . . . . . . . . . . 6. Manageability Considerations . . . . . . . . . . . . . . . .16
6.1. Control of Function and Policy . . . . . . . . . . . . . 6.1. Control of Function and Policy . . . . . . . . . . . . .17
6.1.1. Child PCE . . . . . . . . . . . . . . . . . . . . . . 6.1.1. Child PCE . . . . . . . . . . . . . . . . . . . . . .17
6.1.2. Parent PCE . . . . . . . . . . . . . . . . . . . . . 6.1.2. Parent PCE . . . . . . . . . . . . . . . . . . . . .17
6.1.3. Policy Control . . . . . . . . . . . . . . . . . . . 6.1.3. Policy Control . . . . . . . . . . . . . . . . . . .18
6.2. Information and Data Models . . . . . . . . . . . . . . . 6.2. Information and Data Models . . . . . . . . . . . . . . .18
6.3. Liveness Detection and Monitoring . . . . . . . . . . . .18
6.3. Liveness Detection and Monitoring . . . . . . . . . . . . 6.4. Verify Correct Operations . . . . . . . . . . . . . . . .18
6.4. Verify Correct Operations . . . . . . . . . . . . . . . . 6.5. Requirements On Other Protocols . . . . . . . . . . . . .19
6.5. Requirements On Other Protocols . . . . . . . . . . . . . 6.6. Impact On Network Operations . . . . . . . . . . . . . .19
6.6. Impact On Network Operations . . . . . . . . . . . . . . 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . .19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . .19
7.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 7.2. H-PCE-CAPABILITY TLV Flags . . . . . . . . . . . . . . .19
7.2. H-PCE-CAPABILITY TLV Flags . . . . . . . . . . . . . . . 7.3. Domain-ID TLV Domain type . . . . . . . . . . . . . . . .20
7.3. Domain-ID TLV Domain type . . . . . . . . . . . . . . . . 7.4. H-PCE-FLAG TLV Flags . . . . . . . . . . . . . . . . . .20
7.4. H-PCE-FLAG TLV Flags . . . . . . . . . . . . . . . . . . 7.5. OF Codes . . . . . . . . . . . . . . . . . . . . . . . .21
7.5. OF Codes . . . . . . . . . . . . . . . . . . . . . . . . 7.6. METRIC Types . . . . . . . . . . . . . . . . . . . . . .21
7.6. METRIC Types . . . . . . . . . . . . . . . . . . . . . . 7.7. New PCEP Error-Types and Values . . . . . . . . . . . . .21
7.7. New PCEP Error-Types and Values . . . . . . . . . . . . . 7.8. New NO-PATH-VECTOR TLV Bit Flag . . . . . . . . . . . . .22
7.8. New NO-PATH-VECTOR TLV Bit Flag . . . . . . . . . . . . . 7.9. SVEC Flag . . . . . . . . . . . . . . . . . . . . . . . .22
7.9. SVEC Flag . . . . . . . . . . . . . . . . . . . . . . . . 7.10. NO-PATH VECTOR TLV Bit Flag. . . . . . . . . . . . . . .22
7.10. NO-PATH VECTOR TLV Bit Flag. . . . . . . . . . . . . . . 8. Security Considerations . . . . . . . . . . . . . . . . . . .22
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9. Contributing Authors. . . . . . . . . . . . . . . . . . . . .23
9. Contributing Authors. . . . . . . . . . . . . . . . . . . . . 10. References . . . . . . . . . . . . . . . . . . . . . . . . .23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10.1. Normative References . . . . . . . . . . . . . . . . . .23
10.1. Normative References . . . . . . . . . . . . . . . . . . 10.2. Informative References . . . . . . . . . . . . . . . . .24
10.2. Informative References . . . . . . . . . . . . . . . . . Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .
1. Introduction 1. Introduction
The Path Computation Element communication Protocol (PCEP) provides The Path Computation Element communication Protocol (PCEP) provides
a mechanism for Path Computation Elements (PCEs) and Path Computation a mechanism for Path Computation Elements (PCEs) and Path Computation
Clients (PCCs) to exchange requests for path computation and Clients (PCCs) to exchange requests for path computation and
responses that provide computed paths. responses that provide computed paths.
The capability to compute the routes of end-to-end inter-domain MPLS The capability to compute the routes of end-to-end inter-domain MPLS
Traffic Engineering (MPLS-TE) and GMPLS Label Switched Paths (LSPs) Traffic Engineering (MPLS-TE) and GMPLS Label Switched Paths (LSPs)
skipping to change at page 14, line 29 skipping to change at page 14, line 29
common. common.
The Domain Diverse O-bit can be used in Hierarchical PCE path The Domain Diverse O-bit can be used in Hierarchical PCE path
computation to compute synchronized domain diverse end to end path or computation to compute synchronized domain diverse end to end path or
diverse domain sequences. diverse domain sequences.
When domain diverse O bit is set, it is applied to the transit When domain diverse O bit is set, it is applied to the transit
domains. The other bit in SVEC object (N, L, S etc.) MAY be set and domains. The other bit in SVEC object (N, L, S etc.) MAY be set and
MUST still be applied in the ingress and egress shared domain. MUST still be applied in the ingress and egress shared domain.
3.6. PCEP-ERROR object 3.6. PCEP-ERROR Object
3.6.1. Hierarchy PCE Error-Type 3.6.1. Hierarchy PCE Error-Type
A new PCEP Error-Type [RFC5440] is used for the H-PCE extension as A new PCEP Error-Type [RFC5440] is used for the H-PCE extension as
defined below: defined below:
+------------+-----------------------------------------+ +------------+-----------------------------------------+
| Error-Type | Meaning | | Error-Type | Meaning |
+------------+-----------------------------------------+ +------------+-----------------------------------------+
| TBD8 | H-PCE error | | TBD8 | H-PCE error |
 End of changes. 6 change blocks. 
64 lines changed or deleted 63 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/