draft-ietf-ippm-ioam-direct-export-04.txt   draft-ietf-ippm-ioam-direct-export-05.txt 
IPPM H. Song IPPM H. Song
Internet-Draft Futurewei Internet-Draft Futurewei
Intended status: Standards Track B. Gafni Intended status: Standards Track B. Gafni
Expires: January 2, 2022 Nvidia Expires: January 13, 2022 Nvidia
T. Zhou T. Zhou
Z. Li Z. Li
Huawei Huawei
F. Brockners F. Brockners
Cisco Cisco
S. Bhandari, Ed. S. Bhandari, Ed.
Thoughtspot Thoughtspot
R. Sivakolundu R. Sivakolundu
Cisco Cisco
T. Mizrahi, Ed. T. Mizrahi, Ed.
Huawei Huawei
July 1, 2021 July 12, 2021
In-situ OAM Direct Exporting In-situ OAM Direct Exporting
draft-ietf-ippm-ioam-direct-export-04 draft-ietf-ippm-ioam-direct-export-05
Abstract Abstract
In-situ Operations, Administration, and Maintenance (IOAM) is used In-situ Operations, Administration, and Maintenance (IOAM) is used
for recording and collecting operational and telemetry information. for recording and collecting operational and telemetry information.
Specifically, IOAM allows telemetry data to be pushed into data Specifically, IOAM allows telemetry data to be pushed into data
packets while they traverse the network. This document introduces a packets while they traverse the network. This document introduces a
new IOAM option type called the Direct Export (DEX) option, which is new IOAM option type called the Direct Export (DEX) option, which is
used as a trigger for IOAM data to be directly exported or locally used as a trigger for IOAM data to be directly exported or locally
aggregated without being pushed into in-flight data packets. The aggregated without being pushed into in-flight data packets. The
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 January 2, 2022. This Internet-Draft will expire on January 13, 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 23 skipping to change at page 5, line 23
entity. Therefore, an IOAM encapsulating node that supports the DEX entity. Therefore, an IOAM encapsulating node that supports the DEX
option MUST support the ability to incorporate the DEX option option MUST support the ability to incorporate the DEX option
selectively into a subset of the packets that are forwarded by it. selectively into a subset of the packets that are forwarded by it.
Various methods of packet selection and sampling have been previously Various methods of packet selection and sampling have been previously
defined, such as [RFC7014] and [RFC5475]. Similar techniques can be defined, such as [RFC7014] and [RFC5475]. Similar techniques can be
applied by an IOAM encapsulating node to apply DEX to a subset of the applied by an IOAM encapsulating node to apply DEX to a subset of the
forwarded traffic. forwarded traffic.
The subset of traffic that is forwarded or transmitted with a DEX The subset of traffic that is forwarded or transmitted with a DEX
option SHOULD not exceed 1/N of the interface capacity on any of the option SHOULD NOT exceed 1/N of the interface capacity on any of the
IOAM encapsulating node's interfaces. It is noted that this IOAM encapsulating node's interfaces. It is noted that this
requirement applies to the total traffic that incorporates a DEX requirement applies to the total traffic that incorporates a DEX
option, including traffic that is forwarded by the IOAM encapsulating option, including traffic that is forwarded by the IOAM encapsulating
node and probe packets that are generated by the IOAM encapsulating node and probe packets that are generated by the IOAM encapsulating
node. In this context N is a parameter that can be configurable by node. In this context N is a parameter that can be configurable by
network operators. If there is an upper bound, M, on the number of network operators. If there is an upper bound, M, on the number of
IOAM transit nodes in any path in the network, then it is recommended IOAM transit nodes in any path in the network, then it is recommended
to use an N such that N >> M. The rationale is that a packet that to use an N such that N >> M. The rationale is that a packet that
includes a DEX option may trigger an exported packet from each IOAM includes a DEX option may trigger an exported packet from each IOAM
transit node along the path for a total of M exported packets. Thus, transit node along the path for a total of M exported packets. Thus,
skipping to change at page 6, line 6 skipping to change at page 6, line 6
exported to a receiving entity, either proactively or on-demand. If exported to a receiving entity, either proactively or on-demand. If
IOAM data is exported, the format and encapsulation of the packet IOAM data is exported, the format and encapsulation of the packet
that contains the exported data is not within the scope of the that contains the exported data is not within the scope of the
current document. For example, the export format can be based on current document. For example, the export format can be based on
[I-D.spiegel-ippm-ioam-rawexport]. [I-D.spiegel-ippm-ioam-rawexport].
An IOAM node that performs DEX-triggered exporting MUST support the An IOAM node that performs DEX-triggered exporting MUST support the
ability to limit the rate of the exported packets. The rate of ability to limit the rate of the exported packets. The rate of
exported packets SHOULD be limited so that the number of exported exported packets SHOULD be limited so that the number of exported
packets is significantly lower than the number of packets that are packets is significantly lower than the number of packets that are
exported by the device. The exported data rate SHOULD not exceed 1/N forwarded by the device. The exported data rate SHOULD NOT exceed 1/
of the interface capacity on any of the IOAM node's interfaces. It N of the interface capacity on any of the IOAM node's interfaces. It
is recommended to use N>100. Depending on the IOAM node's is recommended to use N>100. Depending on the IOAM node's
architecture considerations, the export rate may be limited to a architecture considerations, the export rate may be limited to a
lower number in order to avoid loading the IOAM node. lower number in order to avoid loading the IOAM node.
Exported packets SHOULD not be exported over a path or a tunnel that Exported packets SHOULD NOT be exported over a path or a tunnel that
is subject to IOAM direct exporting. Furthermore, IOAM encapsulating is subject to IOAM direct exporting. Furthermore, IOAM encapsulating
nodes that push a DEX option into traversing packets MUST avoid nodes that can identify a packet as an IOAM exported packet MUST NOT
pushing an IOAM header into IOAM exported packets. This requirement push a DEX option into such a packet. This requirement is intended
is intended to prevent nested exporting and/or exporting loops. to prevent nested exporting and/or exporting loops.
A transit IOAM node that does not support the DEX option SHOULD A transit IOAM node that does not support the DEX option SHOULD
ignore it. A decapsulating node that does not support the DEX option ignore it. A decapsulating node that does not support the DEX option
MUST remove it, along with any other IOAM options carried in the MUST remove it, along with any other IOAM options carried in the
packet if such exist. packet if such exist.
3.2. The DEX Option Format 3.2. The DEX Option Format
The format of the DEX option is depicted in Figure 2. The length of The format of the DEX option is depicted in Figure 2. The length of
the DEX option is either 8 octets or 16 octets, as the Flow ID and the DEX option is either 8 octets or 16 octets, as the Flow ID and
skipping to change at page 11, line 33 skipping to change at page 11, line 33
DEX header. DEX header.
Authors' Addresses Authors' Addresses
Haoyu Song Haoyu Song
Futurewei Futurewei
2330 Central Expressway 2330 Central Expressway
Santa Clara 95050 Santa Clara 95050
USA USA
Email: haoyu.song@huawei.com Email: haoyu.song@futurewei.com
Barak Gafni Barak Gafni
Nvidia 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@nvidia.com Email: gbarak@nvidia.com
Tianran Zhou Tianran Zhou
 End of changes. 9 change blocks. 
12 lines changed or deleted 12 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/