| rfc9232v2.txt | rfc9232.txt | |||
|---|---|---|---|---|
| skipping to change at line 12 ¶ | skipping to change at line 12 ¶ | |||
| Internet Engineering Task Force (IETF) H. Song | Internet Engineering Task Force (IETF) H. Song | |||
| Request for Comments: 9232 Futurewei | Request for Comments: 9232 Futurewei | |||
| Category: Informational F. Qin | Category: Informational F. Qin | |||
| ISSN: 2070-1721 China Mobile | ISSN: 2070-1721 China Mobile | |||
| P. Martinez-Julia | P. Martinez-Julia | |||
| NICT | NICT | |||
| L. Ciavaglia | L. Ciavaglia | |||
| Rakuten Mobile | Rakuten Mobile | |||
| A. Wang | A. Wang | |||
| China Telecom | China Telecom | |||
| April 2022 | May 2022 | |||
| Network Telemetry Framework | Network Telemetry Framework | |||
| Abstract | Abstract | |||
| Network telemetry is a technology for gaining network insight and | Network telemetry is a technology for gaining network insight and | |||
| facilitating efficient and automated network management. It | facilitating efficient and automated network management. It | |||
| encompasses various techniques for remote data generation, | encompasses various techniques for remote data generation, | |||
| collection, correlation, and consumption. This document describes an | collection, correlation, and consumption. This document describes an | |||
| architectural framework for network telemetry, motivated by | architectural framework for network telemetry, motivated by | |||
| skipping to change at line 894 ¶ | skipping to change at line 894 ¶ | |||
| reasons. | reasons. | |||
| * Conventional OAM-based approaches for control plane KPI | * Conventional OAM-based approaches for control plane KPI | |||
| measurement, which include Ping (L3), Traceroute (L3), Y.1731 | measurement, which include Ping (L3), Traceroute (L3), Y.1731 | |||
| [y1731] (L2), and so on. One common issue behind these methods is | [y1731] (L2), and so on. One common issue behind these methods is | |||
| that they only measure the KPIs instead of reflecting the actual | that they only measure the KPIs instead of reflecting the actual | |||
| running status of these protocols, making them less effective or | running status of these protocols, making them less effective or | |||
| efficient for control plane troubleshooting and network | efficient for control plane troubleshooting and network | |||
| optimization. | optimization. | |||
| * How more research is needed for the BGP monitioring protocol | * How more research is needed for the BGP monitoring protocol (BMP). | |||
| (BMP). BMP is an example of the control plane telemetry; it is | BMP is an example of the control plane telemetry; it is currently | |||
| currently used for monitoring BGP routes and enables rich | used for monitoring BGP routes and enables rich applications, such | |||
| applications, such as BGP peer analysis, Autonomous System (AS) | as BGP peer analysis, Autonomous System (AS) analysis, prefix | |||
| analysis, prefix analysis, and security analysis. However, the | analysis, and security analysis. However, the monitoring of other | |||
| monitoring of other layers, protocols, and the cross-layer, cross- | layers, protocols, and the cross-layer, cross-protocol KPI | |||
| protocol KPI correlations are still in their infancy (e.g., IGP | correlations are still in their infancy (e.g., IGP monitoring is | |||
| monitoring is not as extensive as BMP), which requires further | not as extensive as BMP), which requires further research. | |||
| research. | ||||
| Note that the requirement and solutions for network congestion | Note that the requirement and solutions for network congestion | |||
| avoidance are also applicable to the control plane telemetry. | avoidance are also applicable to the control plane telemetry. | |||
| 3.1.3. Forwarding Plane Telemetry | 3.1.3. Forwarding Plane Telemetry | |||
| An effective forwarding plane telemetry system relies on the data | An effective forwarding plane telemetry system relies on the data | |||
| that the network device can expose. The quality, quantity, and | that the network device can expose. The quality, quantity, and | |||
| timeliness of data must meet some stringent requirements. This | timeliness of data must meet some stringent requirements. This | |||
| raises some challenges for the network data plane devices where the | raises some challenges for the network data plane devices where the | |||
| skipping to change at line 1352 ¶ | skipping to change at line 1351 ¶ | |||
| [IPPM-IOAM-DIRECT-EXPORT] | [IPPM-IOAM-DIRECT-EXPORT] | |||
| Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F., | Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F., | |||
| Bhandari, S., Ed., Sivakolundu, R., and T. Mizrahi, Ed., | Bhandari, S., Ed., Sivakolundu, R., and T. Mizrahi, Ed., | |||
| "In-situ OAM Direct Exporting", Work in Progress, | "In-situ OAM Direct Exporting", Work in Progress, | |||
| Internet-Draft, draft-ietf-ippm-ioam-direct-export-07, 13 | Internet-Draft, draft-ietf-ippm-ioam-direct-export-07, 13 | |||
| October 2021, <https://datatracker.ietf.org/doc/html/ | October 2021, <https://datatracker.ietf.org/doc/html/ | |||
| draft-ietf-ippm-ioam-direct-export-07>. | draft-ietf-ippm-ioam-direct-export-07>. | |||
| [IPPM-POSTCARD-BASED-TELEMETRY] | [IPPM-POSTCARD-BASED-TELEMETRY] | |||
| Song, H., Mirsky, G., Filsfils, C., Abdelsalam, A., Zhou, | Song, H., Mirsky, G., Filsfils, C., Abdelsalam, A., Zhou, | |||
| T., Li, Z., Shin, J., and K. Lee, "In-Situ OAM Marking- | T., Li, Z., Mishra, G., Shin, J., and K. Lee, "In-Situ OAM | |||
| based Direct Export", Work in Progress, Internet-Draft, | Marking-based Direct Export", Work in Progress, Internet- | |||
| draft-song-ippm-postcard-based-telemetry-11, 15 November | Draft, draft-song-ippm-postcard-based-telemetry-12, 12 May | |||
| 2021, <https://datatracker.ietf.org/doc/html/draft-song- | 2022, <https://datatracker.ietf.org/doc/html/draft-song- | |||
| ippm-postcard-based-telemetry-11>. | ippm-postcard-based-telemetry-12>. | |||
| [NETCONF-DISTRIB-NOTIF] | [NETCONF-DISTRIB-NOTIF] | |||
| Zhou, T., Zheng, G., Voit, E., Graf, T., and P. Francois, | Zhou, T., Zheng, G., Voit, E., Graf, T., and P. Francois, | |||
| "Subscription to Distributed Notifications", Work in | "Subscription to Distributed Notifications", Work in | |||
| Progress, Internet-Draft, draft-ietf-netconf-distributed- | Progress, Internet-Draft, draft-ietf-netconf-distributed- | |||
| notif-03, 10 January 2022, | notif-03, 10 January 2022, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-netconf- | <https://datatracker.ietf.org/doc/html/draft-ietf-netconf- | |||
| distributed-notif-03>. | distributed-notif-03>. | |||
| [NETCONF-UDP-NOTIF] | [NETCONF-UDP-NOTIF] | |||
| skipping to change at line 1586 ¶ | skipping to change at line 1585 ¶ | |||
| Framework", RFC 8924, DOI 10.17487/RFC8924, October 2020, | Framework", RFC 8924, DOI 10.17487/RFC8924, October 2020, | |||
| <https://www.rfc-editor.org/info/rfc8924>. | <https://www.rfc-editor.org/info/rfc8924>. | |||
| [RFC9069] Evens, T., Bayraktar, S., Bhardwaj, M., and P. Lucente, | [RFC9069] Evens, T., Bayraktar, S., Bhardwaj, M., and P. Lucente, | |||
| "Support for Local RIB in the BGP Monitoring Protocol | "Support for Local RIB in the BGP Monitoring Protocol | |||
| (BMP)", RFC 9069, DOI 10.17487/RFC9069, February 2022, | (BMP)", RFC 9069, DOI 10.17487/RFC9069, February 2022, | |||
| <https://www.rfc-editor.org/info/rfc9069>. | <https://www.rfc-editor.org/info/rfc9069>. | |||
| [RFC9197] Brockners, F., Ed., Bhandari, S., Ed., and T. Mizrahi, | [RFC9197] Brockners, F., Ed., Bhandari, S., Ed., and T. Mizrahi, | |||
| Ed., "Data Fields for In Situ Operations, Administration, | Ed., "Data Fields for In Situ Operations, Administration, | |||
| and Maintence (IOAM)", RFC 9197, DOI 10.17487/RFC9197, | and Maintenance (IOAM)", RFC 9197, DOI 10.17487/RFC9197, | |||
| April 2022, <https://www.rfc-editor.org/info/rfc9197>. | May 2022, <https://www.rfc-editor.org/info/rfc9197>. | |||
| [W3C.REC-xml-20081126] | [W3C.REC-xml-20081126] | |||
| Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and | Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and | |||
| F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth | F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth | |||
| Edition)", World Wide Web Consortium Recommendation REC- | Edition)", World Wide Web Consortium Recommendation REC- | |||
| xml-20081126, November 2008, | xml-20081126, November 2008, | |||
| <https://www.w3.org/TR/2008/REC-xml-20081126>. | <https://www.w3.org/TR/2008/REC-xml-20081126>. | |||
| [y1731] ITU-T, "Operations, administration and maintenance (OAM) | [y1731] ITU-T, "Operations, administration and maintenance (OAM) | |||
| functions and mechanisms for Ethernet-based networks", | functions and mechanisms for Ethernet-based networks", | |||
| End of changes. 4 change blocks. | ||||
| 17 lines changed or deleted | 16 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/ | ||||