| < draft-mirsky-ippm-hybrid-two-step-11.txt | draft-mirsky-ippm-hybrid-two-step-12.txt > | |||
|---|---|---|---|---|
| IPPM Working Group G. Mirsky | IPPM Working Group G. Mirsky | |||
| Internet-Draft ZTE Corp. | Internet-Draft Ericsson | |||
| Intended status: Standards Track W. Lingqiang | Intended status: Standards Track W. Lingqiang | |||
| Expires: 9 January 2022 G. Zhui | Expires: 30 July 2022 G. Zhui | |||
| ZTE Corporation | ZTE Corporation | |||
| H. Song | H. Song | |||
| Futurewei Technologies | Futurewei Technologies | |||
| 8 July 2021 | 26 January 2022 | |||
| Hybrid Two-Step Performance Measurement Method | Hybrid Two-Step Performance Measurement Method | |||
| draft-mirsky-ippm-hybrid-two-step-11 | draft-mirsky-ippm-hybrid-two-step-12 | |||
| Abstract | Abstract | |||
| Development of, and advancements in, automation of network operations | Development of, and advancements in, automation of network operations | |||
| brought new requirements for measurement methodology. Among them is | brought new requirements for measurement methodology. Among them is | |||
| the ability to collect instant network state as the packet being | the ability to collect instant network state as the packet being | |||
| processed by the networking elements along its path through the | processed by the networking elements along its path through the | |||
| domain. This document introduces a new hybrid measurement method, | domain. This document introduces a new hybrid measurement method, | |||
| referred to as hybrid two-step, as it separates the act of measuring | referred to as hybrid two-step, as it separates the act of measuring | |||
| and/or calculating the performance metric from the act of collecting | and/or calculating the performance metric from the act of collecting | |||
| 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 9 January 2022. | This Internet-Draft will expire on 30 July 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 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 | |||
| and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
| extracted from this document must include Simplified BSD License text | extracted from this document must include Revised BSD License text as | |||
| as described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
| provided without warranty as described in the Simplified BSD License. | provided without warranty as described in the Revised BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Conventions used in this document . . . . . . . . . . . . . . 3 | 2. Conventions used in this document . . . . . . . . . . . . . . 3 | |||
| 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 | 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 | |||
| 3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . 4 | 3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 5 | 4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 4.1. Operation of the HTS Ingress Node . . . . . . . . . . . . 7 | 4.1. Operation of the HTS Ingress Node . . . . . . . . . . . . 7 | |||
| skipping to change at page 17, line 19 ¶ | skipping to change at page 17, line 19 ¶ | |||
| [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/info/rfc8174>. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [I-D.ietf-ippm-ioam-data] | [I-D.ietf-ippm-ioam-data] | |||
| Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields | Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields | |||
| for In-situ OAM", Work in Progress, Internet-Draft, draft- | for In-situ OAM", Work in Progress, Internet-Draft, draft- | |||
| ietf-ippm-ioam-data-14, 24 June 2021, | ietf-ippm-ioam-data-17, 13 December 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-ippm- | <https://datatracker.ietf.org/doc/html/draft-ietf-ippm- | |||
| ioam-data-14>. | ioam-data-17>. | |||
| [I-D.ietf-ippm-ioam-direct-export] | [I-D.ietf-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., Sivakolundu, R., and T. Mizrahi, "In-situ | Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ | |||
| OAM Direct Exporting", Work in Progress, Internet-Draft, | OAM Direct Exporting", Work in Progress, Internet-Draft, | |||
| draft-ietf-ippm-ioam-direct-export-03, 17 February 2021, | draft-ietf-ippm-ioam-direct-export-07, 13 October 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-ippm- | <https://datatracker.ietf.org/doc/html/draft-ietf-ippm- | |||
| ioam-direct-export-03>. | ioam-direct-export-07>. | |||
| [I-D.ietf-raw-use-cases] | [I-D.ietf-raw-use-cases] | |||
| Papadopoulos, G. Z., Thubert, P., Theoleyre, F., and C. J. | Papadopoulos, G. Z., Thubert, P., Theoleyre, F., and C. J. | |||
| Bernardos, "RAW use cases", Work in Progress, Internet- | Bernardos, "RAW use cases", Work in Progress, Internet- | |||
| Draft, draft-ietf-raw-use-cases-01, 21 February 2021, | Draft, draft-ietf-raw-use-cases-03, 20 October 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-raw-use- | <https://datatracker.ietf.org/doc/html/draft-ietf-raw-use- | |||
| cases-01>. | cases-03>. | |||
| [I-D.song-ippm-postcard-based-telemetry] | [I-D.song-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, "Postcard-based On-Path | T., Li, Z., Shin, J., and K. Lee, "In-Situ OAM Marking- | |||
| Flow Data Telemetry using Packet Marking", Work in | based Direct Export", Work in Progress, Internet-Draft, | |||
| Progress, Internet-Draft, draft-song-ippm-postcard-based- | draft-song-ippm-postcard-based-telemetry-11, 15 November | |||
| telemetry-09, 19 February 2021, | 2021, <https://datatracker.ietf.org/doc/html/draft-song- | |||
| <https://datatracker.ietf.org/doc/html/draft-song-ippm- | ippm-postcard-based-telemetry-11>. | |||
| postcard-based-telemetry-09>. | ||||
| [P4.INT] "In-band Network Telemetry (INT)", P4.org Specification, | [P4.INT] "In-band Network Telemetry (INT)", P4.org Specification, | |||
| October 2017. | October 2017. | |||
| [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- | [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- | |||
| 384, and HMAC-SHA-512 with IPsec", RFC 4868, | 384, and HMAC-SHA-512 with IPsec", RFC 4868, | |||
| DOI 10.17487/RFC4868, May 2007, | DOI 10.17487/RFC4868, May 2007, | |||
| <https://www.rfc-editor.org/info/rfc4868>. | <https://www.rfc-editor.org/info/rfc4868>. | |||
| [RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme, | [RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme, | |||
| skipping to change at page 19, line 4 ¶ | skipping to change at page 18, line 47 ¶ | |||
| "Alternate-Marking Method for Passive and Hybrid | "Alternate-Marking Method for Passive and Hybrid | |||
| Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321, | Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321, | |||
| January 2018, <https://www.rfc-editor.org/info/rfc8321>. | January 2018, <https://www.rfc-editor.org/info/rfc8321>. | |||
| [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., | [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., | |||
| Decraene, B., Litkowski, S., and R. Shakir, "Segment | Decraene, B., Litkowski, S., and R. Shakir, "Segment | |||
| Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, | Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, | |||
| July 2018, <https://www.rfc-editor.org/info/rfc8402>. | July 2018, <https://www.rfc-editor.org/info/rfc8402>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Greg Mirsky | ||||
| ZTE Corp. | ||||
| Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com | Greg Mirsky | |||
| Ericsson | ||||
| Email: gregimirsky@gmail.com | ||||
| Wang Lingqiang | Wang Lingqiang | |||
| ZTE Corporation | ZTE Corporation | |||
| No 19 ,East Huayuan Road | No 19 ,East Huayuan Road | |||
| Beijing | Beijing | |||
| Phone: +86 10 82963945 | Phone: +86 10 82963945 | |||
| Email: wang.lingqiang@zte.com.cn | Email: wang.lingqiang@zte.com.cn | |||
| Guo Zhui | Guo Zhui | |||
| ZTE Corporation | ZTE Corporation | |||
| End of changes. 17 change blocks. | ||||
| 24 lines changed or deleted | 23 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/ | ||||