<?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-chen-opsawg-intent-webassembly-framework-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Intent-Driven WebAssembly Framework">WebAssembly Framework for Network Management in Heterogeneous Edge Networks</title>
    <seriesInfo name="Internet-Draft" value="draft-chen-opsawg-intent-webassembly-framework-00"/>
    <author fullname="Zonghua Cheng">
      <organization>China Telecom</organization>
      <address>
        <email>chenzhongh@chinatelecom.cn</email>
      </address>
    </author>
    <author fullname="Jianping Sun">
      <organization>China Telecom</organization>
      <address>
        <email>kongjianp@chinatelecom.cn</email>
      </address>
    </author>
    <author fullname="Yuanyuan Yang">
      <organization>Huawei</organization>
      <address>
        <email>yangyuanyuan55@huawei.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Operations and Management</area>
    <workgroup>Operations and Management Area Working Group</workgroup>
    <keyword>intent</keyword>
    <keyword>webassembly</keyword>
    <keyword>edge</keyword>
    <abstract>
      <?line 50?>

<t>This document describes an architecture for executing WebAssembly (WASM) modules for network management on heterogeneous edge devices. It describes dynamic bytecode dispatching, the Universal Bytecode Interface (UBI) for abstracting heterogeneous network element capabilities, and metadata models for capability exposure, bytecode deployment, execution context, intent-driven discovery, and security audits. The framework decouples management scripts from platform-specific interfaces. It reuses existing mechanisms for software update, payload manifests, integrity protection, and transport where applicable.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://billwuqin.github.io/webassembly-for-the-edge/draft-chen-opsawg-intent-webassembly-framework.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-chen-opsawg-intent-webassembly-framework/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Operations and Management Area Working Group Working Group mailing list (<eref target="mailto:opsawg@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/opsawg/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/opsawg/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/billwuqin/webassembly-for-the-edge"/>.</t>
    </note>
  </front>
  <middle>
    <?line 54?>

<section anchor="introduction">
      <name>Introduction</name>
      <section anchor="background-and-problem-statement">
        <name>Background and Problem statement</name>
        <t>As automated network management evolves, network operators increasingly rely on dynamic, closed-loop control mechanisms. Structured tool interfaces can expose network node capabilities for automated orchestration. Large language models can generate execution logic for management tasks. However, executing dynamic operational scripts or telemetry-collection logic directly on heterogeneous and constrained network devices poses security risks and resource challenges.
Container-based execution may introduce startup and memory overhead that is unsuitable for some constrained nodes. WebAssembly <xref target="WASM"/> provides an alternative for lightweight management tasks, subject to the capabilities and limits of the host runtime.</t>
      </section>
      <section anchor="use-cases">
        <name>Use Cases</name>
        <t>WebAssembly-based sandboxing, Universal Bytecode Interfaces, and automated orchestration support the following network management use cases:
   a) Telemetry Collection: Distributing lightweight bytecode to edge nodes to collect and process local telemetry, returning the results needed for network management.
   b) Policy Adjustment: Running short-lived tasks on edge nodes or compute boards for traffic inspection and service protection. Each sandbox executes a task with its own permissions and resource limits. Concurrent tasks support different user or service policies, subject to the node’s available capacity. Packet inspection uses authorized host capabilities.
   c) Device Management: Executing device management operations through authorized host functions. Tasks can access and process local resources without uploading all raw data, supporting deployments with data-transfer or privacy constraints.</t>
      </section>
    </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?>

<ul spacing="normal">
        <li>
          <t>WASM Sandbox: A lightweight, isolated virtual machine environment
running inside a host process, executing WebAssembly bytecode with
linear memory isolation.</t>
        </li>
        <li>
          <t>UBI (Universal Bytecode Interface): An abstraction layer that exposes
host functions to WASM modules. UBI interfaces describe available
device capabilities and hide hardware-specific implementations.</t>
        </li>
        <li>
          <t>Node Profile: A structured metadata model used by the framework to
advertise a network element's supported UBI interfaces, execution
capabilities, runtime information, and required host function
privileges. Capability advertisement does not itself authorize task
execution.</t>
        </li>
        <li>
          <t>UBI-DP (Universal Bytecode Distribution Protocol): The encapsulation
and messaging mechanism used to dispatch compiled WASM bytecode
binaries along with metadata across network management channels.</t>
        </li>
        <li>
          <t>WIT (WebAssembly Interface Types): The interface definition language used by the WebAssembly Component Model to define types and functions crossing component boundaries.</t>
        </li>
      </ul>
    </section>
    <section anchor="architectural-framework-overview">
      <name>Architectural Framework Overview</name>
      <t>The proposed framework consists of three logical planes. They separate task orchestration, policy coordination, and execution on edge devices:</t>
      <figure anchor="arch">
        <name>Intent based Framework</name>
        <artwork align="center"><![CDATA[
   +--------------------------------------------------------+
   |        Intent & Orchestration Plane (Management)       |
   | [Intent Parsing] -> [Workflow Compile] -> [Cap. Match] |
   +--------------------------------------------------------+
                                |
                                v (Task and constraints)
   +--------------------------------------------------------+
   |        Coordination & Policy Plane (Control Layer)     |
   | [Static Audit Matrix] -> [CaaS Pool] -> [Hash and Sign]|
   +--------------------------------------------------------+
                                |
                                v(UBI-DP Dispatching)
   +----------------------------------------------------------------------+
   |             Embodied Execution Plane (Device Layer)                  |
   | [WASM Sandbox] -> [UBI Host Functions] -> [Platform Implementations] |
   +----------------------------------------------------------------------+
]]></artwork>
      </figure>
      <ol spacing="normal" type="1"><li>
          <t>Intent &amp; Orchestration Plane: Translates network operator intents into structured workflow models and maps required management tools. It identifies target nodes using Node Profiles and passes task constraints to the Coordination &amp; Policy Plane.</t>
        </li>
        <li>
          <t>Coordination &amp; Policy Plane: Acts as the central management controller. It audits requested tasks against security policies, compiles modules via Compilation-as-a-Service (CaaS), and generates cryptographically signed bytecode distribution packages. The signed metadata binds the module digest to its approved host functions and resource limits.</t>
        </li>
        <li>
          <t>Embodied Execution Plane: The physical edge node running embedded WASM runtimes. It validates the module and its associated policy, enforces resource limits, and restricts device access through authorized UBI host functions. A warm process pool retains initialized runtime processes to reduce sandbox setup time; task state and permissions are reset before reuse.
  Host functions expose the sandbox host’s basic operations, such as reading a counter or updating a permitted policy. The UBI defines the interface visible to the module; platform-specific implementations access local APIs, drivers, or management services. Each invocation is checked against the task’s permissions.</t>
        </li>
      </ol>
    </section>
    <section anchor="core-operational-mechanisms">
      <name>Core Operational Mechanisms</name>
      <section anchor="dynamic-resource-and-capability-discovery-mechanism">
        <name>Dynamic Resource and Capability Discovery Mechanism</name>
        <t>The discovery mechanism maps task requirements to available node capabilities:</t>
        <ol spacing="normal" type="1"><li>
            <t>Capability Advertisement: An edge node registers or updates its Node Profile using an existing management channel, such as CoAP <xref target="RFC7252"/> or HTTP/3 <xref target="RFC9114"/>. The profile describes platform information, supported UBI interfaces, and available execution capabilities.</t>
          </li>
          <li>
            <t>Semantic Feature Graph: The controller maintains a capability catalog, optionally represented as a graph, including supported operations and resource budgets.</t>
          </li>
          <li>
            <t>Intent-Driven Matching Filter: The controller selects nodes supporting the required UBI primitives and resource limits.</t>
          </li>
        </ol>
      </section>
      <section anchor="bytecode-dispatching-lifecycle">
        <name>Bytecode Dispatching Lifecycle</name>
        <t>Bytecode distribution <bcp14>MUST</bcp14> be atomic, secure, and self-contained.
   The network controller utilizes the UBI-DP format to encapsulate the
   binary and its metadata payload through the following lifecycle:</t>
        <t>Step 1: Discovery. Edge Node registers its profile, declaring local
     UBI primitives.
   Step 2: Audit. Controller matches permissions via the Static Symbol
     Audit Matrix.
   Step 3: Transport. Controller compiles code, computes SHA-256
     fingerprints, signs payloads, and transmits via HTTP Semantics
     <xref target="RFC9110"/> or CoAP <xref target="RFC7252"/>.
   Step 4: Execution. Edge Node validates signatures, provisions execution
     threads, isolates environments, and executes the authorized module.</t>
      </section>
      <section anchor="wasm-bytecode-semantic-properties-and-core-capabilities">
        <name>WASM Bytecode Semantic Properties and Core Capabilities</name>
        <t>WASM bytecode dispatched via UBI-DP <bcp14>MUST</bcp14> conform to strict structural
   and behavioral boundaries:</t>
        <t>a) Single-Threaded Non-Blocking Loop: To prevent thread starvation on
      low-power nodes, bytecode <bcp14>SHALL NOT</bcp14> spawn guest-level OS threads.
   b) Virtual Memory Page Restriction: Memory configuration uses fixed
      WebAssembly Memory Pages (1 page = 64 KB), statically locked at
      compilation.
   c) AOT Compliant Structure: Modules <bcp14>MUST</bcp14> allow instantaneous
      translation into native machine instructions via AOT engines,
      bypassing JIT overhead.</t>
      </section>
      <section anchor="universal-bytecode-interface-ubi-specifications">
        <name>Universal Bytecode Interface (UBI) Specifications</name>
      </section>
      <section anchor="telemetry-and-sensing-domain">
        <name>Telemetry and Sensing Domain</name>
        <artwork><![CDATA[
   interface telemetry {
       record metric-data {
           metric-name: string,
           timestamp: u64,
           payload: list<u8>
       }
       read-metric: func(name: string) -> result<metric-data, string>
   }
]]></artwork>
      </section>
      <section anchor="actuation-and-control-domain">
        <name>Actuation and Control Domain</name>
        <artwork><![CDATA[
   interface actuation {
       enum pin-value { low, high }
       gpio-write: func(pin: u32, value: pin-value) -> result<_, string>
       i2c-transfer: func(
           bus-id: u32,
           addr: u32,
           tx-data: list<u8>,
           rx-len: u32
       ) -> result<list<u8>, string>
   }
]]></artwork>
      </section>
      <section anchor="media-processing-domain">
        <name>Media Processing Domain</name>
        <artwork><![CDATA[
   interface media {
       enum resolution-mode {
           res-640x480,
           res-1280x720,
           res-1920x1080
       }
       audio-start: func(mode: u32, sample-rate: u32) -> result<_, string>
       camera-capture: func(res: resolution-mode) -> result<list<u8>, string>
   }
]]></artwork>
      </section>
    </section>
    <section anchor="metadata-definitions-and-schemas">
      <name>Metadata Definitions and Schemas</name>
      <t>The framework uses three types of manifests for different lifecycle
stages:</t>
      <ol spacing="normal" type="1"><li>
          <t>Platform Manifest: describes device capabilities and execution
environment.</t>
        </li>
        <li>
          <t>Data Collection Manifest: describes data subscriptions and runtime
collection context.</t>
        </li>
        <li>
          <t>SUIT Manifest: describes secure software delivery and execution
parameters for WASM components.</t>
        </li>
      </ol>
      <t>These manifests address different lifecycle stages and avoid
duplicating information.</t>
      <section anchor="platform-capability-manifest">
        <name>Platform Capability Manifest</name>
        <t>The Platform Manifest describes the capabilities and execution environment of an edge node.</t>
        <t>It can reuse the platform information model defined in
draft-ietf-opsawg-collected-data-manifest.</t>
        <t>The WASM/UBI extension may include:</t>
        <ul spacing="normal">
          <li>
            <t>WASM runtime information;</t>
          </li>
          <li>
            <t>supported UBI interfaces;</t>
          </li>
          <li>
            <t>available host functions;</t>
          </li>
          <li>
            <t>security capabilities.</t>
          </li>
        </ul>
        <artwork><![CDATA[
{
  "ubi-wasm-extension:server-metadata": {
    "runtime-version": "wasm-runtime-v1",
    "supported-ubi-interfaces": [
      "telemetry.read-metric",
      "actuation.gpio-write"
    ]
  },
  "ubi-wasm-extension:governance-and-security": {
    "authentication-supported": [
      "mTLS_v1.3"
    ],
    "capability-tokens-defined": [
      "telemetry_read",
      "net_outbound"
    ]
  }
}
]]></artwork>
      </section>
      <section anchor="data-collection-manifest">
        <name>Data Collection Manifest</name>
        <t>The Data Collection Manifest describes data collection subscriptions and runtime collection context.</t>
        <t>It reuses the data collection model defined in
draft-ietf-opsawg-collected-data-manifest.</t>
        <t>The manifest may reference external resource policies using policy identifiers.</t>
        <artwork><![CDATA[
{
 "data-collection": {
    "platform-id": "edge-node-hetero-01",
    "subscription-id": 1001,
    "current-period": 300,
    "policy-id": "tier_heavy_compute",
    "runtime-status": {
       "cpu-percent": 87.5,
       "action-triggered": "forced-downsampling"
    }
 }
}
]]></artwork>
      </section>
      <section anchor="suit-manifest-and-bytecode-distribution-envelope">
        <name>SUIT Manifest and Bytecode Distribution Envelope</name>
        <t>To securely deliver WebAssembly (WASM) bytecode components to
   constrained edge nodes, the distribution framework adopts the
   Software Updates for Internet of Things (SUIT) manifest architecture.
   The management controller encapsulates the compiled WASM binary and
   its execution policy within a CBOR-based SUIT Manifest, protected
   via CBOR Object Signing and Encryption (COSE) <xref target="RFC9052"/>.</t>
        <t>The SUIT manifest enforces the strict sequential workflow required
   for trusted edge execution:</t>
        <ol spacing="normal" type="1"><li>
            <t>Manifest Authentication: The recipient edge node validates the
COSE signature of the SUIT manifest using pre-configured trust
anchors.</t>
          </li>
          <li>
            <t>Applicability Verification: The device checks whether the
manifest's target hardware identifiers, vendor IDs, and class IDs
match its local hardware profile.</t>
          </li>
          <li>
            <t>Dependency Resolution: The node verifies and resolves any required
UBI interface dependencies declared in the manifest.</t>
          </li>
          <li>
            <t>Payload Fetching: The standalone core .wasm binary payload is
retrieved via secure transport (e.g., CoAP block-wise transfer
<xref target="RFC7252"/>).</t>
          </li>
          <li>
            <t>Installation &amp; Sandbox Initialization: The verified WASM module is
loaded into the isolated runtime environment with static memory
page constraints and authorized UBI host symbols.</t>
          </li>
        </ol>
        <t>The following example illustrates possible WASM-specific execution parameters associated with a SUIT Manifest. Existing SUIT mechanisms, including manifest authentication, component identification, applicability conditions, and payload retrieval, follow the SUIT specification.</t>
        <t>The runtime-parameters field represents a framework-specific extension for constraining WASM execution. The definition of these parameters in a SUIT Manifest requires corresponding SUIT extension definitions.</t>
        <artwork><![CDATA[
{
  "suit-manifest-version": 1,
  "suit-sequence-number": 42,
  "suit-common": {
    "suit-components": [
      "wasm-telemetry-module"
    ]
  },
  "suit-install": [
    {
      "suit-condition-vendor-id": "example-vendor-id",
      "suit-condition-class-id": "example-edge-class-id"
    },
    {
      "suit-directive-fetch": {
        "uri": "coap://management-server.local/wasm/module.wasm",
        "digest": {
          "algorithm": "SHA-256",
          "value": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
        }
      }
    }
  ],
  "suit-execute": [
    {
      "runtime-parameters": {
        "allowed-memory-pages-max": 256,
        "execution-timeout-ms": 10000,
        "allowed-host-functions": [
          "telemetry.read-metric",
          "actuation.gpio-write"
        ]
      }
    }
  ]
}
]]></artwork>
      </section>
      <section anchor="ubi-resource-constraint-policy">
        <name>UBI Resource Constraint Policy</name>
        <t>Resource constraints are modeled separately from manifests.</t>
        <t>Platform Manifest describes available capabilities.
Data Collection Manifest references runtime policies.
SUIT Manifest describes execution constraints.</t>
        <t>The resource policy defines:
- concurrency limits;
- rate limits;
- sandbox quotas;
- resource isolation rules.</t>
        <t>Manifests reference the policy using policy identifiers.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This section details the security mechanisms, static analysis controls,
   and boundary enforcement strategies required to ensure safe bytecode
   execution within managed network environments.</t>
      <section anchor="static-symbol-audit-matrix-and-link-time-verification">
        <name>Static Symbol Audit Matrix and Link-Time Verification</name>
        <t>To prevent malicious or corrupted management code from executing
   unauthorized operations, the Management Controller <bcp14>MUST</bcp14> execute a
   mandatory Ahead-of-Time Static Symbol Audit before bytecode
   encapsulation.</t>
        <t>The audit pipeline enforces the following validation steps for
   self-contained core modules:</t>
        <ol spacing="normal" type="1"><li>
            <t>Import Table Extraction: The audit engine parses the WASM binary
structure, filtering all tokens located within the "Import Section".
This maps every external host function identifier requested by the
bytecode.</t>
          </li>
          <li>
            <t>Capability-Matrix Intersection: The extracted import symbols are
cross-checked against the allowed-host-functions list
declared in the Node Profile or execution policy.</t>
          </li>
          <li>
            <t>Link-Time Rejection: The binary is scanned to ensure no raw
hardware address references bypass the UBI layer. Any mismatch or
inclusion of unauthorized tokens <bcp14>SHALL</bcp14> result in an immediate
Link-Time rejection, aborting the transmission.</t>
          </li>
        </ol>
      </section>
      <section anchor="sandbox-boundary-enforcement">
        <name>Sandbox Boundary Enforcement</name>
        <t>The execution of dynamically provisioned bytecode on remote physical
   devices mandates severe security practices. This framework achieves
   endogenous security via layers of defensive validation:</t>
        <ol spacing="normal" type="1"><li>
            <t>Linear Memory Boundary Isolation: Embedded runtimes <bcp14>MUST</bcp14>
leverage virtual memory page capping to ensure that buffer
overflows inside the sandboxed application cannot compromise
host address spaces.</t>
          </li>
          <li>
            <t>File System Namespacing: Runtimes <bcp14>MUST</bcp14> map the sandbox internal
root '/' directory to an ephemeral host path using chroot
primitives to avoid directory traversal vectors.</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>TBC per <xref target="I-D.opsarea-rfc5706bis"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests IANA to create a registry for Universal Bytecode
   Interface (UBI) Functional Symbols under the Operations and
   Management Area.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="WASM" target="https://webassembly.github.io/spec/core/">
          <front>
            <title>WebAssembly Core Specification</title>
            <author>
              <organization>WebAssembly Community Group</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="RFC7252">
          <front>
            <title>The Constrained Application Protocol (CoAP)</title>
            <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
            <author fullname="K. Hartke" initials="K." surname="Hartke"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.</t>
              <t>CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7252"/>
          <seriesInfo name="DOI" value="10.17487/RFC7252"/>
        </reference>
        <reference anchor="RFC9114">
          <front>
            <title>HTTP/3</title>
            <author fullname="M. Bishop" initials="M." role="editor" surname="Bishop"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9114"/>
          <seriesInfo name="DOI" value="10.17487/RFC9114"/>
        </reference>
        <reference anchor="RFC9110">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t>This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
        <reference anchor="I-D.opsarea-rfc5706bis">
          <front>
            <title>Guidelines for Considering Operations and Management in IETF Specifications</title>
            <author fullname="Benoît Claise" initials="B." surname="Claise">
              <organization>Everything OPS</organization>
            </author>
            <author fullname="Joe Clarke" initials="J." surname="Clarke">
              <organization>Cisco</organization>
            </author>
            <author fullname="Adrian Farrel" initials="A." surname="Farrel">
              <organization>Old Dog Consulting</organization>
            </author>
            <author fullname="Samier Barguil" initials="S." surname="Barguil">
              <organization>Nokia</organization>
            </author>
            <author fullname="Carlos Pignataro" initials="C." surname="Pignataro">
              <organization>Blue Fern Consulting</organization>
            </author>
            <author fullname="Ran Chen" initials="R." surname="Chen">
              <organization>ZTE</organization>
            </author>
            <date day="20" month="October" year="2025"/>
            <abstract>
              <t>   New Protocols or Protocol Extensions are best designed with due
   consideration of the functionality needed to operate and manage them.
   Retrofitting operations and management considerations is suboptimal.
   The purpose of this document is to provide guidance to authors and
   reviewers on what operational and management aspects should be
   addressed when defining New Protocols or Protocol Extensions.

   This document obsoletes RFC 5706, replacing it completely and
   updating it with new operational and management techniques and
   mechanisms.  It also introduces a requirement to include an
   "Operational Considerations" section in new RFCs in the IETF Stream.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-opsarea-rfc5706bis-06"/>
        </reference>
      </references>
    </references>
    <?line 441?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81c63Lc1pH+P09xdly1FpPB8CJKlia2E4qkIiaSyBWpuLwu
lwsDnJmBhQEQHIDkRNHWvsb+22fZR9kn2a+7zw3kUJvE+2NVFUWDS58+ffry
9QVOkmTUFV2pZ2qsvtPzI2P0el5u1Ms2Xeubuv2gFnWr3uqO//0mrdKlXuuq
U0WlXulOt/VSV7rujTrNl9o9aMajdD5v9TXInlUdnk9O2uJaV9vXGI+ytNPL
ut3MQHdRj0Z5nVW4OVN5my66JFvpKqkbk94sk0Lo3eh5agklC0co2dsbmX6+
Lowp6qrbNKBwdnr1UqkvVFqaGuwUVa4bjb+qbjxRY50XXd0WaUk/zo5e4P+w
3/HZu6uX41HVr+e6nY1ycDcbZXVldGV6M1Nd2+sRNvd4lLY6BdXzRrdphzWN
Sqs8ktN4RHwt27pvPveYOgId9R0eLaql+j09Ph590Bu8nM9GKlGya/pXtHH6
qSH2ESTbg0Ol/rGFlBJRje9dX6dFiesi+t8VultM63ZJd9I2W+HOqusaM9vd
pQfpEg556h7bpQu787a+MXpXSOzSq8uiW/VzvDwvyvKm/3NR7Q5Os26TbqUT
2hk9XkL6povW8q9NhdK0qB8ksPv3KdB01a3L8WiU9t2qbknyYECpRV+Woo//
WlfLVZ+qYxBc8j1sNK2Kv7C0Z7heVKm60qXO6jXf11aGxMJfVvT67zJ6qJNn
plk1vr/MH4q0augkLvvq71rlAxb4mV7+Gxb5vk+rDf6nvk+37uVVn97oYkB+
gyc39rUnT3634iemWAEyq+p2jTevoYgjsmL/S6nvji7fzJiQczaxHziuW60u
G50ViyLjtcfybNoudXzw0ZFFR2/w5m4GGrvymj87/pPQpu4tuF73VdFtnKKP
RkmSqHRuujbNuhG9erUqjIIb6tlqcm2ytphrMidW/aLTWdeDb3KP+lZnfUfH
Fa/yiHa9o9Z13pd4kR6srB9dB3usK7Ua+FHSWqx3XWTaTNVZvHa+wcEVmZpv
sHqd47HCNGlHJ72cKKi8el9B4q1JS/XCPUP+t12kmVaP3r8422E+3E6J5eHq
jkPoDbOXpU0Keyu6QpsJ+5K17lI4xJQ2pkvZl39qA1k0tYFgJhGXuinrDZGb
OFFh13Cnnb7FJWuPuQQIbCmrsYeNrGbweEt00x6eGgK5wi69uYJ0hgMk8UYi
JXE1HThr67Vq4D5IFxNjFYzXY4GIeFvdG7yvbwvD8ljrbAUjMGvZmqkX3Q28
vOobCgMT1aSbsk5zWrBYwDEZ2cGSuWzamhQD+xP2IeXKNHXbqZuVBpG0aUro
+LzUU9G5dZHnpR6NvqBzaqEq/DJ+f6FepBkHDpAhUhdtjdfWynRgg/bJanpk
SN9rmJrOt6mXvq7Lazo6d6/myFC3BlxniAUGe4aythp/4VSsik1UVtZG50lZ
1w0fVVuXkWim6hIxkC0Am6xxL0gV2lCJGmi/akV6EOuSqKHnvIZJadJJ2v1U
vSbLh+Ovlj024jSN6JKe4ikdKVJZL3GqRC/ad5eaD+DyVX2joUyTyESdEdUu
RMJYnMaARsea37WbJKvLUs7SLpEXLX6LnIZWQ+dD8AAbKKroIKwZK5KFCbrc
FmCOX2q1qfsWtgnBYrVqCaUcHUPcRKdN4O5ALWx1nW5I0KwnmjSh7frGWuUa
8EmR5aw0tLNbpcBoRvUALEVHCme1ea2HnEK0kFPstz5+JMf16RMp83WRW59X
Yr8VO3QmVBbLVQffj7/viX2igMF+hqigGeyVBgdP3JbFuiBxL/j2qjYww77q
ijWZxYi1/z205xjbN6zmEX9WKAZ05vUte77PeT3rtR5QNXDasHkSHwsceH1D
OrLFkOAksA/ww4El3eHoy4qCcOIUZaZO4EXgrEXVYiF5bwiZsItnydMvq2fM
JkQOlg0ULsNuvC5OoCiwtYqIEqdQm77syFvrHFvaHlqmxOh8R13UcDkbdZT/
3JuObszUu75iWgaBsktKSC+XoyPVjrgj116vmx72Nq/TNhezhewW4kjJp7IY
xVW3pO2RD5yq0zRbuaOyekwqwIupG4RwxXpwUylYo4XtdyxDdGUKKVcwn9Zr
mT+6vFgsdGvPqCWePSe0cw5cdxSSdvff//4fWOmacCtZB+loBuOcqgv4Xd3F
u+MAIbCi+AtExQobKzWLOttRJ2zvEdyeqdPgeORmHPsDSu9W8PTL1b1VFn3F
PFDk412TE0wzVpL7CuOEZli2dQ+RNBSsaHn4F9WmN4pi98QJT/hy4Vle4ycS
jlwLkWeD0JxChbzjwHlQyMKRIGSHNONELwrAKvo9GlGgRgajKIUxavzm/eUV
5Vj0/+rtOf/73em/vD97d3pC/758dfT6tf/HyD5x+er8/euT8K/w5vH5mzen
b0/kZVxVg0uj8Zuj78di+uPzi6uz87dHr8eUtHYDXEeBHTox1xK/GpgZJJ+a
kQNdOb3z4vjiv/5z/xCe8Z/evTw+2N9/Du8oP57tf3WIH4juNuLXFVyo/ISm
bUaI+DptiQodAJQG3rgkp2TI+m4okrTk9X71A0nmx5n6ep41+4ff2gu04cFF
J7PBRZbZ/Sv3XhYhbrm0ZRkvzcH1O5Ie8nv0/eC3k3t08evflgg7Ktl/9ttv
R+zZf8XJgboUHzFTR7HXBLQydclu+7pArIOKr1OCu4j/Fa7UFQMhBvqt9Wmw
WwQt+Bi2H2sfkwcwuvfKpPhChxjEgdmAKuuTLxNmAaGBoz8Tb3awhSoAbAIP
6QZmxAFZUJGRhYb2TWrIkrD5wpSXilCV08jgs4SMdSv3YuyKpLCC0yb0GqHf
dSPQXhyP3dZb2gMQ5qKg7OwI0MKjuyHeJ1+YQ2wSMD0O72phJs0hmK4wJP87
qcSX3mODwHBvUVogZIZZh4UGyieVDl23+s990d51lUKCfBY2Q4AKOMKnJ55B
SetqCKuqO4pCulwE78shRgh51oIGJCcXW5UgBH8cO6TZ1YjtUAhyhbrCphC1
08Ci4DZj0uUg7xARQx1cdscxGHvJRUGczgqRObL8ls+8ROovDtwfWZq1tTHb
4AytVQFU2019d3aFfDUyjJA1Xm0abewm/JFB65yrDzA9Vo076XZTV7TqG1Yh
2hq9rrnsJNoa7IBZJoFk/rU5JUG8Sw476igk4BB/KFWeX1Pg1zc2gWcoQgaX
R5pKMQzHZMFnq7WAe9BBplhpyTA3gBBNynkGI5UBZpwIrqBwiNBGRRavkAGp
OxxlM4DZaPRv+EN8/Tr5B//8mt7+q7J/pKyq/lmdD/DsBW1CPQoIZMc+/1d5
+wf73kXakpB/VMm36gcq+y0AffmkoGhyFVYzBZSBAv4ob/8yzj/756//6xPX
6hEBoGGq1Zmd/0ORHkfnCcFa3Gwlemxz4NfkzXcGIr0kX5qpI6pQkMDa4tZJ
ML0EmbqUn69Ss2L+L4tl9eP/A5E+sr7sJJSRfpk8Pydd/nO6ntd5AYM89ZZi
5WuhcyTe+7uBrGOwIFKlUPKK/P9L50Lk+oUt/KizYcT7pcp8d49s1x9n6gsq
C0p98xvb9FCSqoY+B/Ame+IkBcipvhlnmhzq+BM7rP3pZ40aHpggOVfD71Vz
bBGNijrwrlH0vnGmbWsoHHMQiELsjLN3qKoUxQrqjwAvUIbKVVibEPbsmWO0
YNMQqssacZaRdbp86zOWxQHoYPpZ6wMiyUAsNVJNAGstI8EQzcQ4S90y91Ir
5C1CiD63TZdgCori6zAhP7QR1vhq7XWRWm/IDCWpSdLk0uaVj8iwd8Tlu4IU
Ba5N09XLNm1WFE8Q+AwOmUNiKNcGfIB080O6tAHHPeojN8J6LtsVjvAunuUE
lraGrKKtr+8liVszZxLw4+nDtiehvVltDIdBn/57RI0orvPcwQ+LxkRPrqHI
Oe8+YpWYYCaNqbOC0btETOA8gnCEZu8w6fAcyYeO2oJam+huSY7J6u8myEcK
UHftU+KGypJI6OjQFYMVMEvvOjxpH5QqDEyBa2q2VmE0Vdbosd+IVnPZVXQ9
rlS0XIyBfcz1ouYfQEEk8lfDg7H1UJKSW4LY5yIEvERcj+RyBVxJSlKyuTsU
tCdXQdk4F6LlKrPSBQGLLpFsBGDJsQTUdl2Ygood1izlvH6zrUY+9JnuIKTK
cHRxBh65Xt8a7pfGxXexEWNrP0V1XUtPh6qRcGrZB0qwrSUSEyRdFkMkV1td
gDzPoyrtG19+5grhiS3kvnOqRIcTQf0T10kIL0pVwrcYIszNPpEP2jpGqYdA
UKFEdK+IPXN+O1r1KE4wOBeMDEov4QEgNH+MOCGylNihWh/LNXTXkriH24OK
HNdHF+rjx9++e3n81cGTg0+fiParq6uL3cf28vP9/cNPn6YOEPMaoafkzn6Y
XT2cqXEx1YskaucMymHWqV9qsE7Y6KVOuVv2e/KO4nCCz6YucyVmmsatJOgN
kpolNKwRDeA+RUP2VkmZBs+zv6UWTFb2bCuB9XrYBPcuZ97jRDrL5WMXdd2E
whuLhNTLgmre95g11FKl2isHxKiOJoVZG1VJbEhBYZ0g+oBf5iZPlDs6DKZe
FwudbTLqC4HDF1vDBxeHqBrQ1dyv4aCmXdOsXCSZ7SLkU5cNOdAQbQa0yCeK
n7BoUNSA69Q+Z2XPxfVkSjc33sX7eOW6Ys5VD+vppduQWMxlpxu1PwsWOrXT
I0MjoQWswk6o01ciBSRi5IQE3A6lPPW0D2aCxrlqHLSsI1A18N8U5olVC+Ev
N4iRlnYM5wPlxxaG0aEPqHsEQUc1cWVzoy5fHSUHT54KTfjkJVUZCRtNOOYb
JzkTNQy5OUKskR17I7JlI2/Ue2Lr9xxAYPZwFmJ9LOIQtYkFtkwsz+0eY6PV
oBxDeTJzaKtxJq6+mTj1tZoUBWqJMaLsjB+8OnvnAMfXkM+0dsJ+/zhyJ9IB
iksfvjTChcHUaS7bBLSb/ZngYKAJD4dFa2iJuV6l10VNKDLUFkQ30x2kZ9Wy
1MkV7xorvAX+ewGt49GY13XdQAdqiEtfM2jmx7gZd53a3N+mXtD+pKlvoB3s
LKKWuC/PKuzjplJLAqpJCYqlOr90AncdnD/Z2ucbqUleULHlncVK3HWyN2jr
xbK3WQN3LRbFrc4tO3FNJiJl1KN9aCFofqOeHqo/vgCyNWwP7HFp4+RsbZnV
KnqoiWY76gj7ILBcFjjQ0BmeUb2H0TQfTEregMqzHZ5KuXFqSXY2sWGUQAmM
bTS6Wi+90/YWSdF504K6WhLCmVga8w3lIHRCfzi78n1Q0bu/YSpiMH4i+CI0
+Dhn1xVTP6kpWoVyTgBXvlunPrrUu8ViLaN6HFXCjtLfoz/2hozj0HlWy0l8
n4F2l66hcf3Tw8Et6zZm8K2m+7p/9q27+SksnuaJrDBjJPooXmeHkmTpI34d
8Text5ncJ9klCQMJWJ/6Vp8rhjwsjNQ/7zesqx7gvKgSuJ9eq49kHhO1KhAt
PM/LpqiTGyRn2rKM57H3xwcTxW/NAoF4Az8N2KY/xUHmW1iWVCy9eW+SIhfK
8fU0z9v7V7tblk2Q9eBuewvDFS7d5Zg3/84Dkn2jc2j0heQin9ewNT86FCih
ipJ9dUIp/lC/cDN5erh3e/hsb3L3+v7Bs73brw623Hh+sHe7v/ds755GUV5d
Jzx2YGVKS9rzMSnlDAnlwnzl8+eTQRXbNAG+EE/B1PD07O6G/nZRQpIWjER9
SLFdBIp1anuSoRTMDlJqwFKIrhdhqoc73aG17BHMCNtfcrAA7vc1pjf2tVk8
rfVAYyYE1yiKwlEBL58Q92GcYDtZesb0c5lZCehWktpRNLViJ6xAGiD38j3c
4jZ6AhzDnFOuaR7Aer3AK5XD15pxGUmGw7Gv0BOYhWyNjuRHpkQ54xYZKpGh
zSXqIh/lPc9FddLA84mIuG8v5SjNcjuRM713DtH+tg6ghLwlOgM6/zTK17D6
WccNd87qmdK2dMl2xiTlpobxSIZOaQ7WDZ3aY9E5e5LEiUnkxtLcJTCL46I4
40d9KKkh0JwMai/x4r/BvYeyNboXcrVhuYTfc4WwO8mblDRhXON+XiQ3qVkn
nrEZJfi6TRzyH8+syxlb5hIKtTTDOVNjftVf3x+Lrxl7fhOiH/jFKz9YBzH2
0XQaxbGxc1ZjH1+mIWTI+OeP+PvT5AHmlwQMqrTKdAI1SJwAwiYIuVLpU4BA
4jmNWVtfvb786Xp/+tguaHcVMtekqz9gwcRqxNZt/UTbCvtBbvZT3XeMRqN9
jKJA8ZBzEBV66O5dzxH5hwediNrqRMKsJBnCXWK/2AbcT9b8VrPPyDRbRFtF
sy2+amsLJbYZ5yvWbazBY14psBkO2te8CjqfMRl9QkafyGRfshdpaxCTPL2/
t7fvDl1GkhIkMEVN9x7v2Yg6FsYsfVhW+xMQ6fXmJ5saOvLOPAhy98YzyMSb
nghTwRvXn301feKD9ViGC4BxiiVSSlayMddWId36puJoDPGILiGCD1RpEAz4
5Lf3sE8rJCRIzqShWttYgaTABolt884+xwnRwY4HxHOHYchMBpcHtY0QotO8
prlMW3y4dDHqva2dUSRiJA/zIe99ReUT5DO0v52gUfHAtq+GbG0fxCUPGzqG
vXdf/mBk1kWpslNE6sDTtI86fnH+zg4rDuQ9cRNykphxpwGPqnMZUaPmoBQA
c8ifmwpE/dHx+eXpjsv+9yTRd3th+n67vsjO1WabA1MvpKISeGgJuWIVUZG5
vp67JXw2fl++yOn15WjgI6VAhkynaAqeOPblzkFzwCou7SJUHdwE6JB/a9et
TlxCSy0cYs4Sgf9e1a1xraMjO1QtyOBPsMTFgDcHxKj4bGg2C0u2EU9u4S99
s8uNzcReBRmIrnJSuBNb8shKZJz009OhYQ1SCqmTeyq2iOU6MSf2AyQoyzsP
doVVkRvvIKoallJC3AxOTKlhtFfuuyb2jVIuk/G1LvKuzMMhDTlKve6llpqj
LE+peU6DJKT3YHxK4dMpvSvxFW6/LcVkfW1rMBZHhon3R3q6nE6kPjWnKkJy
Q4NBLiuzROLK1Q5z94QqsuCkLF0v0PZ7cdk2caLDtcLK4+GpwCIxzEKwHQ8/
TuYiXQz/eHZGKh92/MtS4eJI3Na0E8X3mlGG64cmGGYogepbzo9UUZY9N3Zl
LFz6McR7aL5ELiWA7qiZxnymQ6cyVaeuWyDG5HslcW08eMSBCU+iWRun8e5O
OjAuCCEvbJNK+r6iE1YV0nJitxzM2sSVFRvrXcyLk4pCl3ko71NpP3zWF4nG
4WP+7MQdCY/10fmHYS1r+X5KSTwN9C9ak930MBZaC6MyLgI7FLnKvUzD4oHu
EC7TrL3HNREQZrQgd8URA3/Kx4W4eXgQ7uIc1jFKcRdtII2RJCPb8LWCaP5d
CMzvF2JN/mUHMBx1e6SJ+DcHiERfo4uTB15jN3jnLYZT/oZgkMmWxeWTCkCJ
ZEGOKEY/wO9tQTSzOm34C0MXrxNJQabsZXdJDru2ykz/HoeCxlia5gOqBJ3K
JQy3W62Juq3Pj+MyyJgLTLyfx/O97PDw4PmzRbaf7R8+TxfzxWH27Pnzp4v5
84PDg69SfbivD58ePp8/f3yYpYfPnzx/vj//6tmTg/mzJ0/GnqoronxygEzy
BhGDLZ7fP6H7hjIUEddUNaVH5K4SclQGCniLp7CpSBLeMBKih0wjWRtBsntR
BcjTI2+W+FwxUjt+6vO5mRB6MD9zCnpHGDE8JX/qu7rH3u/amZDRyN8b+OTW
fihEH4fY6T2gUv4IzFclYK2fqxUMPwcIGfGDyZXPU0yYKrDpyXQ09CxhlcE3
cNFAveCoOMvZuD7+DNl65j6AwGVpIVIOz0OK4acbLvhzX3epPOAo+lFmsFpy
nv/GF2tCvsVFDln7M/kVUghXO6Dzwc3WVc6V/XbSWFnlNIFRWjDqXorDk424
MO9yY2hIQNC4VPa5WyMtmo0DtjJnwDF0WeholIlbloarWelCDwZlg8wtPhd3
Ej7VijtaUnYa9AQH7UDm6nVRfUiu6MRjxOkyJdcdWqekDfSNGMertu2bbjh0
xbkSa6kfUScafRUBjHg2hOQYfc8dtSC5y2JdiUqJyJrgXEeNniPqhiT1Qjje
tjU7wDIQWjyzHEANj1eppmh0KZP4UboRAI9F/1xo6HTDyRpRGDanBWfaqSuf
apytGUFesSme3rpR+lm0vLR/KJq7ikSUoFn34ufggEq4me++g5H6DMN0B6gs
Th7bpS9tvWBqSbFK85CI5uKoL0sMqmqRlUTTZzIS7ftUIl+XvISaZmKVixNa
o6Mda5EAAVnhzuJM8nmuK0dT08m2+ZrtLp1bGfbdu7nCYBolfN7sU1yXxwQL
eKd/jvm1CQM5gYzGVWLLrGr6Csmu7DMkVyyO/Kk09NxggnxFgVwPWdAafoNT
rdolEYxwjYV5A8uxJy39VmkjMOzDUa25ndI5CYbdtG43wLjzaLjD9uZ5dMC6
COttXzgPdRo8lDeXaCh84b4+5c6qb7jHM4LknhHMuzCRN1LKf0gqBs1V+2v6
njiMMrKJZDJOWJi4hIL8Dg8bMeicvlkld+TfpNyNhcv9D8QbwrjXOrJfb5av
5dMY2zv2mz5zgWVGM4YyKuimBNkpuWSMeKZUyn/LI4QkvUKiwYL2msJfzMz7
RcgVqXhLlQvjPvKJxulI6xvbROBxpIq+6yDoDNeKvNNpHJmr0zbT8Ffg1hJf
krpfbmCya/UW0qO7nBm/i/dCTmAwxscJeOUmUlRbY9kvd7+0XwvT/miIrFK6
WWnqeVmX0aRI4iTCZit6yeWaYWiIh8/qIo9JtantZF/zFYnF8ZDc3XB89eKY
Jl4ozz5LTqZUigVoS9pF9uSrvafzwnAd6Qt1dvT26MFY7r+Xs07NyOP08SqI
UbSxYztgkRKz+w13InW35+4GtvHYpXVo0Cgpzajhf8GEXr/zHzGZ2v9qwzzN
PtAGjrIPVX0D9LfkGD76OJMMS+ffjBdpaTSNWV+dn5zDItyT8ML/A432QwUC
RwAA

-->

</rfc>
