< draft-mizrahi-ippm-ioam-profile-03.txt   draft-mizrahi-ippm-ioam-profile-04.txt >
Network Working Group T. Mizrahi Network Working Group T. Mizrahi
Internet-Draft Huawei Smart Platforms iLab Internet-Draft Huawei
Intended status: Informational F. Brockners Intended status: Informational F. Brockners
Expires: February 6, 2021 S. Bhandari Expires: August 21, 2021 Cisco
S. Bhandari, Ed.
Thoughtspot
R. Sivakolundu R. Sivakolundu
C. Pignataro C. Pignataro
Cisco Cisco
A. Kfir A. Kfir
B. Gafni B. Gafni
Mellanox Technologies, Inc. Nvidia
M. Spiegel M. Spiegel
Barefoot Networks Barefoot Networks
T. Zhou T. Zhou
Huawei Huawei
J. Lemon J. Lemon
Broadcom Broadcom
August 5, 2020 February 17, 2021
In Situ OAM Profiles In Situ OAM Profiles
draft-mizrahi-ippm-ioam-profile-03 draft-mizrahi-ippm-ioam-profile-04
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 February 6, 2021. This Internet-Draft will expire on August 21, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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
skipping to change at page 3, line 43 skipping to change at page 3, line 43
A profile defines a set of rules that limit the scope or A profile defines a set of rules that limit the scope or
functionality of IOAM. By default, any detail in IOAM that is not functionality of IOAM. By default, any detail in IOAM that is not
specifically addressed or limited by the profile is as defined in specifically addressed or limited by the profile is as defined in
IOAM [I-D.ietf-ippm-ioam-data]. The rest of this section presents a IOAM [I-D.ietf-ippm-ioam-data]. The rest of this section presents a
set of topics that may be addressed in a profile specification. A set of topics that may be addressed in a profile specification. A
profile may include some or all of these topics, and optionally other profile may include some or all of these topics, and optionally other
topics. topics.
A profile may in part be defined using a specific assignment to the A profile may in part be defined using a specific assignment to the
IOAM YANG model. The IOAM YANG model [I-D.zhou-ippm-ioam-yang] IOAM YANG model. The IOAM YANG model [I-D.ietf-ippm-ioam-yang]
defines a set of IOAM-related attributes, such as which IOAM option defines a set of IOAM-related attributes, such as which IOAM option
types are enabled, and which data fields are used. For example, an types are enabled, and which data fields are used. For example, an
IOAM profile that only uses the icremental trace option may be IOAM profile that only uses the icremental trace option may be
defined as such by an assignment to the respective attributes that defined as such by an assignment to the respective attributes that
are defined in the YANG model. It should be noted that while the are defined in the YANG model. It should be noted that while the
YANG model assists in the definition of a profile, it does not YANG model assists in the definition of a profile, it does not
replace the profile definition. Specifically, a profile definition replace the profile definition. Specifically, a profile definition
includes the use case(s) for using the profile, and possibly some includes the use case(s) for using the profile, and possibly some
properties that cannot be defined by an assignment to the YANG model, properties that cannot be defined by an assignment to the YANG model,
such as the semantics of the Opaque State Snapshot field. such as the semantics of the Opaque State Snapshot field.
skipping to change at page 5, line 35 skipping to change at page 5, line 35
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., and T. Mizrahi, "Data Fields Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
for In-situ OAM", draft-ietf-ippm-ioam-data-10 (work in for In-situ OAM", draft-ietf-ippm-ioam-data-11 (work in
progress), July 2020. progress), November 2020.
[I-D.zhou-ippm-ioam-yang] [I-D.ietf-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-ietf-ippm-ioam-
yang-08 (work in progress), July 2020. yang-00 (work in progress), January 2021.
[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.
skipping to change at page 7, line 11 skipping to change at page 7, line 11
An IOAM transit/decapsulating node that receives a packet with IOAM An IOAM transit/decapsulating node that receives a packet with IOAM
options that do not comply to the current profile should forward/ options that do not comply to the current profile should forward/
decapsulate the packet without IOAM processing, if it is able to do decapsulate the packet without IOAM processing, if it is able to do
so. If a decapsulating node is not able to decapsulate an IOAM so. If a decapsulating node is not able to decapsulate an IOAM
option that is not compliant to the current profile, the packet is option that is not compliant to the current profile, the packet is
discarded. discarded.
Authors' Addresses Authors' Addresses
Tal Mizrahi Tal Mizrahi
Huawei Smart Platforms iLab Huawei
8-2 Matam 8-2 Matam
Haifa 3190501 Haifa 3190501
Israel Israel
Email: tal.mizrahi.phd@gmail.com Email: tal.mizrahi.phd@gmail.com
Frank Brockners Frank Brockners
Cisco Systems, Inc. Cisco Systems, Inc.
Hansaallee 249, 3rd Floor Hansaallee 249, 3rd Floor
DUESSELDORF, NORDRHEIN-WESTFALEN 40549 DUESSELDORF, NORDRHEIN-WESTFALEN 40549
Germany Germany
Email: fbrockne@cisco.com Email: fbrockne@cisco.com
Shwetha Bhandari Shwetha Bhandari (editor)
Cisco Systems, Inc. Thoughtspot
Cessna Business Park, Sarjapura Marathalli Outer Ring Road 3rd Floor, Indiqube Orion, 24th Main Rd, Garden Layout, HSR Layout
Bangalore, KARNATAKA 560 087 Bangalore, KARNATAKA 560 102
India India
Email: shwethab@cisco.com Email: shwetha.bhandari@thoughtspot.com
Ramesh Sivakolundu Ramesh Sivakolundu
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Dr. 170 West Tasman Dr.
SAN JOSE, CA 95134 SAN JOSE, CA 95134
U.S.A. U.S.A.
Email: sramesh@cisco.com Email: sramesh@cisco.com
Carlos Pignataro Carlos Pignataro
Cisco Systems, Inc. Cisco Systems, Inc.
7200-11 Kit Creek Road 7200-11 Kit Creek Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
United States United States
Email: cpignata@cisco.com Email: cpignata@cisco.com
Aviv Kfir Aviv Kfir
Mellanox Technologies, Inc. Nvidia
350 Oakmead Parkway, Suite 100
Sunnyvale, CA 94085
U.S.A.
Email: avivk@mellanox.com Email: avivk@nvidia.com
Barak Gafni Barak Gafni
Mellanox Technologies, Inc. Nvidia
350 Oakmead Parkway, Suite 100 350 Oakmead Parkway, Suite 100
Sunnyvale, CA 94085 Sunnyvale, CA 94085
U.S.A. U.S.A.
Email: gbarak@mellanox.com Email: gbarak@nvidia.com
Mickey Spiegel Mickey Spiegel
Barefoot Networks Barefoot Networks
4750 Patrick Henry Drive 4750 Patrick Henry Drive
Santa Clara, CA 95054 Santa Clara, CA 95054
US US
Email: mspiegel@barefootnetworks.com Email: mspiegel@barefootnetworks.com
Tianran Zhou Tianran Zhou
 End of changes. 18 change blocks. 
26 lines changed or deleted 25 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/