draft-ietf-pce-inter-area-as-applicability-04.txt   draft-ietf-pce-inter-area-as-applicability-05.txt 
PCE Working Group D. King PCE Working Group D. King
Internet Draft Old Dog Consulting Internet Draft Old Dog Consulting
Intended status: Informational J. Meuric Intended status: Informational J. Meuric
Expires: December 3, 2014 O. Dugeon Expires: January 29, 2016 O. Dugeon
France Telecom France Telecom
Q. Zhao Q. Zhao
Huawei Technologies Huawei Technologies
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica I+D Telefonica I+D
June 3, 2014 July 28, 2015
Applicability of the Path Computation Element to Inter-Area and Applicability of the Path Computation Element to Inter-Area and
Inter-AS MPLS and GMPLS Traffic Engineering Inter-AS MPLS and GMPLS Traffic Engineering
draft-ietf-pce-inter-area-as-applicability-04 draft-ietf-pce-inter-area-as-applicability-05
Abstract Abstract
The Path Computation Element (PCE) may be used for computing services The Path Computation Element (PCE) may be used for computing services
that traverse multi-area and multi-AS Multiprotocol Label Switching that traverse multi-area and multi-AS Multiprotocol Label Switching
(MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) networks. (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) networks.
This document examines the applicability of the PCE architecture, This document examines the applicability of the PCE architecture,
protocols, and protocol extensions for computing multi-area and protocols, and protocol extensions for computing multi-area and
multi-AS paths in MPLS and GMPLS networks. multi-AS paths in MPLS and GMPLS networks.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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
This Internet-Draft will expire on December, 2014. This Internet-Draft will expire on January 29, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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 (http://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
skipping to change at page 18, line 9 skipping to change at page 18, line 9
9. Point-to-Multipoint 9. Point-to-Multipoint
For the Point-to-Multipoint application scenarios for MPLS-TE LSP, For the Point-to-Multipoint application scenarios for MPLS-TE LSP,
the complexity of domain sequences, domain policies, choice and the complexity of domain sequences, domain policies, choice and
number of domain interconnects is magnified comparing to P2P path number of domain interconnects is magnified comparing to P2P path
computations. Also as the size of the network grows, the number of computations. Also as the size of the network grows, the number of
leaves and branches increase and it in turn puts the scalability of leaves and branches increase and it in turn puts the scalability of
the path computation and optimization into a bigger issue. A the path computation and optimization into a bigger issue. A
solution for the point-to-multipoint path computations may be solution for the point-to-multipoint path computations may be
achieved using the PCEP protocol extension for P2MP [RFC6006] and achieved using the PCEP protocol extension for P2MP [RFC6006] and
using the PCEP P2MP procedures defined in [PCEP-P2MP-INTER-DOMAIN]. using the PCEP P2MP procedures defined in [RFC7334].
10. Optical Domains 10. Optical Domains
The International Telecommunications Union (ITU) defines the ASON The International Telecommunications Union (ITU) defines the ASON
architecture in [G-8080]. [G-7715] defines the routing architecture architecture in [G-8080]. [G-7715] defines the routing architecture
for ASON and introduces a hierarchical architecture. In this for ASON and introduces a hierarchical architecture. In this
architecture, the Routing Areas (RAs) have a hierarchical architecture, the Routing Areas (RAs) have a hierarchical
relationship between different routing levels, which means a parent relationship between different routing levels, which means a parent
(or higher level) RA can contain multiple child RAs. The (or higher level) RA can contain multiple child RAs. The
interconnectivity of the lower RAs is visible to the higher level RA. interconnectivity of the lower RAs is visible to the higher level RA.
skipping to change at page 21, line 7 skipping to change at page 21, line 7
being implemented based on an a previously agreed set of principles. being implemented based on an a previously agreed set of principles.
13.1 Control of Function and Policy 13.1 Control of Function and Policy
As per PCEP [RFC5440] implementation allow the user to configure As per PCEP [RFC5440] implementation allow the user to configure
a number of PCEP session parameters. These are detailed in section a number of PCEP session parameters. These are detailed in section
8.1 of [RFC5440] and will not be repeated here. 8.1 of [RFC5440] and will not be repeated here.
13.2 Information and Data Models 13.2 Information and Data Models
A PCEP MIB module is defined in [PCEP-MIB] that describes managed A PCEP MIB module is defined in [RFC7420] that describes managed
objects for modeling of PCEP communication including: objects for modeling of PCEP communication including:
o PCEP client configuration and status, o PCEP client configuration and status,
o PCEP peer configuration and information, o PCEP peer configuration and information,
o PCEP session configuration and information, o PCEP session configuration and information,
o Notifications to indicate PCEP session changes. o Notifications to indicate PCEP session changes.
skipping to change at page 22, line 15 skipping to change at page 22, line 15
15. IANA Considerations 15. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
16. Acknowledgements 16. Acknowledgements
The author would like to thank Adrian Farrel for his review, and The author would like to thank Adrian Farrel for his review, and
Meral Shirazipour and Francisco Javier Jimenex Chico for their Meral Shirazipour and Francisco Javier Jimenex Chico for their
comments. comments.
This work received funding from the European Union's Seventh
Framework Programme for research, technological development and
demonstration through the PACE project under grant agreement no.
619712.
17. References 17. References
17.1. Normative References 17.1. Normative References
17.2. Informative References 17.2. Informative References
[RFC3060] Moore, B., Ellesson, E., Strassner, J., and A. [RFC3060] Moore, B., Ellesson, E., Strassner, J., and A.
Westerinen, "Policy Core Information Model -- Version 1 Westerinen, "Policy Core Information Model -- Version 1
Specification", RFC 3060, February 2001. Specification", RFC 3060, February 2001.
skipping to change at page 24, line 38 skipping to change at page 24, line 38
Optical Network (ASON). Optical Network (ASON).
[G-7715-2] ITU-T Recommendation G.7715.2 (2007), ASON routing [G-7715-2] ITU-T Recommendation G.7715.2 (2007), ASON routing
architecture and requirements for remote route query. architecture and requirements for remote route query.
[RFC6805] King, D. and A. Farrel, "The Application of the Path [RFC6805] King, D. and A. Farrel, "The Application of the Path
Computation Element Architecture to the Determination Computation Element Architecture to the Determination
of a Sequence of Domains in MPLS & GMPLS", RFC6805, July of a Sequence of Domains in MPLS & GMPLS", RFC6805, July
2010. 2010.
[PCEP-P2MP-INTER-DOMAIN] Zhao, Q., Dhody, D., Ali Z., King, D., [RFC7334] Zhao, Q., Dhody, D., Ali Z., King, D.,
Casellas, R., "PCE-based Computation Casellas, R., "PCE-based Computation
Procedure To Compute Shortest Constrained Procedure To Compute Shortest Constrained
P2MP Inter-domain Traffic Engineering Label Switched P2MP Inter-domain Traffic Engineering Label Switched
Paths", work in progress. Paths", August 2014.
[RFC7420] Stephan, E., Koushik, K., Zhao, Q., King, D., "PCE
Communication Protocol (PCEP) Management Information
Base", Decembe4 2014.
[BGP-LS] Gredler, H., Medved, J., Previdi, S., Farrel, A., and [BGP-LS] Gredler, H., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and TE S. Ray, "North-Bound Distribution of Link-State and TE
Information using BGP", work in progress. Information using BGP", work in progress.
[PCEP-MIB] Stephan, E., Koushik, K., Zhao, Q., King, D., "PCE [DOMAIN-SEQ] Dhody, D., Palle, U., and R. Casellas, "Standard
Communication Protocol (PCEP) Management Information
Base", work in progress.
[DOMAIN-SEQ] Dhody, D., Palle, U., and R. Casellas, "Standard
Representation Of Domain Sequence", work in progress. Representation Of Domain Sequence", work in progress.
18. Author's Addresses 18. Author's Addresses
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK UK
EMail: daniel@olddog.co.uk EMail: daniel@olddog.co.uk
 End of changes. 11 change blocks. 
14 lines changed or deleted 19 lines changed or added

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