< draft-song-opsawg-ifit-framework-02.txt   draft-song-opsawg-ifit-framework-03.txt >
OPSAWG H. Song, Ed. OPSAWG H. Song, Ed.
Internet-Draft Futurewei Internet-Draft Futurewei
Intended status: Informational Z. Li Intended status: Informational Z. Li
Expires: December 14, 2019 T. Zhou Expires: January 9, 2020 T. Zhou
Huawei Huawei
F. Qin F. Qin
China Mobile China Mobile
J. Shin J. Shin
SK Telecom SK Telecom
J. Jin J. Jin
LG U+ LG U+
June 12, 2019 July 8, 2019
In-situ Flow Information Telemetry Framework In-situ Flow Information Telemetry Framework
draft-song-opsawg-ifit-framework-02 draft-song-opsawg-ifit-framework-03
Abstract Abstract
In-situ Flow Information Telemetry (iFIT) is a framework for applying In-situ Flow Information Telemetry (iFIT) is a framework for applying
data plane telemetry techniques such as In-situ OAM (iOAM) and on-path data plane telemetry techniques such as In-situ OAM (iOAM)
Postcard-Based Telemetry (PBT). It enumerates several key components and Postcard-Based Telemetry (PBT). It enumerates several key
and describes how these components are assembled to achieve a components and describes how these components are assembled to
complete working solution for on-path user traffic telemetry in achieve a complete working solution for on-path user traffic
carrier networks. telemetry in carrier networks.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all 14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
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 December 14, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 31 skipping to change at page 2, line 31
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Smart Flow and Data Selection . . . . . . . . . . . . . . . . 5 2. Smart Flow and Data Selection . . . . . . . . . . . . . . . . 5
3. Export Data Reduction . . . . . . . . . . . . . . . . . . . . 5 3. Export Data Reduction . . . . . . . . . . . . . . . . . . . . 5
4. Dynamic Network Probe . . . . . . . . . . . . . . . . . . . . 6 4. Dynamic Network Probe . . . . . . . . . . . . . . . . . . . . 6
5. Encapsulation and Tunnel Modes . . . . . . . . . . . . . . . 6 5. Encapsulation and Tunnel Modes . . . . . . . . . . . . . . . 6
6. On-demand Technique Selection and Integration . . . . . . . . 7 6. On-demand Technique Selection and Integration . . . . . . . . 7
7. Summary and Future Work . . . . . . . . . . . . . . . . . . . 7 7. Summary and Future Work . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
12.1. Normative References . . . . . . . . . . . . . . . . . . 8 12.1. Normative References . . . . . . . . . . . . . . . . . . 8
12.2. Informative References . . . . . . . . . . . . . . . . . 8 12.2. Informative References . . . . . . . . . . . . . . . . . 8
12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 9 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Application-aware network operation is important for user SLA Application-aware network operation is important for user SLA
compliance, service path enforcement, fault diagnosis, and network compliance, service path enforcement, fault diagnosis, and network
resource optimization. In-situ OAM (IOAM) resource optimization. In-situ OAM (IOAM)
[I-D.brockners-inband-oam-data] and PBT [I-D.brockners-inband-oam-data] and PBT
[I-D.song-ippm-postcard-based-telemetry] provide the direct [I-D.song-ippm-postcard-based-telemetry] provide the direct on-path
experience of user traffic. These techniques are invaluable for experience of user traffic. These techniques are invaluable for
application-aware network operations in not only data center and application-aware network operations in not only data center and
enterprise networks but also carrier networks. enterprise networks but also carrier networks.
However, successfully applying such techniques in carrier networks However, successfully applying such techniques in carrier networks
poses several practical challenges: poses several practical challenges:
o C1: IOAM and PBT incur extra packet processing which may strain o C1: IOAM and PBT incur extra packet processing which may strain
the network data plane. The potential impact on the forwarding the network data plane. The potential impact on the forwarding
performance creates an unfavorable "observer effect" which not performance creates an unfavorable "observer effect" which not
skipping to change at page 3, line 47 skipping to change at page 3, line 47
of the flow telemetry data and the packet drop location and reason of the flow telemetry data and the packet drop location and reason
remains unknown if only IOAM is used. A comprehensive solution remains unknown if only IOAM is used. A comprehensive solution
needs the flexibility to switch between different underlying needs the flexibility to switch between different underlying
techniques and adjust the configurations and parameters at techniques and adjust the configurations and parameters at
runtime. runtime.
To address these challenges, we propose a framework based on our To address these challenges, we propose a framework based on our
prototype experience which can help to build a workable data-plane prototype experience which can help to build a workable data-plane
telemetry solution. We name the framework "In-situ Flow Information telemetry solution. We name the framework "In-situ Flow Information
Telemetry" (iFIT) to reflect the fact that this framework is Telemetry" (iFIT) to reflect the fact that this framework is
dedicated to the telemetry data about user/application flow dedicated to the on-path telemetry data about user/application flow
experience. In future, other related data plane OAM techniques such experience. In future, other related data plane OAM techniques such
as IPFPM [RFC8321] can also be integrated into iFIT to provide richer as IPFPM [RFC8321] can also be integrated into iFIT to provide richer
capabilities. The network architecture that applies iFIT is shown in capabilities. The network architecture that applies iFIT is shown in
Figure 1. The key components of iFIT is listed as follows: Figure 1. The key components of iFIT is listed as follows:
o Smart flow and data selection policy to address C1. o Smart flow and data selection policy to address C1.
o Export data reduction to address C2. o Export data reduction to address C2.
o Dynamic network probe to address C3. o Dynamic network probe to address C3.
skipping to change at page 7, line 22 skipping to change at page 7, line 22
iFIT may choose either IOAM or PBT to collect the data; if an iFIT may choose either IOAM or PBT to collect the data; if an
application needs to track down where the packets are lost, it may application needs to track down where the packets are lost, it may
switch from IOAM to PBT. switch from IOAM to PBT.
iFIT can further integrate multiple data plane monitoring and iFIT can further integrate multiple data plane monitoring and
measurement techniques together and present a comprehensive data measurement techniques together and present a comprehensive data
plane telemetry solution to network operating applications. plane telemetry solution to network operating applications.
7. Summary and Future Work 7. Summary and Future Work
Combining with algorithmic and architectural components, iFIT iFIT is a framework for applying on-path data plane telemetry
framework enables a practical solution based on existing techniques techniques. Combining with algorithmic and architectural components,
such as IOAM and PBT for user traffic telemetry in carrier networks. iFIT framework enables a practical telemetry solution based on two
basic on-path traffic data collection patterns: passport (e.g., IOAM
trace and e2e modes) and postcard (e.g., PBT).
The operation of iFIT differs from both active OAM and passive OAM as
defined in [RFC7799]. It does not generate any active probe packets
or passively observe unmodified user packets. Instead, it modifies
selected user packets to collect useful information about them.
Therefore, the iFIT operation can be considered the third mode of
OAM, hybrid OAM, which can provide more flexible and accurate network
OAM.
There are many more challenges and corresponding solutions for iFIT There are many more challenges and corresponding solutions for iFIT
that we did not cover in the current version of this document. For that we did not cover in the current version of this document. For
example, how the telemetry data are stored, analyzed, and visualized; example, how the telemetry data are stored, analyzed, and visualized;
how the telemetry data interfaces and work with the network operation how the telemetry data interfaces and work with the network operation
applications which run machine learning and big data analytic applications which run machine learning and big data analytic
algorithms; and ultimately, how iFIT can support closed control loops algorithms; and ultimately, how iFIT can support closed control loops
for autonomous networking? A complete iFIT framework should also for autonomous networking? A complete iFIT framework should also
consider the cross-domain operations. We leave these topics for consider the cross-domain operations. We leave these topics for
future revisions. future revisions.
8. Security Considerations 8. Security Considerations
TBD No specific security issues are identified other than those have been
discussed in IOAM and PBT drafts.
9. IANA Considerations 9. IANA Considerations
This document includes no request to IANA. This document includes no request to IANA.
10. Contributors 10. Contributors
TBD. TBD.
11. Acknowledgments 11. Acknowledgments
skipping to change at page 8, line 14 skipping to change at page 8, line 26
12. References 12. References
12.1. Normative References 12.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/info/rfc2119>.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/info/rfc7799>.
[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>.
12.2. Informative References 12.2. Informative References
[I-D.brockners-inband-oam-data] [I-D.brockners-inband-oam-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., and d. daniel.bernier@bell.ca, "Data Fields P., Chang, R., and d. daniel.bernier@bell.ca, "Data Fields
skipping to change at page 8, line 38 skipping to change at page 9, line 6
Song, H. and T. Zhou, "In-situ OAM Data Validation Song, H. and T. Zhou, "In-situ OAM Data Validation
Option", draft-song-ippm-ioam-data-validation-option-02 Option", draft-song-ippm-ioam-data-validation-option-02
(work in progress), April 2018. (work in progress), April 2018.
[I-D.song-ippm-ioam-tunnel-mode] [I-D.song-ippm-ioam-tunnel-mode]
Song, H., Li, Z., Zhou, T., and Z. Wang, "In-situ OAM Song, H., Li, Z., Zhou, T., and Z. Wang, "In-situ OAM
Processing in Tunnels", draft-song-ippm-ioam-tunnel- Processing in Tunnels", draft-song-ippm-ioam-tunnel-
mode-00 (work in progress), June 2018. mode-00 (work in progress), June 2018.
[I-D.song-ippm-postcard-based-telemetry] [I-D.song-ippm-postcard-based-telemetry]
Song, H., Zhou, T., Li, Z., and J. Shin, "Postcard-based Song, H., Zhou, T., Li, Z., Shin, J., and K. Lee,
On-Path Flow Data Telemetry", draft-song-ippm-postcard- "Postcard-based On-Path Flow Data Telemetry", draft-song-
based-telemetry-03 (work in progress), April 2019. ippm-postcard-based-telemetry-04 (work in progress), June
2019.
[I-D.song-mpls-extension-header] [I-D.song-mpls-extension-header]
Song, H., Li, Z., Zhou, T., and L. Andersson, "MPLS Song, H., Li, Z., Zhou, T., and L. Andersson, "MPLS
Extension Header", draft-song-mpls-extension-header-02 Extension Header", draft-song-mpls-extension-header-02
(work in progress), February 2019. (work in progress), February 2019.
[I-D.song-opsawg-dnp4iq] [I-D.song-opsawg-dnp4iq]
Song, H. and J. Gong, "Requirements for Interactive Query Song, H. and J. Gong, "Requirements for Interactive Query
with Dynamic Network Probes", draft-song-opsawg-dnp4iq-01 with Dynamic Network Probes", draft-song-opsawg-dnp4iq-01
(work in progress), June 2017. (work in progress), June 2017.
 End of changes. 12 change blocks. 
21 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/