< draft-chen-pce-h-discovery-04.txt   draft-chen-pce-h-discovery-05.txt >
PCE Working Group H. Chen PCE Working Group H. Chen
Internet-Draft Huawei Technologies Internet-Draft Futurewei
Intended status: Standards Track M. Toy Intended status: Standards Track M. Toy
Expires: September 6, 2018 Verizon Expires: January 8, 2020 Verizon
X. Liu X. Liu
Jabil Volta Networks
L. Liu L. Liu
Fujitsu Fujitsu
Z. Li Z. Li
China Mobile China Mobile
March 5, 2018 July 7, 2019
Hierarchical PCE Determination Hierarchical PCE Determination
draft-chen-pce-h-discovery-04 draft-chen-pce-h-discovery-05
Abstract Abstract
This document presents extensions to the Path Computation Element This document presents extensions to the Path Computation Element
Communication Protocol (PCEP) for determining parent child relations Communication Protocol (PCEP) for determining parent child relations
and exchanging the information between a parent and a child PCE in a and exchanging the information between a parent and a child PCE in a
hierarchical PCE system. hierarchical PCE system.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 http://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 September 6, 2018. This Internet-Draft will expire on January 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Conventions Used in This Document . . . . . . . . . . . . . . 4 3. Conventions Used in This Document . . . . . . . . . . . . . . 4
4. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . . 4 4. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . 4
4.1. Determination of Parent Child Relation . . . . . . . . . . 4 4.1. Determination of Parent Child Relation . . . . . . . . . 4
4.2. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2.1. Domain Sub-TLV . . . . . . . . . . . . . . . . . . . . 5 4.2.1. Domain Sub-TLV . . . . . . . . . . . . . . . . . . . 5
4.2.2. PCE ID Sub-TLV . . . . . . . . . . . . . . . . . . . . 6 4.2.2. PCE ID Sub-TLV . . . . . . . . . . . . . . . . . . . 6
4.3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 7 4.3. Procedures . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
A hierarchical PCE architecture is described in RFC 6805, in which a A hierarchical PCE architecture is described in RFC 6805, in which a
parent PCE has a number of child PCEs. A child PCE may also be a parent PCE has a number of child PCEs. A child PCE may also be a
parent PCE, which has multiple child PCEs. parent PCE, which has multiple child PCEs.
For a parent PCE, it needs to obtain the information about each of For a parent PCE, it needs to obtain the information about each of
its child PCEs. The information about a child PCE comprises the its child PCEs. The information about a child PCE comprises the
address or ID of the PCE and the domain for which the PCE is address or ID of the PCE and the domain for which the PCE is
skipping to change at page 9, line 39 skipping to change at page 9, line 15
7. Acknowledgement 7. Acknowledgement
The authors would like to Jescia Chen, Adrian Farrel for their The authors would like to Jescia Chen, Adrian Farrel for their
valuable comments on this draft. valuable comments on this draft.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the [RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the
Path Computation Element Architecture to the Determination Path Computation Element Architecture to the Determination
of a Sequence of Domains in MPLS and GMPLS", RFC 6805, of a Sequence of Domains in MPLS and GMPLS", RFC 6805,
DOI 10.17487/RFC6805, November 2012, DOI 10.17487/RFC6805, November 2012,
<https://www.rfc-editor.org/info/rfc6805>. <https://www.rfc-editor.org/info/rfc6805>.
[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol (PCEP)", RFC 5440, Element (PCE) Communication Protocol (PCEP)", RFC 5440,
DOI 10.17487/RFC5440, March 2009, DOI 10.17487/RFC5440, March 2009,
<https://www.rfc-editor.org/info/rfc5440>. <https://www.rfc-editor.org/info/rfc5440>.
8.2. Informative References 8.2. Informative References
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/ [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
RFC2328, April 1998, DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>. <https://www.rfc-editor.org/info/rfc2328>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
Authors' Addresses Authors' Addresses
Huaimo Chen Huaimo Chen
Huawei Technologies Futurewei
Boston, MA, Boston, MA
USA USA
EMail: Huaimo.chen@huawei.com EMail: Huaimo.chen@futurewei.com
Mehmet Toy Mehmet Toy
Verizon Verizon
USA USA
EMail: mehmet.toy@verizon.com EMail: mehmet.toy@verizon.com
Xufeng Liu Xufeng Liu
Jabil Volta Networks
McLean, VA McLean, VA
USA USA
EMail: Xufeng_Liu@jabil.com EMail: xufeng.liu.ietf@gmail.com
Lei Liu Lei Liu
Fujitsu Fujitsu
USA USA
EMail: lliu@us.fujitsu.com EMail: liulei.kddi@gmail.com
Zhenqiang Li Zhenqiang Li
China Mobile China Mobile
No.32 Xuanwumenxi Ave., Xicheng District No.32 Xuanwumenxi Ave., Xicheng District
Beijing 100032 Beijing 100032
P.R. China P.R. China
EMail: li_zhenqiang@hotmail.com EMail: li_zhenqiang@hotmail.com
 End of changes. 17 change blocks. 
35 lines changed or deleted 36 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/