draft-ietf-pce-stateful-pce-p2mp-07.txt   draft-ietf-pce-stateful-pce-p2mp-08.txt 
PCE Working Group U. Palle PCE Working Group U. Palle
Internet-Draft D. Dhody Internet-Draft D. Dhody
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: October 26, 2018 Y. Tanaka Expires: April 25, 2019 Y. Tanaka
NTT Communications NTT Communications
V. Beeram V. Beeram
Juniper Networks Juniper Networks
April 24, 2018 October 22, 2018
Path Computation Element (PCE) Protocol Extensions for Stateful PCE Path Computation Element (PCE) Protocol Extensions for Stateful PCE
usage for Point-to-Multipoint Traffic Engineering Label Switched Paths usage for Point-to-Multipoint Traffic Engineering Label Switched Paths
draft-ietf-pce-stateful-pce-p2mp-07 draft-ietf-pce-stateful-pce-p2mp-08
Abstract Abstract
The Path Computation Element (PCE) has been identified as an The Path Computation Element (PCE) has been identified as an
appropriate technology for the determination of the paths of point- appropriate technology for the determination of the paths of point-
to-multipoint (P2MP) TE Label Switched Paths (LSPs). This document to-multipoint (P2MP) TE Label Switched Paths (LSPs). This document
provides extensions required for Path Computation Element provides extensions required for Path Computation Element
Communication Protocol (PCEP) so as to enable the usage of a stateful Communication Protocol (PCEP) so as to enable the usage of a stateful
PCE capability in supporting P2MP TE LSPs. PCE capability in supporting P2MP TE LSPs.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 October 26, 2018. This Internet-Draft will expire on April 25, 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
skipping to change at page 26, line 38 skipping to change at page 26, line 38
Bit Meaning Reference Bit Meaning Reference
13 Active Stateful [This I-D] 13 Active Stateful [This I-D]
PCE with P2MP PCE with P2MP
14 Passive Stateful [This I-D] 14 Passive Stateful [This I-D]
PCE with P2MP PCE with P2MP
15 Stateful PCE [This I-D] 15 Stateful PCE [This I-D]
Initiation with P2MP Initiation with P2MP
11.2. STATEFUL-PCE-CAPABILITY TLV 11.2. STATEFUL-PCE-CAPABILITY TLV
The STATEFUL-PCE-CAPABILITY TLV is defined in [RFC8231] and a The STATEFUL-PCE-CAPABILITY TLV is defined in [RFC8231] and a
registry was created to manage the flags in the TLV. IANA is registry was created to manage the flags in the TLV. IANA is
requested to confirm the early allocation of the following code- requested to confirm the early allocation of the following code-
points in the aforementioned registry. points in the aforementioned registry.
Bit Description Reference Bit Description Reference
25 P2MP-CAPABILITY [This I-D] 25 P2MP-CAPABILITY [This I-D]
24 P2MP-LSP-UPDATE- [This I-D] 24 P2MP-LSP-UPDATE- [This I-D]
CAPABILITY CAPABILITY
23 P2MP-LSP- [This I-D] 23 P2MP-LSP- [This I-D]
skipping to change at page 32, line 37 skipping to change at page 32, line 37
[RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody,
"PCEPS: Usage of TLS to Provide a Secure Transport for the "PCEPS: Usage of TLS to Provide a Secure Transport for the
Path Computation Element Communication Protocol (PCEP)", Path Computation Element Communication Protocol (PCEP)",
RFC 8253, DOI 10.17487/RFC8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-pce-pcep-yang] [I-D.ietf-pce-pcep-yang]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep- Communications Protocol (PCEP)", draft-ietf-pce-pcep-
yang-07 (work in progress), March 2018. yang-09 (work in progress), October 2018.
Appendix A. Contributor Addresses Appendix A. Contributor Addresses
Yuji Kamite Yuji Kamite
NTT Communications Corporation NTT Communications Corporation
Granpark Tower Granpark Tower
3-4-1 Shibaura, Minato-ku 3-4-1 Shibaura, Minato-ku
Tokyo 108-8118 Tokyo 108-8118
Japan Japan
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 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/