<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-mayer-bpm-ioam-gob-01" category="exp" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="IOAM GOB">Global Opaque Block for IOAM Pre-allocated Trace Option</title>
    <seriesInfo name="Internet-Draft" value="draft-mayer-bpm-ioam-gob-01"/>
    <author initials="A." surname="Mayer" fullname="Andrea Mayer">
      <organization>Univ. of Rome Tor Vergata / CNIT / Common Net</organization>
      <address>
        <email>andrea.mayer@uniroma2.it</email>
      </address>
    </author>
    <author initials="S." surname="Salsano" fullname="Stefano Salsano">
      <organization>Univ. of Rome Tor Vergata / CNIT</organization>
      <address>
        <email>stefano.salsano@uniroma2.it</email>
      </address>
    </author>
    <author initials="J." surname="Iurman" fullname="Justin Iurman">
      <organization>6WIND</organization>
      <address>
        <email>justin.iurman@gmail.com</email>
      </address>
    </author>
    <author initials="D. R." surname="Lopez" fullname="Diego R. Lopez">
      <organization>Telefonica</organization>
      <address>
        <email>diego.r.lopez@telefonica.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <workgroup>BPM</workgroup>
    <keyword>IOAM</keyword>
    <keyword>IPv6</keyword>
    <keyword>In-band telemetry</keyword>
    <keyword>Metadata</keyword>
    <abstract>
      <?line 103?>

<t>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.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://eip-home.github.io/ioam-gob/draft-mayer-bpm-ioam-gob.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-mayer-bpm-ioam-gob/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        BPM Working Group mailing list (<eref target="mailto:bpm@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/bpm/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/bpm/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/eip-home/ioam-gob"/>.</t>
    </note>
  </front>
  <middle>
    <?line 131?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The IOAM Pre-allocated Trace Option (PTO) defined in <xref target="RFC9197"/> and
<xref target="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.</t>
      <t>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
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 <xref target="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.</t>
      <t>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.</t>
      <t>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
<xref target="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 <xref target="backward-compatibility"/>.</t>
      <t>The GOB is pre-allocated by the encapsulating node. Transit nodes <bcp14>MAY</bcp14>
read or update the GOB payload, subject to the bounds established at
encapsulation time, but they <bcp14>MUST NOT</bcp14> alter the overall GOB size or the
layout of the enclosing PTO option.</t>
      <t>This document specifies the GOB format, length and alignment rules, and
processing behavior for encapsulating, transit, and egress or collector
nodes.</t>
      <t>An implementation and experimental evaluation of the proposed GOB approach
within the Linux IOAM framework are described in <xref target="implementation-status"/>.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>The following terms are used in this document:</t>
      <dl>
        <dt>GOB:</dt>
        <dd>
          <t>Global Opaque Block. A structured global metadata region inserted into
the IOAM PTO.</t>
        </dd>
        <dt>GOB Trailer:</dt>
        <dd>
          <t>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.</t>
        </dd>
        <dt>GOB Payload:</dt>
        <dd>
          <t>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.</t>
        </dd>
        <dt>Self-describing GOB:</dt>
        <dd>
          <t>A GOB that consists of the GOB Payload followed by the GOB Trailer.</t>
        </dd>
        <dt>Compact GOB:</dt>
        <dd>
          <t>A GOB that consists of the GOB Payload only, with size and schema
implied by the IOAM-Namespace.</t>
        </dd>
        <dt>GOB-implying namespace:</dt>
        <dd>
          <t>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.</t>
        </dd>
        <dt>Node Data Space:</dt>
        <dd>
          <t>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.</t>
        </dd>
        <dt>PTO:</dt>
        <dd>
          <t>The IOAM Pre-allocated Trace Option defined in <xref target="RFC9197"/> and
<xref target="RFC9486"/>.</t>
        </dd>
        <dt>Node Data List:</dt>
        <dd>
          <t>The sequence of pre-allocated per-node data slots defined by the PTO
format.</t>
        </dd>
        <dt>Ingress Node:</dt>
        <dd>
          <t>The encapsulating node that inserts the IOAM PTO and, when present,
allocates and initializes the GOB.</t>
        </dd>
        <dt>Transit Node:</dt>
        <dd>
          <t>An IOAM-capable node along the path that may process the PTO and may
read or update the GOB payload.</t>
        </dd>
        <dt>Egress or Collector Node:</dt>
        <dd>
          <t>A node that removes, terminates, exports, or otherwise interprets the
IOAM information carried in the packet.</t>
        </dd>
        <dt>Schema:</dt>
        <dd>
          <t>A 24-bit identifier that specifies how the GOB Payload is to be
interpreted.</t>
        </dd>
      </dl>
    </section>
    <section anchor="design-overview">
      <name>Design Overview</name>
      <t>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.</t>
      <t>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.</t>
      <t>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
<bcp14>MAY</bcp14> modify the contents of the GOB payload, but <bcp14>MUST NOT</bcp14> modify the GOB
Trailer. Legacy transit nodes require no modification: they process the
node data space according to <xref target="RFC9197"/> and never access the GOB.</t>
      <t>Whether an option carries a GOB, and in which format, is determined by
its IOAM-Namespace (<xref target="namespace-implied"/>). An optional bit in the PTO
header can additionally indicate a self-describing GOB in the packet
itself (<xref target="g-bit-ver"/>).</t>
      <t>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 (<xref target="use-cases"/>).</t>
      <t>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.</t>
      <t>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 <xref target="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 (<xref target="RFC9673"/>). The interaction of
the GOB with the Loopback and Active flags of <xref target="RFC9322"/> is not
specified in this version of the document.</t>
    </section>
    <section anchor="gob-format">
      <name>GOB Format</name>
      <section anchor="pto-layout-with-gob">
        <name>PTO Layout with GOB</name>
        <t>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.</t>
        <t>The resulting layout is:</t>
        <ol spacing="normal" type="1"><li>
            <t>PTO fixed header</t>
          </li>
          <li>
            <t>Node Data Space (hosting the Node Data List)</t>
          </li>
          <li>
            <t>GOB Payload</t>
          </li>
          <li>
            <t>GOB Trailer (self-describing format only)</t>
          </li>
          <li>
            <t>Tail padding, if required to satisfy alignment of the enclosing
Hop-by-Hop Options header; such padding is outside the IOAM option</t>
          </li>
        </ol>
        <t>The presence and the format of the GOB are determined as specified in
<xref target="mode-determination"/>. 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.</t>
        <t>The GOB appears at most once in a PTO option.</t>
      </section>
      <section anchor="gob-trailer-fields">
        <name>GOB Trailer Fields</name>
        <t>The GOB Trailer is 4 octets long and contains the following fields:</t>
        <dl>
          <dt>GOB Len:</dt>
          <dd>
            <t>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.</t>
          </dd>
          <dt>Schema:</dt>
          <dd>
            <t>A 24-bit field that identifies the format of the GOB Payload. The
value 0xFFFFFF indicates that no schema is associated with the GOB;
in this case, the GOB Payload <bcp14>MUST NOT</bcp14> be interpreted. This mirrors
the corresponding rule for the Opaque State Snapshot Schema ID in
<xref target="RFC9197"/>. The structure of the Schema value space is defined in
<xref target="schema-semantics"/>.</t>
          </dd>
        </dl>
        <t>The total size of the GOB is therefore:</t>
        <artwork><![CDATA[
GOB_PLEN = GOB_Len * 4
GOB_SIZE = 4 + GOB_PLEN
]]></artwork>
        <t>where the 4 additional octets correspond to the GOB Trailer itself. The
GOB Payload consists of the <tt>GOB_PLEN</tt> octets that immediately precede
the GOB Trailer.</t>
        <t>In the compact format the GOB Trailer is absent: <tt>GOB_SIZE</tt> equals the
GOB Payload size implied by the IOAM-Namespace.</t>
        <t>The Schema field allows the GOB Payload to be interpreted according to
a structured format.</t>
      </section>
      <section anchor="byte-level-layout">
        <name>Byte-Level Layout</name>
        <t>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
<xref target="g-bit-ver"/> is used.</t>
        <figure>
          <name>IOAM PTO with Global Opaque Block (GOB) at the tail</name>
          <artwork><![CDATA[
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                             |
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
        <t>More explicitly, the internal structure is:</t>
        <figure>
          <name>Detailed PTO layout with Node Data Space and tail GOB</name>
          <artwork><![CDATA[
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 ________________________/
]]></artwork>
        </figure>
        <t>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.</t>
      </section>
      <section anchor="namespace-implied">
        <name>Namespace-Implied GOB</name>
        <t>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:</t>
        <dl>
          <dt>Self-describing format:</dt>
          <dd>
            <t>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.</t>
          </dd>
          <dt>Compact format:</dt>
          <dd>
            <t>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 <bcp14>MUST</bcp14> be a multiple of 4 octets. The sizes of 4, 8, 12 and 16
octets are <bcp14>RECOMMENDED</bcp14> for standardized registrations; other
multiples of 4 octets are allowed. The schema of the GOB Payload is
likewise implied by the namespace.</t>
          </dd>
        </dl>
        <t>The following rules apply to both formats:</t>
        <ul spacing="normal">
          <li>
            <t>a GOB-implying namespace is dedicated: every PTO that carries its
Namespace-ID <bcp14>MUST</bcp14> carry a GOB in the designated format. In the
self-describing format the GOB Len field <bcp14>MAY</bcp14> be zero, in which case
the GOB consists of the trailer only;</t>
          </li>
          <li>
            <t>a GOB-aware node determines the presence and the format of the GOB
from the Namespace-ID and <bcp14>MUST NOT</bcp14> rely on the G bit for an option
whose Namespace-ID is GOB-implying;</t>
          </li>
          <li>
            <t>the encapsulating node sets the Reserved octet of the PTO fixed
header to zero, as required by <xref target="RFC9197"/>. The only exception is
the optional indication of <xref target="g-bit-ver"/>, which is allowed for the
self-describing format only: in the compact format the Reserved
octet <bcp14>MUST</bcp14> be zero.</t>
          </li>
        </ul>
        <t>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.</t>
        <t>In the compact format, the GOB occupies the last <tt>GOB_SIZE</tt> octets of
the IOAM option, where <tt>GOB_SIZE</tt> is the implied size, and the
validity check of <xref target="internal-pto-offsets"/> applies with the implied
<tt>GOB_SIZE</tt> substituted for <tt>4 * (GOB_Len + 1)</tt>. All other processing
rules apply unchanged, with size and schema derived from a
Namespace-ID lookup instead of being parsed from the packet.</t>
        <t>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 <xref target="g-bit-ver"/> under a Namespace-ID that
is not GOB-implying.</t>
        <t>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.</t>
        <t>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 <xref target="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 <xref target="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 (<xref target="security-considerations"/>).</t>
      </section>
      <section anchor="g-bit-ver">
        <name>Optional In-Band Indication: G Bit and Ver Field</name>
        <t>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.</t>
        <t>The G bit is carried in the last octet of the second word of the PTO
fixed header, defined as Reserved in <xref target="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.</t>
        <dl>
          <dt>G bit:</dt>
          <dd>
            <t>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
<bcp14>MUST NOT</bcp14> be set in an option that carries a compact GOB or no GOB.</t>
          </dd>
          <dt>Ver:</dt>
          <dd>
            <t>A 2-bit field carrying the version of the GOB extension. This
document defines version 0. An encapsulating node that sets the G
bit <bcp14>MUST</bcp14> set Ver to 0. A GOB-aware node that receives a PTO with the
G bit set and an unsupported Ver value <bcp14>MUST NOT</bcp14> parse or modify the
GOB; it still processes the Node Data Space according to
<xref target="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.</t>
          </dd>
        </dl>
        <t>The remaining 5 bits are reserved: they <bcp14>MUST</bcp14> be set to zero by the
encapsulating node and ignored on receipt.</t>
        <t>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 <bcp14>MUST NOT</bcp14> be set with a compact GOB, whose last word would
otherwise be parsed as a trailer.</t>
        <t>An encapsulating node <bcp14>MAY</bcp14> set the G bit in any option that carries a
self-describing GOB. It <bcp14>MUST</bcp14> 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 <xref target="RFC9197"/> that the Reserved
octet be zero on transmission; see <xref target="iana-considerations"/>.</t>
      </section>
    </section>
    <section anchor="length-and-alignment-rules">
      <name>Length and Alignment Rules</name>
      <t>This section defines the length relations used when the GOB is present
in the IOAM PTO.</t>
      <section anchor="gob-length">
        <name>GOB Length</name>
        <t>In the self-describing format, the GOB Payload length is determined by
the GOB Len field:</t>
        <artwork><![CDATA[
GOB_PLEN = GOB_Len * 4
]]></artwork>
        <t>The total GOB size, including the fixed 4-octet GOB Trailer, is:</t>
        <artwork><![CDATA[
GOB_SIZE = 4 + GOB_PLEN
]]></artwork>
        <t>The GOB Len field is set by the ingress node at encapsulation time.</t>
        <t>In the compact format, <tt>GOB_SIZE</tt> is the size implied by the
IOAM-Namespace and equals the GOB Payload length.</t>
        <t>Transit nodes <bcp14>MAY</bcp14> modify the content of the GOB Payload, but <bcp14>MUST NOT</bcp14>
modify the GOB Trailer and therefore <bcp14>MUST NOT</bcp14> alter the total GOB
size.</t>
      </section>
      <section anchor="internal-pto-offsets">
        <name>Internal PTO Offsets</name>
        <t>Let:</t>
        <ul spacing="normal">
          <li>
            <t><tt>X</tt> be the offset of the start of the Node Data Space, immediately
following the PTO fixed header;</t>
          </li>
          <li>
            <t><tt>Y</tt> be the offset immediately following the Node Data Space;</t>
          </li>
          <li>
            <t><tt>Y'</tt> be the offset immediately following the GOB, that is,
the end of the IOAM option;</t>
          </li>
          <li>
            <t><tt>Y''</tt> 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;</t>
          </li>
          <li>
            <t><tt>RemainingLen_init</tt> be the initial value of the RemainingLen field,
set by the ingress node at encapsulation time.</t>
          </li>
        </ul>
        <t>The offsets <tt>X</tt>, <tt>Y</tt>, <tt>Y'</tt> and <tt>Y''</tt> are counted from the first octet
that follows the Option Length field of the IOAM option, so that <tt>Y'</tt>
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.</t>
        <t>Then:</t>
        <artwork><![CDATA[
X   = (sizeof(IOAM_TLV) - 2) + sizeof(IOAM_PTO_HDR)
Y   = X + RemainingLen_init * 4
Y'  = Y + GOB_SIZE
Y'' = HBH_LEN - 6
]]></artwork>
        <t>In these expressions:</t>
        <ul spacing="normal">
          <li>
            <t><tt>sizeof(IOAM_TLV)</tt> is 4 octets (Option Type, Option Length, Reserved
and IOAM Type), and <tt>sizeof(IOAM_TLV) - 2</tt> excludes the <tt>Option Type</tt>
and <tt>Option Length</tt> octets, which precede the origin of the offsets;</t>
          </li>
          <li>
            <t><tt>sizeof(IOAM_PTO_HDR)</tt> is the fixed PTO header size, 8 octets;</t>
          </li>
          <li>
            <t><tt>HBH_LEN</tt> is the total size of the Hop-by-Hop Options header
(<xref target="option-length"/>), and the 6 octets are those that precede the
origin of the offsets in the layout of the figures: <tt>Next Header</tt>,
<tt>Hdr Ext Len</tt>, a 2-octet PadN option, <tt>Option Type</tt> and
<tt>Option Length</tt>;</t>
          </li>
          <li>
            <t><tt>RemainingLen</tt> retains its exact meaning from <xref target="RFC9197"/>: it counts
only the pre-allocated Node Data Space and does not include the GOB.</t>
          </li>
        </ul>
        <t>The Node Data Space starts immediately after the PTO fixed header and
spans <tt>RemainingLen_init * 4</tt> octets. The GOB occupies the last
<tt>GOB_SIZE</tt> octets of the IOAM option.</t>
        <t>Let <tt>PTO_LEN</tt> 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 <tt>RemainingLen</tt> be the current (received) value of the field. The
following validity check holds for a well-formed option at any point
along the path:</t>
        <artwork><![CDATA[
4 * (GOB_Len + 1) <= PTO_LEN - sizeof(IOAM_PTO_HDR)
                     - RemainingLen * 4
]]></artwork>
        <t>The check holds with equality at encapsulation time and is preserved
along the path, since RemainingLen can only decrease. A GOB-aware node
<bcp14>MUST</bcp14> treat the GOB as invalid if this check fails.</t>
        <t>In the compact format the same check applies with the implied
<tt>GOB_SIZE</tt> in place of <tt>4 * (GOB_Len + 1)</tt>.</t>
      </section>
      <section anchor="option-length">
        <name>IOAM Option Length and Hop-by-Hop Header Length</name>
        <t>The IOAM Option Length field <bcp14>MUST</bcp14> be set to <tt>Y'</tt>: 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 <tt>Y''</tt>, is carried in a
separate Pad1 or PadN option.</t>
        <t>The enclosing Hop-by-Hop Options header length is derived from the total
size of the header, including:</t>
        <ul spacing="normal">
          <li>
            <t>the 2-octet <tt>Next Header</tt> and <tt>Hdr Ext Len</tt> fields;</t>
          </li>
          <li>
            <t>any PadN option used to align the start of the IOAM option;</t>
          </li>
          <li>
            <t>the IOAM option itself;</t>
          </li>
          <li>
            <t>any final tail padding (Pad1 or PadN option).</t>
          </li>
        </ul>
        <t>Let <tt>HBH_LEN</tt> 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:</t>
        <artwork><![CDATA[
HBH_LEN = ALIGN(4 + sizeof(IOAM_TLV) + sizeof(IOAM_PTO_HDR)
                + RemainingLen_init * 4 + GOB_SIZE, 8)
]]></artwork>
        <t>where the leading 4 octets account for:</t>
        <ul spacing="normal">
          <li>
            <t>2 octets for <tt>Next Header</tt> and <tt>Hdr Ext Len</tt>;</t>
          </li>
          <li>
            <t>2 octets for the PadN option that aligns the IOAM option start.</t>
          </li>
        </ul>
        <t>A different arrangement of the options in the header changes the
leading term accordingly.</t>
        <t>The IPv6 <tt>Hdr Ext Len</tt> field is encoded as:</t>
        <artwork><![CDATA[
Hdr Ext Len = HBH_LEN / 8 - 1
]]></artwork>
        <t>For example, with 20 octets of pre-allocated node data
(<tt>RemainingLen_init</tt> = 5) and a 16-octet compact GOB, the IOAM Option
Length is 46 and <tt>HBH_LEN</tt> 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 <tt>HBH_LEN</tt> is 40, with no tail padding.</t>
      </section>
      <section anchor="alignment-semantics">
        <name>Alignment Semantics</name>
        <t>As specified in <xref target="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.</t>
        <t>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.</t>
        <t>More specifically:</t>
        <ul spacing="normal">
          <li>
            <t><tt>Y</tt> identifies the end of the Node Data Space;</t>
          </li>
          <li>
            <t><tt>Y'</tt> identifies the end of the GOB and of the IOAM option;</t>
          </li>
          <li>
            <t><tt>Y''</tt> identifies the aligned end, including padding that lies outside
the IOAM option.</t>
          </li>
        </ul>
        <t>The difference between <tt>Y'</tt> and <tt>Y''</tt> 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.</t>
      </section>
      <section anchor="preservation-of-pto-semantics">
        <name>Preservation of PTO Semantics</name>
        <t>The presence of the GOB does not alter the semantics of <tt>RemainingLen</tt>
or the pre-allocated nature of the PTO. In particular, <tt>RemainingLen</tt>
counts only the Node Data Space, exactly as in <xref target="RFC9197"/>, and the
Node Data Space starts at the same offset as in the base PTO format.</t>
        <t>The ingress node determines, at encapsulation time:</t>
        <ul spacing="normal">
          <li>
            <t>the size of the Node Data Space, via <tt>RemainingLen_init</tt>;</t>
          </li>
          <li>
            <t>the GOB size;</t>
          </li>
          <li>
            <t>the IOAM option length and the final tail padding.</t>
          </li>
        </ul>
        <t>The following budget constraints apply:</t>
        <ul spacing="normal">
          <li>
            <t><tt>RemainingLen_init &lt;= 127</tt>, due to the 7-bit RemainingLen field; note
that the GOB does not consume this budget;</t>
          </li>
          <li>
            <t>the total PTO option content, <tt>sizeof(IOAM_PTO_HDR) +
RemainingLen_init * 4 + GOB_SIZE</tt>, is bounded by the length limits of
the enclosing encapsulation (approximately 253 octets for the IPv6
Hop-by-Hop encapsulation of <xref target="RFC9486"/>).</t>
          </li>
        </ul>
        <t>Transit nodes operate only within the pre-allocated bounds of the Node
Data Space and, for GOB-aware nodes, of the GOB Payload, and <bcp14>MUST NOT</bcp14>
change the overall layout of the PTO option.</t>
        <t>In this way, the pre-allocated model of the PTO is preserved while
extending the option with a structured global metadata region.</t>
      </section>
    </section>
    <section anchor="backward-compatibility">
      <name>Backward Compatibility</name>
      <t>This section shows that the GOB is transparent to legacy IOAM transit
nodes, that is, nodes that implement <xref target="RFC9197"/> without GOB support.</t>
      <section anchor="structural-transparency-to-legacy-transit-nodes">
        <name>Structural Transparency to Legacy Transit Nodes</name>
        <t>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
<xref target="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".</t>
        <t>A compliant transit node therefore only writes within the interval:</t>
        <artwork><![CDATA[
[X + (RemainingLen - NodeLen - SoS) * 4, X + RemainingLen * 4)
]]></artwork>
        <t>where <tt>X</tt> is the start of the data space (<xref target="internal-pto-offsets"/>) and
<tt>SoS</tt> is the size of the Opaque State Snapshot, if present. Since
RemainingLen starts at <tt>RemainingLen_init</tt> and can only decrease, no
compliant node can ever write at or beyond <tt>X + RemainingLen_init * 4</tt>,
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.</t>
      </section>
      <section anchor="overflow-behavior">
        <name>Overflow Behavior</name>
        <t>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 (<xref target="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 <bcp14>SHOULD</bcp14> set <tt>RemainingLen_init = h * NodeLen</tt>
for the expected number <tt>h</tt> 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.</t>
        <t>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 <tt>RemainingLen_init</tt>,
but does not affect the integrity of the GOB.</t>
      </section>
      <section anchor="gob-only-mode">
        <name>GOB-Only Mode</name>
        <t>An ingress node <bcp14>MAY</bcp14> set <tt>RemainingLen_init = 0</tt>, 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.</t>
        <t>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 (<xref target="RFC9197"/>).</t>
      </section>
      <section anchor="legacy-decapsulating-nodes-and-collectors">
        <name>Legacy Decapsulating Nodes and Collectors</name>
        <t>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 <tt>NodeLen * 4</tt>, which provides a detection opportunity.</t>
      </section>
      <section anchor="path-mtu">
        <name>Path MTU</name>
        <t>Section 4.4.1 of <xref target="RFC9197"/> relates RemainingLen to the path MTU for
the node data space. An ingress node inserting a GOB <bcp14>MUST</bcp14> also account
for <tt>GOB_SIZE</tt> octets when assessing path MTU constraints.</t>
      </section>
      <section anchor="applicability-to-the-two-gob-formats">
        <name>Applicability to the Two GOB Formats</name>
        <t>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 <xref target="g-bit-ver"/>, the option is additionally fully
compliant with <xref target="RFC9197"/> as currently specified.</t>
        <t>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
<xref target="legacy-decapsulating-nodes-and-collectors"/>.</t>
      </section>
    </section>
    <section anchor="processing-semantics">
      <name>Processing Semantics</name>
      <section anchor="mode-determination">
        <name>GOB Mode Determination</name>
        <t>A GOB-aware node that supports the IOAM-Namespace of a received PTO
determines how to process the tail of the option as follows:</t>
        <ol spacing="normal" type="1"><li>
            <t>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 <tt>GOB_SIZE</tt> octets of the option,
with size and schema as configured for the namespace. The G bit is
not examined.</t>
          </li>
          <li>
            <t>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.</t>
          </li>
          <li>
            <t>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 <xref target="RFC9197"/>.</t>
          </li>
        </ol>
        <figure anchor="fig-mode">
          <name>GOB mode determination at a GOB-aware node</name>
          <artwork><![CDATA[
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)
]]></artwork>
        </figure>
        <t>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.</t>
        <t>A node that does not support the IOAM-Namespace of the option does not
process its IOAM data fields, as specified in <xref target="RFC9197"/>, and is
outside the scope of this procedure.</t>
      </section>
      <section anchor="ingress-node-behavior">
        <name>Ingress Node Behavior</name>
        <t>An ingress node that inserts a GOB into the PTO:</t>
        <ul spacing="normal">
          <li>
            <t><bcp14>MUST</bcp14> 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;</t>
          </li>
          <li>
            <t>in the self-describing format, <bcp14>MUST</bcp14> set the GOB Len and Schema
fields in the GOB Trailer;</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> insert the GOB in every option that carries a GOB-implying
Namespace-ID;</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> set the G bit to 1 and the Ver field to 0 if the Namespace-ID
is not GOB-implying; <bcp14>MAY</bcp14> do so for a self-describing GOB in a
GOB-implying namespace; <bcp14>MUST</bcp14> leave the Reserved octet at zero in
all other cases;</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> set <tt>RemainingLen_init</tt> according to the size of the Node Data
Space only, without including the GOB (e.g., <tt>RemainingLen_init =
h * NodeLen</tt> for <tt>h</tt> expected IOAM hops);</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> determine the final PTO layout, including the Node Data Space,
the GOB, and any required tail padding;</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> account for the GOB size when assessing path MTU constraints.</t>
          </li>
        </ul>
        <t>The ingress node <bcp14>MAY</bcp14> initialize the GOB Payload with structured
metadata, zero values, or other schema-defined initial content.</t>
      </section>
      <section anchor="transit-node-behavior">
        <name>Transit Node Behavior</name>
        <t>Legacy IOAM transit nodes require no modification: they process the
Node Data Space according to the procedures of <xref target="RFC9197"/> and, as
shown in <xref target="backward-compatibility"/>, never access the GOB.</t>
        <t>A GOB-aware transit node that processes a PTO containing a GOB:</t>
        <ul spacing="normal">
          <li>
            <t><bcp14>MUST</bcp14> verify the validity check of <xref target="internal-pto-offsets"/> before
accessing the GOB;</t>
          </li>
          <li>
            <t><bcp14>MAY</bcp14> read the GOB Payload;</t>
          </li>
          <li>
            <t><bcp14>MAY</bcp14> update fields within the GOB Payload, subject to the schema in
use;</t>
          </li>
          <li>
            <t><bcp14>MUST NOT</bcp14> modify the GOB Trailer (GOB Len and Schema fields), when
present;</t>
          </li>
          <li>
            <t><bcp14>MUST NOT</bcp14> modify PTO fixed-header fields, other than Flags and
RemainingLen as allowed by <xref target="RFC9197"/>;</t>
          </li>
          <li>
            <t><bcp14>MUST NOT</bcp14> change the overall size or layout of the PTO option.</t>
          </li>
        </ul>
        <t>A transit node <bcp14>MUST</bcp14> confine any GOB update to the pre-allocated GOB
Payload bounds established by the ingress node.</t>
        <t>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
<bcp14>SHOULD</bcp14> define update rules that remain meaningful under these
conditions, for example commutative and associative aggregation
functions.</t>
      </section>
      <section anchor="egress-or-collector-behavior">
        <name>Egress or Collector Behavior</name>
        <t>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 <tt>GOB_PLEN</tt> octets that immediately precede it.
In the compact format, the GOB Payload is the last <tt>GOB_SIZE</tt> octets
of the option. The node data recorded along the path occupies the
region between <tt>X + RemainingLen * 4</tt>, where RemainingLen is the
received value, and the start of the GOB Payload.</t>
        <t>Such a node:</t>
        <ul spacing="normal">
          <li>
            <t><bcp14>MUST</bcp14> verify the validity check of <xref target="internal-pto-offsets"/>; if the
check fails, the GOB <bcp14>MUST</bcp14> be considered invalid and <bcp14>MUST NOT</bcp14> be
parsed;</t>
          </li>
          <li>
            <t><bcp14>MAY</bcp14> parse the GOB Payload according to the Schema field, or to the
schema implied by the IOAM-Namespace;</t>
          </li>
          <li>
            <t><bcp14>MAY</bcp14> export the GOB content as structured metadata or as raw bytes;</t>
          </li>
          <li>
            <t><bcp14>MAY</bcp14> ignore the GOB Payload if the Schema value is unknown or not
supported.</t>
          </li>
        </ul>
        <t>If the Schema value is unknown, the node <bcp14>MUST NOT</bcp14> infer semantics beyond
the presence and length of the GOB.</t>
        <t>The export of the GOB content to a collector, for example by means of
IPFIX <xref target="RFC7011"/>, is outside the scope of this document.</t>
      </section>
    </section>
    <section anchor="relation-to-pto-semantics">
      <name>Relation to PTO Semantics</name>
      <t>The GOB preserves the pre-allocated semantics of the IOAM PTO.</t>
      <t>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.</t>
      <t>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.</t>
      <t>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.</t>
    </section>
    <section anchor="schema-semantics">
      <name>Schema Semantics and Extensibility</name>
      <t>The Schema field identifies the format of the GOB Payload. As for the
Opaque State Snapshot Schema ID of <xref target="RFC9197"/>, the Schema field is
interpreted within the context of the IOAM-Namespace indicated by the
Namespace-ID field of the enclosing PTO.</t>
      <t>A Schema value may identify:</t>
      <ul spacing="normal">
        <li>
          <t>a set of path metrics, for example the aggregates of a per-node
measurement;</t>
        </li>
        <li>
          <t>another structured metadata format defined by a specification;</t>
        </li>
        <li>
          <t>a locally defined or domain-specific format.</t>
        </li>
      </ul>
      <t>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.</t>
      <t>Following the model used by <xref target="RFC9197"/> for the Namespace-ID, the
24-bit Schema value space is divided into two subranges:</t>
      <ul spacing="normal">
        <li>
          <t>an operator-assigned range from 0x000000 to 0x7FFFFF, and</t>
        </li>
        <li>
          <t>an IANA-assigned range from 0x800000 to 0xFFFFFE.</t>
        </li>
      </ul>
      <t>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.</t>
      <t>The IANA-assigned range is intended for globally defined schemas
specified in future documents, allowing new and interoperable GOB
payload formats.</t>
      <t>In the compact format (<xref target="namespace-implied"/>), 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.</t>
      <t>The Schema value 0xFFFFFF is reserved and indicates that no schema is
associated with the GOB, consistent with the Opaque State Snapshot rule
of <xref target="RFC9197"/>, where "the Schema ID <bcp14>MUST</bcp14> be set to 0xFFFFFF to mean no
schema". An encapsulating node that inserts a GOB without an associated
schema <bcp14>MUST</bcp14> set the Schema field to 0xFFFFFF. When the Schema field is
0xFFFFFF, nodes <bcp14>MUST NOT</bcp14> interpret the GOB Payload beyond its presence
and length. Future specifications that define allocation policies for
Schema values <bcp14>MUST</bcp14> preserve this reservation.</t>
    </section>
    <section anchor="use-cases">
      <name>Use Cases</name>
      <t>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 (<xref target="implementation-status"/>).</t>
      <t>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
<xref target="draft-eip-arch"/>; earlier work on the integration of EIP into the
IOAM framework is described in <xref target="salsano25cscn"/>. This document does
not specify it and requests no schema registration for it.</t>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>[RFC Editor: please remove this section before publication.]</t>
      <t>This section records the status of known implementations of the
mechanism defined by this specification, following the approach
suggested by <xref target="RFC7942"/>.</t>
      <t>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 "<bcp14>MUST NOT</bcp14> modify the GOB
Trailer" requirement of this document is enforced at the eBPF verifier
level.</t>
      <t>The compact format was implemented and first exercised during the
IETF 127 hackathon, in the Linux kernel and in iproute2 (branches
<tt>ioam6-gob_v4</tt> 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.</t>
      <t>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, 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.</t>
      <t>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".</t>
      <t>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 <xref target="mayer26noms"/>.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>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.</t>
      <t>For this reason, deployments of the GOB <bcp14>SHOULD</bcp14> be limited to controlled
or trusted domains, consistent with the limited-domain assumptions often
applied to IOAM deployments.</t>
      <t>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 <xref target="internal-pto-offsets"/> rejects GOB sizes that are
inconsistent with the option length and with the current RemainingLen
value, and <bcp14>MUST</bcp14> 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 <bcp14>SHOULD</bcp14> 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 <bcp14>SHOULD</bcp14> also verify that the size of the
region between <tt>X + RemainingLen * 4</tt> and the start of the GOB Payload
is an integer multiple of <tt>NodeLen * 4</tt> octets. The compact format is
not exposed to this issue, since the GOB size is not carried in the
packet.</t>
      <t>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 <xref target="internal-pto-offsets"/> 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.</t>
      <t>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 <bcp14>SHOULD</bcp14> describe any
additional confidentiality, integrity, or authorization requirements.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document defines the Global Opaque Block (GOB) as an extension to
the IOAM Pre-allocated Trace Option.</t>
      <t>As discussed in <xref target="backward-compatibility"/>, 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.</t>
      <t>The mechanism defined in this document, in which the presence and the
format of the GOB are bound to the IOAM-Namespace
(<xref target="namespace-implied"/>), 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.</t>
      <t>The optional G bit and Ver field of <xref target="g-bit-ver"/> are placed in the
Reserved octet of the PTO fixed header. Since <xref target="RFC9197"/> requires
transit nodes to ignore the Reserved field, their use does not affect
legacy transit behavior. However, <xref target="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.</t>
      <t>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
<xref target="namespace-implied"/> does not depend on either choice.</t>
      <t>In addition, <xref target="schema-semantics"/> 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.</t>
      <t>This version of the document does not request IANA actions. Future
versions may request updates to the relevant IOAM <xref target="IANA-ioam-types"/>
or IPv6 <xref target="IANA-ipv6-parameters"/> registries, depending on whether,
and how, the optional indication is standardized.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8200">
          <front>
            <title>Internet Protocol, Version 6 (IPv6) Specification</title>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="July" year="2017"/>
            <abstract>
              <t>This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="86"/>
          <seriesInfo name="RFC" value="8200"/>
          <seriesInfo name="DOI" value="10.17487/RFC8200"/>
        </reference>
        <reference anchor="RFC9197">
          <front>
            <title>Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)</title>
            <author fullname="F. Brockners" initials="F." role="editor" surname="Brockners"/>
            <author fullname="S. Bhandari" initials="S." role="editor" surname="Bhandari"/>
            <author fullname="T. Mizrahi" initials="T." role="editor" surname="Mizrahi"/>
            <date month="May" year="2022"/>
            <abstract>
              <t>In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for IOAM. IOAM-Data-Fields can be encapsulated into a variety of protocols, such as Network Service Header (NSH), Segment Routing, Generic Network Virtualization Encapsulation (Geneve), or IPv6. IOAM can be used to complement OAM mechanisms based on, e.g., ICMP or other types of probe packets.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9197"/>
          <seriesInfo name="DOI" value="10.17487/RFC9197"/>
        </reference>
        <reference anchor="RFC9486">
          <front>
            <title>IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)</title>
            <author fullname="S. Bhandari" initials="S." role="editor" surname="Bhandari"/>
            <author fullname="F. Brockners" initials="F." role="editor" surname="Brockners"/>
            <date month="September" year="2023"/>
            <abstract>
              <t>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 outlines how IOAM Data-Fields are encapsulated in IPv6.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9486"/>
          <seriesInfo name="DOI" value="10.17487/RFC9486"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="IANA-ioam-types" target="https://www.iana.org/assignments/ioam/ioam.xhtml#data-field-types">
          <front>
            <title>IOAM Data Field Types</title>
            <author initials="" surname="IANA" fullname="IANA">
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="IANA-ipv6-parameters" target="https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml">
          <front>
            <title>Internet Protocol Version 6 (IPv6) Parameters</title>
            <author initials="" surname="IANA" fullname="IANA">
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="draft-eip-arch" target="https://datatracker.ietf.org/doc/draft-eip-arch/">
          <front>
            <title>Extensible In-band Processing (EIP) Architecture and Framework</title>
            <author initials="S." surname="Salsano" fullname="Stefano Salsano">
              <organization/>
            </author>
            <author initials="H." surname="ElBakoury" fullname="Hesham ElBakoury">
              <organization/>
            </author>
            <author initials="D. R." surname="Lopez" fullname="Diego R. Lopez">
              <organization/>
            </author>
            <date year="2026"/>
          </front>
          <refcontent>Internet-Draft draft-eip-arch</refcontent>
        </reference>
        <reference anchor="salsano25cscn">
          <front>
            <title>Integrating Extensible In-Band Processing (EIP) into the IOAM Framework: A Unified Approach to In-Packet Telemetry and Metadata</title>
            <author initials="S." surname="Salsano" fullname="Stefano Salsano">
              <organization/>
            </author>
            <author initials="A." surname="Mayer" fullname="Andrea Mayer">
              <organization/>
            </author>
            <author initials="G." surname="Sidoretti" fullname="Giulio Sidoretti">
              <organization/>
            </author>
            <author initials="P." surname="Loreti" fullname="Pierpaolo Loreti">
              <organization/>
            </author>
            <author initials="L." surname="Bracciale" fullname="Lorenzo Bracciale">
              <organization/>
            </author>
            <author initials="H." surname="ElBakoury" fullname="Hesham ElBakoury">
              <organization/>
            </author>
            <author initials="D. R." surname="Lopez" fullname="Diego R. Lopez">
              <organization/>
            </author>
            <date year="2025"/>
          </front>
          <refcontent>IEEE CSCN 2025 Conference</refcontent>
        </reference>
        <reference anchor="mayer26noms">
          <front>
            <title>Integrating the Global Opaque Block into the IOAM Framework: A Unified Approach to In-Packet Telemetry and Metadata</title>
            <author initials="A." surname="Mayer" fullname="Andrea Mayer">
              <organization/>
            </author>
            <author initials="S." surname="Salsano" fullname="Stefano Salsano">
              <organization/>
            </author>
            <author initials="G." surname="Sidoretti" fullname="Giulio Sidoretti">
              <organization/>
            </author>
            <author initials="P." surname="Loreti" fullname="Pierpaolo Loreti">
              <organization/>
            </author>
            <author initials="L." surname="Bracciale" fullname="Lorenzo Bracciale">
              <organization/>
            </author>
            <author initials="H." surname="ElBakoury" fullname="Hesham ElBakoury">
              <organization/>
            </author>
            <author initials="D. R." surname="Lopez" fullname="Diego R. Lopez">
              <organization/>
            </author>
            <date year="2026"/>
          </front>
          <refcontent>IEEE/IFIP NOMS 2026</refcontent>
        </reference>
        <reference anchor="RFC9673">
          <front>
            <title>IPv6 Hop-by-Hop Options Processing Procedures</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="G. Fairhurst" initials="G." surname="Fairhurst"/>
            <date month="October" year="2024"/>
            <abstract>
              <t>This document specifies procedures for processing IPv6 Hop-by-Hop options in IPv6 routers and hosts. It modifies the procedures specified in the IPv6 Protocol Specification (RFC 8200) to make processing of the IPv6 Hop-by-Hop Options header practical with the goal of making IPv6 Hop-by-Hop options useful to deploy and use at IPv6 routers and hosts. This document updates RFC 8200.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9673"/>
          <seriesInfo name="DOI" value="10.17487/RFC9673"/>
        </reference>
        <reference anchor="RFC9322">
          <front>
            <title>In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags</title>
            <author fullname="T. Mizrahi" initials="T." surname="Mizrahi"/>
            <author fullname="F. Brockners" initials="F." surname="Brockners"/>
            <author fullname="S. Bhandari" initials="S." surname="Bhandari"/>
            <author fullname="B. Gafni" initials="B." surname="Gafni"/>
            <author fullname="M. Spiegel" initials="M." surname="Spiegel"/>
            <date month="November" year="2022"/>
            <abstract>
              <t>In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in packets while they traverse a path between two points in the network. This document defines two new flags in the IOAM Trace Option headers, specifically the Loopback and Active flags.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9322"/>
          <seriesInfo name="DOI" value="10.17487/RFC9322"/>
        </reference>
        <reference anchor="RFC7011">
          <front>
            <title>Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information</title>
            <author fullname="B. Claise" initials="B." role="editor" surname="Claise"/>
            <author fullname="B. Trammell" initials="B." role="editor" surname="Trammell"/>
            <author fullname="P. Aitken" initials="P." surname="Aitken"/>
            <date month="September" year="2013"/>
            <abstract>
              <t>This document specifies the IP Flow Information Export (IPFIX) protocol, which serves as a means for transmitting Traffic Flow information over the network. In order to transmit Traffic Flow information from an Exporting Process to a Collecting Process, a common representation of flow data and a standard means of communicating them are required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. This document obsoletes RFC 5101.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="77"/>
          <seriesInfo name="RFC" value="7011"/>
          <seriesInfo name="DOI" value="10.17487/RFC7011"/>
        </reference>
        <reference anchor="RFC7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
      </references>
    </references>
    <?line 1258?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>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.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+196XYb15ng//sUd6gfTSYAJNK0rFBxd6jNYh9tY9FJPJkc
swAUyGoBVeiqAilYdp5lnmWebL71blUFUbacM31Oq087BFB1129fx+OxaYt2
mZ/YvW+W1TRb2tfr7D83uX20rGbv7KKq7dnr05f2TZ2PsyV8l7X53J7X2SyH
J9uiKvdMNp3W+TWMQE9+8/rRnsHHLqt6e2Lz92tj5tWszFYwybzOFu14lW3z
ejxdr8ZFla3Gl9V0fO/QNJvpqmgaGLLdruHZs6fnz0yxrk9sW2+a9ujevT/c
OzI3Vf3usq426xP76M1L8y7fwjfzE2PtmFbKf7y5vs9/lONpVs5tmy/zVd7W
W/r2Zd5m86zNzHVebnJ8NxjRWp5+7y8wU1Fe2m/wtz34fpUVyxMLy/5TkbeL
SVVfwpdZPbs6sVdtu25O7t7FR/Cb4jqf6EN38Yu707q6afK78PZdnK9orzZT
OJ1iPb6qVvldPQj4bQln17R+TH1mwi9Niso9fXfoPCdX7WppTNPC5n/IllUJ
G9rmjWlWWd3+8J+bCqY4sWVl1sWJ/VtbzUa2qeq2zhcN/LVd4R9/NybbtFdV
zYfLF7h3Ws7rPLMvcUo8FGuLssHvJ+F3sO2sLH7MEEDgx+/K4npiq4X9FvZh
zwGo/pzDE21m79rHr87O8X+q1aoq7au85RFyPu29jOab0Bb/tCmLulplR5OC
nnKLetvmi6ys7Nts2cD/hut6O4m//cSVxYtpeJ5JwyMOruffAV6L0p5t6lVW
hqv590n0ZbKY+385e/UknvE/aKRJQS/96RK/ncyqVTTbkwJwzX47sS+qdf5j
ON2TSfJ1MuE5oMWiKotZFs86xxEn9WSJb/6pdU/x1KasYDUtwDhCxrfPHj8A
3JQ//3D4h6/0z+MH9+XPo8PDP+izh18d459np69OGVwR3ZoTml9JERGSJ3gL
z4p8CfQGH+ElepDEf+4McDh+YEGL0ween798AT8rLt3c3EyKrMwYL4HYXJar
vGwbwij6z+Q9os4dJA/jBU7O69tzS15f3x+vsxqmbfM6XXcJ35V5C+SyAqSq
lghNSNHsfbuPROnAvnGv/rb7iZeZfuZdwlUW5SK8TKYnSHGIrkWbe/q+zcum
mC5zR1Zhm7McZgUquf/07M2BPUXa1+azdlPnFp94hjMizd652178Hcbh4M3n
eXOVrezT5aPsXbWpt+mrzyfd33Yizg7kAZiAt47uHd2nj0AjZ8Cr4LiDmx8/
wRNMzvEWF4nw1gJXfZfXnnEA27wbj3QXhxLqc/TlrJmVXQC8rOE64Ubi+3rU
e19F2Va2vcqZybvLOrGnFigjwP/cnq7XdZXNriw8CeO8wTW29lwZKt2yMtRf
csk7OEvw4zfFZlnAu8W8qvO2LToPvCnyep1VywpuDJ7oPoBflz9W9hGc8qzI
lvmtYWknvDig+LIHKJ4+fWofv338in4HFlcucljELGdpAvZ5dL+sVj1ERO8Q
r6ZPLvtn3tvOe/nYpf7/f299yAz3dvfs2dkb++r1y7f0EJDK8Xhss2mDWNoa
E2DXSk7RzrK6xqO/AUEN2L+7n2Hh2ey/OX99AC+Wttms1yCC2TVd1HiZX+fL
kV0sqxv9G4STddZe8Ue7drhspvm2gttcgxBYVvPctjQDLmliz6+KxgIh2SBf
sPN8UZR504Urw3C1D9L7wQhgA+R22h+wrhDSYLXwIWsRAOtqvoEV2MziIpa5
WUfbvOTh3eHU+SWOtl7C2uYWhsBBW5A3UPrCvys6kZEBepfX9E08IG2Nhmrg
jHLgCQWgEj2Iy/I/L4umNbDrdbXeLOnVBUhpnfmS8WCfN1k9t0Xb2Ks8m4/M
ppzLQhA06sq9+S3KSSVs+kVeWhISRnaZX2azLZ8SnD8cXUszNAYvt4Qrq+EI
CB/x7F8/kgM5oc/+tGHd9DrwarwwOPxmM7syNJSdbnEpAIKbGZ0VIXFVLrc0
yDyfZesGt4ykg7YHIANSyBIYclWbMs/nDY44pQWMM9hvPjHnfNINEiYaEMdi
ZqUbxuXCs3ZabfB3AgiDWx2/AgyT6zhjiG/y5WIMi53VxRTXwSON3DiMJAA2
pQHdcFnM4KCWeXnZXtHkzewKTtcWc9g9ErIaQA1ADM6kWMIHVPYeWkYuA9Io
TN26KZrixzwcBJdcrGAOAIHp1kGxXzQ+bPDrKUE/ni3AToPbXmfbZZXx6aJy
xGCf2eNxNWuBkFZMjq+zJfy3wFtm3C8QdWBRcCfHlh5t6GimFWyQF9oE4A6v
AmLzdm6KOocr3UEubNYAsOYzpvAwFQjUFkVuhgTQ52ZXWXmZ8xXBeuXhWSZz
AdD95wammU/saSlLACSdFq2cKaKSQfCHs8Y13BB+J1eK18hgVOez6hIUCiF6
1aY1pTtcOM5FcbmpaXKGM3yTYK2+Bszo4jgisidsdgUwvKStIRLBfJsmZ/gj
FAFyaZAiIpGpi1kjdwS3vlnPaTxUfZmL4nNEQuEeYG+MQyClzo1SqAmT+FUx
nwMxM3fg1pjGEaGm5X+Emlum5kxk6X4+fBCd6OefCdb4MyhG8Bn2eV3MmYC6
1dibbIsbRHDawggsZwPb4lPMlgyyjos7+R2BgzabCQehHTusxIOl0yRENIDr
KakIL6IRkojmH08m6XTlIhYFUJW5mTLFG8NoGbJCJlPxqU/w7PqY0E4uM8tw
goBRmUgAIkaF3I1hqsBTHOA4DBTrdZ7VjamQyHlQH+1gRHaAEZmUEX0mChpP
fwIbmufrZbWVM0Pdjq4GSTdStS2yfodteJzAhvDGiMvwYCskLjzyTaXkR4HC
3JZUI0usbsoumTbE/Bo90GXWtI5AIqVOTxSkrLyuGYWzRucx50zcHbB+jK4n
Zyok3vSSeN6Nsg+Ak2pVtHCLI3dRMe03Ce33xHuWNSI5fcsEbG6FFSwcignl
BH7wY15XbooOrbe3ovUmovUBLQHqTejjINWDXz8p36fzwh9R55sXjOT9lF3e
Zipi4O7hGc8BC0cCurTfDtJ+R/zzEukEHyOBV3ZJ4BlQwBSNvTRtlDqM7M0V
3KeyEtWU8vdFQwStl40ANJleERkuGKSttpgBPaxD6C+FDIc8xnR4DKxtsSwu
rxBQQVRTwM4uL4EAMWWGDWZOPAeGkzWwU8LrlEHpScKSi8VWN9YA1IM4NGsE
1kws7Mr5kmhNo4YIMkTfQAF9R7gdypsGEHNQkg2ZySgRoXEZCPYfkbl3SvSB
BE5wS8S5WiwakKGAANbFdThsVwi3+29zYtb2eHI8OYRXTYAzwC1OibIsCzhL
3SUDA0gEOYBHLnL6TV0geohaFZ+3kxsRPsqq7RXqGVUWFQtQRTuxr4GUmGEh
nameCOq2X1AnVQ6ULBQG2i2xPJAHtj8yCM5zOmeiE1NAXTzJMRHSFlB7WbRb
IBseD1E9iu5CiGdXMJggVfJAYF+efm9gz3NcNqOA27zQTcSD6X/AVpSpE9Nr
bN60gPxFc0X6XyiD4IkVKyCI0w2B69a+/O7tOWjf54AgyoQruBpYL81EHIHP
zSyzLWKMQBiMuqwaJQIM6h0JROmqY0GO1QQsLluKNdXWGyBZxDBMQFWm+VV2
XcAiiOeG5zZSvGEmkwMhaJpEFyOEMgakcGRfhLYixeEb7+GOC/puaXPUMRwd
YSyq1hVKwoTgYucxgdXhRVFu3jMGL9Q2RDRLSL0ylHjqMdxPu2kITu6gteoa
dTDgi7SmJyi1FfSZwegdXBMy+cbu4W3tjfh/8dbw72+f/s/vzr59+gT/fvv8
9MUL94eRJ94+f/3diyf+L//m49cvXz599YRfRiiIvjJ7AIN7fLZ7r9+cn71+
dfpij/lWeMu4YUaiAq2zAO+kEjQmOoVHj9/83/9zeAyn8T/EUwGyOX9AXwV8
uLnKQ1WbPyKUGpYqSUMFwAQIKODCEFJAgL5CiQkJC5zm7/6GJ/P3E/vH6Wx9
ePyv8gVuOPpSzyz6ks6s+03nZT7Enq96pnGnGX2fnHS83tPvo8967sGXf/y3
Jcj1dnz44N/+1TCMMAkkNpbXq4b5ZsMHH13WiTEAzCfmpM/ciZR7h4AgNLco
QRZghtxW6MYN1IkJDW9F0MRpcHUqqqp0SGy6RyQaOcue8HYUdGGGUMSlmYSz
EneoAKuIPzkag4wKf3rLsrNlrtXI2t4w8dS1iTUyYOUfsbAgJy9Wq3xeAEle
oqMbAH6WzwMiJ9unRaBMT1QULwF9QivSWYUNyHJ1jWpxSSRzmpKHv7mqliJw
xIPDEDtNMLD7t90Tx1M4ZTsDKZ2BYUaXJ+clIBYvXRUKYx7Lgj9tTDb6IEFN
dY9bbCfUz7xETLOXqf3JqXXANNm456VmZBjwHUI3Gp2FAeACYNFuiPHZE6I3
qObBJTQq3qEWfpNtGxFhM4ZjpFQUfnCNQhNdIqz4FUoh5G59q0s97whrfZKN
qj2L4j08oWYjOCxYSNsIDvrRX6Csas8CyAPRDoW8rihgr4uMuLvtEfRgyTCr
LvNjRpkd5hhrA4NMdBC4VJ2gyYESlaygx2fi1AkWDZcVCaqLEJNQCbP+qM9K
FgZwJh2/xxgjNnYkaE1sFyEtH1mQqHztCINQnN2GsA/ZNEgvP3rURwlIpDid
WYExNN0k6ggvY5VtVZlyF47TwPcGHSe7REGY96mTfh47AdetIdgtKEQg4QHz
ZFqEuxmhIFTBEXjD3U3RBOy8ERCh0wlNYYE11uuySGoIiXnqo+MxKcve0hya
TOHsgIN3KEMhcjmioRcqSGB6QrhsX1+jRprfBDovGrnmyT0ScenarDJ0tfHt
N2ZZXRZoB9vaOSm2SHhV/XGgl6iCgF64SFxcOUd9CYRNN7qawpYk+lbB2bCn
yfmYkKJkTNRHFmgPnDwqvmSmy5xVOVIPA+VCjG2I2SsgBFaNblkok9u/hEDM
rMR81Ds0ZJTzx2A+0R0RsIHMXGd1gdgwFj1g3cNkMiF3ifRANgnQBAu2a5Mt
bKeAIMY1XUjXuOYhc9Ay1reLyHNhInb8Kb4RZ/gyoddCdEc9dQeOedkx9m0a
FX4oLk+2ztt8CEtBu8p8js+oVZ80rkSLe16tx9PtGP7HvBbGJnyGgBg0v6Zg
Fb5zwvMKHkAVPVsscpYBDC08Nkk5f0QfVGUUyRJY+MiWxIbngmm5EcqpJFiP
SSwFvdyNlqdSFxlYDV7QiK+KbsgbKFXxxelZ2Z14s0DibAQxXWxHAi8kRUZC
jtPSUdl2enbwUmSSfcF2kmgW9SLBJ35PHEwnrLsHzKJrOJnNACcIMKqUHYv1
BR5RVsOcCwgFEiBv8PQ+RJZqmOkJ/ilqpHItWjJT8Wv/wwcnoI0FG9hS9FHn
GFoHEXz5oeXWmVU/waqK818iExrDvnHeyD7jSDj5gDk4INCCHFF3Vn18F1DJ
sKHa2xDg4aayiwztD0CJ61JN4uxCY5rhLZwEGETDVjm6E4tmhcthW1eDj7S5
ujBWuAWYc0xz+i3oyYRw59BRfZQ9hk1vJE3Z2rmjdGqz8NIIEmWmJI6hsnvW
EDtlW/Eyz7qG4sQe7I4XDx/obHwhu4jeIO2Z52t4zFSOroWkgB1q6mSRYI1r
CRmUkVVDNl4wGTZSsYViIRZFjDjsI6DxKmCeQAp+KA5S2lD0IGnvRgkuE6pq
nZMvAmdEiu4nc2yAIV70ELkAUnhRrpySnwxtlehNQQmhQT4rQggMOq8rECaI
RTHpceZ3OFyj+hLDYyikylUAdP4bbu3+V18QXjPZBqqQzVSfUvAkgYyMZ1W1
Rgsqne/pDEMjQTjKLhs+KRrvi6MjoFmMFbGXpt1xhQBOICfiZM8IZ+HTHQLg
F2zCpCUg9TUkG9HKeoK/yPcpFlwWnhyT/ahvumhEHBVZZo3QyZjDUTw0/y+Q
vxIdUjAHFrhZEqaJlbZoTow5nHS0RnM0SYew+6hFKsrGqtmB+WISyuXmeBJZ
OPYHbCSIHgfmSwAE3JrIH8ArFi4wgqgtwHsDzNAjV2pcxpixANZjyeQh+4FU
uikGpRTzKZ7jgJklUSDmwweUSsb6BGErOgnPeITQVqCUPDJSaBTMN8zrAFeB
WIJAC+zd+woaMqmWnRiNwBZgpsAF+GpV3/0klYDwIbxGiv5u/Cjn3o2rwTWW
gx68xa2RM1TDIxvZ2L6INi3RfR+Q8sd+o0TvI8ZEDoauZQiWvCnJH46WGB/h
gyvkWKB7uDr4s5ifuLdbROcegxMMoVsiX3Ovghqs0WkEzQCgyDJpPTC4rOj9
M/oXeH5pNLhejbaCi2maalYQKjtKCCM+JEWXqRry+FHnRJwEGdvZhZmtirqu
ajUFgewHgLSumOQgx3K8Sijc2xZFqLclsJ0rAFM+DotwWzprjbjAyTTjGLYc
grzAG2chr2gCExANwrseO+HDecbaCh0u6d2ziZM9hABH//jHPxCWfnjz4ukr
+zU+8QNapn5nj+nrt2f/6yl8fWx/b/UpesXc4Bg06HEgOSoY+6NRxTwCeJIX
+VrDw09h6kKnvNBxGW68XVitwiaZgmxTfTbezlIajIKlQNkL3e+FBeqZLRvH
23V9bOf7iMH03N8bw3rmrYvhYD2+nECbMFEYlSNAQFEebdt8/IKCZpnRpr4J
liHIZcOzTvENDrONvYuR+cb0SvoDunrnHMk2UDSGD5PB+c9iPiVCzN4SiiPZ
lMtYsMmWiswixUSKBN4R6tQTBtbX5ELnmOh7tvvvsOe7o57vvjDhp3vw3pH9
AoD5S3vffmUf2D98ync81jGt5/fjX/l/4cJ+gv9/BTKOfc6KGnx+Pq8xG4Ic
MPT7m2z+Cpk2P6+f6Gf7UzjYZ18ZzYrpTPyZ4Am/wrnxdxdaJM/TA/r8b7my
SEiw+4f3pwfB7yh9yek9I1H4p8gq/xufGf3jk0CJdkznsX90HC5Rn3cH+BMg
00/f/DNW9sv+RSv7x/BzseA78NA/frOV/Zc8s4htDP37L3Nm6jvef4AA/5Py
yn4E+KeubPjfG1F+/okrQ1b34YTTqL7eix0tw2p0oOru/WzMS4wC07wEdAK3
ajFAnhvYh5qT/2au/81ch/7vj5+Zv37m5dn904PPymV1fX/9rY7vV/1Ljm9o
uITT/u3e33/VcL9wdb/+cp983tVlv+TsDgfPrv0NV/erz+628gX8m0wmux/4
h337ee91/c+/1/Ray/HAxf5kZ593dfnnPbvfEmNvixPlP5mefE///dVn99mJ
8TefVYq3rz/v6h79BoIA2snOv33x2YT57//lsywuPbidkpuX6Q/vs3mqb2Wf
6dh0m7jP//3D0L8HYzTUsZsGZJGhx+4mqsETSpWQbNNl4HpLHVDkkEFHEda0
+pmthukz0/wSfQ6hhdW7yFIvF2a0kOG1AWnQrqum0KxeCQ9IHCgnbHjXGFtM
S4FFza6q2lDMDHrwlkv2jGJw52y5oRuS5JaqpHi6SpJnaBAfJ4X5W2w85Rwb
9muHcqf3ujv3R7BNcfyYtnsqt46+8kZlHzTVl0AYOM0wOAMmL1AfawMvHtlS
5+xHXm573XhGnHyrMCSmL9QocegRIGC4kRlw5LGdORDxxeKNW/xwpxti8kmO
v51J96cDSaJdQ3vD4cFGw4OjuOAkMbM/hJlTYCiiMEwxdRmmkU09yDc96YZ4
ay2ckyCu45eFeIunK/XZuLA3H+2WxIS2QTD8LEPH0LxYwCkwGkgONUYVaOzo
48ief9u1IzCe9DlRMHLAqmPVY5pGRidOkzLMZ62rzeUVvNwJF5ef6I0kbrzr
CSYfGfn3JAxsirFLK/TXr5d0mLF7s6GAYvx6ZB+M7OERHd0h1k8RXxOecpA/
Qr49KkGXAZ35UWLIdU2NRJpgKRyZswknpdEyvnhZQCf710flwijL4l3O4cED
RzdJ/T4cMoPxsEQvwhINALO/Y+ToQQR2KbIvdX5iMWpt60ujBFnTJtH76ZgD
xFNY9GkA6rjSFG07lO2hR+CzHzH0b8oOo5EPh0OnrXhf+0C1DdzPD92WObKQ
WYWPUmxvRbMw2l0DpKLNU8EhdRbXyEEkKIrDDjiESCMjrCQzpLEL4YXgepOg
Ko2fbyQ2fEeqNvFlmEdIPNw/n1zmi2QgBHVczsRd8vezXHO65XT7HXM2csz5
GGGFbPV/D180E5D+/Jtwh4qGDpdxOwLyc5e7xzlO/WA9lIJiQrQdhSDkCRsv
6CF9TqKfECb0Z1ejoLsZLxQwCSwdHZAc3EH0H3Jd+xGr2Wyz1qgJEjIC17VM
I6FgAVenPIs6D58VSUwpDMfs6gIp6KNo4Qyv8tk7vnw1HY/XbTWWXGaMdpUY
fBdqoTUMgrmazbQBiXUjVMFeHNvfkdGawg1+bw8PLoD/g/jHAXtBPaiQrm1K
Drec9+czxXnVmYnwbVlV7zZrzENpKctjAWBFUZNZ3YRxkI5FKhPDwA8k+21F
JUqGCek0n2UgyTLYyPEZPj5JrwZRE2ueSMwBwxot1cUkUXHTYhGEB9/ArRn6
TdPpBRDUnE/RCnhTN9UGKOc0F1lRUvyaissv5CVxUx+KepVhVjicPsvOYRWJ
agmo2wbP5hKlOuqLpkvk5ZFfSJu949QsXTPcsQlkPI7coQRxleQ4laT0ZRiE
0FP+oCtiZUjniO53owUtBkiP5KhQCILwmpGRld2G3MnkWTwr7sD0hKEJ/KQp
hnEuSyxP6LN8HUQqkNTAPdVzYmELxHWMJW2YVHmVi0LGJZIkkpEo/pHi7ULE
0OjIHvzwRRsQLziebmskRjdMSopCwD3kYAyyiJsY6X8lqIZXFpQt4fSoucUA
MGSenbIVv6g0VcCQcCkUmpcvFsWsQNiB06IKd8bHiuPpFkjIQfCT6fjwKWzQ
T3R4P5QdByrNdC5X75F5vyb5SzoMRtxfZ0BQhgT0vygxTZg+TCSs3VGIHVzQ
9FRpWS9BJ96VY8iqVRwRyxROk798MYk4oREE0TkmXhVxsg2Dq5TXCVIKw5SJ
d3m+xseKWs8T4d9FtXkI8/SWhBdXeMr5Nj0SENl43xIWhRFkwJxcFCuaHCjC
VfKXSSzyuQJcHkZoVlAcBuPDfXmyjly1rguWrGk+hH65YpWny8rVw4ppjmDt
CcfQzVpfLgskF84SQhYkcgsCdiLkuCH6lF6TzeqqCbL35hVeH4aWN/lsUwMb
GdPQc5lU0iDu3BHgABqp9VfP3LpPQOp9VHBA7Z810tV+uOOppzGnvYkkncQT
iokTZWSgeA8AzioHFHZbRYlbIjSDsywaR9Ypj5Dj8ExGXG1ER6gZnCysUwGS
hnIiqyVfHLJIuKl3ZXWzzOeXqpQPZEVz2p0eKYCFKypEJ0OCBkglvTn5rOLf
okqdEsARw0FAb6dZg9g+yKZUT+9hUz5WOjYrkHQZKRsAJYj5oTkL84hiu6Ci
OJyeo15pzSdJCojuzNAn5OQs2/DMmFntYyFhzC9traOi6XYUJzSaIwo0RjiU
AMzS21rC/KdljrtDXZVyvphFFGIBoyfRLELrbJg4H44CaSHI2+q5rBN3fhhZ
PVhFTHlVZAQKp7w3EoUqmbSXfpygjE/yc5bEuo8kQ7yTWMYZPZJqU/kyr6FZ
zkEIDBAGSOMSUR52jCiyGGROoCGlpZYAfDjbP3PRilN7FISEhxk1PUqXL64n
pYNstwSfvnWPUt6GEtGdNo2em6mai3Avf2bNGV9PDQeS1D3Li2vamovF4cth
uKL8f0xjwrB6SXLLmSKy+OIOj0kBnIlPVGTHykMkAqAoLV1JXOFsHWt+GCxs
e1ErTYGgrzxaiNAqGH8ia+g5eS/eoITm0oAiLdxtoIcsuuwZERQAf11AsCKy
JFuqti/AT7I6o25fkUcC/suyqjndiq5njbLTKQ3Au5fCEah/gfaoaZYe2Xqv
2sjt9Zmeicj7anWYd8psomVtyqdxGartmXNpkcQQjVZq5eb+qqS5hfpJbq62
QSpLinqi0ARYNhJZ06drkyZmfLGBaa76LuXEty5cvh9h0ApHdxHSThR9ehG+
j7MR63UY5sehog+FLwvR+/JHeVl8pKZxNZQd5LeKC0TgekWtiX2Lxbw1mY/e
BLKY4bKcVSBwtvgcQ5ZcVcTzxium9mK1ohtGlUP6wTyEk8jRmALyRkfW4qS6
Fz4l8tRlbX2LdhCp/dVIabiwArboaABWkuBITrUbRwsifmCiit5UUkiylXhu
Z4T6mM9LjdaqIaZ5yh3L7u6cE8otQWrByStqQAvdgaxKhDULAnwe+VjGnekr
5+mytH6LCAqSDS90pi/rfdhO17Ww9SSOpOVSqVCaSzvpOdqg6IkrXdeTHN9j
UYxz402cGx+VUWpd6cCeinXuRii5nwHmTGNJkR++luKGH+702gmNeZG35Im4
+OsFGYcQK9lZq8JlGzCYjlUprgcVOOeuur5ptKZffJ9O03X4dhMyaTJ+/V9u
/76Y44gwjcSG3p9QLUN3xnYO3Ln/c9iX60z9ftb09a5TecSGRXKNXIR6+w/I
yd2CpOKOyCzDVeLJyv9pGHPu9tsgFIzwjkZ80gh/fC7k3gRmHWWnL4paVRHT
qdokdgshm4zP3ZP3ZV9xQkNui6ZSa61uNROBVPwjfDnH91RpYNaO3NmoJbmz
1giMKW3dlaVBTXNHFZBOflu4SxqJH+SjLIXSYZzq13Yf0bJa7OOOfzh/8ecD
O7ZHB0D5wu8BT354/uTbA/M9vfNX+LkDCESIMSjna/u9EE6kZgYDWL62zx89
/wHp9tjeZ1LKVLChQHOEANwPo3m6oIso1XVfbg0jc0fxFY5CPxCZGjS2+YA1
5c7QuNcLdGQBkxB+eBGMfyHjXETTXCR2Q0kmZKysi8vCSQkCsw/TXelxOkrP
NCgonszc64HMRAPICbp3unmag7EbsI39Dx8YnKWqz88/H3jb2P3Q3dySLEgg
FewMVcm+vXmVP0wRFHA/sRdBoPwFov5FECp/geaUI+HGFGmlGBddguigySV0
qNGFRQMexSG1DRt5yeBD4gfiWCB8nVAJZ0RAJImuecTObP64pAULFq7W16Q/
MIpQ+raBUWy5XKOJqktmEbsuolCEXp9e6DtzPr2Uok2Ip9oLBEOCKKHgDFEi
kgVeYrUhsKgwchTLUNxXydFT/VuSNN6Av6jZyixxCfEFyjpmm5r6fuyL5jw/
iJmKJ7TGs9PE8XhVodGYCedNvlyOUcxChU/Kk7Apdl2BzGHigm9CHTuORvvH
r62cGJCNXurYG644jplgJK6GayW9zDnlhksmqTROdC4tnc2qTDQh2koJwuf5
DLTKJu8qr4bkNtY5VcCjeDw6VGT/nPtOq12AaNDszJQmJxs/fBsfbyENcfB6
+/y7LDJKHkvAsPEwApIn2Tjy44c7MbkLelf0sf3EgoCcXmgEWjYCy5vZrPuB
epg8aGweWQiEMyP0IoFVCYv0LfRocvgZ19MmuWaU2FdR48Uedm2OJPMQrUEB
6RQ6dJt4vlD1SsqKEyEwIWtRqdHpU8Sq8Rel3xGlZ64Zknrxk1B4DSBesOSe
ymexJBQLwclXUhVAx+0JidzvOaYDJYGOqc5zuLaQDA4fXByaMTHPxBvcywKD
KKReXucK1KaBF445u1pbzoLLsQ7SIoOplYpXX9vTF2ffvNo/TgQ4EnYGZLqU
YA3IdoFMB5LJQVrPYQnLxOP2oWszYrBIGAhYjvQHiuPYDS0P0+eJuQSnxhWQ
EGCaDkQQ9JA5j4MZuQx2jU63sI6NRg6IAKPHTM45LuKgW0LDhLecUomScxWs
e4Cc6guVs2pO5jK9oCBD0EvDd0HEG9tDPkuEIxBbsLSXxKkc3QuY+FCpx/0+
nexr++UBG5W9jzqy+LUxNTQvHDU4vi/3EcibDFRfHuHF49j3T7p42Ji4QORx
F9gn9i9sfDweWJLpIdAw/RfH3SUd35NDAoQI8Z1MYXcCA9hb9QUDRCSdo0gi
xMatGJW2U4IO77SpjHQBaWKRiRrwhLGjD5ymoMgcgIHxDoxCq9G4gAn7QE6I
Cu2MAp7ibVmg2ZoHjgpxWGeX/N2urqQzEHi5LfOLoOhrjDoQ82lo0HeBxtFP
SUD8C27QQYnFrh3Xcrllhe/7i7SoT8Bah0wsw2/oinYZUZK3NXsix9A8f84h
545KbYaV1SPGqxSHwrraGzTsJ2YK5Leb3MXn84356HydMpImOFrW+cOwzBVV
k1TIDntAGfFc+JLVS+ps2yO1RNymkYLYgZ1Rf1uKdq0N/AYHHIQnluHesNjq
DOmoLQTYeX4VhNb21Uz0RsWoZGKsRGhs1kdqmHZCh5JRWDn0qmHHrKhRRJy3
EuiWPhZyQBsMpWQxFA0mvwhYRVYyH4086lcTnGwWSnCdDWBx8R7WoTKW2tD7
ZK6g9mK/ybATZT7dzC/zVho3woythGYyAejKG6BrHR59BcIv4ooA2lfk9u1a
FB8icDBKBvqLRx6Yc7PKWYXhdeiemHr3qbi95hr7+6QSe59sxAI7UUwffi8H
tixWrmxaTInjS9ynfibvixWbDI6+/CKVhVD2MFH5vV31LA86XgCODhIyFDRN
SfrhcM+aAIJMbA9h02SsTGLkWI8zIYx8N0H1Uy3sG0vPUUG8M4n4ALo26lkl
d7YKXgw1ZC58ajgCTXmnhsiyMPLRrhrsXXskDYXs47ChECiaA52GEp+bFtYK
QLTb5rSn7ZSRM3X2+qAEqGtdEzkWwwhYcUgz/X0rG4Udnrt5Z8SGpMJxWB+/
cSp+T8zf+LVY6vD3TgespOssCQNh5O9ww1l0qg63r4rqE2YJLdiTgl9Jrh9T
WHRcRrNqxGa8folX3lMaDnPs4RMuTdBUad9ceUWCl1lz7SQRgpCv1S3YdITj
7EuMaiOF/rArnZOMSe7bIy3G9+sKC1DjMsTrxkjM/boCXCZ32nW2FA3kb2i1
3x9c1dvq7QGSslHHuo/fRuoeOuLURRlq6sEB7w9F/ZNWYi5gttjNKUP0VkAk
B5RLEqOOxyZaoGesfbqQtk6NjGAjahTrTpZOFB/yvc+o8VqtMasXgz6Pi5Fx
8cMqFHi1GJGQ02OjRp3u8symJGMPtZ8AbrHsKTU+cqWFy81qyj16iERcVWsU
UYza/yTiEraAjQzsI2nOJaV0sxh+gGvP+/AIadYKG4+SX0kMMhQU7FKCOAC6
6WIBtTBwkVJuIci3918j+z4wkWArSIhbo2H24151fwmKcCb9EIyn4yNh7dqK
LCL/ciMnxGdoMbg/TDTD1q1ofCmaXBpa9clJfKtX2aaJ+mXKNWJcJBfW1/y8
SFKT1lNNaulm2PnaXgH8CAZeGGXtWLOcqovLZV+gw2kR9ynBi3/IdlnpUqKF
X80KKYKHDrpCHZLJdVB3kx6ZV+FdkE1Bt/l6LPEwDbohuYa4bp8Ds5q4Sjjm
sQgqp20k+oub7uMER0caDJaU3jlQ6a1J5L6saUP4ZJ+DHKURy5OqUe3VppH2
BwyXc6wIjw5H8Vz0EI2RweCHtHmCUtVLDHgOQ4E0DGaMLQ7tSxSUqKtdCAwa
FNULCfcuRkGd6DA60kTBUk4fUSW3rDwWSsKkq1KbhfKE6UF+eLmugFUN4jMn
STl8Rmgw+5iN8K5Yh1bxg4cJVliHFV58WwnXiqBKJWR21CcMjlyQEs4YIHzU
OoQiWl1+SZIMTnHi11UxFxKxNdSQw4utHL/KuupoV8RYUGUd7iRonNlgk2K/
Xgcy2q1Adaew4ZU8Y/qLtQcUkOBKZLMnUdPMV9xkupz7jkJo4NIb7+mwKb2F
aDLuVBZaRoL7M0vMgJlSLg9FiEt1eqnjvSk9xXPz+aB48nJQsCBPVWc3iXbF
dsmG0VqKMDu40zZBlUlsCyqzk5i1KhqXs+HRQQ7SJ6GZKAmN+Ylm4kU1Ayj0
nqlj9+QcNfSbRF3Haz3TbRDWKuEixGVabVmJjU+BHOKZkGwI64+bA8N9tgxB
I7YEEM5rQHsgIRnX6C/s5hicIB/QZV6SWrWVAFOkJ0S58tqEFsoLFQBJkHEB
Da4pO9oapEsAgTOKpVux5iDbeXn+HRY2iEX2SBshc1FKv13bJR6CyinEYrWW
dkiIKMd9EmWnSySNkuJxhOgTG+06wYm9Z0hHGjbsycSBQYJ3dYoOy1kmyp2s
8/yGc/+4Y4GYqlzeh5YGV00v6C1F2fQ+GLpxucIm8tyTKYgEG77dUVQsvy9V
CsEAUJIqIsOBa/x+3NBQG3x2K0aAYGs+0vjIRYMniWQwMieSSQojwStn/388
ryyhkZL1am6XNh5QAbS0h+k/iw38NxDnSbOPOus0GlUATzsfAKlXSRx3pe46
EgaTzPuACyB9RBoelC3oxGo7JVJlbY0wlt4C/cwN8U7NgCcu4NrzxaJlWTdv
QiNkFjIl1Xk6vZkf8ni9DZiNp2/CnuMOxnHQMavmPOc4Go+ayTRjWMLYjehi
lN/4pgmB6VeCiF+S7B12cLAf7vS0dei5Ns7R+Ej4vaZiUKiVCao6UJe7uHlK
T7PwrNHAOu7fMdBaIhIVvLUgaxK0QMerxwwXIdGXv99JHZKHcAjKGor6nUVp
WIMBQaI84RC9SfFZtBPVTsqe/B6u/0AYjf5LjOGeYC+T3+Z8doWWp+eEQ+zM
svp4jpUcsY8UjzKONBjct7SNEkKHj+eLiX3dSnpFYEWTBwJa4Y7R5SaQLiYr
u01O2ShwL4DEADryhjUEHBoHiUYX0tRzmtIJxcUgMe3ilBAcxrkuhvqbSSn+
CB7kyCPE/Mn8fjxOSGmMFYZL3I3/NQF8ulIXwS/Bk532ta4+ngt4cWD2UA4i
vKze9fRDoV9XyGz3tW6AgMhBhKAIeQ/9mgbnT/NWJG4D5pIH/T2GIR3fgHZ5
iE/1QoZLrk8WlI5wD0dgADjxF70PV2vxbg+0utwdwOwxK3pcZw63vgq9VpmL
v0tIuCsuF6lg2bu80RgZ8gteiwtQkSP24lGkurmFIDJAbrnKAMOi8T1gNE9v
FOOKZpG5+heOcLhsKePIRZRyRZLHp2mNMXHq6JDa2Y/FZyZCo7RLUtdPWcT1
3KibGU+lOD7f1C5tw/ftDYyLqYwe9e3VEk8iQ1DLYvM7ldvZp8AGABDh2GWh
LSOHuDCCd4/TM0p+oQYiYa2x3ZWkRtHLMl9Y4MYPEMMLehKL3SlPcRZbh18Y
bYGu4wTLfqgnxafpdfRE4k4SaBMqESKUGzFOq8MkZQfFPtcTs1rVyhiOghnB
3US6h2TimlfUaJECbwd6QGaDOZ8PeXHYplB1n74qFtzDKHNlf6jxYrS1Xj9A
yJZSx4Mz+8LAb12ZCF/WJA6+wY3s55PLyajXnIdpNoFplyPeri68adfZZw/c
qp00KuYwTY9iv2iayZZ68311s5HkEm+Dbm6BZ97NF4TnuS3RgdxOVe7YuvHu
fdNtN6TiFIuYztPq2jGP+EIpvjtocS2seuybVnFykZiQmB6F3sqAHr3oOlE/
uWXrrrxpEaSENDapwYPc4kD40eFbMs0d8BD/PBrq9hqqNztsopJRLrZ/ZxXx
FBYG16S9TyjMNWXPlJV1BUBP0AMXTQ3PkyvW36QJuhC1wB8ZhQMkuqX2YEO8
3jS5g9JuV96OVNWVvQ84ntpXluwbzqUqjCXkTVkmwx+5FrgNAaefRFaYzNeu
i+vRRDP1RDloOZ8d0Q6n8Y1zuURUmcqc0JoSnKXRvMJi6J9H65JinQRw5E2b
TZdFc+XNPSHuYoP6jJo1RrVmKFQFQFgyxNEmkkR66Dqw+CnltbAdAw+QlFBp
YAqnSyiGtSwZ+7AHryR5kK+1dlopmsIMZVdT9IQr1uBskvD2YlPTHV1uMjip
Ns976kCR4TYsn8Yb2KwbTHNYyfrRiiKb6MCzJFNEtn5xubgADHGdhVKbQDKz
MBDFXe05tJbLj5xuv3aFO90SsEZNRZ5j8ldLdoa4EZkW6plzfTspMEGVYyTZ
CQQpX/AMOyFjp0FxcCx8iDEKMqtNy6F8YpGn5of0+fISDYzkf1rADuh1JrpP
GW5gIOd4iGXB3D3g7Uk7aJcXj7/R1uQEex/rMDxUXtkMl1e+jdY/8o1Ao9qq
9MjFN7ftLIidjD9WkDEZvN9aY6LVsVXBW8m1BJ+N84CivDD1GLh41L74jgut
85iGAvAAopwTl/ZO8Cj4I9gRtvDcUMIDrvRXciN1c6Po7fOP/Clq5o5aJ0lY
4LylqNjqFEdgtUw5FZdTSa+jw+pD3kISipShto5r7bKk62Qg+1WBCO98YU1v
P3MUnxvynWF190YHYYWzC0E9fT/JU4cVqEoOGkatyRWXQa/szncCk5Q7waLE
ytA+9JYjY4xwIF8RN04g9MmRcgIBvOghYLS5pxYxmQrKdpmzN8/O/irtp7+6
d3iIElTSWThWYIOm03cAtFVdrPpCj3FBGjfi6vyGpezSNu1BEYyONIw7K8oN
e4Fi0V5FAbKU8eii1vbkvmt5siBBOdRaksg7FD0Nye9RV+ykLvjE3ioWtLeS
H0fv2KSD/WAMZyctlpqAxHm60oXeHy8VPfNuAgrvnLgrCmKHhCHSVcU97NmF
6BqVhTFHQM0427B7fshSKDd/xCVm2rqab7j2z5xWCUScI0RNEiHKCYzzILk3
8WSOegwaphPgClem1uCPhK87JyN5GIUgJYfgb8w30/VBaM7TLgNyMKyRCFgJ
TQRxLZOwH0ENF0JLyeCio3ZvC/FNSMvb6GKfcj0uFzzbaUPc0wr39h2fT12E
tPlYL+VYaxt1KD2XavBO9kCRkfqQIR0I7HS+DqGkUkQGzajKhI//Zlw5jcnx
Ktvq3rdSi11KfhCTBxisqcRlSC5xWJXetLKgwgVWmc+zZsP1iDhlUrTtHhYk
xxzU3cx87o5m02SUZ7Jcbt1zsBYOpxjrw2EqQyjSh1WIlBvAe6g7RMFXHs2N
b0K4hWff4/bwuEEz2OCXAks6rwjYWro/oN8dAa91wbRc2U49U9GG0/7gpstA
KZt1grl8YZkXjlDXbiWhsUCtLyGMsHNHGp8P9PLGLZOkg6h9U6E6TQmOUrO/
FKJe1WNYM+c20e8sVd97f4/+kYHv/VfUGJ0FX3r37PTV6cB7D4L36LWnWp5l
YD66cFJP3LUgGYCryC49ipQgm1b1OzfKiRiEXGyFDCbIkAKdlEVvtJCZln0o
OqpvXPQ0YHadaCBXTPqWSM8X/6rykBAs/Iqcm2uMPJbTkSVqKmnPiad1gZky
B5gmmzaRgX+xIU6hSIYuAIXEMr/xJZ/ppDGUFLWutesxQlEqg8n9+x8+dPu4
YCERUMpT2pmUBGXbwklk7Gmiti7pkU4xoCOpwx8X4Vc9hFVhwdh4HRg+mYTm
uKieHb0G4obsfKMC8M/YRSRm6aCQpg9m8xs0CcXwRtqgEK/7oZ9l4e5Myq1Y
WdsLNqydNXwRA7dg+BvBDSPeeWV7Oytdxq4bX7k4IH/ahyByJUQnH8wfxBKl
QKKPaFZLoGuk0X3OpMXx+Cg7qtZhvNYxsc8YASLCrdYaZiSB0L2usMdtTlKD
CW9blqL6gOCyT18kheI7IDWP0fUAcgxg/5jcED/7QGj67JN0BFzQCVAX8gW6
SrKa7GHA2IgS+TrjCaN3RFE2w+FdXuknGkORnXQgaGoL7EoqlDZiKyjaERew
lrBJ0E+K1WY1AtL8nv4wzWbFcUTkJ4gkCVkSa8NI/csxLQHYXKaB0Sa2vWNG
iJ4EHeEYKHO7kULRKpVSCrUEL3qBQIred2QUJgHcQYfq+OOetWD7xL4u8RPi
GLoO1GqINyMmF6JRGdVnNiqYYlysVMgNYpX2n569OYAffCH7pxJVaj58mNcg
94/zYj3O6tkVmizyrAbaWFtmaj4d59JX24YBnVuUw94XNdA+eiOK3iMPQpMt
GxDWjr6cNbOSq4VHohTISoYskQT2WytVtdHhkTcU2a1EKWqJxIHfLK6fRbdD
VGhDVfl6b82Yv6Hz/+m8IHa9xqrIGmNsI5rL3gS73kyXgo6Tvye5cVryXoxK
OC+cEBsv4ulV+Ta+1HogoPK8IeZrkWeVxCixMptdAXBfgrTUqkRGFoU/HB9R
kMopiU8gsVSbepYnKwj1DuFtL0DTf2/fAQKDlEex9ti2ZAujrwigr0Hnywgi
z6KKMgMxJKkCIT7afXbjoaIZlrEgbhLaOTMpXuGKuSb2zU3Jvi8YP06iUvn4
wCUwp7ERw01MRp0KP86haIJ4L6AfCZsfaVhRUlAy8fyaZb5w7l+V5/vbKexY
ZBrRIbFO4sve5m1IrCWfJ7p8I7cXWWpGzmFDdoY8NOJ4zdifkKES/UDiOSG1
gGc2bX6k1jmJy1CTT+a7bNn80ZtnOCSQkZVpsTU1IrB8sSJxLlDF+xRkssOF
o6hYi8a5Jk0w8Z4QqYCoPyQt3LL5HE1fmsPG9gsa/0TEyHDDewOePSOj7qVV
cyNTHlfigH2TvYWXRDsi6zIQXQCVazJBnHcF2Jusy4858yR/n9eYCgYXuKmF
Wpizp+fPMA8d5PfZO+BveNd9OM8X5m9yH5UxILeNuSiqbHV/fFlNf7g+vvDR
blQyviI3m6qFbBC4LuqK65ZQO0IUb+ZmmgMJO5jYR2jsCdfPEga2+gExURKa
Xb0XXFVQ67YhqeA2JWXCYIOMZQttqpcZziXZcNk3KlnuyEl4JifWZ3Y4L4Xm
GHFeBkttizCshTLJ0iIx30T1any5mS9cqSEWaHpVFpzkC62SolE8Q6E6rkrL
rjIwx/dIUz5+EM5O2VsY3FFcU18a2YK7i6E9SLGdL+/Fg91qIV9q2Uaj+ydj
IMEEYTo6N4j7k1iEhcMx/q7enmgjH7hGUBDPHr/EagJAxLDpjcS9AFXO67qS
2Bopjk49HFSy5f0EBiWEqEgQHBG+OcwyHrM448FhlW+h5oOYqN6dwwFyE7dU
nkQSg3rLuuNPLIPKuhiz4mRadfD1BMGLD6JRQd0Fk7PkTQwc9wQHZ6T4kJp5
hQbIRjgREO0+zuLqv8IhjCc4/YDrw48Ieamc0AhbChEWHxsthzoMIvDG0fHI
fsE9Ko8VxA5G5FnGLSA7jvOQXL553uIBATBXa5cIiMAUkqiQTkw3xXJOtW1R
SqdlSE8DUuUywgwYccVRRCpJFeV4sSwur9rI5bzfUUbsx5WRpAmJCRjYwSiS
w9DXctW26+bk7t1LOODNdAJ7vlvm7SVQufVdpNlIssdMysYgc23xl1KKTsa7
QHgQd4vnSMI57oecI3KtVBT9sgeqxiuxfZ1Tnlpbb+2pPwrQMdV0Q5TDtbPg
2gCl0zQSITVWNEH7yRGCRVzB+F1KY2TFZZVt4STdpu8djthWBfgBTL2quyx4
P7RlGPV98M6D1l2aHDrqUWho0qP7ZbXi1JA7WPiBGgnZx1GeSaAbhg6Z/kod
zHTQbj7NOUhJm2Vgzcnp1tEnIgUT+12ZbeByamqkplFY1ci/5ZKRnMPZxdZQ
bqnkBburiztJYZh4fV1QMSiOkKChyeqwNSLFiH+SqwiSlSFr8FVvkYx66kow
COyPqslwvQuU4mqkXXMqf1RTtroYMpt+Y5O8PVZrJ+ZjrlXFajGLes1yPAzP
ccV+PYHCHkuCKPa1HOKI/oJS/PuIvOjRhrNGZVy69jgVDiNjVkXDZ4SCK5x+
hoYZTFQIbwyxH0umgTi5WbcOyzValkOOgiggJD6LpUZFUbAY2/JkHGq7mJke
RtBWgQnKyS8BtW86cvWntL6s8/8gNqM6kth0gE8DCe27rW7hJR/ALoFUoTJn
gkgN19Z47aIUOHg4yaBSPV3698nhMvviHaHkzWQEseUSYasdXAKfNMmcUzg/
zPWlbMUGaXUb56xy0H1fJMsJMnwu8Yk2jcAnhGAmJkp/r3SKqKIt4UL9BCZb
IjHYulk4TbwnBy6IWRJEc54hQy3QxnwULMVLWExPIKJY6uSQ2DPrLNsRy5Xa
r4GRwFlLQ3uwcfbgQivMcsMr9BHxSikN1sXYaJWxburw7kCgj0b3UAV8l01s
B7OJo2LVnSwLwxkuqHSKA4B61zQItUE/lte+GXjQdUhZvO96qEfWVz8ubS7S
42ygOsrqef/UjnvY4zoKgAnViX7hzuXp+qykETXclIAdVsJ9H/OP9uozgSWG
y35qRZsIW+JxgObCYrCrlxb0lgPd5R1gO2tsYYlyA5zDQMzsQcg8EVyUI25K
CcNMA0q59vF8RHRDLLlbwmiKEx3toMWudlsl0PMpBBnthtr9lpvN7iYOcdaO
r5ztkRxE/OiMHDvxDu+QBk7sk4DfYyVorIEAst6mziPbS18DQW9bcm0wOWyZ
eMtIWmM4K5xnMNy8LePMm+giAjenYRFBmL72e2Q73yyyysZxdEiOYm+6ZLyI
s9S+Ba6gXkwS2rjO5XrDjdGnztsSCHpShYZ7U/FbyOM3hHzaDxWvgzVS0m+u
cwmrxfiaAhURE5UMeZvEDSS+Ixd+Kw4X7Gwb1NChg52zkwHOZeQrxIxU6EEB
MxNLt7NsUTwteX57JN7BOAkWe4UzPAIMe0eB8Afk/Sm9fqAVNDhIbbBp64SK
4s6LZrZpGpXNh9MVApIaV64zPZXrtDwK58qJlhDG6oUyO7qiuNSdNvdEi2IQ
axpG3yHAusAxDuSnZAOUn1zpJ4HXrqNAXfN6wEGJ7oiFqBW8G29ERT+GXddm
0E/umk271WNJYepCEGHccMW9pDAsx+AVXBlyxRXLmB+pGfikx5quRRyYVcBh
yvn5ZrpG4xPQ4uFbzolYo+FLuok9uvaQC+wZ8TNt1VdNVQgi+qUxLb6kX9Q4
kIIZNT6mL4Y6dTQEzBTlO46EMFFnwhCtkHSIfyzOOQ09ZOwZ3tVv28W/CDmQ
jnzlPMijS2tZsEGOEUJEmeSCBvppSPW7pMAKkZQm8beiBuOjhd3wEsXMrALV
n6TGlUkK0KniOrHPqxvUG0ZxshMSeV0BbaRPbqhcjEC8Dm3WeBJ0NEdhhi6q
ryiIm0nC05YuA6Wnu6TpAXx/rqNQQEEE6vZ1pYtsglaKSoww4ooD/cn0RV0p
GX7dnQfV0oxvYblAIxg9Dxve2oBUnVLy/mZKoeeUPwXLQ0I8wsqhqK3i8PFu
EToSN1lwAFr4ZzbL1xgDRQXB0JDkSQ53qXaEkZM2MQOfarchYQ8TS7vn4HbL
9YtGWEeDYYSKw2R91QwT0cn3OibxKVoed6HEWmOhDqzN35Fscyct8mRUYapa
En2Lt6jao0uN6aHBaRdvKnHSQ8lDPVTlm7xoKRX1qipm0uVPhQREmU6c688S
xMfnOhjtZyhGYEdA335fMJ/U/i9NX2DZfl8Y34HIkC5oyIU4AXNXj7TtBDil
IZFKxD0BDlrDmq4jTxNi28rRYiL3KMG5FH4qIiCy45nGAtfNnlLqLTvV9fJ7
9qyxp0mb2ih+QsCRF0FiWSZ5TxJTpKykiVgHo2SjkgBAZn6NqEMs8cMHWgzZ
VtFfC9eOBjrqHKG/ra/vj7Ghywp1VDYO0a4KlNwZvsgoVmqVJ1aOANXCKh0x
nSwaG/Is2P54PLZITlDmPJ1pZ3KJYDnhUpP5/Os9IDuNK8XAsisXkXxnT5f5
+4yw5/EyX61G9ttsBXM9KqgWIxk/croGUGWWS+DrNVYbUw4uMiZrC6WeFTPZ
K8BwtUo4GUtoDMlDoUWcxVf8+TwHhESwfO0K+LH2DYfThIpnarF3hnjggc5S
/1wt9Vas80wN5AyMNP3Dg/im2CyLCljxHNhr2xY8JVe2gXubbjTLpFVHsYnN
87zQ53lzBSrw0+Wj7F21qbdumDnmRywRdvPrAigiYI4C7hiwtpvc8v8AnVv+
qsLcAAA=

-->

</rfc>
