draft-ietf-pce-applicability-actn-02.txt   draft-ietf-pce-applicability-actn-03.txt 
PCE Working Group D. Dhody PCE Working Group D. Dhody
Internet-Draft Y. Lee Internet-Draft Y. Lee
Intended status: Informational Huawei Technologies Intended status: Informational Huawei Technologies
Expires: May 1, 2018 D. Ceccarelli Expires: September 2, 2018 D. Ceccarelli
Ericsson Ericsson
October 28, 2017 March 1, 2018
Applicability of Path Computation Element (PCE) for Abstraction and Applicability of Path Computation Element (PCE) for Abstraction and
Control of TE Networks (ACTN) Control of TE Networks (ACTN)
draft-ietf-pce-applicability-actn-02 draft-ietf-pce-applicability-actn-03
Abstract Abstract
Abstraction and Control of TE Networks (ACTN) refers to the set of Abstraction and Control of TE Networks (ACTN) refers to the set of
virtual network operations needed to orchestrate, control and manage virtual network operations needed to orchestrate, control and manage
large-scale multi-domain TE networks so as to facilitate network large-scale multi-domain TE networks so as to facilitate network
programmability, automation, efficient resource sharing, and end-to- programmability, automation, efficient resource sharing, and end-to-
end virtual service aware connectivity and network function end virtual service aware connectivity and network function
virtualization services. virtualization services.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 May 1, 2018. This Internet-Draft will expire on September 2, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
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 3, line 27 skipping to change at page 3, line 27
[RFC8051] describes general considerations for a stateful PCE [RFC8051] describes general considerations for a stateful PCE
deployment and examines its applicability and benefits, as well as deployment and examines its applicability and benefits, as well as
its challenges and limitations through a number of use cases. its challenges and limitations through a number of use cases.
[RFC8231] describes a set of extensions to PCEP to provide stateful [RFC8231] describes a set of extensions to PCEP to provide stateful
control. A stateful PCE has access to not only the information control. A stateful PCE has access to not only the information
carried by the network's Interior Gateway Protocol (IGP), but also carried by the network's Interior Gateway Protocol (IGP), but also
the set of active paths and their reserved resources for its the set of active paths and their reserved resources for its
computations. The additional state allows the PCE to compute computations. The additional state allows the PCE to compute
constrained paths while considering individual LSPs and their constrained paths while considering individual LSPs and their
interactions. [I-D.ietf-pce-pce-initiated-lsp] describes the setup, interactions. [RFC8281] describes the setup, maintenance and
maintenance and teardown of PCE-initiated LSPs under the stateful PCE teardown of PCE-initiated LSPs under the stateful PCE model.
model.
[RFC8231] also describes the active stateful PCE. The active PCE [RFC8231] also describes the active stateful PCE. The active PCE
functionality allows a PCE to reroute an existing LSP or make changes functionality allows a PCE to reroute an existing LSP or make changes
to the attributes of an existing LSP, or a PCC to delegate control of to the attributes of an existing LSP, or a PCC to delegate control of
specific LSPs to a new PCE. specific LSPs to a new PCE.
1.1.1. Role of PCE in SDN 1.1.1. Role of PCE in SDN
Software-Defined Networking (SDN) refers to a separation between the Software-Defined Networking (SDN) refers to a separation between the
control elements and the forwarding components so that software control elements and the forwarding components so that software
skipping to change at page 8, line 25 skipping to change at page 8, line 25
2.3. Customer mapping function 2.3. Customer mapping function
In ACTN, there is a need to map customer virtual network (VN) In ACTN, there is a need to map customer virtual network (VN)
requirements into network provisioning request to the PNC. That is, requirements into network provisioning request to the PNC. That is,
the customer requests/commands are mapped into network provisioning the customer requests/commands are mapped into network provisioning
requests that can be sent to the PNC. Specifically, it provides requests that can be sent to the PNC. Specifically, it provides
mapping and translation of a customer's service request into a set of mapping and translation of a customer's service request into a set of
parameters that are specific to a network type and technology such parameters that are specific to a network type and technology such
that network configuration process is made possible. that network configuration process is made possible.
[I-D.ietf-pce-pce-initiated-lsp] describes the setup, maintenance and [RFC8281] describes the setup, maintenance and teardown of PCE-
teardown of PCE-initiated LSPs under the stateful PCE model, without initiated LSPs under the stateful PCE model, without the need for
the need for local configuration on the PCC, thus allowing for a local configuration on the PCC, thus allowing for a dynamic network
dynamic network that is centrally controlled and deployed. To that is centrally controlled and deployed. To instantiate or delete
instantiate or delete an LSP, the PCE sends the Path Computation LSP an LSP, the PCE sends the Path Computation LSP Initiate Request
Initiate Request (PCInitiate) message to the PCC. As described in (PCInitiate) message to the PCC. As described in
[I-D.ietf-pce-stateful-hpce], for inter-domain LSP in Hierarchical [I-D.ietf-pce-stateful-hpce], for inter-domain LSP in Hierarchical
PCE architecture, the initiation operations can be carried out at the PCE architecture, the initiation operations can be carried out at the
parent PCE. In which case after parent PCE finishes the E2E path parent PCE. In which case after parent PCE finishes the E2E path
computation, it can send the PCInitiate message to the child PCE, the computation, it can send the PCInitiate message to the child PCE, the
child PCE further propagates the initiate request to the LSR. The child PCE further propagates the initiate request to the LSR. The
customer request is received by the MDSC (parent PCE) and based on customer request is received by the MDSC (parent PCE) and based on
the business logic, global abstracted topology, network conditions the business logic, global abstracted topology, network conditions
and local policy, the MDSC (parent PCE) translates this into per and local policy, the MDSC (parent PCE) translates this into per
domain LSP initiation request that a PNC (child PCE) can understand domain LSP initiation request that a PNC (child PCE) can understand
and act on. This can be done via the PCInitiate message. and act on. This can be done via the PCInitiate message.
skipping to change at page 12, line 6 skipping to change at page 12, line 6
* A-B: (A-B13,B13-B31,B31-B) * A-B: (A-B13,B13-B31,B31-B)
* A-C: (A-B13,B13-B31,B34-B43,B43-C) * A-C: (A-B13,B13-B31,B34-B43,B43-C)
* Per Domain Path Instantiation: Based on the above path * Per Domain Path Instantiation: Based on the above path
computation, MDSC can issue the path instantiation request to computation, MDSC can issue the path instantiation request to
each PNC via PCInitiate message (see each PNC via PCInitiate message (see
[I-D.ietf-pce-stateful-hpce] and [I-D.ietf-pce-stateful-hpce] and
[I-D.leedhody-pce-vn-association]). A suitable stitching [I-D.leedhody-pce-vn-association]). A suitable stitching
mechanism would be use to stitch these per domain LSPs. One mechanism would be used to stitch these per domain LSPs. One
such mechanism is described in such mechanism is described in
[I-D.lee-pce-lsp-stitching-hpce], where PCEP is extended to [I-D.lee-pce-lsp-stitching-hpce], where PCEP is extended to
support stitching in stateful H-PCE context. support stitching in stateful H-PCE context.
* Per Domain Path Report: Each PNC should report the status of * Per Domain Path Report: Each PNC should report the status of
the per-domain LSP to the MDSC via PCRpt message, as per the the per-domain LSP to the MDSC via PCRpt message, as per the
Hierarchy of stateful PCE ([I-D.ietf-pce-stateful-hpce]). The Hierarchy of stateful PCE ([I-D.ietf-pce-stateful-hpce]). The
status of the end to end LSP (A-B and A-C) is made up when all status of the end to end LSP (A-B and A-C) is made up when all
the per domain LSP are reported up by the PNCs. the per domain LSP are reported up by the PNCs.
skipping to change at page 13, line 35 skipping to change at page 13, line 35
7. Security Considerations 7. Security Considerations
The ACTN framework described in [I-D.ietf-teas-actn-framework] The ACTN framework described in [I-D.ietf-teas-actn-framework]
defines key components and interfaces for managed traffic engineered defines key components and interfaces for managed traffic engineered
networks. It also list various security considerations such as networks. It also list various security considerations such as
request and control of resources, confidentially of the information, request and control of resources, confidentially of the information,
and availability of function which should be taken into and availability of function which should be taken into
consideration. consideration.
When PCEP is used on the MPI/MMI, this interface needs to be secured, When PCEP is used on the MPI, this interface needs to be secured, use
use of [RFC8253] is RECOMENDED. Each PCEP extension listed in this of [RFC8253] is RECOMENDED. Each PCEP extension listed in this
document, presents its individual security considerations, which document, presents its individual security considerations, which
continue to apply. continue to apply.
8. Acknowledgments 8. Acknowledgments
The authors would like to thank Jonathan Hardwick for the inspiration The authors would like to thank Jonathan Hardwick for the inspiration
behind this document. Further thanks to Avantika for her comments behind this document. Further thanks to Avantika for her comments
with suggested text. with suggested text.
9. References 9. References
skipping to change at page 16, line 5 skipping to change at page 16, line 5
Extensions for Stateful PCE", RFC 8231, Extensions for Stateful PCE", RFC 8231,
DOI 10.17487/RFC8231, September 2017, DOI 10.17487/RFC8231, September 2017,
<https://www.rfc-editor.org/info/rfc8231>. <https://www.rfc-editor.org/info/rfc8231>.
[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-pce-initiated-lsp] [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP Computation Element Communication Protocol (PCEP)
Extensions for PCE-initiated LSP Setup in a Stateful PCE Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", draft-ietf-pce-pce-initiated-lsp-11 (work in Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
progress), October 2017. <https://www.rfc-editor.org/info/rfc8281>.
[I-D.ietf-pce-stateful-hpce] [I-D.ietf-pce-stateful-hpce]
Dhody, D., Lee, Y., Ceccarelli, D., Shin, J., King, D., Dhody, D., Lee, Y., Ceccarelli, D., Shin, J., King, D.,
and O. Dios, "Hierarchical Stateful Path Computation and O. Dios, "Hierarchical Stateful Path Computation
Element (PCE).", draft-ietf-pce-stateful-hpce-01 (work in Element (PCE).", draft-ietf-pce-stateful-hpce-02 (work in
progress), June 2017. progress), October 2017.
[I-D.ietf-teas-pce-central-control] [I-D.ietf-teas-pce-central-control]
Farrel, A., Zhao, Q., Li, Z., and C. Zhou, "An Farrel, A., Zhao, Q., Li, Z., and C. Zhou, "An
Architecture for Use of PCE and PCEP in a Network with Architecture for Use of PCE and PCEP in a Network with
Central Control", draft-ietf-teas-pce-central-control-05 Central Control", draft-ietf-teas-pce-central-control-05
(work in progress), September 2017. (work in progress), September 2017.
[I-D.ietf-teas-actn-requirements] [I-D.ietf-teas-actn-requirements]
Lee, Y., Dhody, D., Belotti, S., Pithewan, K., Ceccarelli, Lee, Y., Ceccarelli, D., Miyasaka, T., Shin, J., and K.
D., Miyasaka, T., Shin, J., and K. Lee, "Requirements for Lee, "Requirements for Abstraction and Control of TE
Abstraction and Control of TE Networks", draft-ietf-teas- Networks", draft-ietf-teas-actn-requirements-08 (work in
actn-requirements-07 (work in progress), October 2017. progress), January 2018.
[I-D.ietf-teas-actn-framework] [I-D.ietf-teas-actn-framework]
Ceccarelli, D. and Y. Lee, "Framework for Abstraction and Ceccarelli, D. and Y. Lee, "Framework for Abstraction and
Control of Traffic Engineered Networks", draft-ietf-teas- Control of Traffic Engineered Networks", draft-ietf-teas-
actn-framework-11 (work in progress), October 2017. actn-framework-11 (work in progress), October 2017.
[I-D.ietf-teas-actn-info-model] [I-D.ietf-teas-actn-info-model]
Lee, Y., Belotti, S., Dhody, D., Ceccarelli, D., and B. Lee, Y., Belotti, S., Dhody, D., Ceccarelli, D., and B.
Yoon, "Information Model for Abstraction and Control of TE Yoon, "Information Model for Abstraction and Control of TE
Networks (ACTN)", draft-ietf-teas-actn-info-model-04 (work Networks (ACTN)", draft-ietf-teas-actn-info-model-07 (work
in progress), October 2017. in progress), February 2018.
[I-D.ietf-pce-inter-area-as-applicability] [I-D.ietf-pce-inter-area-as-applicability]
King, D., Meuric, J., Dugeon, O., Zhao, Q., Dhody, D., and King, D., Meuric, J., Dugeon, O., Zhao, Q., Dhody, D., and
O. Dios, "Applicability of the Path Computation Element to O. Dios, "Applicability of the Path Computation Element to
Inter-Area and Inter-AS MPLS and GMPLS Traffic Inter-Area and Inter-AS MPLS and GMPLS Traffic
Engineering", draft-ietf-pce-inter-area-as- Engineering", draft-ietf-pce-inter-area-as-
applicability-06 (work in progress), July 2016. applicability-06 (work in progress), July 2016.
[I-D.dhodylee-pce-pcep-ls] [I-D.dhodylee-pce-pcep-ls]
Dhody, D., Lee, Y., and D. Ceccarelli, "PCEP Extension for Dhody, D., Lee, Y., and D. Ceccarelli, "PCEP Extension for
Distribution of Link-State and TE Information.", draft- Distribution of Link-State and TE Information.", draft-
dhodylee-pce-pcep-ls-08 (work in progress), June 2017. dhodylee-pce-pcep-ls-09 (work in progress), January 2018.
[I-D.leedhody-pce-vn-association] [I-D.leedhody-pce-vn-association]
Lee, Y., Dhody, D., Zhang, X., and D. Ceccarelli, "PCEP Lee, Y., Dhody, D., Zhang, X., and D. Ceccarelli, "PCEP
Extensions for Establishing Relationships Between Sets of Extensions for Establishing Relationships Between Sets of
LSPs and Virtual Networks", draft-leedhody-pce-vn- LSPs and Virtual Networks", draft-leedhody-pce-vn-
association-03 (work in progress), September 2017. association-04 (work in progress), February 2018.
[I-D.litkowski-pce-state-sync] [I-D.litkowski-pce-state-sync]
Litkowski, S., Sivabalan, S., and D. Dhody, "Inter Litkowski, S., Sivabalan, S., and D. Dhody, "Inter
Stateful Path Computation Element communication Stateful Path Computation Element communication
procedures", draft-litkowski-pce-state-sync-02 (work in procedures", draft-litkowski-pce-state-sync-02 (work in
progress), August 2017. progress), August 2017.
[I-D.ietf-pce-association-policy] [I-D.ietf-pce-association-policy]
Dhody, D., Sivabalan, S., Litkowski, S., Tantsura, J., and Dhody, D., Sivabalan, S., Litkowski, S., Tantsura, J., and
J. Hardwick, "Path Computation Element communication J. Hardwick, "Path Computation Element communication
Protocol extension for associating Policies and LSPs", Protocol extension for associating Policies and LSPs",
draft-ietf-pce-association-policy-01 (work in progress), draft-ietf-pce-association-policy-02 (work in progress),
June 2017. February 2018.
[I-D.lee-teas-actn-abstraction] [I-D.lee-teas-actn-abstraction]
Lee, Y., Dhody, D., Ceccarelli, D., and O. Dios, Lee, Y., Dhody, D., Ceccarelli, D., and O. Dios,
"Abstraction and Control of TE Networks (ACTN) Abstraction "Abstraction and Control of TE Networks (ACTN) Abstraction
Methods", draft-lee-teas-actn-abstraction-02 (work in Methods", draft-lee-teas-actn-abstraction-02 (work in
progress), June 2017. progress), June 2017.
[I-D.lee-pce-lsp-stitching-hpce] [I-D.lee-pce-lsp-stitching-hpce]
Lee, Y., Dhody, D., and D. Ceccarelli, "PCEP Extensions Lee, Y., Dhody, D., and D. Ceccarelli, "PCEP Extensions
for Stitching LSPs in Hierarchical Stateful PCE Model", for Stitching LSPs in Hierarchical Stateful PCE Model",
draft-lee-pce-lsp-stitching-hpce-00 (work in progress), draft-lee-pce-lsp-stitching-hpce-01 (work in progress),
June 2017. December 2017.
Authors' Addresses Authors' Addresses
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066 Bangalore, Karnataka 560066
India India
EMail: dhruv.ietf@gmail.com EMail: dhruv.ietf@gmail.com
 End of changes. 17 change blocks. 
36 lines changed or deleted 35 lines changed or added

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