| < draft-ietf-teas-sf-aware-topo-model-02.txt | draft-ietf-teas-sf-aware-topo-model-03.txt > | |||
|---|---|---|---|---|
| Network Working Group I. Bryskin | Network Working Group I. Bryskin | |||
| Internet-Draft Huawei Technologies | Internet-Draft Huawei Technologies | |||
| Intended status: Informational X. Liu | Intended status: Informational X. Liu | |||
| Expires: March 25, 2019 Volta Networks | Expires: September 12, 2019 Volta Networks | |||
| Y. Lee | Y. Lee | |||
| J. Guichard | J. Guichard | |||
| Huawei Technologies | Huawei Technologies | |||
| L. Contreras | L. Contreras | |||
| Telefonica | Telefonica | |||
| D. Ceccarelli | D. Ceccarelli | |||
| Ericsson | Ericsson | |||
| J. Tantsura | J. Tantsura | |||
| Nuage Networks | Apstra Networks | |||
| September 21, 2018 | ||||
| March 11, 2019 | ||||
| SF Aware TE Topology YANG Model | SF Aware TE Topology YANG Model | |||
| draft-ietf-teas-sf-aware-topo-model-02 | draft-ietf-teas-sf-aware-topo-model-03 | |||
| Abstract | Abstract | |||
| This document describes a YANG data model for TE network topologies | This document describes a YANG data model for TE network topologies | |||
| that are network service and function aware. | that are network service and function aware. | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted 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. | |||
| skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 March 25, 2019. | This Internet-Draft will expire on September 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 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 | |||
| skipping to change at page 2, line 28 ¶ | skipping to change at page 2, line 28 ¶ | |||
| 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 6 | 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7 | 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 8 | 4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 5. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 15 | 5. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 6. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 17 | 6. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 17 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 | |||
| 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 | |||
| 9.1. Normative References . . . . . . . . . . . . . . . . . . 23 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 23 | |||
| 9.2. Informative References . . . . . . . . . . . . . . . . . 24 | 9.2. Informative References . . . . . . . . . . . . . . . . . 24 | |||
| 9.3. Normative References . . . . . . . . . . . . . . . . . . 25 | ||||
| Appendix A. Companion YANG Model for Non-NMDA Compliant | Appendix A. Companion YANG Model for Non-NMDA Compliant | |||
| Implementations . . . . . . . . . . . . . . . . . . 26 | Implementations . . . . . . . . . . . . . . . . . . 26 | |||
| A.1. SF Aware TE Topology State Module . . . . . . . . . . . . 26 | A.1. SF Aware TE Topology State Module . . . . . . . . . . . . 26 | |||
| Appendix B. Data Examples . . . . . . . . . . . . . . . . . . . 28 | Appendix B. Data Examples . . . . . . . . . . . . . . . . . . . 28 | |||
| B.1. A Topology with Multiple Connected Network Functions . . 28 | B.1. A Topology with Multiple Connected Network Functions . . 28 | |||
| B.2. A Topology with an Encapsulated Network Service . . . . . 33 | B.2. A Topology with an Encapsulated Network Service . . . . . 33 | |||
| Appendix C. Use Cases for SF Aware Topology Models . . . . . . . 37 | Appendix C. Use Cases for SF Aware Topology Models . . . . . . . 37 | |||
| C.1. Exporting SF/NF Information to Network Clients and Other | C.1. Exporting SF/NF Information to Network Clients and Other | |||
| Network SDN Controllers . . . . . . . . . . . . . . . . . 37 | Network SDN Controllers . . . . . . . . . . . . . . . . . 37 | |||
| C.2. Flat End-to-end SFCs Managed on Multi-domain Networks . 38 | C.2. Flat End-to-end SFCs Managed on Multi-domain Networks . 38 | |||
| skipping to change at page 24, line 41 ¶ | skipping to change at page 24, line 41 ¶ | |||
| 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-18 (work in | Topologies", draft-ietf-teas-yang-te-topo-18 (work in | |||
| progress), June 2018. | progress), June 2018. | |||
| [I-D.ietf-netmod-revised-datastores] | [I-D.ietf-netmod-revised-datastores] | |||
| Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., | Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., | |||
| and R. Wilton, "Network Management Datastore | and R. Wilton, "Network Management Datastore | |||
| Architecture", draft-ietf-netmod-revised-datastores-10 | Architecture", draft-ietf-netmod-revised-datastores-10 | |||
| (work in progress), January 2018. | (work in progress), January 2018. | |||
| 9.2. Informative References | ||||
| [RFC7498] Quinn, P., Ed. and T. Nadeau, Ed., "Problem Statement for | ||||
| Service Function Chaining", RFC 7498, | ||||
| DOI 10.17487/RFC7498, April 2015, | ||||
| <https://www.rfc-editor.org/info/rfc7498>. | ||||
| [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function | ||||
| Chaining (SFC) Architecture", RFC 7665, | ||||
| DOI 10.17487/RFC7665, October 2015, | ||||
| <https://www.rfc-editor.org/info/rfc7665>. | ||||
| [I-D.ietf-netmod-yang-tree-diagrams] | ||||
| Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- | ||||
| ietf-netmod-yang-tree-diagrams-06 (work in progress), | ||||
| February 2018. | ||||
| 9.3. Normative References | ||||
| [ETSI-NFV-TERM] | [ETSI-NFV-TERM] | |||
| ETSI, "Network Functions Virtualisation (NFV); Terminology | ETSI, "Network Functions Virtualisation (NFV); Terminology | |||
| for Main Concepts in NFV", ETSI GS NFV 003 V1.2.1, | for Main Concepts in NFV", ETSI GS NFV 003 V1.2.1, | |||
| December 2014. | December 2014. | |||
| [I-D.ietf-teas-yang-te] | [I-D.ietf-teas-yang-te] | |||
| Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and | Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and | |||
| I. Bryskin, "A YANG Data Model for Traffic Engineering | I. Bryskin, "A YANG Data Model for Traffic Engineering | |||
| Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work | Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work | |||
| in progress), July 2018. | in progress), July 2018. | |||
| skipping to change at page 26, line 5 ¶ | skipping to change at page 25, line 36 ¶ | |||
| 3GPP, "Study on management and orchestration of network | 3GPP, "Study on management and orchestration of network | |||
| slicing for next generation network", 3GPP TR 28.801 | slicing for next generation network", 3GPP TR 28.801 | |||
| V2.0.0, September 2017, | V2.0.0, September 2017, | |||
| <http://www.3gpp.org/ftp/Specs/html-info/28801.htm>. | <http://www.3gpp.org/ftp/Specs/html-info/28801.htm>. | |||
| [RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for | [RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for | |||
| Abstraction and Control of TE Networks (ACTN)", RFC 8453, | Abstraction and Control of TE Networks (ACTN)", RFC 8453, | |||
| DOI 10.17487/RFC8453, August 2018, | DOI 10.17487/RFC8453, August 2018, | |||
| <https://www.rfc-editor.org/info/rfc8453>. | <https://www.rfc-editor.org/info/rfc8453>. | |||
| 9.2. Informative References | ||||
| [RFC7498] Quinn, P., Ed. and T. Nadeau, Ed., "Problem Statement for | ||||
| Service Function Chaining", RFC 7498, | ||||
| DOI 10.17487/RFC7498, April 2015, | ||||
| <https://www.rfc-editor.org/info/rfc7498>. | ||||
| [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function | ||||
| Chaining (SFC) Architecture", RFC 7665, | ||||
| DOI 10.17487/RFC7665, October 2015, | ||||
| <https://www.rfc-editor.org/info/rfc7665> | ||||
| [I-D.ietf-netmod-yang-tree-diagrams] | ||||
| Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- | ||||
| ietf-netmod-yang-tree-diagrams-06 (work in progress), | ||||
| February 2018. | ||||
| Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations | Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations | |||
| The YANG module ietf-te-topology-sf defined in this document is | The YANG module ietf-te-topology-sf defined in this document is | |||
| designed to be used in conjunction with implementations that support | designed to be used in conjunction with implementations that support | |||
| the Network Management Datastore Architecture (NMDA) defined in | the Network Management Datastore Architecture (NMDA) defined in | |||
| [I-D.ietf-netmod-revised-datastores]. In order to allow | [I-D.ietf-netmod-revised-datastores]. In order to allow | |||
| implementations to use the model even in cases when NMDA is not | implementations to use the model even in cases when NMDA is not | |||
| supported, the following companion module, ietf-te-topology-sf-state, | supported, the following companion module, ietf-te-topology-sf-state, | |||
| is defined as state model, which mirrors the module ietf-te-topology- | is defined as state model, which mirrors the module ietf-te-topology- | |||
| sf defined earlier in this document. However, all data nodes in the | sf defined earlier in this document. However, all data nodes in the | |||
| skipping to change at page 49, line 10 ¶ | skipping to change at page 49, line 10 ¶ | |||
| Luis Miguel Contreras Murillo | Luis Miguel Contreras Murillo | |||
| Telefonica | Telefonica | |||
| EMail: luismiguel.contrerasmurillo@telefonica.com | EMail: luismiguel.contrerasmurillo@telefonica.com | |||
| Daniele Ceccarelli | Daniele Ceccarelli | |||
| Ericsson | Ericsson | |||
| EMail: daniele.ceccarelli@ericsson.com | EMail: daniele.ceccarelli@ericsson.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Nuage Networks | Apstra Networks | |||
| EMail: jefftant.ietf@gmail.com | EMail: jefftant.ietf@gmail.com | |||
| End of changes. 9 change blocks. | ||||
| 27 lines changed or deleted | 25 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||