| < draft-zhang-alto-oam-yang-02.txt | draft-ietf-alto-oam-yang-00.txt > | |||
|---|---|---|---|---|
| ALTO WG J. Zhang | ALTO WG J. Zhang | |||
| Internet-Draft Tongji University | Internet-Draft Tongji University | |||
| Intended status: Standards Track D. Dhody | Intended status: Standards Track D. Dhody | |||
| Expires: 8 September 2022 Huawei Technologies | Expires: 14 October 2022 Huawei Technologies | |||
| K. Gao | K. Gao | |||
| Sichuan University | Sichuan University | |||
| R. Schott | R. Schott | |||
| Deutsche Telekom | Deutsche Telekom | |||
| 7 March 2022 | 12 April 2022 | |||
| A Yang Data Model for OAM and Management of ALTO Protocol | A Yang Data Model for OAM and Management of ALTO Protocol | |||
| draft-zhang-alto-oam-yang-02 | draft-ietf-alto-oam-yang-00 | |||
| Abstract | Abstract | |||
| This document defines a YANG data model for Operations, | This document defines a YANG data model for Operations, | |||
| Administration, and Maintenance (OAM) & Management of Application- | Administration, and Maintenance (OAM) & Management of Application- | |||
| Layer Traffic Optimization (ALTO) Protocol. The operator can use the | Layer Traffic Optimization (ALTO) Protocol. The operator can use the | |||
| data model to create and update ALTO information resources, manage | data model to create and update ALTO information resources, manage | |||
| the access control, configure server-to-server communication and | the access control, configure server-to-server communication and | |||
| server discovery, and collect statistical data. | server discovery, and collect statistical data. | |||
| skipping to change at page 2, line 4 ¶ | skipping to change at page 2, line 4 ¶ | |||
| 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 8 September 2022. | This Internet-Draft will expire on 14 October 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2022 IETF Trust and the persons identified as the | Copyright (c) 2022 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 (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 2, line 31 ¶ | skipping to change at page 2, line 31 ¶ | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 | 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 | 3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 | |||
| 4. Design Scope and Requirements . . . . . . . . . . . . . . . . 4 | 4. Design Scope and Requirements . . . . . . . . . . . . . . . . 4 | |||
| 4.1. Scope of Data Model for ALTO O&M . . . . . . . . . . . . 4 | 4.1. Scope of Data Model for ALTO O&M . . . . . . . . . . . . 4 | |||
| 4.2. Basic Requirements . . . . . . . . . . . . . . . . . . . 5 | 4.2. Basic Requirements . . . . . . . . . . . . . . . . . . . 5 | |||
| 4.3. Additional Requirements for Extensibility . . . . . . . . 6 | 4.3. Additional Requirements for Extensibility . . . . . . . . 6 | |||
| 4.4. Overview of ALTO O&M Data Model for Reference ALTO | ||||
| Architecture . . . . . . . . . . . . . . . . . . . . . . 6 | ||||
| 5. Design of ALTO O&M Data Model . . . . . . . . . . . . . . . . 6 | 5. Design of ALTO O&M Data Model . . . . . . . . . . . . . . . . 6 | |||
| 5.1. Overview of ALTO O&M Data Model . . . . . . . . . . . . . 6 | 5.1. Overview of ALTO O&M Data Model . . . . . . . . . . . . . 7 | |||
| 5.2. Meta Information of ALTO Server . . . . . . . . . . . . . 8 | 5.2. Meta Information of ALTO Server . . . . . . . . . . . . . 9 | |||
| 5.3. ALTO Information Resources Configuration Management . . . 8 | 5.3. ALTO Information Resources Configuration Management . . . 9 | |||
| 5.4. Data Sources . . . . . . . . . . . . . . . . . . . . . . 11 | 5.4. Data Sources . . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 5.4.1. Yang DataStore Data Source . . . . . . . . . . . . . 12 | 5.4.1. Yang DataStore Data Source . . . . . . . . . . . . . 13 | |||
| 5.4.2. Prometheus Data Source . . . . . . . . . . . . . . . 12 | 5.4.2. Prometheus Data Source . . . . . . . . . . . . . . . 13 | |||
| 5.5. Model for ALTO Server-to-server Communication . . . . . . 12 | 5.5. Model for ALTO Server-to-server Communication . . . . . . 13 | |||
| 6. Design of ALTO O&M Statistics Data Model . . . . . . . . . . 13 | 6. Design of ALTO O&M Statistics Data Model . . . . . . . . . . 13 | |||
| 7. Extension of ALTO O&M Data Model . . . . . . . . . . . . . . 14 | 6.1. Model for ALTO Logging and Fault Management . . . . . . . 14 | |||
| 8. ALTO OAM YANG Module . . . . . . . . . . . . . . . . . . . . 15 | 6.2. Model for ALTO-specific Performance Monitoring . . . . . 14 | |||
| 8.1. The ietf-alto Module . . . . . . . . . . . . . . . . . . 15 | 7. Extension of ALTO O&M Data Model . . . . . . . . . . . . . . 15 | |||
| 8.2. The ietf-alto-stats Module . . . . . . . . . . . . . . . 27 | 8. ALTO OAM YANG Module . . . . . . . . . . . . . . . . . . . . 16 | |||
| 9. Security Considerations . . . . . . . . . . . . . . . . . . . 30 | 8.1. The ietf-alto Module . . . . . . . . . . . . . . . . . . 16 | |||
| 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 | 8.2. The ietf-alto-stats Module . . . . . . . . . . . . . . . 28 | |||
| 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 | 9. Security Considerations . . . . . . . . . . . . . . . . . . . 31 | |||
| 11.1. Normative References . . . . . . . . . . . . . . . . . . 31 | 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 | |||
| 11.2. Informative References . . . . . . . . . . . . . . . . . 32 | 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 | |||
| 11.1. Normative References . . . . . . . . . . . . . . . . . . 32 | ||||
| 11.2. Informative References . . . . . . . . . . . . . . . . . 33 | ||||
| Appendix A. Example Module for Information Resource Creation | Appendix A. Example Module for Information Resource Creation | |||
| Algorithm . . . . . . . . . . . . . . . . . . . . . . . . 33 | Algorithm . . . . . . . . . . . . . . . . . . . . . . . . 34 | |||
| Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 34 | Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 35 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 | |||
| 1. Introduction | 1. Introduction | |||
| This document defines a YANG data model for the Operations, | This document defines a YANG data model for the Operations, | |||
| Administration, and Maintenance (OAM) & Management of Application- | Administration, and Maintenance (OAM) & Management of Application- | |||
| Layer Traffic Optimization (ALTO) Protocol. The basic purpose of | Layer Traffic Optimization (ALTO) Protocol. The basic purpose of | |||
| this YANG data model is discussed in Section 16 of [RFC7285]. The | this YANG data model is discussed in Section 16 of [RFC7285]. The | |||
| operator can use the data model to create and update ALTO information | operator can use the data model to create and update ALTO information | |||
| resources, manage the access control, configure server-to-server | resources, manage the access control, configure server-to-server | |||
| communication and server discovery, and collect statistical data. | communication and server discovery, and collect statistical data. | |||
| skipping to change at page 6, line 10 ¶ | skipping to change at page 6, line 10 ¶ | |||
| | management. | | | | management. | | | |||
| +--------------------------------------+------------------------+ | +--------------------------------------+------------------------+ | |||
| Table 2: Basic Requirements of Data Model for ALTO O&M. | Table 2: Basic Requirements of Data Model for ALTO O&M. | |||
| 4.3. Additional Requirements for Extensibility | 4.3. Additional Requirements for Extensibility | |||
| R8: As the ALTO protocol is extensible, the data model for ALTO O&M | R8: As the ALTO protocol is extensible, the data model for ALTO O&M | |||
| should allow for augmentation to support potential future extensions. | should allow for augmentation to support potential future extensions. | |||
| 5. Design of ALTO O&M Data Model | 4.4. Overview of ALTO O&M Data Model for Reference ALTO Architecture | |||
| Figure 1 shows a reference architecture for ALTO server | ||||
| implementation and YANG modules that server components implement. | ||||
| The server manager, information resource manager and data source | ||||
| listeners need to implement ietf-alto.yang (see Section 5). The | ||||
| performance monitor and logging and fault manager need to implement | ||||
| ietf-alto-stats.yang (see Section 6). | ||||
| The data broker and algorithm plugins are not in the scope of the | ||||
| data model defined in this document. But user specified YANG modules | ||||
| can be applied to different algorithm plugins by augmenting the data | ||||
| model defined in this document (see Section 7). | ||||
| +----------------------+ +-----------------+ | ||||
| | Performance Monitor: |<-----| Server Manager: | | ||||
| | ietf-alto-stats.yang |<-+ +-| ietf-alto.yang | | ||||
| +----------------------+ | | +-----------------+ | ||||
| report | ||||
| +----------------------+ | | +-------------------+ | ||||
| | Logging and Fault | +---| Information | | ||||
| | Manager: |<---+ | Resource Manager: | | ||||
| | ietf-alto-stats.yang |<-----| ietf-alto.yang | | ||||
| +----------------------+ +-------------------+ | ||||
| ^| | ||||
| || callback | ||||
| |v | ||||
| ............. .............................. | ||||
| / \ ------> . Algorithm Plugin: . | ||||
| . Data Broker . read . example-ietf-alto-alg.yang . | ||||
| ............... .............................. | ||||
| ^ | ||||
| | write | ||||
| +----------------+ Southbound ++=============++ | ||||
| | Data Source | API || || | ||||
| | Listener: | <==========> || Data Source || | ||||
| | ietf-alto.yang | || || | ||||
| +----------------+ ++=============++ | ||||
| Figure 1: A Reference ALTO Server Architecture and YANG Modules | ||||
| 5. Design of ALTO O&M Data Model | ||||
| 5.1. Overview of ALTO O&M Data Model | 5.1. Overview of ALTO O&M Data Model | |||
| The ietf-alto module defined in this document provide all the basic | The ietf-alto module defined in this document provide all the basic | |||
| ALTO O&M data models fitting the requirements listed in Section 4. | ALTO O&M data models fitting the requirements listed in Section 4. | |||
| The container "alto-server" in the ietf-alto module contains all the | The container "alto-server" in the ietf-alto module contains all the | |||
| configured and operational parameters of the adminstrated ALTO server | configured and operational parameters of the adminstrated ALTO server | |||
| instance. | instance. | |||
| NOTE: So far, the ALTO YANG module only focuses on the ALTO server | NOTE: So far, the ALTO YANG module only focuses on the ALTO server | |||
| skipping to change at page 13, line 6 ¶ | skipping to change at page 14, line 4 ¶ | |||
| metrics data which is provided by a Prometheus server. The source- | metrics data which is provided by a Prometheus server. The source- | |||
| uir is used to establish the connection with the Prometheus server. | uir is used to establish the connection with the Prometheus server. | |||
| The query-data is used to speficify the potential query expression in | The query-data is used to speficify the potential query expression in | |||
| PromQL. | PromQL. | |||
| 5.5. Model for ALTO Server-to-server Communication | 5.5. Model for ALTO Server-to-server Communication | |||
| TBD. | TBD. | |||
| 6. Design of ALTO O&M Statistics Data Model | 6. Design of ALTO O&M Statistics Data Model | |||
| 6.1. Model for ALTO Logging and Fault Management | ||||
| As section 16.2.1 and section 16.2.3 of [RFC7285] suggest, the YANG | ||||
| data module defined in this document contains statistics for logging | ||||
| and failure detection. | ||||
| NOTE: The detailed YANG module will appear in the future version. | ||||
| 6.2. Model for ALTO-specific Performance Monitoring | ||||
| As section 16.2.5 of [RFC7285] suggests, the YANG data module defined | As section 16.2.5 of [RFC7285] suggests, the YANG data module defined | |||
| in this document also contains statistics for ALTO-specific | in this document also contains statistics for ALTO-specific | |||
| performance metrics. | performance metrics. | |||
| More specifically, this data model contains the following measurement | More specifically, this data model contains the following measurement | |||
| information suggested by [RFC7971]: | information suggested by [RFC7971]: | |||
| * Measurement of impact | * Measurement of impact | |||
| skipping to change at page 31, line 25 ¶ | skipping to change at page 32, line 28 ¶ | |||
| [RFC Editor: Please replace RFCthis with the published RFC number for | [RFC Editor: Please replace RFCthis with the published RFC number for | |||
| this document.] | this document.] | |||
| 11. References | 11. References | |||
| 11.1. Normative References | 11.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/rfc/rfc2119>. | |||
| [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
| DOI 10.17487/RFC3688, January 2004, | DOI 10.17487/RFC3688, January 2004, | |||
| <https://www.rfc-editor.org/info/rfc3688>. | <https://www.rfc-editor.org/rfc/rfc3688>. | |||
| [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for | [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for | |||
| the Network Configuration Protocol (NETCONF)", RFC 6020, | the Network Configuration Protocol (NETCONF)", RFC 6020, | |||
| DOI 10.17487/RFC6020, October 2010, | DOI 10.17487/RFC6020, October 2010, | |||
| <https://www.rfc-editor.org/info/rfc6020>. | <https://www.rfc-editor.org/rfc/rfc6020>. | |||
| [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", | [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", | |||
| RFC 6991, DOI 10.17487/RFC6991, July 2013, | RFC 6991, DOI 10.17487/RFC6991, July 2013, | |||
| <https://www.rfc-editor.org/info/rfc6991>. | <https://www.rfc-editor.org/rfc/rfc6991>. | |||
| [RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S., | [RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S., | |||
| Previdi, S., Roome, W., Shalunov, S., and R. Woundy, | Previdi, S., Roome, W., Shalunov, S., and R. Woundy, | |||
| "Application-Layer Traffic Optimization (ALTO) Protocol", | "Application-Layer Traffic Optimization (ALTO) Protocol", | |||
| RFC 7285, DOI 10.17487/RFC7285, September 2014, | RFC 7285, DOI 10.17487/RFC7285, September 2014, | |||
| <https://www.rfc-editor.org/info/rfc7285>. | <https://www.rfc-editor.org/rfc/rfc7285>. | |||
| [RFC7286] Kiesel, S., Stiemerling, M., Schwan, N., Scharf, M., and | [RFC7286] Kiesel, S., Stiemerling, M., Schwan, N., Scharf, M., and | |||
| H. Song, "Application-Layer Traffic Optimization (ALTO) | H. Song, "Application-Layer Traffic Optimization (ALTO) | |||
| Server Discovery", RFC 7286, DOI 10.17487/RFC7286, | Server Discovery", RFC 7286, DOI 10.17487/RFC7286, | |||
| November 2014, <https://www.rfc-editor.org/info/rfc7286>. | November 2014, <https://www.rfc-editor.org/rfc/rfc7286>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/rfc/rfc8174>. | |||
| [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. | [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. | |||
| Zhang, "YANG Data Model for Key Chains", RFC 8177, | Zhang, "YANG Data Model for Key Chains", RFC 8177, | |||
| DOI 10.17487/RFC8177, June 2017, | DOI 10.17487/RFC8177, June 2017, | |||
| <https://www.rfc-editor.org/info/rfc8177>. | <https://www.rfc-editor.org/rfc/rfc8177>. | |||
| [RFC8189] Randriamasy, S., Roome, W., and N. Schwan, "Multi-Cost | [RFC8189] Randriamasy, S., Roome, W., and N. Schwan, "Multi-Cost | |||
| Application-Layer Traffic Optimization (ALTO)", RFC 8189, | Application-Layer Traffic Optimization (ALTO)", RFC 8189, | |||
| DOI 10.17487/RFC8189, October 2017, | DOI 10.17487/RFC8189, October 2017, | |||
| <https://www.rfc-editor.org/info/rfc8189>. | <https://www.rfc-editor.org/rfc/rfc8189>. | |||
| [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", | [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", | |||
| BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, | BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, | |||
| <https://www.rfc-editor.org/info/rfc8340>. | <https://www.rfc-editor.org/rfc/rfc8340>. | |||
| [RFC8686] Kiesel, S. and M. Stiemerling, "Application-Layer Traffic | [RFC8686] Kiesel, S. and M. Stiemerling, "Application-Layer Traffic | |||
| Optimization (ALTO) Cross-Domain Server Discovery", | Optimization (ALTO) Cross-Domain Server Discovery", | |||
| RFC 8686, DOI 10.17487/RFC8686, February 2020, | RFC 8686, DOI 10.17487/RFC8686, February 2020, | |||
| <https://www.rfc-editor.org/info/rfc8686>. | <https://www.rfc-editor.org/rfc/rfc8686>. | |||
| [RFC8895] Roome, W. and Y. Yang, "Application-Layer Traffic | [RFC8895] Roome, W. and Y. Yang, "Application-Layer Traffic | |||
| Optimization (ALTO) Incremental Updates Using Server-Sent | Optimization (ALTO) Incremental Updates Using Server-Sent | |||
| Events (SSE)", RFC 8895, DOI 10.17487/RFC8895, November | Events (SSE)", RFC 8895, DOI 10.17487/RFC8895, November | |||
| 2020, <https://www.rfc-editor.org/info/rfc8895>. | 2020, <https://www.rfc-editor.org/rfc/rfc8895>. | |||
| [RFC8896] Randriamasy, S., Yang, R., Wu, Q., Deng, L., and N. | [RFC8896] Randriamasy, S., Yang, R., Wu, Q., Deng, L., and N. | |||
| Schwan, "Application-Layer Traffic Optimization (ALTO) | Schwan, "Application-Layer Traffic Optimization (ALTO) | |||
| Cost Calendar", RFC 8896, DOI 10.17487/RFC8896, November | Cost Calendar", RFC 8896, DOI 10.17487/RFC8896, November | |||
| 2020, <https://www.rfc-editor.org/info/rfc8896>. | 2020, <https://www.rfc-editor.org/rfc/rfc8896>. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [I-D.ietf-alto-cdni-request-routing-alto] | [I-D.ietf-alto-cdni-request-routing-alto] | |||
| Seedorf, J., Yang, Y. R., Ma, K. J., Peterson, J., and J. | Seedorf, J., Yang, Y. R., Ma, K. J., Peterson, J., and J. | |||
| J. Zhang, "Content Delivery Network Interconnection (CDNI) | J. Zhang, "Content Delivery Network Interconnection (CDNI) | |||
| Request Routing: CDNI Footprint and Capabilities | Request Routing: CDNI Footprint and Capabilities | |||
| Advertisement using ALTO", Work in Progress, Internet- | Advertisement using ALTO", Work in Progress, Internet- | |||
| Draft, draft-ietf-alto-cdni-request-routing-alto-22, 16 | Draft, draft-ietf-alto-cdni-request-routing-alto-22, 16 | |||
| February 2022, <https://www.ietf.org/archive/id/draft- | February 2022, <https://datatracker.ietf.org/doc/html/ | |||
| ietf-alto-cdni-request-routing-alto-22.txt>. | draft-ietf-alto-cdni-request-routing-alto-22>. | |||
| [I-D.ietf-alto-path-vector] | [I-D.ietf-alto-path-vector] | |||
| Gao, K., Lee, Y., Randriamasy, S., Yang, Y. R., and J. J. | Gao, K., Lee, Y., Randriamasy, S., Yang, Y. R., and J. J. | |||
| Zhang, "An ALTO Extension: Path Vector", Work in Progress, | Zhang, "An ALTO Extension: Path Vector", Work in Progress, | |||
| Internet-Draft, draft-ietf-alto-path-vector-24, 7 March | Internet-Draft, draft-ietf-alto-path-vector-25, 20 March | |||
| 2022, <https://www.ietf.org/archive/id/draft-ietf-alto- | 2022, <https://datatracker.ietf.org/doc/html/draft-ietf- | |||
| path-vector-24.txt>. | alto-path-vector-25>. | |||
| [I-D.ietf-alto-performance-metrics] | [I-D.ietf-alto-performance-metrics] | |||
| Wu, Q., Yang, Y. R., Lee, Y., Dhody, D., Randriamasy, S., | Wu, Q., Yang, Y. R., Lee, Y., Dhody, D., Randriamasy, S., | |||
| and L. M. C. Murillo, "ALTO Performance Cost Metrics", | and L. M. C. Murillo, "ALTO Performance Cost Metrics", | |||
| Work in Progress, Internet-Draft, draft-ietf-alto- | Work in Progress, Internet-Draft, draft-ietf-alto- | |||
| performance-metrics-26, 2 March 2022, | performance-metrics-28, 21 March 2022, | |||
| <https://www.ietf.org/archive/id/draft-ietf-alto- | <https://datatracker.ietf.org/doc/html/draft-ietf-alto- | |||
| performance-metrics-26.txt>. | performance-metrics-28>. | |||
| [I-D.ietf-alto-unified-props-new] | [I-D.ietf-alto-unified-props-new] | |||
| Roome, W., Randriamasy, S., Yang, Y. R., Zhang, J. J., and | Roome, W., Randriamasy, S., Yang, Y. R., Zhang, J. J., and | |||
| K. Gao, "An ALTO Extension: Entity Property Maps", Work in | K. Gao, "An ALTO Extension: Entity Property Maps", Work in | |||
| Progress, Internet-Draft, draft-ietf-alto-unified-props- | Progress, Internet-Draft, draft-ietf-alto-unified-props- | |||
| new-24, 28 February 2022, | new-24, 28 February 2022, | |||
| <https://www.ietf.org/archive/id/draft-ietf-alto-unified- | <https://datatracker.ietf.org/doc/html/draft-ietf-alto- | |||
| props-new-24.txt>. | unified-props-new-24>. | |||
| [RFC7921] Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | [RFC7921] Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | |||
| Nadeau, "An Architecture for the Interface to the Routing | Nadeau, "An Architecture for the Interface to the Routing | |||
| System", RFC 7921, DOI 10.17487/RFC7921, June 2016, | System", RFC 7921, DOI 10.17487/RFC7921, June 2016, | |||
| <https://www.rfc-editor.org/info/rfc7921>. | <https://www.rfc-editor.org/rfc/rfc7921>. | |||
| [RFC7971] Stiemerling, M., Kiesel, S., Scharf, M., Seidel, H., and | [RFC7971] Stiemerling, M., Kiesel, S., Scharf, M., Seidel, H., and | |||
| S. Previdi, "Application-Layer Traffic Optimization (ALTO) | S. Previdi, "Application-Layer Traffic Optimization (ALTO) | |||
| Deployment Considerations", RFC 7971, | Deployment Considerations", RFC 7971, | |||
| DOI 10.17487/RFC7971, October 2016, | DOI 10.17487/RFC7971, October 2016, | |||
| <https://www.rfc-editor.org/info/rfc7971>. | <https://www.rfc-editor.org/rfc/rfc7971>. | |||
| [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., | [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., | |||
| Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model | Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model | |||
| for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, | for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, | |||
| March 2018, <https://www.rfc-editor.org/info/rfc8346>. | March 2018, <https://www.rfc-editor.org/rfc/rfc8346>. | |||
| Appendix A. Example Module for Information Resource Creation Algorithm | Appendix A. Example Module for Information Resource Creation Algorithm | |||
| The base data model defined by ietf-alto.yang does not include any | The base data model defined by ietf-alto.yang does not include any | |||
| choice cases for information resource creation algorithms. But | choice cases for information resource creation algorithms. But | |||
| developers may augment the ietf-alto.yang data model with definitions | developers may augment the ietf-alto.yang data model with definitions | |||
| for any custom creation algorithms for different information | for any custom creation algorithms for different information | |||
| resources. The following example module demonstrates the parameters | resources. The following example module demonstrates the parameters | |||
| of a network map creation algorithm that translates an IETF layer 3 | of a network map creation algorithm that translates an IETF layer 3 | |||
| unicast topology into a network map. | unicast topology into a network map. | |||
| End of changes. 31 change blocks. | ||||
| 50 lines changed or deleted | 103 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/ | ||||