< draft-li-teas-hierarchy-ip-controllers-02.txt   draft-li-teas-hierarchy-ip-controllers-03.txt >
TEAS Working Group Z. Li TEAS Working Group Z. Li
Internet-Draft D. Dhody Internet-Draft D. Dhody
Intended status: Informational H. Chen Intended status: Informational Huawei Technologies
Expires: September 6, 2019 Huawei Technologies Expires: January 9, 2020 H. Chen
March 5, 2019 Futurewei Technologies
July 8, 2019
Hierarchy of IP Controllers (HIC) Hierarchy of IP Controllers (HIC)
draft-li-teas-hierarchy-ip-controllers-02 draft-li-teas-hierarchy-ip-controllers-03
Abstract Abstract
This document describes the interactions between various IP This document describes the interactions between various IP
controllers in a hierarchical fashion to provide various IP services. controllers in a hierarchical fashion to provide various IP services.
It describes how the Abstraction and Control of Traffic Engineered It describes how the Abstraction and Control of Traffic Engineered
Networks (ACTN) framework is applied to the Hierarchy of IP Networks (ACTN) framework is applied to the Hierarchy of IP
controllers (HIC) as well as document the interactions with other controllers (HIC) as well as document the interactions with other
protocols like BGP, Path Computation Element Communication Protocol protocols like BGP, Path Computation Element Communication Protocol
(PCEP) to provide end to end dynamic services spanning multiple (PCEP) to provide end to end dynamic services spanning multiple
skipping to change at page 1, line 39 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 September 6, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 2, line 34 skipping to change at page 2, line 35
4.3. L2VPN and EVPN service . . . . . . . . . . . . . . . . . 11 4.3. L2VPN and EVPN service . . . . . . . . . . . . . . . . . 11
5. Possible Features/Extensions . . . . . . . . . . . . . . . . 11 5. Possible Features/Extensions . . . . . . . . . . . . . . . . 11
6. Other Considerations . . . . . . . . . . . . . . . . . . . . 12 6. Other Considerations . . . . . . . . . . . . . . . . . . . . 12
6.1. Control Plane . . . . . . . . . . . . . . . . . . . . . . 12 6.1. Control Plane . . . . . . . . . . . . . . . . . . . . . . 12
6.1.1. PCE / PCEP . . . . . . . . . . . . . . . . . . . . . 12 6.1.1. PCE / PCEP . . . . . . . . . . . . . . . . . . . . . 12
6.1.2. BGP . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.1.2. BGP . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2. Management Plane . . . . . . . . . . . . . . . . . . . . 15 6.2. Management Plane . . . . . . . . . . . . . . . . . . . . 15
6.2.1. YANG Models . . . . . . . . . . . . . . . . . . . . . 15 6.2.1. YANG Models . . . . . . . . . . . . . . . . . . . . . 15
6.2.2. Protocol Considerations . . . . . . . . . . . . . . . 16 6.2.2. Protocol Considerations . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 16 10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 17
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . 17
11.2. Informative References . . . . . . . . . . . . . . . . . 17 11.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
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
running in a centralized system called a controller, can act to running in a centralized system called a controller, can act to
program the devices in the network to behave in specific ways. A program the devices in the network to behave in specific ways. A
required element in an SDN architecture is a component that plans how required element in an SDN architecture is a component that plans how
the network resources will be used and how the devices will be the network resources will be used and how the devices will be
programmed. It is possible to view this component as performing programmed. It is possible to view this component as performing
skipping to change at page 10, line 46 skipping to change at page 10, line 46
A----B----C----ASBR1------ASBR2----D----E----F A----B----C----ASBR1------ASBR2----D----E----F
/ / / / / / / / / / / / / / / /
/ / / / / / / / / / / / / / / /
CE----G----H----I----ASBR3------ASBR4----J----K----L------CE CE----G----H----I----ASBR3------ASBR4----J----K----L------CE
Figure 4: L3VPN Figure 4: L3VPN
Based on the user data in L3SM model, the network configurations need Based on the user data in L3SM model, the network configurations need
to be trickle down to the network device to setup the L3VPN. to be trickle down to the network device to setup the L3VPN.
[I-D.aguado-opsawg-l3sm-l3nm] describes the need for a YANG model for
use between the entity that interacts directly with the customer
(service orchestrator) and the entity in charge of network
orchestration and control which, according to [RFC8309], can be
referred as Service Delivery Model. The resulting model is called
the L3VPN Network Model (L3NM).
Based on the QoS or Policy requirement for the L3VPN service, the Based on the QoS or Policy requirement for the L3VPN service, the
Super Controller may - Super Controller may -
o Set the tunnel selection policy at the PE/ASBR routers so that o Set the tunnel selection policy at the PE/ASBR routers so that
they could select the existing tunnels they could select the existing tunnels
o Select an existing tunnels at the controller level and bind it to o Select an existing tunnels at the controller level and bind it to
the VPN service the VPN service
o Initiate the process of creating a new tunnel based on the QoS o Initiate the process of creating a new tunnel based on the QoS
requirement and bind it the VPN service requirement and bind it the VPN service
o Initiate the process of creating a new tunnel based on the the o Initiate the process of creating a new tunnel based on the the
policy policy
Refer [I-D.lee-teas-te-service-mapping-yang] for more details from Refer [I-D.ietf-teas-te-service-mapping-yang] for more details from
ACTN perspective. ACTN perspective.
Apart from the Management plane interface based on respective YANG Apart from the Management plane interface based on respective YANG
models, the control plane interface PCEP could be used for path models, the control plane interface PCEP could be used for path
computation and setup. computation and setup.
4.3. L2VPN and EVPN service 4.3. L2VPN and EVPN service
There are two fundamentally different kinds of Layer 2 VPN service There are two fundamentally different kinds of Layer 2 VPN service
that a service provider could offer to a customer: Virtual Private that a service provider could offer to a customer: Virtual Private
skipping to change at page 16, line 21 skipping to change at page 16, line 26
developed. developed.
BGP Flowspec: [I-D.wu-idr-flowspec-yang-cfg] defines a YANG data BGP Flowspec: [I-D.wu-idr-flowspec-yang-cfg] defines a YANG data
model for Flow Specification implementations. The configuration model for Flow Specification implementations. The configuration
data is described as flow specification rules that can be data is described as flow specification rules that can be
distributed as BGP NLRI to a network element. The rules can be distributed as BGP NLRI to a network element. The rules can be
used to filter Distributed Denial of Service attacks (DDoS) used to filter Distributed Denial of Service attacks (DDoS)
besides other use cases. Note that a network configuration model besides other use cases. Note that a network configuration model
at the Domain Controller level needs to be developed. at the Domain Controller level needs to be developed.
[I-D.wu-model-driven-management-virtualization] provides a framework
that describes and discusses an architecture for service and network
management automation that takes advantage of YANG modeling
technologies. This is quite apt for HIC and includes interactions
between multiple YANG models as described in
[I-D.wu-model-driven-management-virtualization].
[Editor's Note - the above list should be extended.] [Editor's Note - the above list should be extended.]
6.2.2. Protocol Considerations 6.2.2. Protocol Considerations
The Network Configuration Protocol (NETCONF) [RFC6241] provides The Network Configuration Protocol (NETCONF) [RFC6241] provides
mechanisms to install, manipulate, and delete the configuration of mechanisms to install, manipulate, and delete the configuration of
network devices. The RESTCONF [RFC8040] describes an HTTP-based network devices. The RESTCONF [RFC8040] describes an HTTP-based
protocol that provides a programmatic interface for accessing data protocol that provides a programmatic interface for accessing data
defined in YANG, using the data-store concepts defined in NETCONF. defined in YANG, using the data-store concepts defined in NETCONF.
skipping to change at page 20, line 33 skipping to change at page 20, line 45
[I-D.ietf-teas-actn-yang] [I-D.ietf-teas-actn-yang]
Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O., Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O.,
Shin, J., and S. Belotti, "Applicability of YANG models Shin, J., and S. Belotti, "Applicability of YANG models
for Abstraction and Control of Traffic Engineered for Abstraction and Control of Traffic Engineered
Networks", draft-ietf-teas-actn-yang-03 (work in Networks", draft-ietf-teas-actn-yang-03 (work in
progress), February 2019. progress), February 2019.
[I-D.ietf-pce-applicability-actn] [I-D.ietf-pce-applicability-actn]
Dhody, D., Lee, Y., and D. Ceccarelli, "Applicability of Dhody, D., Lee, Y., and D. Ceccarelli, "Applicability of
Path Computation Element (PCE) for Abstraction and Control the Path Computation Element (PCE) to the Abstraction and
of TE Networks (ACTN)", draft-ietf-pce-applicability- Control of TE Networks (ACTN)", draft-ietf-pce-
actn-08 (work in progress), December 2018. applicability-actn-12 (work in progress), May 2019.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-19 (work in Interfaces", draft-ietf-teas-yang-te-21 (work in
progress), February 2019. progress), April 2019.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-19 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), February 2019. progress), June 2019.
[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., and D. King,
and O. Dios, "Hierarchical Stateful Path Computation "Hierarchical Stateful Path Computation Element (PCE).",
Element (PCE).", draft-ietf-pce-stateful-hpce-06 (work in draft-ietf-pce-stateful-hpce-11 (work in progress), July
progress), October 2018. 2019.
[I-D.ietf-teas-yang-path-computation] [I-D.ietf-teas-yang-path-computation]
Busi, I., Belotti, S., Lopezalvarez, V., Dios, O., Sharma, Busi, I., Belotti, S., Lopezalvarez, V., Dios, O., Sharma,
A., Shi, Y., Vilata, R., Sethuraman, K., Scharf, M., and A., Shi, Y., Vilata, R., Sethuraman, K., Scharf, M., and
D. Ceccarelli, "Yang model for requesting Path D. Ceccarelli, "Yang model for requesting Path
Computation", draft-ietf-teas-yang-path-computation-04 Computation", draft-ietf-teas-yang-path-computation-05
(work in progress), November 2018. (work in progress), March 2019.
[I-D.ietf-mpls-seamless-mpls] [I-D.ietf-mpls-seamless-mpls]
Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz, Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz,
M., and D. Steinberg, "Seamless MPLS Architecture", draft- M., and D. Steinberg, "Seamless MPLS Architecture", draft-
ietf-mpls-seamless-mpls-07 (work in progress), June 2014. ietf-mpls-seamless-mpls-07 (work in progress), June 2014.
[I-D.ietf-bess-evpn-yang] [I-D.ietf-bess-evpn-yang]
Brissette, P., Shah, H., Hussain, I., Tiruveedhula, K., Brissette, P., Shah, H., Hussain, I., Tiruveedhula, K.,
and J. Rabadan, "Yang Data Model for EVPN", draft-ietf- and J. Rabadan, "Yang Data Model for EVPN", draft-ietf-
bess-evpn-yang-06 (work in progress), October 2018. bess-evpn-yang-07 (work in progress), March 2019.
[I-D.ietf-bess-l2vpn-yang] [I-D.ietf-bess-l2vpn-yang]
Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B., Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B.,
and K. Tiruveedhula, "YANG Data Model for MPLS-based and K. Tiruveedhula, "YANG Data Model for MPLS-based
L2VPN", draft-ietf-bess-l2vpn-yang-09 (work in progress), L2VPN", draft-ietf-bess-l2vpn-yang-10 (work in progress),
October 2018. July 2019.
[I-D.ietf-bess-l3vpn-yang] [I-D.ietf-bess-l3vpn-yang]
Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S., Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S.,
Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model
for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-04 (work for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-04 (work
in progress), October 2018. in progress), October 2018.
[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-13 (work in progress), February 2019. dhodylee-pce-pcep-ls-13 (work in progress), February 2019.
[I-D.lee-teas-te-service-mapping-yang] [I-D.ietf-teas-te-service-mapping-yang]
Lee, Y., Dhody, D., Ceccarelli, D., Tantsura, J., Lee, Y., Dhody, D., Ceccarelli, D., Tantsura, J.,
Fioccola, G., and Q. Wu, "Traffic Engineering and Service Fioccola, G., and Q. Wu, "Traffic Engineering and Service
Mapping Yang Model", draft-lee-teas-te-service-mapping- Mapping Yang Model", draft-ietf-teas-te-service-mapping-
yang-13 (work in progress), December 2018. yang-01 (work in progress), March 2019.
[I-D.dugeon-pce-stateful-interdomain] [I-D.dugeon-pce-stateful-interdomain]
Dugeon, O., Meuric, J., Lee, Y., and D. Ceccarelli, "PCEP Dugeon, O., Meuric, J., Lee, Y., and D. Ceccarelli, "PCEP
Extension for Stateful Inter-Domain Tunnels", draft- Extension for Stateful Inter-Domain Tunnels", draft-
dugeon-pce-stateful-interdomain-02 (work in progress), dugeon-pce-stateful-interdomain-02 (work in progress),
March 2019. March 2019.
[I-D.luo-grow-bgp-controller-based-ts] [I-D.luo-grow-bgp-controller-based-ts]
Luo, Y., Ou, L., Huang, X., Zhuang, S., and Z. Li, Luo, Y., Ou, L., Huang, X., Zhuang, S., and Z. Li,
"Traffic Steering Based on BGP Controller", draft-luo- "Traffic Steering Based on BGP Controller", draft-luo-
grow-bgp-controller-based-ts-00 (work in progress), March grow-bgp-controller-based-ts-00 (work in progress), March
2018. 2018.
[I-D.ietf-idr-rtc-hierarchical-rr] [I-D.ietf-idr-rtc-hierarchical-rr]
Dong, J., Chen, M., and R. Raszuk, "Extensions to RT- Dong, J., Chen, M., and R. Raszuk, "Extensions to RT-
Constrain in Hierarchical Route Reflection Scenarios", Constrain in Hierarchical Route Reflection Scenarios",
draft-ietf-idr-rtc-hierarchical-rr-03 (work in progress), draft-ietf-idr-rtc-hierarchical-rr-03 (work in progress),
July 2017. July 2017.
[I-D.ietf-idr-bgp-model] [I-D.ietf-idr-bgp-model]
Patel, K., Jethanandani, M., and S. Hares, "BGP YANG Model Jethanandani, M., Patel, K., and S. Hares, "BGP YANG Model
for Service Provider Networks", draft-ietf-idr-bgp- for Service Provider Networks", draft-ietf-idr-bgp-
model-04 (work in progress), February 2019. model-06 (work in progress), June 2019.
[I-D.wu-idr-flowspec-yang-cfg] [I-D.wu-idr-flowspec-yang-cfg]
Wu, N., Zhuang, S., and A. Choudhary, "A YANG Data Model Wu, N., Zhuang, S., and A. Choudhary, "A YANG Data Model
for Flow Specification", draft-wu-idr-flowspec-yang-cfg-02 for Flow Specification", draft-wu-idr-flowspec-yang-cfg-02
(work in progress), October 2015. (work in progress), October 2015.
[I-D.aguado-opsawg-l3sm-l3nm]
Aguado, A., Dios, O., Lopezalvarez, V.,
daniel.voyer@bell.ca, d., and L. Munoz, "Layer 3 VPN
Network Model", draft-aguado-opsawg-l3sm-l3nm-00 (work in
progress), May 2019.
[I-D.wu-model-driven-management-virtualization]
Wu, Q., Boucadair, M., Jacquenet, C., Contreras, L.,
Lopez, D., Xie, C., Cheng, W., and Y. Lee, "A Framework
for Automating Service and Network Management with YANG",
draft-wu-model-driven-management-virtualization-05 (work
in progress), July 2019.
[ISO10589] [ISO10589]
ISO, "Intermediate system to Intermediate system routing ISO, "Intermediate system to Intermediate system routing
information exchange protocol for use in conjunction with information exchange protocol for use in conjunction with
the Protocol for providing the Connectionless-mode Network the Protocol for providing the Connectionless-mode Network
Service (ISO 8473)", ISO/IEC 10589:2002, 1992. Service (ISO 8473)", ISO/IEC 10589:2002, 1992.
Authors' Addresses Authors' Addresses
Zhenbin Li Zhenbin Li
Huawei Technologies Huawei Technologies
skipping to change at page 23, line 4 skipping to change at page 23, line 27
Authors' Addresses Authors' Addresses
Zhenbin Li Zhenbin Li
Huawei Technologies Huawei Technologies
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
EMail: lizhenbin@huawei.com EMail: lizhenbin@huawei.com
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
Huaimo Chen Huaimo Chen
Huawei Technologies Futurewei Technologies
Boston, MA Boston, MA
USA USA
EMail: huaimo.chen@huawei.com EMail: huaimo.chen@futurewei.com
 End of changes. 23 change blocks. 
32 lines changed or deleted 61 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/