draft-ietf-pce-p2mp-req-04.txt   draft-ietf-pce-p2mp-req-05.txt 
Network Working Group S. Yasukawa Network Working Group S. Yasukawa
Internet Draft NTT Internet Draft NTT
Category: Informational A. Farrel Category: Informational A. Farrel
Created: December 4, 2009 Old Dog Consulting Created: January 29, 2010 Old Dog Consulting
Expires: June 4, 2010 Expires: July 29, 2010
PCC-PCE Communication Requirements for Point to Multipoint PCC-PCE Communication Requirements for Point to Multipoint
Multiprotocol Label Switching Traffic Engineering (MPLS-TE) Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
draft-ietf-pce-p2mp-req-04.txt draft-ietf-pce-p2mp-req-05.txt
Abstract
The Path Computation Element (PCE) provides path computation
functions in support of traffic engineering in Multi-Protocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) networks.
Extensions to the MPLS and GMPLS signaling and routing protocols have
been made in support of point-to-multipoint (P2MP) Traffic Engineered
(TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
already established, and since P2MP TE LSP routes are sometimes
complex to compute, it is likely that PCE will be used for P2MP LSPs.
Generic requirements for a communication protocol between Path
Computation Clients (PCCs) and PCEs are presented in "Path
Computation Element (PCE) Communication Protocol Generic
Requirements". This document complements the generic requirements and
presents a detailed set of PCC-PCE communication protocol
requirements for point-to-multipoint MPLS/GMPLS traffic engineering.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Copyright Notice
The Path Computation Element (PCE) provides path computation
functions in support of traffic engineering in Multi-Protocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) networks.
Extensions to the MPLS and GMPLS signaling and routing protocols have Copyright (c) 2010 IETF Trust and the persons identified as the
been made in support of point-to-multipoint (P2MP) Traffic Engineered document authors. All rights reserved.
(TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
already established, and since P2MP TE LSP routes are sometimes
complex to compute, it is likely that PCE will be used for P2MP LSPs.
Generic requirements for a communication protocol between Path This document is subject to BCP 78 and the IETF Trust's Legal
Computation Clients (PCCs) and PCEs are presented in "Path Provisions Relating to IETF Documents
Computation Element (PCE) Communication Protocol Generic (http://trustee.ietf.org/license-info) in effect on the date of
Requirements". This document complements the generic requirements and publication of this document. Please review these documents
presents a detailed set of PCC-PCE communication protocol carefully, as they describe your rights and restrictions with respect
requirements for point-to-multipoint MPLS/GMPLS traffic engineering. to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Although this document is not a protocol specification, this Although this document is not a protocol specification, this
convention is adopted for clarity of description of requirements. convention is adopted for clarity of description of requirements.
1. Introduction 1. Introduction
skipping to change at page 2, line 26 skipping to change at page 2, line 41
that is capable of computing a network path or route based on a that is capable of computing a network path or route based on a
network graph, and applying computational constraints. The intention network graph, and applying computational constraints. The intention
is that the PCE is used to compute the path of Traffic Engineered is that the PCE is used to compute the path of Traffic Engineered
Label Switched Paths (TE LSPs) within Multiprotocol Label Switching Label Switched Paths (TE LSPs) within Multiprotocol Label Switching
(MPLS) and Generalized MPLS (GMPLS) networks. (MPLS) and Generalized MPLS (GMPLS) networks.
Requirements for point-to-multipoint (P2MP) MPLS TE LSPs are Requirements for point-to-multipoint (P2MP) MPLS TE LSPs are
documented in [RFC4461] and signaling protocol extensions for documented in [RFC4461] and signaling protocol extensions for
setting up P2MP MPLS TE LSPs are defined in [RFC4875]. P2MP MPLS TE setting up P2MP MPLS TE LSPs are defined in [RFC4875]. P2MP MPLS TE
networks are considered in support of various features including networks are considered in support of various features including
layer 3 multicast VPNs [RFC4834]. layer 3 multicast virtual private networks [RFC4834].
Path computation for P2MP TE LSPs presents a significant challenge, Path computation for P2MP TE LSPs presents a significant challenge,
and network optimization of multiple P2MP TE LSPs requires and network optimization of multiple P2MP TE LSPs requires
considerable computational resources. PCE offers a way to offload considerable computational resources. PCE offers a way to offload
such path computations from Label Switching Routers (LSRs). such path computations from Label Switching Routers (LSRs).
The applicability of the PCE-based path computation architecture to The applicability of the PCE-based path computation architecture to
P2MP MPLS TE is described in a companion document [PCE-P2MP-APP]. No P2MP MPLS TE is described in a companion document [RFC5671]. No
further attempt is made to justify the use of PCE for P2MP MPLS TE further attempt is made to justify the use of PCE for P2MP MPLS TE
within this document. within this document.
This document presents a set of PCC-PCE communication protocol This document presents a set of PCC-PCE communication protocol
(PCECP) requirements for P2MP MPLS traffic engineering. It (PCECP) requirements for P2MP MPLS traffic engineering. It
supplements the generic requirements documented in [RFC4657]. supplements the generic requirements documented in [RFC4657].
2. PCC-PCE Communication Requirements for P2MP MPLS Traffic Engineering 2. PCC-PCE Communication Requirements for P2MP MPLS Traffic Engineering
This section sets out additional requirements not covered in This section sets out additional requirements not covered in
skipping to change at page 9, line 31 skipping to change at page 9, line 45
It would be possible to consider applying different authorization It would be possible to consider applying different authorization
policies for P2MP Path Computation Requests compared to other policies for P2MP Path Computation Requests compared to other
requests. requests.
5. IANA Considerations 5. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
6. Acknowledgments 6. Acknowledgments
Thanks to Dean Cheng, Young Lee, Quintin Zhao, Daniel King, and Thanks to Dean Cheng, Young Lee, Quintin Zhao, Daniel King, Fabien
Fabien Verhaeghe for their comments and suggestions on this document. Verhaeghe, and Francis Dupont for their comments and suggestions on
this document.
7. References 7. References
7.1. Normative Reference 7.1. Normative Reference
[RFC2119] Bradner, S., "Key words for use in RFCs to indicate [RFC2119] Bradner, S., "Key words for use in RFCs to indicate
requirements levels", RFC 2119, March 1997. requirements levels", RFC 2119, March 1997.
[RFC4657] Ash, J., and Le Roux, J.L., "Path Computation Element [RFC4657] Ash, J., and Le Roux, J.L., "Path Computation Element
(PCE) Communication Protocol Generic Requirements", (PCE) Communication Protocol Generic Requirements",
RFC 4657, September 2006. RFC 4657, September 2006.
[RFC5394] Bryskin, I., Papadimitriou, D., Berger, L., and Ash, [RFC5394] Bryskin, I., Papadimitriou, D., Berger, L., and Ash,
J., "Policy-Enabled Path Computation Framework", J., "Policy-Enabled Path Computation Framework",
RFC 5394, December 2008. RFC 5394, December 2008.
[PCE-P2MP-APP] S. Yasukawa et al., "Applicability of the Path [RFC5671] Yasukawa, S., and Farrel, A., "Applicability of the
Computation Element to Point-to-Multipoint Traffic Path Computation Element (PCE) to Point-to-Multipoint
Engineering", draft-ietf-pce-p2mp-app, work in (P2MP) MPLS and GMPLS Traffic Engineering (TE)", RFC
progress. 5671, October 2009.
7.2. Informative Reference 7.2. Informative Reference
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for V., and G. Swallow, "RSVP-TE: Extensions to RSVP for
LSP Tunnels", RFC 3209, December 2001. LSP Tunnels", RFC 3209, December 2001.
[RFC4461] S. Yasukawa, Editor "Signaling Requirements for [RFC4461] S. Yasukawa, Editor "Signaling Requirements for
Point-to-Multipoint Traffic Engineered MPLS LSPs", Point-to-Multipoint Traffic Engineered MPLS LSPs",
RFC4461, April 2006. RFC4461, April 2006.
skipping to change at page 11, line 4 skipping to change at page 11, line 22
Communication Protocol (PCEP)", RFC 5541, June 2009. Communication Protocol (PCEP)", RFC 5541, June 2009.
8. Authors' Addresses 8. Authors' Addresses
Seisho Yasukawa Seisho Yasukawa
NTT Corporation NTT Corporation
9-11, Midori-Cho 3-Chome 9-11, Midori-Cho 3-Chome
Musashino-Shi, Tokyo 180-8585, Musashino-Shi, Tokyo 180-8585,
Japan Japan
Email: yasukawa.seisho@lab.ntt.co.jp Email: yasukawa.seisho@lab.ntt.co.jp
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
9. Full Copyright Statement
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
 End of changes. 12 change blocks. 
28 lines changed or deleted 45 lines changed or added

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