< draft-chen-pce-forward-search-p2mp-path-15.txt   draft-chen-pce-forward-search-p2mp-path-16.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 P2MP TE LSP Inter-Domain Path Computation A Forward-Search P2MP TE LSP Inter-Domain Path Computation
draft-chen-pce-forward-search-p2mp-path-15 draft-chen-pce-forward-search-p2mp-path-16
Abstract Abstract
This document presents a forward search procedure for computing a This document presents a forward search procedure for computing a
path for a Point-to-MultiPoint (P2MP) Traffic Engineering (TE) Label path for a Point-to-MultiPoint (P2MP) Traffic Engineering (TE) Label
Switched Path (LSP) crossing a number of domains through using Switched Path (LSP) crossing a number of domains through using
multiple Path Computation Elements (PCEs). In addition, extensions multiple Path Computation Elements (PCEs). In addition, extensions
to the Path Computation Element Communication Protocol (PCEP) for to the Path Computation Element Communication Protocol (PCEP) for
supporting the forward search procedure are described. supporting the forward search procedure are described.
skipping to change at page 2, line 32 skipping to change at page 2, line 32
7.4. Node Flags Object . . . . . . . . . . . . . . . . . . . . 12 7.4. Node Flags Object . . . . . . . . . . . . . . . . . . . . 12
7.5. Request Message Extension . . . . . . . . . . . . . . . . 12 7.5. Request Message Extension . . . . . . . . . . . . . . . . 12
7.6. Reply Message Extension . . . . . . . . . . . . . . . . . 13 7.6. Reply Message Extension . . . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9.1. Request Parameter Bit Flags . . . . . . . . . . . . . . . 14 9.1. Request Parameter Bit Flags . . . . . . . . . . . . . . . 14
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 14 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
11.1. Normative References . . . . . . . . . . . . . . . . . . 14 11.1. Normative References . . . . . . . . . . . . . . . . . . 14
11.2. Informative References . . . . . . . . . . . . . . . . . 15 11.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
RFC 4105 "Requirements for Inter-Area MPLS TE" lists the requirements RFC 4105 "Requirements for Inter-Area MPLS TE" lists the requirements
for computing a shortest path for a TE LSP crossing multiple IGP for computing a shortest path for a TE LSP crossing multiple IGP
areas; and RFC 4216 "MPLS Inter-Autonomous System (AS) TE areas; and RFC 4216 "MPLS Inter-Autonomous System (AS) TE
Requirements" describes the requirements for computing a shortest Requirements" describes the requirements for computing a shortest
path for a TE LSP crossing multiple ASes. RFC 5671 "Applicability of path for a TE LSP crossing multiple ASes. RFC 5671 "Applicability of
PCE to P2MP MPLS and GMPLS TE" examines the applicability of PCE to PCE to P2MP MPLS and GMPLS TE" examines the applicability of PCE to
path computation for P2MP TE LSPs in MPLS and GMPLS networks. path computation for P2MP TE LSPs in MPLS and GMPLS networks.
skipping to change at page 14, line 33 skipping to change at page 14, line 33
A new RP Object Flag has been defined in this document. IANA is A new RP Object Flag has been defined in this document. IANA is
requested to make the following allocation from the "PCEP RP Object requested to make the following allocation from the "PCEP RP Object
Flag Field" Sub-Registry: Flag Field" Sub-Registry:
Bit Description Reference Bit Description Reference
18 FSPC (F-bit) This I-D 18 FSPC (F-bit) This I-D
19 Transfer Request (T-bit) This I-D 19 Transfer Request (T-bit) This I-D
10. Acknowledgement 10. Acknowledgement
The author would like to thank Julien Meuric, Daniel King, Cyril The author would like to appreciate Dhruv Dhody for his great
contributions and to thank Julien Meuric, Daniel King, Cyril
Margaria, Ramon Casellas, Olivier Dugeon and Oscar Gonzalez de Dios Margaria, Ramon Casellas, Olivier Dugeon and Oscar Gonzalez de Dios
for their valuable comments on this draft. for their valuable comments on this draft.
11. References 11. References
11.1. Normative References 11.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,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
skipping to change at page 15, line 30 skipping to change at page 15, line 30
Element (PCE)-Based Architecture", RFC 4655, Element (PCE)-Based Architecture", RFC 4655,
DOI 10.17487/RFC4655, August 2006, DOI 10.17487/RFC4655, August 2006,
<https://www.rfc-editor.org/info/rfc4655>. <https://www.rfc-editor.org/info/rfc4655>.
[RFC5862] Yasukawa, S. and A. Farrel, "Path Computation Clients [RFC5862] Yasukawa, S. and A. Farrel, "Path Computation Clients
(PCC) - Path Computation Element (PCE) Requirements for (PCC) - Path Computation Element (PCE) Requirements for
Point-to-Multipoint MPLS-TE", RFC 5862, Point-to-Multipoint MPLS-TE", RFC 5862,
DOI 10.17487/RFC5862, June 2010, DOI 10.17487/RFC5862, June 2010,
<https://www.rfc-editor.org/info/rfc5862>. <https://www.rfc-editor.org/info/rfc5862>.
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/