--- 1/draft-ietf-ippm-ioam-flags-01.txt 2020-07-27 02:13:10.762216958 -0700 +++ 2/draft-ietf-ippm-ioam-flags-02.txt 2020-07-27 02:13:10.798217443 -0700 @@ -1,29 +1,29 @@ IPPM T. Mizrahi Internet-Draft Huawei Smart Platforms iLab Intended status: Standards Track F. Brockners -Expires: July 29, 2020 S. Bhandari +Expires: January 28, 2021 S. Bhandari R. Sivakolundu C. Pignataro Cisco A. Kfir B. Gafni Mellanox Technologies, Inc. M. Spiegel Barefoot Networks J. Lemon Broadcom - January 26, 2020 + July 27, 2020 In-situ OAM Flags - draft-ietf-ippm-ioam-flags-01 + draft-ietf-ippm-ioam-flags-02 Abstract In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document presents new flags in the IOAM Trace Option headers. Specifically, the document defines the Loopback and Active flags. Status of This Memo @@ -34,21 +34,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 29, 2020. + This Internet-Draft will expire on January 28, 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -194,22 +194,21 @@ active OAM protocols, which may run in higher layers and make use of the active flag. An example of an IOAM deployment scenario is illustrated in Figure 1. The figure depicts two endpoints, a source and a destination. The data traffic from the source to the destination is forwarded through a set of network devices, including an IOAM encapsulating node, which incorporates one or more IOAM options, a decapsulating node, which removes the IOAM options, optionally one or more transit nodes. The IOAM options are encapsulated in one of the IOAM encapsulation types, - e.g., [I-D.ietf-sfc-ioam-nsh], or - [I-D.ioametal-ippm-6man-ioam-ipv6-options]. + e.g., [I-D.ietf-sfc-ioam-nsh], or [I-D.ietf-ippm-ioam-ipv6-options]. +--------+ +--------+ +--------+ +--------+ +--------+ | | | IOAM |.....| IOAM |.....| IOAM | | | +--------+ +--------+ +--------+ +--------+ +--------+ | L2/L3 |<===>| L2/L3 |<===>| L2/L3 |<===>| L2/L3 |<===>| L2/L3 | +--------+ +--------+ +--------+ +--------+ +--------+ Source Encapsulating Transit Decapsulating Destination Node Node Node <------------ IOAM domain -----------> @@ -344,50 +342,48 @@ IOAM is assumed to be deployed in a restricted administrative domain, thus limiting the scope of the threats above and their affect. This is a fundamental assumtion with respect to the security aspects of IOAM, as further discussed in [I-D.ietf-ippm-ioam-data]. 9. References 9.1. Normative References [I-D.ietf-ippm-ioam-data] - Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., - Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, - P., remy@barefootnetworks.com, r., daniel.bernier@bell.ca, - d., and J. Lemon, "Data Fields for In-situ OAM", draft- - ietf-ippm-ioam-data-08 (work in progress), October 2019. + Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields + for In-situ OAM", draft-ietf-ippm-ioam-data-10 (work in + progress), July 2020. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . 9.2. Informative References - [I-D.ietf-sfc-ioam-nsh] - Brockners, F. and S. Bhandari, "Network Service Header - (NSH) Encapsulation for In-situ OAM (IOAM) Data", draft- - ietf-sfc-ioam-nsh-02 (work in progress), September 2019. - - [I-D.ioametal-ippm-6man-ioam-ipv6-options] + [I-D.ietf-ippm-ioam-ipv6-options] Bhandari, S., Brockners, F., Pignataro, C., Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., Spiegel, M., Krishnan, S., and R. Asati, - "In-situ OAM IPv6 Options", draft-ioametal-ippm-6man-ioam- - ipv6-options-02 (work in progress), March 2019. + "In-situ OAM IPv6 Options", draft-ietf-ippm-ioam- + ipv6-options-02 (work in progress), July 2020. + + [I-D.ietf-sfc-ioam-nsh] + Brockners, F. and S. Bhandari, "Network Service Header + (NSH) Encapsulation for In-situ OAM (IOAM) Data", draft- + ietf-sfc-ioam-nsh-04 (work in progress), June 2020. [I-D.spiegel-ippm-ioam-rawexport] Spiegel, M., Brockners, F., Bhandari, S., and R. Sivakolundu, "In-situ OAM raw data export with IPFIX", - draft-spiegel-ippm-ioam-rawexport-02 (work in progress), - July 2019. + draft-spiegel-ippm-ioam-rawexport-03 (work in progress), + March 2020. [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, May 2016, . Authors' Addresses Tal Mizrahi Huawei Smart Platforms iLab Israel