| rfc9731v2.txt | rfc9731.txt | |||
|---|---|---|---|---|
| skipping to change at line 12 ¶ | skipping to change at line 12 ¶ | |||
| Internet Engineering Task Force (IETF) Y. Lee, Ed. | Internet Engineering Task Force (IETF) Y. Lee, Ed. | |||
| Request for Comments: 9731 Samsung Electronics | Request for Comments: 9731 Samsung Electronics | |||
| Category: Standards Track D. Dhody, Ed. | Category: Standards Track D. Dhody, Ed. | |||
| ISSN: 2070-1721 Huawei | ISSN: 2070-1721 Huawei | |||
| D. Ceccarelli | D. Ceccarelli | |||
| Cisco | Cisco | |||
| I. Bryskin | I. Bryskin | |||
| Individual | Individual | |||
| B. Yoon | B. Yoon | |||
| ETRI | ETRI | |||
| February 2025 | March 2025 | |||
| A YANG Data Model for Virtual Network (VN) Operations | A YANG Data Model for Virtual Network (VN) Operations | |||
| Abstract | Abstract | |||
| A Virtual Network (VN) is a network provided by a service provider to | A Virtual Network (VN) is a network provided by a service provider to | |||
| a customer for the customer to use in any way it wants as though it | a customer for the customer to use in any way it wants as though it | |||
| were a physical network. This document provides a YANG data model | were a physical network. This document provides a YANG data model | |||
| generally applicable to any mode of VN operations. This includes VN | generally applicable to any mode of VN operations. This includes VN | |||
| operations as per the Abstraction and Control of TE Networks (ACTN) | operations as per the Abstraction and Control of TE Networks (ACTN) | |||
| skipping to change at line 87 ¶ | skipping to change at line 87 ¶ | |||
| 7. Security Considerations | 7. Security Considerations | |||
| 8. IANA Considerations | 8. IANA Considerations | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| 9.2. Informative References | 9.2. Informative References | |||
| Appendix A. Performance Constraints | Appendix A. Performance Constraints | |||
| Appendix B. JSON Example | Appendix B. JSON Example | |||
| B.1. VN JSON | B.1. VN JSON | |||
| B.2. TE Topology JSON | B.2. TE Topology JSON | |||
| Acknowledgments | Acknowledgments | |||
| Contributors' Addresses | Contributors | |||
| Authors' Addresses | Authors' Addresses | |||
| 1. Introduction | 1. Introduction | |||
| Abstraction and Control of TE Networks (ACTN) describes a set of | Abstraction and Control of TE Networks (ACTN) describes a set of | |||
| management and control functions used to operate one or more Traffic | management and control functions used to operate one or more Traffic | |||
| Engineered (TE) networks to construct a Virtual Network (VN). A VN | Engineered (TE) networks to construct a Virtual Network (VN). A VN | |||
| is represented to customers and is built from the abstractions of the | is represented to customers and is built from the abstractions of the | |||
| underlying TE networks [RFC8453]. This document provides a YANG data | underlying TE networks [RFC8453]. This document provides a YANG data | |||
| model [RFC7950] generally applicable to any mode of VN operation. | model [RFC7950] generally applicable to any mode of VN operation. | |||
| skipping to change at line 553 ¶ | skipping to change at line 553 ¶ | |||
| Matrix on one | matrices/tet:connectivity-matrix | | Matrix on one | matrices/tet:connectivity-matrix | | |||
| abstract node and|---------------------------------------->| | abstract node and|---------------------------------------->| | |||
| constraints in | | | constraints in | | | |||
| the conn. matrix)| HTTP 200 | | the conn. matrix)| HTTP 200 | | |||
| |<----------------------------------------| | |<----------------------------------------| | |||
| | | | | | | |||
| | | | | | | |||
| CNC calls RPC to | RPC /vn compute | | CNC calls RPC to | RPC /vn compute | | |||
| compute the VN |---------------------------------------->| | compute the VN |---------------------------------------->| | |||
| as per the | | | as per the | | | |||
| refered TE-Topo | | | referred TE-Topo | | | |||
| | | | | | | |||
| | HTTP 200 (Computed VN) | | | HTTP 200 (Computed VN) | | |||
| |<----------------------------------------| | |<----------------------------------------| | |||
| | | | | | | |||
| Figure 9: VN Compute with Reference to TE Toplogy YANG Data Model | Figure 9: VN Compute with Reference to TE Topology YANG Data Model | |||
| The VN compute RPC allows the optional inclusion of the constraints | The VN compute RPC allows the optional inclusion of the constraints | |||
| and the optimization criteria at the VN as well as at the individual | and the optimization criteria at the VN as well as at the individual | |||
| VN-member level. Thus, the RPC can be used independently to get the | VN-member level. Thus, the RPC can be used independently to get the | |||
| computed VN result without creating an abstract topology first. | computed VN result without creating an abstract topology first. | |||
| +--------+ +--------+ | +--------+ +--------+ | |||
| | CNC | | MDSC | | | CNC | | MDSC | | |||
| +--------+ +--------+ | +--------+ +--------+ | |||
| | | | | | | |||
| skipping to change at line 2509 ¶ | skipping to change at line 2509 ¶ | |||
| Thanks to: | Thanks to: | |||
| * Andy Bierman for the YANGDIR review. | * Andy Bierman for the YANGDIR review. | |||
| * Darren Dukes and Susan Hares for the RTGDIR review. | * Darren Dukes and Susan Hares for the RTGDIR review. | |||
| * Behcet Sarikaya for the GENART review. | * Behcet Sarikaya for the GENART review. | |||
| * Bo Wu for the OPSDIR review. | * Bo Wu for the OPSDIR review. | |||
| * Shivan Sahib for the SECDIR review. | * Shivan Sahib for the SECDIR review. | |||
| * Deb Cooley, Francesca Palombini, Gunter Van de Velde, and Mahesh | * Deb Cooley, Francesca Palombini, Gunter Van de Velde, and Mahesh | |||
| Jethanandani for the IESG review. | Jethanandani for the IESG review. | |||
| Contributors' Addresses | Contributors | |||
| Qin Wu | Qin Wu | |||
| Huawei Technologies | Huawei Technologies | |||
| Email: bill.wu@huawei.com | Email: bill.wu@huawei.com | |||
| Peter Park | Peter Park | |||
| KT | KT | |||
| Email: peter.park@kt.com | Email: peter.park@kt.com | |||
| Haomian Zheng | Haomian Zheng | |||
| End of changes. 5 change blocks. | ||||
| 5 lines changed or deleted | 5 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||