< draft-chen-pce-forward-search-p2p-path-computation-16.txt   draft-chen-pce-forward-search-p2p-path-computation-17.txt >
PCE Working Group H. Chen PCE Working Group H. Chen
Internet-Draft Futurewei Internet-Draft Futurewei
Intended status: Standards Track D. Dhody Intended status: Standards Track July 7, 2019
Expires: January 8, 2020 Huawei Technologies Expires: January 8, 2020
July 7, 2019
A Forward-Search P2P TE LSP Inter-Domain Path Computation A Forward-Search P2P TE LSP Inter-Domain Path Computation
draft-chen-pce-forward-search-p2p-path-computation-16 draft-chen-pce-forward-search-p2p-path-computation-17
Abstract Abstract
This document presents a forward search procedure for computing paths This document presents a forward search procedure for computing paths
for Point-to-Point (P2P) Traffic Engineering (TE) Label Switched for Point-to-Point (P2P) Traffic Engineering (TE) Label Switched
Paths (LSPs) crossing a number of domains using multiple Path Paths (LSPs) crossing a number of domains using multiple Path
Computation Elements (PCEs). In addition, extensions to the Path Computation Elements (PCEs). In addition, extensions to the Path
Computation Element Communication Protocol (PCEP) for supporting the Computation Element Communication Protocol (PCEP) for supporting the
forward search procedure are described. forward search procedure are described.
skipping to change at page 2, line 47 skipping to change at page 2, line 47
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
11.1. Request Parameter Bit Flags . . . . . . . . . . . . . . 16 11.1. Request Parameter Bit Flags . . . . . . . . . . . . . . 16
11.2. New PCEP Object . . . . . . . . . . . . . . . . . . . . 16 11.2. New PCEP Object . . . . . . . . . . . . . . . . . . . . 16
11.2.1. NODE-FLAGS Object . . . . . . . . . . . . . . . . . 16 11.2.1. NODE-FLAGS Object . . . . . . . . . . . . . . . . . 16
11.3. New PCEP TLV . . . . . . . . . . . . . . . . . . . . . . 17 11.3. New PCEP TLV . . . . . . . . . . . . . . . . . . . . . . 17
11.3.1. DOMAIN-ID TLV . . . . . . . . . . . . . . . . . . . 17 11.3.1. DOMAIN-ID TLV . . . . . . . . . . . . . . . . . . . 17
12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17 12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
13.1. Normative References . . . . . . . . . . . . . . . . . . 18 13.1. Normative References . . . . . . . . . . . . . . . . . . 18
13.2. Informative References . . . . . . . . . . . . . . . . . 18 13.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
It would be useful to extend MPLS TE capabilities across multiple It would be useful to extend MPLS TE capabilities across multiple
domains (i.e., IGP areas or Autonomous Systems) to support inter- domains (i.e., IGP areas or Autonomous Systems) to support inter-
domain resources optimization, to provide strict QoS guarantees domain resources optimization, to provide strict QoS guarantees
between two edge routers located within distinct domains. between two edge routers located within distinct domains.
[RFC4105] "Requirements for Inter-Area MPLS TE" lists the [RFC4105] "Requirements for Inter-Area MPLS TE" lists the
requirements for computing a shortest path for a TE LSP crossing requirements for computing a shortest path for a TE LSP crossing
skipping to change at page 17, line 48 skipping to change at page 17, line 48
Each bit should be tracked with the following qualities: Each bit should be tracked with the following qualities:
o Bit number (counting from bit 0 as the most significant bit) o Bit number (counting from bit 0 as the most significant bit)
o Name flag o Name flag
o Reference o Reference
12. Acknowledgement 12. Acknowledgement
The authors would like to thank Julien Meuric, Daniel King, Ramon The authors would like to appreciate Dhruv Dhody for his great
contributions and to thank Julien Meuric, Daniel King, Ramon
Casellas, Cyril Margaria,Olivier Dugeon, Oscar Gonzalez de Dios, Casellas, Cyril Margaria,Olivier Dugeon, Oscar Gonzalez de Dios,
Udayasree Palle, Reeja Paul and Sandeep Kumar Boina for their Udayasree Palle, Reeja Paul and Sandeep Kumar Boina for their
valuable comments on this draft. valuable comments on this draft.
13. References 13. References
13.1. Normative References 13.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, Requirement Levels", BCP 14, RFC 2119,
skipping to change at page 19, line 12 skipping to change at page 19, line 12
Paths", RFC 6006, DOI 10.17487/RFC6006, September 2010, Paths", RFC 6006, DOI 10.17487/RFC6006, September 2010,
<https://www.rfc-editor.org/info/rfc6006>. <https://www.rfc-editor.org/info/rfc6006>.
[PCE-HIERARCHY-EXT] [PCE-HIERARCHY-EXT]
Zhang, F., Zhao, Q., King, O., Casellas, R., and D. King, Zhang, F., Zhao, Q., King, O., Casellas, R., and D. King,
"Extensions to Path Computation Element Communication "Extensions to Path Computation Element Communication
Protocol (PCEP) for Hierarchical Path Computation Elements Protocol (PCEP) for Hierarchical Path Computation Elements
(PCE) (draft-zhang-pce-hierarchy-extensions-02)", August (PCE) (draft-zhang-pce-hierarchy-extensions-02)", August
2012. 2012.
Authors' Addresses Author's Address
Huaimo Chen Huaimo Chen
Futurewei Futurewei
Boston, MA Boston, MA
USA USA
EMail: Huaimo.chen@futurewei.com EMail: Huaimo.chen@futurewei.com
Dhruv Dhody
Huawei Technologies
Leela Palace
Bangalore, Karnataka 560008
INDIA
EMail: dhruv.dhody@huawei.com
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 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/