Extensions to IOAM Trace Option for Carrying Fixed-Size Data

Abstract

The IOAM Trace-Option data defined in RFC 9197 is a variable-length data, the length of this kind of data varies with the transited IOAM-capable nodes and the selection of data fields processed by each IOAM-capable node. This document extends the IOAM Trace Option to carry a fixed-size data, the length of this kind of data is fixed and doesn't vary with the transited IOAM-capable nodes and the selection of data fields processed by each IOAM-capable node.¶

1. Introduction

[RFC9197] defines In situ Operations, Administration, and Maintenance (IOAM), which collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. As specified in Section 4.1 of [RFC9197], IOAM tracing is defined as two separate options: Pre-allocated Trace Option and Incremental Trace Option. The two IOAM Trace Options share the same format of IOAM Trace-Option header and data. The IOAM Trace-Option data is composed of a set of node data lists; among them each node data list is populated by a node along the forwarding path of IOAM packet.¶

The IOAM Trace-Option data defined in [RFC9197] is a variable-length data, the length of this kind of data varies with the transited IOAM-capable nodes and the selection of data fields processed by each IOAM-capable node. This document extends the IOAM Trace Option to carry a fixed-size data, the length of this kind of data is fixed and doesn't vary with the transited IOAM-capable nodes and the selection of data fields processed by each IOAM-capable node.¶

2. Conventions Used in This Document

3. Problem with the current IOAM Trace Option

As specified in Section 4.4 of [RFC9197], the IOAM Trace Option (including IOAM Pre-allocated Trace Option and IOAM Incremental Trace Option) has a format as below.¶

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Namespace-ID           |NodeLen  | Flags | RemainingLen|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               IOAM Trace-Type                 |  Reserved     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+
|                                                               |  |
|                        node data list [0]                     |  |
|                                                               |  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  D
|                                                               |  a
|                        node data list [1]                     |  t
|                                                               |  a
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                             ...                               ~  S
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  p
|                                                               |  a
|                        node data list [n-1]                   |  c
|                                                               |  e
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  |
|                                                               |  |
|                        node data list [n]                     |  |
|                                                               |  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+

The IOAM Trace Option defined in [RFC9197] is used to stack up multiple metadata from multiple IOAM transit nodes. Specifically, along the forwarding path, each IOAM-capable node adds its own operational and telemetry information into the IOAM Trace Option carried by a data packet in a stacking manner.¶

As described in [I-D.miao-ccwg-hpcc-info], the IOAM Trace Option Data can be used as a congestion control signal for Enhanced High Precision Congestion Control (HPCC++) congestion control mechanism, and at the same time, Congestion Signaling (CSIG) Data can also be used as a congestion control signal for HPCC++. As specified in [I-D.ravi-ippm-csig], a CSIG tag carries a fixed-size aggregate metric computed over the hop devices. Specifically, along the forwarding path, each CSIG-capable node optionally inputs its own congestion information into the CSIG tag carried by a data packet in a compare-and-replace manner.¶

In different application scenarios, either the IOAM Trace Option defined in [RFC9197] or the CSIG tag defined in [I-D.miao-ccwg-hpcc-info] is applicable, or even both of them can be used concurrently, in other words, they're complementary to each other. Then the question goes to that whether it's possible to integrate them together. That is also the problem this document intends to address.¶

4. Extension to the IOAM Trace Option's Flags

In order to integrate the variable-size superimposed data and fixed-size aggregate data into IOAM Trace Option, this document defines the reserved Bit 3 of the Flags field of the IOAM Trace Option as below.¶

 0 1 2 3
+-+-+-+-+
|O|L|A|F|
+-+-+-+-+

Bit 0 "Overflow" (O-bit): When set, the Overflow flag indicates that there are not enough octets left to record the node data, as defined in Section 4.4.1 of [RFC9197].¶

Bit 1 "Loopback" (L-bit): When set, the Loopback flag triggers the sending of a copy of a packet back towards the source, as defined in Section 3 of [RFC9322].¶

Bit 2 "Active" (A-bit): When set, the Active flag indicates that a packet is an active measurement packet rather than a data packet, as defined in Section 3 of [RFC9322].¶

Bit 3 "Fixed-size" (F-bit): When set, the Fixed-size flag indicates that a fixed-size aggregate data rather than a variable-size superimposed data is carried, as defined in Section 5 of this document. As defined in Section 4.4 of [RFC9197], there are two types of IOAM Trace Option, Pre-allocated Trace-Option and Incremental Trace-Option, the F-bit defined in this document can only be used for Pre-allocated Trace-Option. In other words, if the F-bit is set while the IOAM Trace Option-Type indicates it's an Incremental Trace-Option, then the F-bit MUST be ignored by the receiver.¶

5. Fixed-size aggregate data in the IOAM Trace Option

When the IOAM Trace Option is used to carry fixed-size aggregate data, the format of the IOAM Trace Option is shown in figure 3.¶

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Namespace-ID           |NodeLen  | Flags | RemainingLen|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          IOAM Fixed-Data Trace-Type           |  Reserved     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|              Signal Value             |    Locator Metadata   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Namespace-ID:

The same as defined in [RFC9197].¶

NodeLen:

The same as defined in [RFC9197]. MUST be set to 0.¶

Flags:

The same as defined in [RFC9197] and [RFC9322]. This document allocates a single flag as follows:¶

Bit 3

"Fixed-size" (F-bit) (least significant bit). As defined in Section 4 of this document. When set, a fixed-size data space as shown in figure 3 is carried in the IOAM Trace Option.¶

RemainingLen:

The same as defined in [RFC9197]. MUST be set to 0.¶

IOAM Fixed-Data Trace-Type:

The similar as the IOAM Trace-Type defined in Section 4.4.1 of [RFC9197]. There are two differences with the IOAM Trace-Type. One is that only one bit within the 24-bit identifier can be set. If more than one bit is set, then the receiver MUST ignore the IOAM Trace Option and SHOULD log and/or report an error. Another one is that each bit indicates the presence of a fixed-size 4-byte data space, which is composed of a 20-bit Signal Value and a 12-bit Locator Matadata. The definition of Locator Matadata is the same as defined in Section 4.1.3.3 of [I-D.ravi-ippm-csig]. The 24-bit identifier and corresponding Signal Values are defined as follows:¶

Bit 0

Most significant bit. When set, indicates the Signal Value in the data space is Minimum Available Bandwidth - min(ABW), the same as defined in Section 5.1 of [I-D.ravi-ippm-csig].¶

Bit 1

When set, indicates the Signal Value in the data space is Maximum link utilization - max(U/C) or min(ABW/C), the same as defined in Section 5.2 of [I-D.ravi-ippm-csig].¶

Bit 2

When set, indicates the Signal Value in the data space is Maximum Per-hop Delay - max(PD), the same as defined in Section 5.4 of [I-D.ravi-ippm-csig].¶

Bit 3-22

Undefined. These values are available for future assignment in the IOAM Fixed-Data Trace-Type Registry. Every future Signal Value corresponding to one of these bits MUST be 20 bits long. An IOAM encapsulating node MUST set the value of each undefined bit to 0. If an IOAM transit node receives a packet with one or more of these bits set to 1, it MUST ignore these bits and SHOULD log and/or report an error.¶

Bit 23

Reserved; MUST be set to zero upon transmission and be ignored upon receipt. This bit is reserved to allow for future extensions of the IOAM Fixed-Data Trace-Type bit field.¶

6. Security Considerations

As discussed in [RFC9322], IOAM is assumed to be deployed in a restricted administrative domain, thus limiting the scope of the threats above and their effect. However, even given this limited scope, security threats should still be considered and mitigated.¶

Security issues discussed in [RFC9197] apply to this document.¶

7. IANA Considerations

8. Acknowledgements

TBD.¶

9. References