BPM A. Mayer Internet-Draft Univ. of Rome Tor Vergata / CNIT / Common Net Intended status: Experimental S. Salsano Expires: 22 May 2027 Univ. of Rome Tor Vergata / CNIT J. Iurman 6WIND D. R. Lopez Telefonica 18 November 2026 Global Opaque Block for IOAM Pre-allocated Trace Option draft-mayer-bpm-ioam-gob-01 Abstract Extensible metadata carried within the IOAM Pre-allocated Trace Option (PTO) can support packet-level, flow-level, or path-level processing beyond per-node trace data. This document defines the Global Opaque Block (GOB), an extension to the IOAM PTO that introduces a single pre-allocated global metadata region placed at the tail of the option, after the pre-allocated node data space. Since the PTO node data list is populated from the tail of the node data space toward its head, under the control of the RemainingLen field, legacy IOAM transit nodes can never reach the GOB region: the extension is transparent to such nodes by construction, and only the decapsulating node or collector needs to be GOB-aware. The presence and the format of the GOB are bound to the IOAM-Namespace. In the self-describing format, the GOB carries an explicit length and schema identifier in a trailer word; in the compact format, size and schema are implied by the IOAM-Namespace and the block consists of payload only, so that a 4-octet opaque value is carried in exactly 4 octets. In both formats the option is, on the wire, a Pre-allocated Trace Option as specified in RFC 9197, and no change to that specification is required. An optional bit in the PTO header allows a self- describing GOB to be recognized without namespace configuration. The GOB preserves the pre-allocated PTO processing model and can be used to transport path metrics that are updated along the path, or other structured metadata. About This Document This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://eip- home.github.io/ioam-gob/draft-mayer-bpm-ioam-gob.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-mayer-bpm-ioam-gob/. Mayer, et al. Expires 22 May 2027 [Page 1] Internet-Draft IOAM GOB November 2026 Discussion of this document takes place on the BPM Working Group mailing list (mailto:bpm@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/bpm/. Subscribe at https://www.ietf.org/mailman/listinfo/bpm/. Source for this draft and an issue tracker can be found at https://github.com/eip-home/ioam-gob. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 22 May 2027. Copyright Notice Copyright (c) 2026 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 4 3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 6 4. GOB Format . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. PTO Layout with GOB . . . . . . . . . . . . . . . . . . . 7 4.2. GOB Trailer Fields . . . . . . . . . . . . . . . . . . . 7 4.3. Byte-Level Layout . . . . . . . . . . . . . . . . . . . . 8 Mayer, et al. Expires 22 May 2027 [Page 2] Internet-Draft IOAM GOB November 2026 4.4. Namespace-Implied GOB . . . . . . . . . . . . . . . . . . 11 4.5. Optional In-Band Indication: G Bit and Ver Field . . . . 13 5. Length and Alignment Rules . . . . . . . . . . . . . . . . . 14 5.1. GOB Length . . . . . . . . . . . . . . . . . . . . . . . 14 5.2. Internal PTO Offsets . . . . . . . . . . . . . . . . . . 14 5.3. IOAM Option Length and Hop-by-Hop Header Length . . . . . 16 5.4. Alignment Semantics . . . . . . . . . . . . . . . . . . . 17 5.5. Preservation of PTO Semantics . . . . . . . . . . . . . . 17 6. Backward Compatibility . . . . . . . . . . . . . . . . . . . 18 6.1. Structural Transparency to Legacy Transit Nodes . . . . . 18 6.2. Overflow Behavior . . . . . . . . . . . . . . . . . . . . 18 6.3. GOB-Only Mode . . . . . . . . . . . . . . . . . . . . . . 19 6.4. Legacy Decapsulating Nodes and Collectors . . . . . . . . 19 6.5. Path MTU . . . . . . . . . . . . . . . . . . . . . . . . 19 6.6. Applicability to the Two GOB Formats . . . . . . . . . . 19 7. Processing Semantics . . . . . . . . . . . . . . . . . . . . 20 7.1. GOB Mode Determination . . . . . . . . . . . . . . . . . 20 7.2. Ingress Node Behavior . . . . . . . . . . . . . . . . . . 21 7.3. Transit Node Behavior . . . . . . . . . . . . . . . . . . 21 7.4. Egress or Collector Behavior . . . . . . . . . . . . . . 22 8. Relation to PTO Semantics . . . . . . . . . . . . . . . . . . 23 9. Schema Semantics and Extensibility . . . . . . . . . . . . . 23 10. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 24 11. Implementation Status . . . . . . . . . . . . . . . . . . . . 25 12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 14.1. Normative References . . . . . . . . . . . . . . . . . . 28 14.2. Informative References . . . . . . . . . . . . . . . . . 29 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 1. Introduction The IOAM Pre-allocated Trace Option (PTO) defined in [RFC9197] and [RFC9486] provides a structured way to carry in-band operational and telemetry information along a packet path. In the PTO model, the encapsulating node pre-allocates space for node data that can be filled by IOAM-capable nodes along the path. This document defines an extension to the IOAM PTO called the Global Opaque Block (GOB). The GOB is a global metadata region that appears once in the PTO, at the tail of the option, after the pre-allocated node data space. The presence and the format of the GOB are bound to the IOAM-Namespace of the option: a deployment designates GOB- implying namespaces and, for each of them, one of two formats. In the self-describing format, the GOB carries its own length and schema fields in the last 4-octet word of the option, referred to as the GOB Mayer, et al. Expires 22 May 2027 [Page 3] Internet-Draft IOAM GOB November 2026 Trailer. In the compact format, size and schema of the GOB are implied by the IOAM-Namespace, the trailer is omitted, and the block consists of payload only. In both cases the Reserved octet of the PTO header is zero and the option is, on the wire, a Pre-allocated Trace Option as specified in [RFC9197]. As an option, a presence bit in the PTO header (the G bit) indicates a self-describing GOB in the packet itself, so that it can be recognized without namespace configuration. The GOB enables the carriage of structured global metadata within the IOAM PTO, while preserving the existing PTO processing model for per- node trace data. In particular, the GOB can carry path metrics that are updated in flight, such as the aggregation of a per-node measurement along the path, without modifying the semantics of the node data list. The placement of the GOB at the tail of the option makes it transparent to legacy IOAM transit nodes. In the PTO, the node data list is populated from the tail of the pre-allocated node data space toward its head, at offsets derived from the RemainingLen field (Section 4.4.1 of [RFC9197]). A compliant legacy node therefore never writes beyond the node data space and cannot reach the GOB region that follows it. Only the decapsulating node or the collector needs to be GOB-aware. This property is analyzed in detail in Section 6. The GOB is pre-allocated by the encapsulating node. Transit nodes MAY read or update the GOB payload, subject to the bounds established at encapsulation time, but they MUST NOT alter the overall GOB size or the layout of the enclosing PTO option. This document specifies the GOB format, length and alignment rules, and processing behavior for encapsulating, transit, and egress or collector nodes. An implementation and experimental evaluation of the proposed GOB approach within the Linux IOAM framework are described in Section 11. 2. Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. The following terms are used in this document: Mayer, et al. Expires 22 May 2027 [Page 4] Internet-Draft IOAM GOB November 2026 GOB: Global Opaque Block. A structured global metadata region inserted into the IOAM PTO. GOB Trailer: The 4-octet trailer of a self-describing GOB, carried as the last word of the IOAM option and containing the GOB Len and Schema fields. GOB Payload: The content of the GOB. In the self-describing format it immediately precedes the GOB Trailer and its size is determined by the GOB Len field; in the compact format it is the whole GOB and its size is implied by the IOAM-Namespace. Self-describing GOB: A GOB that consists of the GOB Payload followed by the GOB Trailer. Compact GOB: A GOB that consists of the GOB Payload only, with size and schema implied by the IOAM-Namespace. GOB-implying namespace: An IOAM-Namespace designated, by configuration or by registration of its Namespace-ID, as one whose options always carry a GOB, in a given format. Node Data Space: The pre-allocated region that follows the PTO fixed header and hosts the Node Data List. Its size is set at encapsulation time via the RemainingLen field. PTO: The IOAM Pre-allocated Trace Option defined in [RFC9197] and [RFC9486]. Node Data List: The sequence of pre-allocated per-node data slots defined by the PTO format. Ingress Node: The encapsulating node that inserts the IOAM PTO and, when present, allocates and initializes the GOB. Transit Node: An IOAM-capable node along the path that may process the PTO and may read or update the GOB payload. Egress or Collector Node: A node that removes, terminates, exports, or otherwise interprets the IOAM information carried in the packet. Schema: A 24-bit identifier that specifies how the GOB Payload is to be interpreted. Mayer, et al. Expires 22 May 2027 [Page 5] Internet-Draft IOAM GOB November 2026 3. Design Overview The GOB extends the IOAM PTO with a global metadata area that is logically distinct from the per-node node data list. It is intended for metadata that applies to the packet, flow, or path as a whole, rather than to a specific transit node. The GOB appears at most once in a PTO option. When present, it is placed at the tail of the option, after the pre-allocated node data space. In the self-describing format, the GOB consists of a variable-length payload followed by a fixed 4-octet trailer, which is the last word of the IOAM option and carries the GOB length and schema identifier. In the compact format, the GOB consists of payload only, and its size and schema are implied by the IOAM- Namespace. In both formats the GOB is located from the end of the option, using the IOAM option length; any padding used to align the enclosing Hop-by-Hop Options header lies outside the IOAM option and does not affect GOB location. The GOB preserves the pre-allocated nature of the PTO model. The ingress node allocates the GOB space at encapsulation time and determines its size, its schema, and the overall PTO layout. GOB- aware transit nodes MAY modify the contents of the GOB payload, but MUST NOT modify the GOB Trailer. Legacy transit nodes require no modification: they process the node data space according to [RFC9197] and never access the GOB. Whether an option carries a GOB, and in which format, is determined by its IOAM-Namespace (Section 4.4). An optional bit in the PTO header can additionally indicate a self-describing GOB in the packet itself (Section 4.5). The GOB is intended to support structured metadata formats. The use cases experimented so far concern the transport of path metrics, but the mechanism is not restricted to them (Section 10). The addition of the GOB does not change the semantics of the per-node node data list. The GOB complements the PTO by adding a global opaque area while leaving the existing per-node trace structure intact. Mayer, et al. Expires 22 May 2027 [Page 6] Internet-Draft IOAM GOB November 2026 The GOB is located from the end of the IOAM option and does not depend on the encapsulation that carries it. This version of the document specifies length and alignment rules only for the IPv6 Hop- by-Hop Options encapsulation of [RFC9486]; other IOAM encapsulations are outside its scope. As for any Hop-by-Hop option, packets carrying the GOB may be forwarded on a slower path or dropped by nodes that are not configured to process the option ([RFC9673]). The interaction of the GOB with the Loopback and Active flags of [RFC9322] is not specified in this version of the document. 4. GOB Format 4.1. PTO Layout with GOB When the Global Opaque Block (GOB) is present, the IOAM Pre-allocated Trace Option (PTO) is extended by appending a single GOB at the tail of the option, after the pre-allocated Node Data Space. The resulting layout is: 1. PTO fixed header 2. Node Data Space (hosting the Node Data List) 3. GOB Payload 4. GOB Trailer (self-describing format only) 5. Tail padding, if required to satisfy alignment of the enclosing Hop-by-Hop Options header; such padding is outside the IOAM option The presence and the format of the GOB are determined as specified in Section 7.1. If the Namespace-ID is not GOB-implying and the G bit is clear, no GOB is present and PTO processing follows the base PTO format. The GOB appears at most once in a PTO option. 4.2. GOB Trailer Fields The GOB Trailer is 4 octets long and contains the following fields: GOB Len: An 8-bit field that specifies the size of the GOB Payload in units of 4 octets. The value 0 is valid: the GOB then consists of the GOB Trailer only. Schema: A 24-bit field that identifies the format of the GOB Mayer, et al. Expires 22 May 2027 [Page 7] Internet-Draft IOAM GOB November 2026 Payload. The value 0xFFFFFF indicates that no schema is associated with the GOB; in this case, the GOB Payload MUST NOT be interpreted. This mirrors the corresponding rule for the Opaque State Snapshot Schema ID in [RFC9197]. The structure of the Schema value space is defined in Section 9. The total size of the GOB is therefore: GOB_PLEN = GOB_Len * 4 GOB_SIZE = 4 + GOB_PLEN where the 4 additional octets correspond to the GOB Trailer itself. The GOB Payload consists of the GOB_PLEN octets that immediately precede the GOB Trailer. In the compact format the GOB Trailer is absent: GOB_SIZE equals the GOB Payload size implied by the IOAM-Namespace. The Schema field allows the GOB Payload to be interpreted according to a structured format. 4.3. Byte-Level Layout The following figure shows the byte-level layout of the IOAM PTO with a self-describing GOB. In the compact format the GOB Trailer word is absent. The Ver and G bits are zero unless the optional indication of Section 4.5 is used. Mayer, et al. Expires 22 May 2027 [Page 8] Internet-Draft IOAM GOB November 2026 Offset 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 40 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | Hdr Ext Len | PadN Opt | PadN OptLen | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opt Type | IOAM Opt Len | Reserved | IOAM Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Namespace-ID (16b) |NodeLen | Flags |RemainingLen | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IOAM Trace-Type (24b) |Reserved |Ver|G| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Node Data List ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ GOB Payload ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | GOB Len (8b) | Schema (24b) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: IOAM PTO with Global Opaque Block (GOB) at the tail More explicitly, the internal structure is: Mayer, et al. Expires 22 May 2027 [Page 9] Internet-Draft IOAM GOB November 2026 Offset 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 40 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | Hdr Ext Len | PadN Opt | PadN OptLen | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opt Type | IOAM Opt Len | Reserved | IOAM Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ | Namespace-ID (16b) |NodeLen | Flags |RemainingLen | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (A) | IOAM Trace-Type (24b) |Reserved |Ver|G| | X +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ | | | | 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] | | | | | Y +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ | | G ~ GOB Payload ~ O | | B +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ GOB_TRL | GOB Len (8b) | Schema (24b) | Y' +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PadN Opt | PadN OptLen | Padding 16 bits | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Y'' \_________________________8-byte aligned ________________________/ Figure 2: Detailed PTO layout with Node Data Space and tail GOB Mayer, et al. Expires 22 May 2027 [Page 10] Internet-Draft IOAM GOB November 2026 The Node Data Space begins immediately after the PTO fixed header, at the same position as in the base PTO format: this is the write anchor used by all nodes, including legacy ones, to derive the node data recording offset from RemainingLen. The GOB Payload immediately follows the Node Data Space. In the self-describing format, the GOB Trailer is the last 4-octet word of the IOAM option. Any final tail padding is added only to satisfy alignment requirements of the enclosing Hop-by-Hop Options header and lies outside the IOAM option. 4.4. Namespace-Implied GOB The presence and the format of the GOB are bound to the IOAM- Namespace. A deployment designates the IOAM-Namespaces whose options carry a GOB, referred to as GOB-implying namespaces, and for each of them one of the following two formats: Self-describing format: The GOB consists of the GOB Payload followed by the GOB Trailer. The size of the GOB and its schema are carried in the trailer and can differ from packet to packet. Compact format: The GOB consists of the GOB Payload only: the GOB Trailer is not present. The GOB size is implied by the namespace, through configuration or through the registration of the Namespace-ID value; it MUST be a multiple of 4 octets. The sizes of 4, 8, 12 and 16 octets are RECOMMENDED for standardized registrations; other multiples of 4 octets are allowed. The schema of the GOB Payload is likewise implied by the namespace. The following rules apply to both formats: * a GOB-implying namespace is dedicated: every PTO that carries its Namespace-ID MUST carry a GOB in the designated format. In the self-describing format the GOB Len field MAY be zero, in which case the GOB consists of the trailer only; * a GOB-aware node determines the presence and the format of the GOB from the Namespace-ID and MUST NOT rely on the G bit for an option whose Namespace-ID is GOB-implying; * the encapsulating node sets the Reserved octet of the PTO fixed header to zero, as required by [RFC9197]. The only exception is the optional indication of Section 4.5, which is allowed for the self-describing format only: in the compact format the Reserved octet MUST be zero. Mayer, et al. Expires 22 May 2027 [Page 11] Internet-Draft IOAM GOB November 2026 The definition of a GOB-implying namespace, by configuration or by registration, consists of: the GOB format; the version of the GOB format; and, for the compact format, the GOB size in octets and the schema of the GOB Payload. In the compact format, the GOB occupies the last GOB_SIZE octets of the IOAM option, where GOB_SIZE is the implied size, and the validity check of Section 5.2 applies with the implied GOB_SIZE substituted for 4 * (GOB_Len + 1). All other processing rules apply unchanged, with size and schema derived from a Namespace-ID lookup instead of being parsed from the packet. The GOB is mandatory in a GOB-implying namespace because the validity check cannot tell an absent GOB from a present one: if an option were sent without the GOB, the inequality would be satisfied as soon as enough node data has been recorded, and the oldest node data elements, at the tail of the Node Data Space, would be taken for the GOB. A deployment that needs options with and without GOB content under the same Namespace-ID uses the self-describing format with a zero GOB Len, or the optional indication of Section 4.5 under a Namespace-ID that is not GOB-implying. The compact format is intended for standardized compact records and for hardware fast paths: the position and interpretation of the GOB are derived from a single Namespace-ID lookup, without parsing any length information in the packet, and the per-packet overhead of the trailer is removed entirely. In particular, a 4-octet opaque value is carried in exactly 4 octets, which is the most efficient possible transport for it; a 16-octet record is carried in 16 octets. The self-describing format is intended for records whose size or schema can vary from packet to packet. With the Reserved octet at zero, an option of a GOB-implying namespace is, on the wire, a plain Pre-allocated Trace Option whose pre-allocated space extends beyond the RemainingLen window, in both formats: the fields defined by [RFC9197] keep their format and semantics, and the namespace only provides the interpretation context for octets that lie outside all such fields. The mechanism can be deployed without any change to [RFC9197]. The price is that the packet carries no in-band indication of the GOB: correct operation relies on a consistent configuration of the GOB-implying namespaces across the IOAM domain (Section 12). Mayer, et al. Expires 22 May 2027 [Page 12] Internet-Draft IOAM GOB November 2026 4.5. Optional In-Band Indication: G Bit and Ver Field A self-describing GOB can additionally be indicated in the packet itself, by means of the G bit. This indication is optional. It allows a node, a collector or an analysis tool that has no knowledge of the GOB-implying namespaces of a domain to recognize and parse a self-describing GOB, and it allows a self-describing GOB to be carried, on a per-packet basis, under a Namespace-ID that is not GOB- implying. The G bit is carried in the last octet of the second word of the PTO fixed header, defined as Reserved in [RFC9197]. When this indication is in use, the octet is structured as 5 reserved bits, followed by a 2-bit Ver field and by the G bit in the least significant position. G bit: When set to 1, the option carries a self-describing GOB: the last 4-octet word of the option is the GOB Trailer. When set to 0, the option carries no in-band indication: whether a GOB is present, and in which format, depends only on the IOAM-Namespace. The G bit MUST NOT be set in an option that carries a compact GOB or no GOB. Ver: A 2-bit field carrying the version of the GOB extension. This document defines version 0. An encapsulating node that sets the G bit MUST set Ver to 0. A GOB-aware node that receives a PTO with the G bit set and an unsupported Ver value MUST NOT parse or modify the GOB; it still processes the Node Data Space according to [RFC9197]. When the G bit is clear the Ver field is not carried: the version of the GOB format is part of the definition of the GOB-implying namespace. The remaining 5 bits are reserved: they MUST be set to zero by the encapsulating node and ignored on receipt. A set G bit always announces a GOB Trailer. A GOB-aware node that supports the IOAM-Namespace of an option, but has not been configured to treat it as GOB-implying, relies on the G bit alone: this is why the G bit MUST NOT be set with a compact GOB, whose last word would otherwise be parsed as a trailer. An encapsulating node MAY set the G bit in any option that carries a self-describing GOB. It MUST set the G bit when it inserts a self- describing GOB under a Namespace-ID that is not GOB-implying, since the G bit is then the only indication of the GOB. Setting the G bit departs from the requirement of [RFC9197] that the Reserved octet be zero on transmission; see Section 13. Mayer, et al. Expires 22 May 2027 [Page 13] Internet-Draft IOAM GOB November 2026 5. Length and Alignment Rules This section defines the length relations used when the GOB is present in the IOAM PTO. 5.1. GOB Length In the self-describing format, the GOB Payload length is determined by the GOB Len field: GOB_PLEN = GOB_Len * 4 The total GOB size, including the fixed 4-octet GOB Trailer, is: GOB_SIZE = 4 + GOB_PLEN The GOB Len field is set by the ingress node at encapsulation time. In the compact format, GOB_SIZE is the size implied by the IOAM- Namespace and equals the GOB Payload length. Transit nodes MAY modify the content of the GOB Payload, but MUST NOT modify the GOB Trailer and therefore MUST NOT alter the total GOB size. 5.2. Internal PTO Offsets Let: * X be the offset of the start of the Node Data Space, immediately following the PTO fixed header; * Y be the offset immediately following the Node Data Space; * Y' be the offset immediately following the GOB, that is, the end of the IOAM option; * Y'' be the offset of the end of the enclosing Hop-by-Hop Options header, that is, the end of the final tail padding, if any; * RemainingLen_init be the initial value of the RemainingLen field, set by the ingress node at encapsulation time. The offsets X, Y, Y' and Y'' are counted from the first octet that follows the Option Length field of the IOAM option, so that Y' is also the value of that field. The offset 40 in the figures is instead counted from the start of the IPv6 packet, for a Hop-by-Hop Options header that immediately follows the IPv6 header. Mayer, et al. Expires 22 May 2027 [Page 14] Internet-Draft IOAM GOB November 2026 Then: X = (sizeof(IOAM_TLV) - 2) + sizeof(IOAM_PTO_HDR) Y = X + RemainingLen_init * 4 Y' = Y + GOB_SIZE Y'' = HBH_LEN - 6 In these expressions: * sizeof(IOAM_TLV) is 4 octets (Option Type, Option Length, Reserved and IOAM Type), and sizeof(IOAM_TLV) - 2 excludes the Option Type and Option Length octets, which precede the origin of the offsets; * sizeof(IOAM_PTO_HDR) is the fixed PTO header size, 8 octets; * HBH_LEN is the total size of the Hop-by-Hop Options header (Section 5.3), and the 6 octets are those that precede the origin of the offsets in the layout of the figures: Next Header, Hdr Ext Len, a 2-octet PadN option, Option Type and Option Length; * RemainingLen retains its exact meaning from [RFC9197]: it counts only the pre-allocated Node Data Space and does not include the GOB. The Node Data Space starts immediately after the PTO fixed header and spans RemainingLen_init * 4 octets. The GOB occupies the last GOB_SIZE octets of the IOAM option. Let PTO_LEN be the total length of the PTO option content, from the beginning of the PTO fixed header to the end of the GOB, and let RemainingLen be the current (received) value of the field. The following validity check holds for a well-formed option at any point along the path: 4 * (GOB_Len + 1) <= PTO_LEN - sizeof(IOAM_PTO_HDR) - RemainingLen * 4 The check holds with equality at encapsulation time and is preserved along the path, since RemainingLen can only decrease. A GOB-aware node MUST treat the GOB as invalid if this check fails. In the compact format the same check applies with the implied GOB_SIZE in place of 4 * (GOB_Len + 1). Mayer, et al. Expires 22 May 2027 [Page 15] Internet-Draft IOAM GOB November 2026 5.3. IOAM Option Length and Hop-by-Hop Header Length The IOAM Option Length field MUST be set to Y': it covers the option up to the end of the GOB and does not include the padding that follows. That padding, when needed to reach Y'', is carried in a separate Pad1 or PadN option. The enclosing Hop-by-Hop Options header length is derived from the total size of the header, including: * the 2-octet Next Header and Hdr Ext Len fields; * any PadN option used to align the start of the IOAM option; * the IOAM option itself; * any final tail padding (Pad1 or PadN option). Let HBH_LEN denote the total Hop-by-Hop Options header size in octets. For the layout of the figures, in which a 2-octet PadN option precedes the IOAM option and the header carries no other option: HBH_LEN = ALIGN(4 + sizeof(IOAM_TLV) + sizeof(IOAM_PTO_HDR) + RemainingLen_init * 4 + GOB_SIZE, 8) where the leading 4 octets account for: * 2 octets for Next Header and Hdr Ext Len; * 2 octets for the PadN option that aligns the IOAM option start. A different arrangement of the options in the header changes the leading term accordingly. The IPv6 Hdr Ext Len field is encoded as: Hdr Ext Len = HBH_LEN / 8 - 1 For example, with 20 octets of pre-allocated node data (RemainingLen_init = 5) and a 16-octet compact GOB, the IOAM Option Length is 46 and HBH_LEN is ALIGN(52, 8) = 56: the IOAM option is followed by a 4-octet PadN option. With a 4-octet compact GOB, the IOAM Option Length is 34 and HBH_LEN is 40, with no tail padding. Mayer, et al. Expires 22 May 2027 [Page 16] Internet-Draft IOAM GOB November 2026 5.4. Alignment Semantics As specified in [RFC8200], the Hop-by-Hop Options header is encoded so that its total length is a multiple of 8 octets, and the Hdr Ext Len field carries that length in 8-octet units, not including the first 8 octets. The final tail padding used to align the enclosing Hop-by-Hop Options header to an 8-octet boundary is not part of the GOB and is not part of the Node Data List. More specifically: * Y identifies the end of the Node Data Space; * Y' identifies the end of the GOB and of the IOAM option; * Y'' identifies the aligned end, including padding that lies outside the IOAM option. The difference between Y' and Y'' is due only to final alignment padding and does not carry GOB or node-data semantics. The GOB is always located relative to the end of the IOAM option as given by the IOAM option length, never relative to the end of the Hop-by-Hop Options header. 5.5. Preservation of PTO Semantics The presence of the GOB does not alter the semantics of RemainingLen or the pre-allocated nature of the PTO. In particular, RemainingLen counts only the Node Data Space, exactly as in [RFC9197], and the Node Data Space starts at the same offset as in the base PTO format. The ingress node determines, at encapsulation time: * the size of the Node Data Space, via RemainingLen_init; * the GOB size; * the IOAM option length and the final tail padding. The following budget constraints apply: * RemainingLen_init <= 127, due to the 7-bit RemainingLen field; note that the GOB does not consume this budget; Mayer, et al. Expires 22 May 2027 [Page 17] Internet-Draft IOAM GOB November 2026 * the total PTO option content, sizeof(IOAM_PTO_HDR) + RemainingLen_init * 4 + GOB_SIZE, is bounded by the length limits of the enclosing encapsulation (approximately 253 octets for the IPv6 Hop-by-Hop encapsulation of [RFC9486]). Transit nodes operate only within the pre-allocated bounds of the Node Data Space and, for GOB-aware nodes, of the GOB Payload, and MUST NOT change the overall layout of the PTO option. In this way, the pre-allocated model of the PTO is preserved while extending the option with a structured global metadata region. 6. Backward Compatibility This section shows that the GOB is transparent to legacy IOAM transit nodes, that is, nodes that implement [RFC9197] without GOB support. 6.1. Structural Transparency to Legacy Transit Nodes In the Pre-allocated Trace-Option, the node data list is populated from the tail of the data space toward its head. Section 4.4.1 of [RFC9197] specifies that RemainingLen "is used to derive the offset in data space to record the node data element", and that "the recording of the node data element would start from RemainingLen - NodeLen - size of (opaque snapshot) in 4-octet units". A compliant transit node therefore only writes within the interval: [X + (RemainingLen - NodeLen - SoS) * 4, X + RemainingLen * 4) where X is the start of the data space (Section 5.2) and SoS is the size of the Opaque State Snapshot, if present. Since RemainingLen starts at RemainingLen_init and can only decrease, no compliant node can ever write at or beyond X + RemainingLen_init * 4, which is exactly where the GOB begins. The GOB is therefore unreachable by legacy transit nodes, for any number of IOAM hops on the path. 6.2. Overflow Behavior When a transit node finds that RemainingLen is smaller than the space required for its node data element, it sets the Overflow bit (O-bit) and does not record any data ([RFC9197]). With the GOB at the tail of the option, this behavior is preserved exactly: overflow is signaled precisely when the Node Data Space is exhausted, and the GOB is not affected. The ingress node SHOULD set RemainingLen_init = h * NodeLen for the expected number h of IOAM-capable hops; if the path contains more IOAM hops than expected, the additional hops do not record data and the O-bit is set, while the GOB remains intact. Mayer, et al. Expires 22 May 2027 [Page 18] Internet-Draft IOAM GOB November 2026 The use of the variable-length Opaque State Snapshot (bit 22 of the IOAM Trace-Type) consumes RemainingLen faster than the fixed NodeLen accounting and thus affects the dimensioning of RemainingLen_init, but does not affect the integrity of the GOB. 6.3. GOB-Only Mode An ingress node MAY set RemainingLen_init = 0, resulting in an option that carries only the GOB and no node data. In this case, a legacy IOAM transit node finds no room for its node data element and sets the O-bit (or skips the option); the GOB is not affected. In this mode the O-bit is set by the first transit node that processes the option and carries no information. A deployment can avoid this by using, for GOB-only options, a Namespace-ID that is not configured on legacy nodes: a node that does not support the IOAM- Namespace does not process the option ([RFC9197]). 6.4. Legacy Decapsulating Nodes and Collectors A legacy decapsulating node removes the whole IOAM option; the GOB is lost but packet forwarding is unaffected. A legacy collector that parses the raw option content and assumes that node data extends to the end of the option would misinterpret the GOB as the oldest node data elements. Within a GOB deployment domain, the decapsulating node and the collector are GOB-aware by definition, so this situation only arises from misconfiguration. Note that, in that case, the size of the region interpreted as node data would generally not be an integer multiple of NodeLen * 4, which provides a detection opportunity. 6.5. Path MTU Section 4.4.1 of [RFC9197] relates RemainingLen to the path MTU for the node data space. An ingress node inserting a GOB MUST also account for GOB_SIZE octets when assessing path MTU constraints. 6.6. Applicability to the Two GOB Formats The analysis in this section applies to both GOB formats: the GOB occupies the same tail region, outside the RemainingLen window, regardless of whether its size is described by the GOB Trailer or implied by the IOAM-Namespace. When the Reserved octet is zero, that is, in every option of a GOB-implying namespace that does not use the optional indication of Section 4.5, the option is additionally fully compliant with [RFC9197] as currently specified. Mayer, et al. Expires 22 May 2027 [Page 19] Internet-Draft IOAM GOB November 2026 A GOB-aware node on which the Namespace-ID is configured but not designated as GOB-implying, and that finds the G bit clear, processes the option as a base PTO: as a transit node it behaves exactly as a legacy node and cannot reach the GOB; as a decapsulating node or collector it is subject to the considerations of Section 6.4. 7. Processing Semantics 7.1. GOB Mode Determination A GOB-aware node that supports the IOAM-Namespace of a received PTO determines how to process the tail of the option as follows: 1. If the Namespace-ID is configured on the node as a GOB-implying namespace with the compact format, the option carries a compact GOB: payload only, in the last GOB_SIZE octets of the option, with size and schema as configured for the namespace. The G bit is not examined. 2. If the Namespace-ID is configured on the node as a GOB-implying namespace with the self-describing format, the option carries a self-describing GOB: the last 4-octet word of the option is the GOB Trailer, carrying the GOB Len and Schema fields. The G bit is not examined. 3. Otherwise, the node examines the G bit. If the G bit is set, the option carries a self-describing GOB, as in the previous case. If the G bit is clear, the option carries no GOB and is processed as a base PTO according to [RFC9197]. Namespace-ID of the received PTO | +-- GOB-implying, compact format | -> payload only, last GOB_SIZE octets; size and schema | from the namespace; G bit not examined | +-- GOB-implying, self-describing format | -> GOB Trailer (GOB Len, Schema) in the last word; | G bit not examined | +-- not GOB-implying -> examine the G bit G = 1 -> self-describing GOB, trailer in the last word G = 0 -> no GOB: base PTO (RFC 9197) Figure 3: GOB mode determination at a GOB-aware node Mayer, et al. Expires 22 May 2027 [Page 20] Internet-Draft IOAM GOB November 2026 The Namespace-ID takes precedence over the G bit. In particular, if an option of a GOB-implying namespace with the compact format is received with the G bit set, the G bit is ignored and the option is parsed as carrying a compact GOB. A node that does not support the IOAM-Namespace of the option does not process its IOAM data fields, as specified in [RFC9197], and is outside the scope of this procedure. 7.2. Ingress Node Behavior An ingress node that inserts a GOB into the PTO: * MUST allocate the full GOB space at the tail of the option at encapsulation time: GOB Payload and GOB Trailer in the self- describing format, GOB Payload of the implied size in the compact format; * in the self-describing format, MUST set the GOB Len and Schema fields in the GOB Trailer; * MUST insert the GOB in every option that carries a GOB-implying Namespace-ID; * MUST set the G bit to 1 and the Ver field to 0 if the Namespace-ID is not GOB-implying; MAY do so for a self-describing GOB in a GOB- implying namespace; MUST leave the Reserved octet at zero in all other cases; * MUST set RemainingLen_init according to the size of the Node Data Space only, without including the GOB (e.g., RemainingLen_init = h * NodeLen for h expected IOAM hops); * MUST determine the final PTO layout, including the Node Data Space, the GOB, and any required tail padding; * MUST account for the GOB size when assessing path MTU constraints. The ingress node MAY initialize the GOB Payload with structured metadata, zero values, or other schema-defined initial content. 7.3. Transit Node Behavior Legacy IOAM transit nodes require no modification: they process the Node Data Space according to the procedures of [RFC9197] and, as shown in Section 6, never access the GOB. A GOB-aware transit node that processes a PTO containing a GOB: Mayer, et al. Expires 22 May 2027 [Page 21] Internet-Draft IOAM GOB November 2026 * MUST verify the validity check of Section 5.2 before accessing the GOB; * MAY read the GOB Payload; * MAY update fields within the GOB Payload, subject to the schema in use; * MUST NOT modify the GOB Trailer (GOB Len and Schema fields), when present; * MUST NOT modify PTO fixed-header fields, other than Flags and RemainingLen as allowed by [RFC9197]; * MUST NOT change the overall size or layout of the PTO option. A transit node MUST confine any GOB update to the pre-allocated GOB Payload bounds established by the ingress node. Each packet carries its own GOB, which GOB-aware nodes update one after the other, in path order: there are no concurrent writers of the same GOB. This document provides no further guarantee. In particular, a node cannot tell which upstream nodes have updated the GOB Payload, since legacy nodes and nodes that do not support the schema leave it unchanged. A schema whose payload is updated by more than one node SHOULD define update rules that remain meaningful under these conditions, for example commutative and associative aggregation functions. 7.4. Egress or Collector Behavior An egress or collector node that processes a PTO carrying a GOB locates it from the end of the IOAM option. In the self-describing format, the GOB Trailer is the last 4-octet word of the option, and the GOB Payload is the GOB_PLEN octets that immediately precede it. In the compact format, the GOB Payload is the last GOB_SIZE octets of the option. The node data recorded along the path occupies the region between X + RemainingLen * 4, where RemainingLen is the received value, and the start of the GOB Payload. Such a node: * MUST verify the validity check of Section 5.2; if the check fails, the GOB MUST be considered invalid and MUST NOT be parsed; * MAY parse the GOB Payload according to the Schema field, or to the schema implied by the IOAM-Namespace; Mayer, et al. Expires 22 May 2027 [Page 22] Internet-Draft IOAM GOB November 2026 * MAY export the GOB content as structured metadata or as raw bytes; * MAY ignore the GOB Payload if the Schema value is unknown or not supported. If the Schema value is unknown, the node MUST NOT infer semantics beyond the presence and length of the GOB. The export of the GOB content to a collector, for example by means of IPFIX [RFC7011], is outside the scope of this document. 8. Relation to PTO Semantics The GOB preserves the pre-allocated semantics of the IOAM PTO. The ingress node continues to determine the overall PTO allocation at encapsulation time. This includes the size of the node data list and, when present, the size of the GOB. Transit nodes operate only within the pre-allocated space and do not change the overall layout of the PTO. The Node Data List retains its existing semantics and processing model. The GOB does not redefine the per-node trace data structure and does not replace the node data list. Instead, it introduces a distinct global metadata region placed after the node data space, at the tail of the option. In this sense, the pre-allocated nature of the PTO applies both to the per-node trace space and to the GOB. The GOB extends the PTO with a global opaque area while preserving the original PTO processing model. 9. Schema Semantics and Extensibility The Schema field identifies the format of the GOB Payload. As for the Opaque State Snapshot Schema ID of [RFC9197], the Schema field is interpreted within the context of the IOAM-Namespace indicated by the Namespace-ID field of the enclosing PTO. A Schema value may identify: * a set of path metrics, for example the aggregates of a per-node measurement; * another structured metadata format defined by a specification; * a locally defined or domain-specific format. Mayer, et al. Expires 22 May 2027 [Page 23] Internet-Draft IOAM GOB November 2026 This document defines the GOB container, but does not define the internal syntax of individual schema-specific payloads. The semantics of the GOB Payload therefore depend on the specification associated with the Schema value in use. Following the model used by [RFC9197] for the Namespace-ID, the 24-bit Schema value space is divided into two subranges: * an operator-assigned range from 0x000000 to 0x7FFFFF, and * an IANA-assigned range from 0x800000 to 0xFFFFFE. The operator-assigned range is domain specific and managed by the network operator: values in this range identify locally defined schemas, whose meaning is established by configuration within the deployment domain and within the context of the IOAM-Namespace in use. No value in this range has a preassigned meaning. The IANA-assigned range is intended for globally defined schemas specified in future documents, allowing new and interoperable GOB payload formats. In the compact format (Section 4.4), no Schema field is carried in the packet: the schema is bound to the IOAM-Namespace by configuration or registration, and the rules on the Schema field in this section apply to the self-describing format only. The Schema value 0xFFFFFF is reserved and indicates that no schema is associated with the GOB, consistent with the Opaque State Snapshot rule of [RFC9197], where "the Schema ID MUST be set to 0xFFFFFF to mean no schema". An encapsulating node that inserts a GOB without an associated schema MUST set the Schema field to 0xFFFFFF. When the Schema field is 0xFFFFFF, nodes MUST NOT interpret the GOB Payload beyond its presence and length. Future specifications that define allocation policies for Schema values MUST preserve this reservation. 10. Use Cases The use cases implemented and experimented so far concern the transport of path metrics: values that describe the path as a whole and are updated by the nodes along it, such as the minimum, maximum, sum and count of a per-node metric, or the on-path delay of the transit nodes (Section 11). Mayer, et al. Expires 22 May 2027 [Page 24] Internet-Draft IOAM GOB November 2026 The GOB is a general container for structured metadata, and other uses are possible. One potential further use is the carriage of Extensible In-band Processing (EIP) Information Elements [draft-eip-arch]; earlier work on the integration of EIP into the IOAM framework is described in [salsano25cscn]. This document does not specify it and requests no schema registration for it. 11. Implementation Status [RFC Editor: please remove this section before publication.] This section records the status of known implementations of the mechanism defined by this specification, following the approach suggested by [RFC7942]. An open source implementation of the GOB in the Linux kernel IOAM subsystem is available. It covers the self-describing format indicated by the G bit (tail placement of the GOB, GOB Trailer as the last word of the option, unmodified RemainingLen semantics) and the compact format in a GOB-implying namespace, with the implied GOB size configured per IOAM-Namespace, no GOB Trailer and the Reserved octet left at zero. The self-describing format in a GOB-implying namespace, with the G bit clear, is not yet implemented. The implementation covers encapsulation, transit and decapsulation processing, with the corresponding iproute2 support, and includes a dedicated eBPF program type for programmable processing of the GOB Payload. The eBPF program context exposes only the GOB Payload, so that the GOB Trailer is not addressable by the program: the corresponding "MUST NOT modify the GOB Trailer" requirement of this document is enforced at the eBPF verifier level. The compact format was implemented and first exercised during the IETF 127 hackathon, in the Linux kernel and in iproute2 (branches ioam6-gob_v4 of the repositories used by the environment referenced below). Both implemented cases were run with 16-octet and 4-octet GOBs and 20 octets of pre-allocated node data, including a path through a node running an unmodified Linux kernel: that node recorded its node data and left the GOB intact. With a 4-octet GOB, the IOAM option is 34 octets long in the compact format and 38 octets in the self-describing format, and the Hop-by-Hop Options header is 40 and 48 octets long, respectively. With a 16-octet GOB, the IOAM option is 46 and 50 octets long, and the Hop-by-Hop Options header is 56 octets long in both cases. These tests are preliminary: single runs, ICMPv6 traffic only, no error cases. A second use case, the measurement of on-path delay, was exercised during the same hackathon: the GOB carries a time reference written by the encapsulating node and the delay measured by transit nodes, Mayer, et al. Expires 22 May 2027 [Page 25] Internet-Draft IOAM GOB November 2026 and the decapsulating node collects and exports the values. It was run with node data and in the GOB-Only mode. The GOB-Only mode was exercised in the compact format only, with GOBs of 8, 16 and 24 octets (Hop-by-Hop Options header of 24, 32 and 40 octets), one run per configuration. A complete development and test environment, including build instructions and an interactive demonstration of in-flight aggregation (minimum, maximum, sum and count of a per-node metric carried in the GOB Payload), is available at https://github.com/netgroup/ioam-gob-kernel-playground. The demonstration was presented at the IETF 126 hackathon, within the project "In-Network Telemetry Aggregation Using new IOAM extensions". An earlier implementation and experimental evaluation, based on draft-mayer-ioam-gob-01, a predecessor of this document (with the GOB placed at the head of the option), is described in [mayer26noms]. 12. Security Considerations The GOB introduces a global metadata region that may be read or modified by on-path nodes. Unauthorized access to, or modification of, the GOB Payload can affect telemetry interpretation, service behavior, or policy enforcement. For this reason, deployments of the GOB SHOULD be limited to controlled or trusted domains, consistent with the limited-domain assumptions often applied to IOAM deployments. The GOB Trailer is not protected by any checksum or authentication mechanism. A misbehaving or malicious on-path node could corrupt the GOB Trailer; in particular, an inflated GOB Len value could cause a decapsulating node to interpret recorded node data as GOB Payload. The validity check of Section 5.2 rejects GOB sizes that are inconsistent with the option length and with the current RemainingLen value, and MUST be applied by every GOB-aware node before parsing the GOB. The check is evaluated against the current RemainingLen value and becomes less strict as node data is recorded along the path: by itself it does not detect a GOB Len value that overlaps node data already recorded. A decapsulating node or collector SHOULD therefore cross-check the received GOB Len and Schema values against per- namespace configuration, when available. When the Opaque State Snapshot is not in use, it SHOULD also verify that the size of the region between X + RemainingLen * 4 and the start of the GOB Payload is an integer multiple of NodeLen * 4 octets. The compact format is not exposed to this issue, since the GOB size is not carried in the packet. Mayer, et al. Expires 22 May 2027 [Page 26] Internet-Draft IOAM GOB November 2026 When the presence of the GOB is determined by the IOAM-Namespace alone, the packet carries no in-band indication of the GOB: its presence and format, and in the compact format its size and schema, are known only through the configuration of the GOB-implying namespace, and a node cannot detect a configuration mismatch from the packet. An encapsulating node that uses a GOB-implying Namespace-ID without allocating the GOB causes downstream GOB-aware nodes to read, and possibly overwrite, recorded node data as GOB content, once the validity check of Section 5.2 is satisfied. A decapsulating node or collector that does not treat the namespace as GOB-implying interprets the GOB as node data. Deployments need to ensure that the GOB-implying namespaces, with their formats and sizes, are configured consistently on all GOB-aware nodes of the IOAM domain. The security implications of the GOB Payload also depend on the Schema in use. Some schemas may carry purely observational metadata, while others may influence packet treatment or convey more sensitive information. Schema-specific specifications SHOULD describe any additional confidentiality, integrity, or authorization requirements. 13. IANA Considerations This document defines the Global Opaque Block (GOB) as an extension to the IOAM Pre-allocated Trace Option. As discussed in Section 6, the GOB is transparent to legacy IOAM transit nodes: it is placed outside the region that such nodes can address, and the semantics of all existing PTO fields are preserved. The mechanism defined in this document, in which the presence and the format of the GOB are bound to the IOAM-Namespace (Section 4.4), uses the existing codepoint of the IOAM Pre-allocated Trace-Option and does not change its format or its processing: the Reserved octet is zero and all fields keep their meaning. It relies on values of the existing "IOAM Namespace-ID" registry, where each GOB-implying value specifies the GOB format and, for the compact format, the implied GOB size and schema. A future version of this document may request Namespace-ID registrations for standardized compact records. The optional G bit and Ver field of Section 4.5 are placed in the Reserved octet of the PTO fixed header. Since [RFC9197] requires transit nodes to ignore the Reserved field, their use does not affect legacy transit behavior. However, [RFC9197] also requires the encapsulating node to set the Reserved field to zero: standardizing this optional indication requires a formal update of the definition of the Reserved octet of the PTO, allocating its least significant bit as the G bit and the two preceding bits as the Ver field, while the remaining five bits stay reserved. Mayer, et al. Expires 22 May 2027 [Page 27] Internet-Draft IOAM GOB November 2026 As a subordinate fallback, should the update of the PTO Reserved octet definition not be acceptable, a new codepoint can be defined for a PTO variant that carries the G bit and the Ver field. Note, however, that a legacy transit node that does not recognize the new codepoint would skip the option entirely, instead of processing the node data space as it does under the existing codepoint. The mechanism of Section 4.4 does not depend on either choice. In addition, Section 9 divides the 24-bit Schema value space into an operator-assigned range (0x000000 to 0x7FFFFF) and an IANA-assigned range (0x800000 to 0xFFFFFE), with 0xFFFFFF reserved to indicate that no schema is associated with the GOB. A future version of this document is expected to request the creation of a "GOB Schema Identifiers" registry covering the IANA-assigned range. This version of the document does not request IANA actions. Future versions may request updates to the relevant IOAM [IANA-ioam-types] or IPv6 [IANA-ipv6-parameters] registries, depending on whether, and how, the optional indication is standardized. 14. References 14.1. Normative References [IANA-ioam-types] IANA, "IOAM Data Field Types", n.d., . [IANA-ipv6-parameters] IANA, "Internet Protocol Version 6 (IPv6) Parameters", n.d., . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", STD 86, RFC 8200, DOI 10.17487/RFC8200, July 2017, . Mayer, et al. Expires 22 May 2027 [Page 28] Internet-Draft IOAM GOB November 2026 [RFC9197] Brockners, F., Ed., Bhandari, S., Ed., and T. Mizrahi, Ed., "Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)", RFC 9197, DOI 10.17487/RFC9197, May 2022, . [RFC9486] Bhandari, S., Ed. and F. Brockners, Ed., "IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)", RFC 9486, DOI 10.17487/RFC9486, September 2023, . 14.2. Informative References [draft-eip-arch] Salsano, S., ElBakoury, H., and D. R. Lopez, "Extensible In-band Processing (EIP) Architecture and Framework", Internet-Draft draft-eip-arch, 2026, . [mayer26noms] Mayer, A., Salsano, S., Sidoretti, G., Loreti, P., Bracciale, L., ElBakoury, H., and D. R. Lopez, "Integrating the Global Opaque Block into the IOAM Framework: A Unified Approach to In-Packet Telemetry and Metadata", IEEE/IFIP NOMS 2026, 2026. [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", STD 77, RFC 7011, DOI 10.17487/RFC7011, September 2013, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . [RFC9322] Mizrahi, T., Brockners, F., Bhandari, S., Gafni, B., and M. Spiegel, "In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags", RFC 9322, DOI 10.17487/RFC9322, November 2022, . [RFC9673] Hinden, R. and G. Fairhurst, "IPv6 Hop-by-Hop Options Processing Procedures", RFC 9673, DOI 10.17487/RFC9673, October 2024, . Mayer, et al. Expires 22 May 2027 [Page 29] Internet-Draft IOAM GOB November 2026 [salsano25cscn] Salsano, S., Mayer, A., Sidoretti, G., Loreti, P., Bracciale, L., ElBakoury, H., and D. R. Lopez, "Integrating Extensible In-Band Processing (EIP) into the IOAM Framework: A Unified Approach to In-Packet Telemetry and Metadata", IEEE CSCN 2025 Conference, 2025. Acknowledgments The authors thank Alexander Clemm, Ramon Bister and Severin Dellsperger for the discussions on the relationship between the GOB and the IOAM Aggregation Trace and Template Options, and for hosting the GOB demonstration within their IETF 126 Hackathon project. The authors also thank Giulio Sidoretti for his contribution to the Linux implementation, and Hesham ElBakoury for his detailed review of version -00 of this document. Authors' Addresses Andrea Mayer Univ. of Rome Tor Vergata / CNIT / Common Net Email: andrea.mayer@uniroma2.it Stefano Salsano Univ. of Rome Tor Vergata / CNIT Email: stefano.salsano@uniroma2.it Justin Iurman 6WIND Email: justin.iurman@gmail.com Diego R. Lopez Telefonica Email: diego.r.lopez@telefonica.com Mayer, et al. Expires 22 May 2027 [Page 30]