< draft-mizrahi-ippm-ioam-profile-02.txt   draft-mizrahi-ippm-ioam-profile-03.txt >
Network Working Group T. Mizrahi Network Working Group T. Mizrahi
Internet-Draft Huawei Smart Platforms iLab Internet-Draft Huawei Smart Platforms iLab
Intended status: Informational F. Brockners Intended status: Informational F. Brockners
Expires: August 9, 2020 S. Bhandari Expires: February 6, 2021 S. Bhandari
R. Sivakolundu R. Sivakolundu
C. Pignataro C. Pignataro
Cisco Cisco
A. Kfir A. Kfir
B. Gafni B. Gafni
Mellanox Technologies, Inc. Mellanox Technologies, Inc.
M. Spiegel M. Spiegel
Barefoot Networks Barefoot Networks
T. Zhou T. Zhou
Huawei Huawei
J. Lemon J. Lemon
Broadcom Broadcom
February 6, 2020 August 5, 2020
In Situ OAM Profiles In Situ OAM Profiles
draft-mizrahi-ippm-ioam-profile-02 draft-mizrahi-ippm-ioam-profile-03
Abstract Abstract
In Situ Operations, Administration and Maintenance (IOAM) is used for In Situ Operations, Administration and Maintenance (IOAM) is used for
monitoring network performance and for detecting traffic bottlenecks monitoring network performance and for detecting traffic bottlenecks
and anomalies. This is achieved by incorporating IOAM data into in- and anomalies. This is achieved by incorporating IOAM data into in-
flight data packets. This document introduces the concept of use flight data packets. This document introduces the concept of use
case-driven IOAM profiles. An IOAM profile defines a use case or a case-driven IOAM profiles. An IOAM profile defines a use case or a
set of use cases for IOAM, and an associated set of rules that set of use cases for IOAM, and an associated set of rules that
restrict the scope and features of the IOAM specification, thereby restrict the scope and features of the IOAM specification, thereby
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 August 9, 2020. This Internet-Draft will expire on February 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
2. Specifying an IOAM Profile . . . . . . . . . . . . . . . . . 3 2. Specifying an IOAM Profile . . . . . . . . . . . . . . . . . 3
2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 4 2.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 4
2.4. IOAM Option Header Field Values . . . . . . . . . . . . . 4 2.4. IOAM Option Header Field Values . . . . . . . . . . . . . 4
2.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 4 2.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 4
2.6. Timestamp Format . . . . . . . . . . . . . . . . . . . . 5 2.6. Timestamp Format . . . . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Normative References . . . . . . . . . . . . . . . . . . . . 5 5. Normative References . . . . . . . . . . . . . . . . . . . . 5
Appendix A. An IOAM Profile Example . . . . . . . . . . . . . . 6 Appendix A. An IOAM Profile Example . . . . . . . . . . . . . . 5
A.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 A.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
A.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 6 A.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 6
A.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 6 A.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 6
A.4. IOAM Option Header Field Values . . . . . . . . . . . . . 6 A.4. IOAM Option Header Field Values . . . . . . . . . . . . . 6
A.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 6 A.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 6
A.6. Profile Coexistence . . . . . . . . . . . . . . . . . . . 6 A.6. Profile Coexistence . . . . . . . . . . . . . . . . . . . 6
A.7. Validity . . . . . . . . . . . . . . . . . . . . . . . . 7 A.7. Validity . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
IOAM [I-D.ietf-ippm-ioam-data] is used for monitoring traffic in the IOAM [I-D.ietf-ippm-ioam-data] is used for monitoring traffic in the
network by incorporating IOAM data fields into in-flight data network by incorporating IOAM data fields into in-flight data
packets. packets.
This document introduces the concept of use case driven IOAM This document introduces the concept of use case driven IOAM
profiles. The motivation for defining profiles is to limit the scope profiles. The motivation for defining profiles is to limit the scope
skipping to change at page 5, line 34 skipping to change at page 5, line 34
considerations beyond [I-D.ietf-ippm-ioam-data]. considerations beyond [I-D.ietf-ippm-ioam-data].
Moreover, in some cases a profile may limit the set of features of Moreover, in some cases a profile may limit the set of features of
IOAM in a way that reduces the set of potential threats compared to a IOAM in a way that reduces the set of potential threats compared to a
full implementation of IOAM. In fact, a particular IOAM profile can full implementation of IOAM. In fact, a particular IOAM profile can
optimize a particular security posture or requirement. optimize a particular security posture or requirement.
5. Normative References 5. Normative 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., and T. Mizrahi, "Data Fields
Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, for In-situ OAM", draft-ietf-ippm-ioam-data-10 (work in
P., remy@barefootnetworks.com, r., daniel.bernier@bell.ca, progress), July 2020.
d., and J. Lemon, "Data Fields for In-situ OAM", draft-
ietf-ippm-ioam-data-08 (work in progress), October 2019.
[I-D.zhou-ippm-ioam-yang] [I-D.zhou-ippm-ioam-yang]
Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A
YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam- YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam-
yang-05 (work in progress), January 2020. yang-08 (work in progress), July 2020.
[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>.
Appendix A. An IOAM Profile Example Appendix A. An IOAM Profile Example
A.1. Overview A.1. Overview
This section presents an example of an IOAM profile specification. This section presents an example of an IOAM profile specification.
The profile makes use of the Hop limit, Node ID and Transit delay The profile makes use of the Hop limit, Node ID and Transit delay
data fields, and is thus called the HNT profile for short. data fields, and is thus called the HNT profile for short.
A.2. Use Cases A.2. Use Cases
This profile is intended for path tracing and transit delay This profile is intended for path tracing and transit delay
monitoring, while using compact data with just two data fields per monitoring, while using compact data with just two data fields per
 End of changes. 9 change blocks. 
13 lines changed or deleted 10 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/