< draft-mirsky-ippm-hybrid-two-step-04.txt   draft-mirsky-ippm-hybrid-two-step-05.txt >
IPPM Working Group G. Mirsky IPPM Working Group G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Standards Track W. Lingqiang Intended status: Standards Track W. Lingqiang
Expires: April 10, 2020 G. Zhui Expires: October 16, 2020 G. Zhui
ZTE Corporation ZTE Corporation
October 8, 2019 April 14, 2020
Hybrid Two-Step Performance Measurement Method Hybrid Two-Step Performance Measurement Method
draft-mirsky-ippm-hybrid-two-step-04 draft-mirsky-ippm-hybrid-two-step-05
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 39 skipping to change at page 1, line 39
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 April 10, 2020. This Internet-Draft will expire on October 16, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . 3 3. Problem Overview . . . . . . . . . . . . . . . . . . . . . . 4
4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 4 4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 5
4.1. Operation of the HTS Ingress Node . . . . . . . . . . . . 5 4.1. Operation of the HTS Ingress Node . . . . . . . . . . . . 6
4.2. Operation of the HTS Transient Node . . . . . . . . . . . 7 4.2. Operation of the HTS Transient Node . . . . . . . . . . . 7
4.3. Operation of the HTS Egress Node . . . . . . . . . . . . 8 4.3. Operation of the HTS Egress Node . . . . . . . . . . . . 8
4.4. Considerations for HTS Timers . . . . . . . . . . . . . . 8 4.4. Considerations for HTS Timers . . . . . . . . . . . . . . 8
4.5. Deploying HTS in a Multicast Network . . . . . . . . . . 8 4.5. Deploying HTS in a Multicast Network . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Successful resolution of challenges of automated network operation, Successful resolution of challenges of automated network operation,
as part of, for example, overall service orchestration or data center as part of, for example, overall service orchestration or data center
operation, relies on a timely collection of accurate information that operation, relies on a timely collection of accurate information that
reflects the state of network elements on an unprecedented scale. reflects the state of network elements on an unprecedented scale.
Because performing the analysis and act upon the collected Because performing the analysis and act upon the collected
information requires considerable computing and storage resources, information requires considerable computing and storage resources,
the network state information is unlikely to be processed by the the network state information is unlikely to be processed by the
network elements themselves but will be relayed into the data storage network elements themselves but will be relayed into the data storage
facilities, e.g., data lakes. The process of producing, collecting facilities, e.g., data lakes. The process of producing, collecting
network state information also referred to in this document as network state information also referred to in this document as
network telemetry, and transporting it for post-processing should network telemetry, and transporting it for post-processing should
work equally well with data flows or injected in the network test work equally well with data flows or injected in the network test
packets. RFC 7799 [RFC7799] describes a combination of elements of packets. RFC 7799 [RFC7799] describes a combination of elements of
passive and active measurement as a hybrid measurement. passive and active measurement as a hybrid measurement.
Several technical methods have been proposed to enable collection of Several technical methods have been proposed to enable the collection
network state information instantaneous to the packet processing, of network state information instantaneous to the packet processing,
among them [P4.INT] and [I-D.ietf-ippm-ioam-data]. among them [P4.INT] and [I-D.ietf-ippm-ioam-data]. The
instantaneous, i.e., in the data packet itself, collection of
telemetry information simplifies the process of attribution of
telemetry information to the particular monitored flow. On the other
hand, this collection method impacts the data packets, potentially
changing their treatment by the networking nodes. Also, the amount
of information the instantaneous method collects might be incomplete
because of the limited space it can be allotted. Other proposals
defined methods to collect telemetry information in a separate packet
from each node traversed by the monitored data flow. Examples of
this approach to collecting telemetry information are
[I-D.ietf-ippm-ioam-direct-export] and
[I-D.song-ippm-postcard-based-telemetry]. These methods allow data
collection from any arbitrary path and avoid directly impacting data
packets. On the other hand, the correlation of data and the
monitored flow requires that each packet with telemetry information
also includes characteristic information about the monitored flow.
This document introduces Hybrid Two-Step (HTS) as a new hybrid This document introduces Hybrid Two-Step (HTS) as a new hybrid
measurement method that separates measuring or calculating the measurement method that allows achieving better accuracy of a
measurement by separating the act of measuring or calculating the
performance metric from the collecting and transporting this performance metric from the collecting and transporting this
information. The Hybrid Two-Step method extends the two-step mode of information. The Hybrid Two-Step method extends the two-step mode of
Residence Time Measurement (RTM) defined in [RFC8169] to on-path Residence Time Measurement (RTM) defined in [RFC8169] to on-path
network state collection and transport. network state collection and transport. HTS allows the collection of
telemetry information from any arbitrary path, does not change data
packets of the monitored flow and makes the process of attribution of
telemetry to the data flow simple.
2. Conventions used in this document 2. Conventions used in this document
2.1. Terminology 2.1. Terminology
RTM Residence Time Measurement RTM Residence Time Measurement
ECMP Equal Cost Multipath ECMP Equal Cost Multipath
MTU Maximum Transmission Unit MTU Maximum Transmission Unit
skipping to change at page 10, line 23 skipping to change at page 10, line 33
[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>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., Brockners, F., Bhandari, S., Pignataro, C., Gredler, H.,
Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov,
P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon, P., remy@barefootnetworks.com, r., daniel.bernier@bell.ca,
"Data Fields for In-situ OAM", draft-ietf-ippm-ioam- d., and J. Lemon, "Data Fields for In-situ OAM", draft-
data-07 (work in progress), September 2019. ietf-ippm-ioam-data-09 (work in progress), March 2020.
[I-D.ietf-ippm-ioam-direct-export]
Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,
Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ
OAM Direct Exporting", draft-ietf-ippm-ioam-direct-
export-00 (work in progress), February 2020.
[I-D.song-ippm-postcard-based-telemetry]
Song, H., Zhou, T., Li, Z., Shin, J., and K. Lee,
"Postcard-based On-Path Flow Data Telemetry", draft-song-
ippm-postcard-based-telemetry-07 (work in progress), April
2020.
[P4.INT] "In-band Network Telemetry (INT)", P4.org Specification, [P4.INT] "In-band Network Telemetry (INT)", P4.org Specification,
October 2017. October 2017.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/info/rfc7799>. May 2016, <https://www.rfc-editor.org/info/rfc7799>.
[RFC8169] Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S., [RFC8169] Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S.,
and A. Vainshtein, "Residence Time Measurement in MPLS and A. Vainshtein, "Residence Time Measurement in MPLS
 End of changes. 12 change blocks. 
18 lines changed or deleted 50 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/