| < draft-mizrahi-ippm-ioam-profile-04.txt | draft-mizrahi-ippm-ioam-profile-05.txt > | |||
|---|---|---|---|---|
| Network Working Group T. Mizrahi | Network Working Group T. Mizrahi | |||
| Internet-Draft Huawei | Internet-Draft Huawei | |||
| Intended status: Informational F. Brockners | Intended status: Informational F. Brockners | |||
| Expires: August 21, 2021 Cisco | Expires: February 20, 2022 Cisco | |||
| S. Bhandari, Ed. | S. Bhandari, Ed. | |||
| Thoughtspot | Thoughtspot | |||
| R. Sivakolundu | R. Sivakolundu | |||
| C. Pignataro | C. Pignataro | |||
| Cisco | Cisco | |||
| A. Kfir | A. Kfir | |||
| B. Gafni | B. Gafni | |||
| Nvidia | Nvidia | |||
| M. Spiegel | M. Spiegel | |||
| Barefoot Networks | Barefoot Networks | |||
| T. Zhou | T. Zhou | |||
| Huawei | Huawei | |||
| J. Lemon | J. Lemon | |||
| Broadcom | Broadcom | |||
| February 17, 2021 | August 19, 2021 | |||
| In Situ OAM Profiles | In Situ OAM Profiles | |||
| draft-mizrahi-ippm-ioam-profile-04 | draft-mizrahi-ippm-ioam-profile-05 | |||
| 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 21, 2021. | This Internet-Draft will expire on February 20, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 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 | |||
| 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-11 (work in | for In-situ OAM", draft-ietf-ippm-ioam-data-14 (work in | |||
| progress), November 2020. | progress), June 2021. | |||
| [I-D.ietf-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-ietf-ippm-ioam- | YANG Data Model for In-Situ OAM", draft-ietf-ippm-ioam- | |||
| yang-00 (work in progress), January 2021. | yang-01 (work in progress), July 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. | |||
| End of changes. 6 change blocks. | ||||
| 7 lines changed or deleted | 7 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/ | ||||