<?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-miao-agw-cross-domain-scenario-analysis-01" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="AGW Scenario &amp; Requirements for Cross-Domain ">Agent Gateway Scenario Analysis and Functional Requirements for Cross-Domain Multi-Agent Communication</title>
    <seriesInfo name="Internet-Draft" value="draft-miao-agw-cross-domain-scenario-analysis-01"/>
    <author initials="C." surname="Miao" fullname="Chuanyang Miao">
      <organization>ZTE Corporation</organization>
      <address>
        <email>miao.chuanyang@zte.com.cn</email>
      </address>
    </author>
    <author initials="R." surname="Chen" fullname="Ran Chen">
      <organization>ZTE Corporation</organization>
      <address>
        <email>chen.ran@zte.com.cn</email>
      </address>
    </author>
    <author initials="J." surname="Yan" fullname="Jinjie Yan">
      <organization>ZTE Corporation</organization>
      <address>
        <email>yan.jinjie@zte.com.cn</email>
      </address>
    </author>
    <author initials="X." surname="Zhang" fullname="Xiaoqiu Zhang">
      <organization>China Mobile</organization>
      <address>
        <email>zhangxiaoqiu@chinamobile.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="20"/>
    <abstract>
      <?line 38?>

<t>This document analyzes the communication gaps in three representative multi-agent scenarios: single-domain single-agent, single-domain multi-agent, and cross-domain multi-agent. For each scenario, it examines whether an Agent Gateway is needed, what capabilities it should provide, and where it should be deployed. Based on the consolidated gap analysis, this document derives a set of universal functional requirements for the Agent Gateway as a standardized cross-domain trust boundary and protocol termination layer. The findings aim to guide the design of interoperable agent communication infrastructure.</t>
    </abstract>
  </front>
  <middle>
    <?line 43?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>As agent technology evolves from single-device intelligence to multi-device collaboration and cross-domain interconnection, there is a growing demand for multi-agent communication across home, vehicle, and enterprise campus scenarios. Typical use cases include:</t>
      <ul spacing="normal">
        <li>
          <t>Multiple sub-agents (lighting, security, HVAC) within a home collaborating to execute an "arrive home" scene;</t>
        </li>
        <li>
          <t>A vehicle agent communicating with a user home agent across domains to enable "auto-arm when leaving, pre-condition when approaching";</t>
        </li>
        <li>
          <t>Agents from different vendors (e.g., User Home Agent and 3rd-party Vehicle Agent) needing to cooperate across trust domains.</t>
        </li>
      </ul>
      <t>However, current agent communication architectures lack a standardized cross-domain trust boundary and protocol termination layer. This document aims to analyze three representative scenarios (single-domain single-agent, single-domain multi-agent, and cross-domain multi-agent), identify gaps in existing solutions, and argue for the necessity, capability requirements, and deployment options of an Agent Gateway as a universal infrastructure component.</t>
    </section>
    <section anchor="conventions">
      <name>Conventions Used in This Document</name>
      <section anchor="abbreviations">
        <name>Abbreviations</name>
        <ul spacing="normal">
          <li>
            <t>AGW: Agent Gateway</t>
          </li>
          <li>
            <t>HITL: Human-in-the-loop</t>
          </li>
          <li>
            <t>HVAC: Heating, Ventilation and Air Conditioning</t>
          </li>
        </ul>
      </section>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all
   capitals, as shown here.</t>
      </section>
    </section>
    <section anchor="scenario-analysis-and-gap-identification">
      <name>Scenario Analysis and Gap Identification</name>
      <section anchor="scenario-1-single-domain-single-agent-1-agent-multiple-nodes">
        <name>Scenario 1: Single-Domain Single-Agent (1 Agent + Multiple Nodes)</name>
        <section anchor="use-case-description">
          <name>Use Case Description</name>
          <t>A home has a single Agent managing multiple smart devices (physical nodes). For example:</t>
          <ul spacing="normal">
            <li>
              <t>A central hub (Node A) runs the Supervisor Agent;</t>
            </li>
            <li>
              <t>A smart speaker (Node B) serves as the voice interaction interface;</t>
            </li>
            <li>
              <t>A ZigBee gateway (Node C) connects ZigBee lights and sensors.</t>
            </li>
          </ul>
          <t>The Supervisor Agent communicates with each node via a soft bus (e.g., DSoftBus, local MQTT) and provides a unified service externally. Users issue commands via voice or app; the Supervisor Agent parses the intent and dispatches tasks to the appropriate node. Naturally, if all household devices are assigned IP addresses, a mesh network can be established over the home network. Furthermore, the aforementioned devices can communicate directly via peer-to-peer (P2P) protocols.</t>
        </section>
        <section anchor="is-an-agent-gateway-needed">
          <name>Is an Agent Gateway Needed</name>
          <t>No. In this scenario, all communication occurs within the same trust domain (home LAN). The Supervisor Agent can interact directly with each node. There is no cross-domain security boundary. External access (e.g., mobile app) typically goes through the vendor cloud, which is outside the scope of Agent Gateway.</t>
        </section>
        <section anchor="gaps-in-current-solutions">
          <name>Gaps in Current Solutions</name>
          <artwork><![CDATA[
*-------------------------------------------------------------------------*
|      Issue              |                Description                    |
*-------------------------*-----------------------------------------------*
| Lack of standardized    |The Supervisor Agent's capabilities (Skills)   |
| external interface      |have no standard way to be exposed externally; |
|                         |apps must use vendor-specific private APIs     |
*-------------------------*-----------------------------------------------*
| Node discovery and      |Nodes register via soft bus, but registration  |
| registration rely on    |format and heartbeat mechanisms are            |
| proprietary protocols   |non-standard                                   |
*-------------------------*-----------------------------------------------*
| Insufficient offline    |Some solutions rely on cloud-based intent      |
| autonomy                |parsing, degrading local orchestration         |
|                         |when disconnected                              |
*-------------------------*-----------------------------------------------*

]]></artwork>
          <t>Note: Gaps in this scenario are more about "external exposure" and "standardization," but introducing an Agent Gateway is not strictly necessary; these gaps could be addressed by enhancing the Supervisor Agent itself.</t>
        </section>
      </section>
      <section anchor="scenario-2-single-domain-multi-agent-multiple-agents-within-one-domain">
        <name>Scenario 2: Single-Domain Multi-Agent (Multiple Agents Within One Domain)</name>
        <section anchor="use-case-description-1">
          <name>Use Case Description</name>
          <t>A home contains multiple independent agents, each managing a different subsystem, requiring inter-operation. For example:</t>
          <ul spacing="normal">
            <li>
              <t>Lighting Agent: manages all lighting devices;</t>
            </li>
            <li>
              <t>Security Agent: manages door locks, cameras, alarms;</t>
            </li>
            <li>
              <t>Environment Agent: manages HVAC, curtains, air purifiers.</t>
            </li>
          </ul>
          <t>These agents may run on different hardware nodes (central hub, smart speaker, dedicated gateway). They need to discover each other's capabilities, subscribe to events, and collaboratively execute scenes (e.g., "away mode": Security Agent arms, Lighting Agent turns off lights, Environment Agent switches to energy-saving mode).</t>
        </section>
        <section anchor="is-an-agent-gateway-needed-1">
          <name>Is an Agent Gateway Needed</name>
          <t>Yes, but with a different role than in the cross-domain scenario. Here, the Agent Gateway should act as an intra-domain registry and task routing layer, rather than a cross-domain security boundary.</t>
        </section>
        <section anchor="required-capabilities">
          <name>Required Capabilities</name>
          <ul spacing="normal">
            <li>
              <t>Intra-domain Agent Card Registration and Discovery: Each agent registers its Skills and capability description (Agent Card) with the Gateway; the Gateway maintains a domain-wide capability index.</t>
            </li>
            <li>
              <t>Intra-domain Task Routing: When Agent A needs to invoke a Skill of Agent B, the request goes through the Gateway, which handles addressing and optional load balancing.</t>
            </li>
            <li>
              <t>Event Bus: Support publish/subscribe model so agents can subscribe to events from other agents (e.g., security alarm triggered -&gt; lighting turns on).</t>
            </li>
            <li>
              <t>Local-first: All communication should complete within the LAN, without depending on public internet connectivity.</t>
            </li>
          </ul>
        </section>
        <section anchor="deployment-location">
          <name>Deployment Location</name>
          <ul spacing="normal">
            <li>
              <t>Standalone device: e.g., home central hub, NAS, or high-performance router.</t>
            </li>
            <li>
              <t>Collocated with Supervisor Agent: If the domain has a single Supervisor Agent managing all sub-agents, it can also serve as the Gateway.</t>
            </li>
          </ul>
        </section>
        <section anchor="gaps-in-current-solutions-1">
          <name>Gaps in Current Solutions</name>
          <artwork><![CDATA[
*-------------------------*-----------------------------------------------*
|      Issue              |                Description                    |
*-------------------------*-----------------------------------------------*
| No standard inter-agent |Agents discover each other via proprietary     |
| discovery               |soft bus or hardcoded addresses; no unified    |
|                         |registry                                       |
*-------------------------*-----------------------------------------------*
| Task routing depends on |Agent A must know Agent B's address and        |
| point-to-point          |protocol,creating tight coupling               |
| connections             |                                               |
*-------------------------*-----------------------------------------------*
| No standardized event   |Event formats and subscription mechanisms      |
| subscription            |vary across vendors, hindering cross-brand     |
|                         |collaboration                                  |
*-------------------------*-----------------------------------------------*
| Unclear intra-domain    |No unified authentication between agents; a    |
| security boundary       |malicious agent could impersonate another      |
*-------------------------*-----------------------------------------------*

]]></artwork>
        </section>
      </section>
      <section anchor="scenario-3-cross-domain-multi-agent-communication">
        <name>Scenario 3: Cross-Domain Multi-Agent Communication</name>
        <section anchor="use-case-description-2">
          <name>Use Case Description</name>
          <t>Two or more agents from different trust domains need to communicate across domain boundaries. Typical use cases:</t>
          <ul spacing="normal">
            <li>
              <t>Home Domain &lt;-&gt; Vehicle Domain: As the owner drives home, the vehicle agent sends an "estimated arrival in 10 minutes" event to the home agent, which pre-conditions the HVAC, turns on lights, and disarms the security system.</t>
            </li>
            <li>
              <t>Home Domain &lt;-&gt; Cloud LLM Agent: A user queries home status or issues commands via a cloud-based LLM agent, which invokes Skills exposed by the home agent.</t>
            </li>
            <li>
              <t>Home Domain A &lt;-&gt; Home Domain B (neighbor assistance): Neighbor A's security agent detects an anomaly and notifies neighbor B's security agent to increase vigilance.</t>
            </li>
          </ul>
        </section>
        <section anchor="is-an-agent-gateway-needed-2">
          <name>Is an Agent Gateway Needed</name>
          <t>Strongly needed. Cross-domain scenarios face fundamental challenges including NAT traversal, trust establishment, protocol translation, and information hiding. An Agent Gateway is an essential cross-domain trust boundary and protocol termination layer.</t>
        </section>
        <section anchor="required-capabilities-1">
          <name>Required Capabilities</name>
          <ul spacing="normal">
            <li>
              <t>External A2A Endpoint: Expose standardized endpoints, such as for /.well-known/agent.json and POST /a2a/tasks, supporting HTTP/HTTPS.</t>
            </li>
            <li>
              <t>Authentication and Authorization: for example, Support OAuth2 Device Flow, JWT issuance and verification, and Scope whitelisting.</t>
            </li>
            <li>
              <t>Aggregated Agent Card: Merge all intra-domain Skills into a single Card for external exposure, hiding internal topology.</t>
            </li>
            <li>
              <t>Reverse Channel Management: Accept reverse WebSocket/MQTT connections from the intra-domain Supervisor Agent for task dispatch and artifact return.</t>
            </li>
            <li>
              <t>Cross-domain Federation: Establish mutual trust with Gateways in other domains, exchange aggregated Cards, and enable cross-domain discovery and Task Proxy.</t>
            </li>
            <li>
              <t>HITL (Human-in-the-Loop): For high-risk Skills (e.g., unlock door), support suspending the Task and pushing a confirmation request to the user's app.</t>
            </li>
            <li>
              <t>Audit Logging: Record the full chain of cross-domain calls (issuer, skill_id, status, timestamp).</t>
            </li>
          </ul>
        </section>
        <section anchor="deployment-location-1">
          <name>Deployment Location</name>
          <ul spacing="normal">
            <li>
              <t>Home network edge: Deployed on the home gateway (router/ONT) or a standalone edge computing device, serving as the sole external entry point for the home domain.</t>
            </li>
            <li>
              <t>Cloud: If the home lacks public reachability, deploy on the vendor cloud as a Relay Gateway; the home Supervisor Agent connects via a reverse channel.</t>
            </li>
            <li>
              <t>Hybrid mode: Cloud Gateway acts as global Registry and Auth Broker; Edge Gateway performs local A2A termination (when publicly reachable).</t>
            </li>
          </ul>
        </section>
        <section anchor="gaps-in-current-solutions-2">
          <name>Gaps in Current Solutions</name>
          <artwork><![CDATA[
*-------------------------*-----------------------------------------------*
|      Issue              |                Description                    |
*-------------------------*-----------------------------------------------*
| Cross-domain discoverye |mDNS/BLE limited to LAN; cloud-to-cloud        |
| unavailable             |integration costly; no standardized Agent      |
|                         |Card format                                    |
*-------------------------*-----------------------------------------------*
| No standard NAT         |Direct connection requires public IP/DDNS;     |
| traversal solution      |reverse channel protocols are proprietary      |
*-------------------------*-----------------------------------------------*
| No standardized event   |Event formats and subscription mechanisms      |
| subscription            |vary across vendors, hindering cross-brand     |
|                         |collaboration                                  |
*-------------------------*-----------------------------------------------*
| Cross-domain trust      |No unified Federation trust bootstrap process; |
| establishment is        |Scope models inconsistent                      |
| difficult               |                                               |
*-------------------------*-----------------------------------------------*
| No standard HITL        |Actions like unlocking doors lack a            |
| mechanism for high-risk |standardized human-in-the-loop confirmation    |
| operations              |workflow                                       |
*-------------------------*-----------------------------------------------*
| No cross-domain         |External agents require multiple protocol      |
| semantics for task      |translations to reach the target sub-agent     |
| routing                 |                                               |
*-------------------------*-----------------------------------------------*
| Audit logs scattered    |Cross-domain call chains cannot be traced      |
|                         |end-to-end                                     |
*-------------------------*-----------------------------------------------*

]]></artwork>
        </section>
      </section>
    </section>
    <section anchor="consolidated-gap-analysis">
      <name>Consolidated Gap Analysis</name>
      <t>Based on the analysis of the three scenarios above, common gaps across current agent communication architectures can be summarized as follows:</t>
      <section anchor="core-functions">
        <name>Core Functions</name>
        <artwork><![CDATA[
*-------------------------*-----------------------------------------------*-------------*
|      Function           |                Description                    | Applicable  |
|                         |                                               | Scenarios   |
*-------------------------*-----------------------------------------------*-------------*
| Agent Card Registration |Receive capability registrations from          |             |
| & Aggregation           |intra-domain agents; merge into an aggregated  |2, 3         |
|                         |Card; expose via standardized endpoint         |             |
*-------------------------*-----------------------------------------------*-------------*
| A2A Protocol Termination|Support standard A2A Task interface (POST      |             |
|                         |/a2a/tasks); translate external requests into  |3            |
|                         |internal commands                              |             |
*-------------------------*-----------------------------------------------*-------------*
| Authentication &        |Support JWT/OAuth2; verify caller identity and |3 (optional  |
| Authorization           |Scope whitelist                                |for 2)       |
*-------------------------*-----------------------------------------------*-------------*
| Reverse Channel         |Accept reverse WebSocket/MQTT connections from |             |
| Management              |intra-domain Supervisor Agent for task dispatch|3            |
*-------------------------*-----------------------------------------------*-------------*
| Task Routing            |Route Tasks to the correct intra-domain agent  |             |
|                         |or cross-domain Gateway based on Skill ID      |2, 3         |
*-------------------------*-----------------------------------------------*-------------*
| Information Hiding      |Do not expose sub-agent count, IP addresses,   |             |
|                         |protocols, or other internal details externally|3            |
*-------------------------*-----------------------------------------------*-------------*
| HITL Trigger            |Mark high-risk Skills with                     |             |
|                         |require_human_approval; suspend Task and wait  |3            |
|                         |for user confirmation                          |             |
*-------------------------*-----------------------------------------------*-------------*
| Audit logging           |Record full chain of cross-domain calls        |3            |
*-------------------------*-----------------------------------------------*-------------*

]]></artwork>
        <t>Core conclusion: As agents evolve from single-node to multi-node and from intra-domain to cross-domain operation, the lack of a standardized trust boundary and protocol termination layer has become a primary bottleneck. The Agent Gateway is the key infrastructure component to fill this gap.</t>
      </section>
      <section anchor="optional-functions">
        <name>Optional Functions</name>
        <artwork><![CDATA[
*-------------------------*-----------------------------------------------*-------------*
|      Function           |                Description                    | Applicable  |
|                         |                                               | Scenarios   |
*-------------------------*-----------------------------------------------*-------------*
| Intra-domain Event Bus  |Support publish/subscribe between intra-domain |             |
|                         |agents                                         |2            |
*-------------------------*-----------------------------------------------*-------------*
| Federation              |Exchange aggregated Cards with other domain    |             |
| Synchronization         |Gateways for cross-domain discovery            |3            |
*-------------------------*-----------------------------------------------*-------------*
| Local Caching & Offline |Cache aggregated Cards and authorization       |             |
| Autonomy                |policies; handle authorized local Tasks when   |2, 3         |
|                         |disconnected                                   |             |
*-------------------------*-----------------------------------------------*-------------*

]]></artwork>
      </section>
      <section anchor="deployment-recommendations">
        <name>Deployment Recommendations</name>
        <ul spacing="normal">
          <li>
            <t>Single-domain multi-agent scenario: The Agent Gateway can be deployed on an intra-domain central hub device, collocated with or separate from the Supervisor Agent.</t>
          </li>
          <li>
            <t>Cross-domain multi-agent scenario: The Agent Gateway should be deployed at the home network edge or in the vendor cloud, serving as the sole external entry point.</t>
          </li>
          <li>
            <t>Hybrid deployment: Cloud Gateway acts as global Registry and Auth Broker; Edge Gateway performs local A2A termination, balancing reachability and low latency.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The Agent Gateway, as the sole entry point for cross-domain communication, must enforce strict security measures:</t>
      <ul spacing="normal">
        <li>
          <t>All external interfaces MUST use TLS 1.3 encryption.</t>
        </li>
        <li>
          <t>Authentication tokens SHOULD have a limited validity period (recommended no more than 24 hours) and support refresh.</t>
        </li>
        <li>
          <t>Cross-domain requests MUST pass mTLS or Federation-level cascading trust verification.</t>
        </li>
        <li>
          <t>Highly sensitive operations (e.g., door lock control) MUST enable the HITL mechanism, and HITL confirmation requests SHOULD be delivered to the user through an independent channel (e.g., mobile push notification).</t>
        </li>
        <li>
          <t>All gateway components SHOULD record complete audit logs, including request source, target, operation, result, and timestamp. Logs MUST be tamper-proof.</t>
        </li>
      </ul>
    </section>
    <section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>TBA.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>TBA.</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="RFC6749">
          <front>
            <title>The OAuth 2.0 Authorization Framework</title>
            <author fullname="D. Hardt" initials="D." role="editor" surname="Hardt"/>
            <date month="October" year="2012"/>
            <abstract>
              <t>The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6749"/>
          <seriesInfo name="DOI" value="10.17487/RFC6749"/>
        </reference>
        <reference anchor="RFC7519">
          <front>
            <title>JSON Web Token (JWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7519"/>
          <seriesInfo name="DOI" value="10.17487/RFC7519"/>
        </reference>
        <reference anchor="RFC8446">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="August" year="2018"/>
            <abstract>
              <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8446"/>
          <seriesInfo name="DOI" value="10.17487/RFC8446"/>
        </reference>
      </references>
    </references>
    <?line 349?>



  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1cW3MbN7J+d5X/A0quyko5JL2+nM051KmtpSU5VkqSvZYc
n+QlNZwByYlmBtzBDGUmSn77ft0NYC6kZHnL8u5D+GCLJAZoNPry9QUcDocP
H6zG6tnDB4mJiyjXY5WU0awa5mlkhtH8ahiXxtphYvIoLYY21kVUpvimiLK1
Te3wz08ePoijaqzSYmYePrD1NE+tTU1RrZeY7Pjo4uXDB1VaZXgzmeuiUt9G
lb6K1urczaUmbi4VFYl6WRdxhcejTL3V/6jTUud4yKqZKdUBk3LIpKjTOqvS
oUx5YPK8LlLQgSfVwwfRdFpqbOuvDx8oNfn2fbPWV7fP+vDB1XyMCTBFXS1M
OaY/h0oYc7Coo2IdFXN1CubQ1KbE6B8vjkBAuTQlL0+fa8yVjRXxcBT7p/72
S6VHsclHcaEUjWpmfhsVmF0Xd5gzxrBRGRWd2ZRSbUK/S4ufU61+iO4yIUgb
/cwP9KakMS0a/x+b+Udaqx8X2EuY92CRFpE6NdM0061Jf6FBH+SJv8U0Juch
NL1qTV6YMgdBKz3mD96+PHj65Mn/hjf/8+Sb52M3lOSrP/gv3zxvBn/z3+0n
nz//y9izZThU0dRWZRRX9P5iAVmDuNckA4ol+RdtVbXQKu4I0jxaWsg1vim1
VqVeltriEaZB5Sx/EcufVws7VjYt5pl2+uLf8ahB77vWBAMW/bamtb8dqZcQ
Ux3Fi7DQQKWV0h+iPC1A+dVCg/gSk/RUDPsstE50MsCYqFJxtIxwDGmV4inM
YBemzhK1LM0qTbRQgclK3fpyqlWil5lZ62SkXkRWJ8oUjlmFNVmaYLGEeKW8
URjg6zaLE12CY9BvZXWlzEyBxStdWuj4rFH3sq+YtEZ3PxHPUYHMqEzSX3SP
Z1VZ20pNTU3fr3k32FplYpOpSpdglpxrFq11OVIXmH+WFglOBfOmuaqMmtdg
BK+caJvOC6I2LfCwWeoymmZayYl3BQWyWUYQsDqu6lKPSMhE7PI0SUgxHj54
pI6LqjRJzdtVvz5KW29/oxET6+audLwoTGbma6VXJiPOzUrojRcfvUpjzVRl
WYon8AaUi8C4L7HjLJo6Zd8ULt4Rjq/QvDydFx86sXdemisshP3n9BwdRFvU
uxuPeFq1MDmkZ6UXaZw5MdK0xLJMLYiJ8mVtGyUB59dLzJCpmr+1JIxFnNWJ
ZnsLtf1aiX1fguFwKbK2VbvY76ICddAlHddlWq0H6tX3k4M9dZVC5kAQ09Le
P7YC7ugPGF9pUpGdqCRx5IE7TJXedzZGVp74nWyeNSajhbAMSC9lLRnkOCEM
trxkwfKyA08Cf1nmpFmQPR2teAMwJkMcQZIyI/m7aAlxjchcznd6JMn+WQyS
dDbDaWHNlS4SU4ItejQfDdQ7IukVkSRaQ8fwrEyGy6is1up7tyf+bo/tguNN
bFi4iTuyCdEjt5WRI+SVudJQ2oEC33n1rfJQgnrIL6mBhZ7Fl59XYTuGO82Z
z86Ab7fSQejU7j1Y5j3Y4QT/p7N1cBb6Q2pZUGAba6LeyhxROa91sGvQPA2Y
RPIbjPK6YwLlKTG9vF+z5NnIIm0YejaMjVXt2iM6o6UpyJOIJTowxYqoptne
kUEH2czbQ8/bXx/FzRi2To8eqQmjqpSPxDaKCnzVg3bNd6+OL07G6lUNUzIE
fMTOhxmkrSPbpL8YoyNR7O9p1awxXJO0JIJFT1KCHkxMB8adAG3UOBG3MBn2
S71WV6ZMrNo5fXd+sTOQ/9XZa/777dHf3x2/PTqkv89fTU5Owh8ygufBB6/f
nbgx9Ffz9MHr09Ojs0OZAJ+q3kenkx92+ARlotdvLo5fn01OdgROdMS4ZPM9
FYsOk6nJneJA4YDiMp3K8bw4eMMzPXmufv3VwaTffpO/CSXhbzIhIjSmyNbu
LTi+Jruio5KmibKMp4HMpVWUkZBZcvRXhSIP4ORjOzL/Fh7+WKTdqbs7ijD8
yVidiyI5jO7eiXDsPnFS8l+NbT8z2OWezPOIZFEdwB2oQ9760qF5uEaxtAvx
/zypmwuCFc1J2/LgLnKYOyV+EFq/XGAD5GsKXsphKSAnjG15m4nCJoAQM7Wo
p2qX6FKTPVXWhQDD8xomcpVaPMwL9z2GrGrB50sYYXn+xR68VMnARyZZGe+4
CYoKcMDfsyje8EA/pvMXsGZzp98yIdycc9rWD2CHKOcDowfygr2+2EJ1y1oT
bCRPxrCSeKOg2cRdM4NFroNTOTzHBy9qSEpmiI2nf7+42POWmlCjszyzVCe8
Xdqi/oBtQXay9Yi9EgyjtbXAazxqeS3hBkiDeO5vZbKC57IOmROnnE9LUruM
KgRC+Cayl+wEaAi7T0AO8mS0o5E6i2D/iAzY6RkJP+QIjnthsiRICOlfZAnr
YQPHb1SUJHAgWBa6oXJtwR1dwZJcQmkKUlMNfzbNUrsgJAyDy2uzfLqBkLG6
JESVm1IPhDTYfbZVOHTdrE0zto4EOytxuFBe4s9S63II6ED/q903T9/sBedo
R15lju2mMzhjyM9CcGZGwJ1icZrYgRjR9dsmhle3HkQRxRZBXwcIqF3e48nk
bE+g86ZwRUUQ7mYrXSnjRwVqFqbrVz2iC3hgpI6cHAGYkLv0MimxJJ33nqoE
SmKhuWFRKU09X4i6MTxScWZqDoBS0IB1TV1ZD/JtDOhDHrXDwcDdb51PP3CQ
59y7dCUQ//fff6f/vh5+rtfXDx9cc3yMgyWF6byuVe/VNpNbXte3UfapNDNl
JwTowK0OoqOVtsnDn2w33tw9v0yzzO4JZdfBSDRG0JG9iFakwGEVRUItLlJ/
WBoCLI2B2ZfJbnpdQ0gsnAPEmIINEYkh7HRMXgwKla5I8SZvoEj3wzO23DBZ
MdkKwbiyEvs+QL458CI0nFTeG98B/qncVy6Gk212Pio1pF6O/lpyIzz7Ar6+
mgJOwXrFi6hIbS5Wrisa10qspa4IegfLQl8WphgG5n/89fl5dlzYeobzSRn3
zmZZWjD51+dkggKwDhxgFR9OI8Gy7CiabVL8VZh8vUE2eReGnImelxFHQ+Lj
TEnOJXC+zbMbecABHB8zO2j9EcZ9bp45WyQ2v9LjYLo6pp/FgLySQnAMCdsJ
OsiKhVhhh0Vop1Fw5sFghwXSpyyIU1tzTQYQqCpTtvsS4UC22LdbLQFS7HNK
3s3izRqhMuSUp90KA9LK6mw26sPNp3242U4J7waM6WLn9+LbXkOSZPie+gju
nPhcAoJJiukDxEwLhGWwJCEKhsKyhwtoNGpF6bae2jVUPB+4+I4GsM0bStyN
1W6CpScu3yGbGMsCBFrgwX0uxKOJLoQ8996092RisBDE/NJS5JljfQI6WVTm
vQmOilVamoJjlN4cFLFxHoD5gscRoi2xGjBgB39alxwB6yAgwNKkqw1jFhCw
K5JIhuZqt4XAB11ATSqaMERKPCQWELLmPAY5B29h5SAMwa+eAxrwSXBIxemZ
VRNlt9JFKzIpPlvEyaEAO3YikvMcxO6Me/xVxL9B77gUwCfH6zMH0webTFUW
+EigLGWMdDlfDy1niHihvTsAPRrxg3Y+w2WnGiaXJiOow9BMsrYdzOV0aYT4
22PV7houC0yQLmISyAhE/nnnj8StERjHejVzgFM2kPiIM9NMQPQxvOf36mL7
BErZwg+NVhy3SXAVIHJVb9vekSg69G53rI5ILCRl5V0upcCtElQiYtBkYpKW
JdhtlpA8I7PJMWi//UYRRWIsIgebh1eENVszk/H4MOqoWmc/F8TFt8LFsXpP
bkXWn7Css6CkxcpcQrmE+Aa/vpATJDMD/7WJiB2ZHgzjUJKMrInYYjHriUs0
QREzE8E8wziwbe7SfLTiBWs7Jnu9NFDWZc1h0eNGzUiEM/hrbwYoQtiihJLX
NFLDcJleUbkgI2yhEI+k87kmyRj+tbF/Ts2KvS6FJ+TLh7O0tDBdk42Qxwk2
5cYyDV1vxT6IcQb8nnykmHpaBw/xFmOx3oj2fDierkCjX50k+LBJ2xEZIZHh
bDN71wyhoLPdYyXbFX/TNoNnk/MBxcgLbBaRYMk4jzL+pGe67O74AGbMiJVk
Me070rE6nkltQ0Stk0/Z8LqNMwPvmiQ8l57oIKMMB8sJDp/faMKnwIgbI6g7
BlD/Enzk139kAHXWimoEAohJunYgZYsXk1xAC6oHLNoEFT2yQw6HBAdLxYby
ASGxsU/BlU/ZqI8B22Di7/b6/Dy7aLsV0UbSdsczmEWO7i4Lc+Wt4J+CSWvC
LR/zGLCdsyr0R4tsHwAN4lK7qhHZFwKsy4zebmzzWjUVNNv98o68uj+eteSM
Y3S2s7SSmG2JFl3aUOyxKEErYmy22RnRJnvFRRupGblaFGwYOTjGuOLtp6U/
g9vlrFuy/Dfw7F0RZ5Imb3ljxYF60BbqCqEsnjPpU11daSrcsfbuw5gGnvXB
jSc7j+BAUlPbUD8jL5TmML4WTpdLlKL397LNVpzYDqWeje/eXONN+7aoidsr
rgwZHgkzt9YtO/XFgODbidBONdXzECBwS+m4FS1x7dPt4P+AEHzJUz4CCBA3
Za6As1UiPQlSupZ0Ybvoa9nMULkYSCrN2aly4ZgTVurJn1WeFnDBdscpl0tC
NyVhj7I6hV6hQAIoj1tCdOCS2xRLSHbSC5HEj11n39/sAeVA1MnJqff1E6lR
AwoS54QwGIVK/AIn5G03Ix91Eik0VWcjgjoDYva5OMTv3Y3fTOeEKW1/8kLt
Fhrbn1IdABCUrFas98aIbdynE1jzBgbOpZ+k4hoIgZAC82QSf0BvSEtJotyz
LzafZfRMNp6ygek8JXCr24jltow6idp5hQBunq1dZ83IKU4voILMU0JzRoJL
MBBSA8uaZbqYh24HspFnkwuoQyR124HTjFBhyJn7TUkcptRKaVSEJfREQYgW
KU04UpMtiRlsiDw/DBfR8a9X4O8aoIW8/eTpBDFvws4WMRhLTM8zuW85PKcQ
TXp/Ho+udJYNyasXj0WqfrYuqnvz+vxCPY6eRo+5/EMPcgBC/Hx1cfHmMf1z
3pXCSddwc2GZO/xchmvMq7oEzCCENK9p0FNYOC5rvczM1UB99/6CtYdhOE2E
wwslUTmXcy4rXFErRCbdAD1q5nPAKrYpTWw5VqcI/zXD7Y4PcvqGz0wD1zng
FZp7KbyBEwUXpeCbyiy5nahLxFtq5yAbDo9fIEw75exOLrYjjvWSImUZ8l5P
z018qavHVP7r4B427a5A1yK5H0xw3wMBOV+8cz0R0FhKLZSajGEvmmnL6Uvo
WulO6sirB5BfVdP+WIg55HFCzzGHuFHnZgbgD2EbYnDDfeKi9Q1L3K7T0Y5u
2p6B6JvSfOgxkpoc1G6nyeHEmCWM2EsfuZUpHnXn6ELbuqAsHOfj9oII43/r
w01iKi/JSlnbhSQWwXzEtLkvAUik75wPGXwCv8tlX/rhfRCJzuecVHirYwPp
oSdmdcaWKeVOt87mqaoGatlRlKCQqP8pTQbOicBYpTlZqny5d/fQ91WrTqp0
Mkfoe+i6C31bITuSUPiWOPfx67OLPa4VO+vBwTM9zwF83cqDDqQKTbxyXpQy
YI2WFBTLCPr3zTi8ouy6J4LkDkPUzMOop8n6PEBJYZpL7Axcr47fRrv6KP05
bzWsaDdvxFNuqdK7Ir84Za+FsShqT/jW0zJNONMydhggNAWxj7Rqnpkpt1O3
cnVk19SLEv683FdHxEf/lEsyWFcLIQvedgS7XOiQ/Wdrz4Gslan8I+TvUHaw
1aBoRAKHZ+ePX5wcAf7laSUY+GRytu9AGGJUkZ2GsmsYjWgVAbOQpeqQTbZ+
7mKn2NiKCqNFLwgU4Womu+l17X0LVRTv8LrfNAkhpLDSIXcVtByQb5kLKnn8
5vEhGLvfbDPAq1A4dJP19KpVA6WiRD/l8keUrv4TovSDTfQqK7Wi9AYsBHxr
KioMLOlUqSzpugY6QJuAsidbABynrxmtw3pRyaC4QR9cOo5K1gic+19+nE33
zLO2OjFY8StNHIjL0kvtAAk7UkNdxa57t7/NIHzsPht0c90R5UW/5bOLW/xk
oQBqezwgfDAD3P538qyDhsJKTU+S5DacAWqqwyF+anhmqZcewYdtcLB82Yro
uLDD7pSRAezOXFdN3r2ZzKdCN3hwR17dH88EZiLSoI6DqKq4UkMrHfRxpUBO
LghR0wAVg0rEy0mg7BYTBBNGzlEXd+lNud8MGjUmN1dgqEHWd8w6xNu5L+Ov
xxDS5iPmhvUmYwC7ugJ8pZSMv3zkzPbdW+5dj6Kt8xyT/iKdxDOqC11JpuwR
EQ1x9ffsJGz//KCszzZ3oH7Z2+T2YxBNTZZLuHoBQbfLyp0kpD3+PJzG55ac
TYbcVLm+Rnym6fJC52ZAM8AF3TfskhnyVUgx9HjdidJ92jrnvIPkF4p2eKyu
nw7Us+7UN/KONrLvsoLSzbYtz3Mz1ffLa4Qxb7xhvmjimWuf6QkOkkZy2N20
Je5yxukmXt/IkCZFtbcfcnetUNQF7y6zo66fdZ6+deqQ2gn521tfX5jX3Vzb
V2Fdz+vv3l88lszaviTP1uwUdOlu01QSo4Ihu6EXQRjSydm1t9TLuN3ODumX
VE/3vhBD+pm2QMUnptm2CF+TtNuUkE9Jx20I370ypN3j0lmXPpOsV+jqj03J
Md+m5fo0baRcTBuG+HzH1Lto6aU5PnTj+5bvXhly3Erkv5Lsrax7aLir0lnV
Bg3GpqbSQPe+wqcxJIS73GAiydJgVxIEvikXeXyj9ZeVEA5TLqTdp7PuaVRe
buZUOfe7dZefwBCH5H/i2OUnvk2yirJ9n5NtkrFXUVp9mr0mfeNqXD8KumF8
n+p7ttcOts+76njt8sQfzRH78V9QQgIKB3xlPAvGxlltuUDgb1Jbd3+6c32a
7zqF+9L8ju8505COjal6EWCIVaVcnLm7ED2c80kFNe7AmoLLVDqlywg5PTM1
VZVpmP5LuWizUc6r3P3Gm655EukzMmbc/I1AwrdOv/beNKD/+8rJ9s/rD/i/
wZBO12dop2zBpM1+St9v0pHTTzFxTi3uzJCnvanvlSGttF2XiqObKndi99t1
PjnGDYacr4t4UZqijxyvQ71w1scHW7vrvqwT5A5W7JR/EQA4+rW7CXNNH23h
BpdUtyDkLQyZ3HgpxlB/EjUJSndwmBCrSEVI0BmXgT4tQLz77ZjtVH8hd9Kt
YZIPzPFX0r/2fn7TTwaEjM54i/V2+ZmkVfPs99S3LyL7kmbc6+yFsFq9jPhH
G0IFvo/ybymn35Xczd+AUVG1ceFVCrGm9FcMuhcv71qO3VrXbH7/4EtUNwdN
t3untsuTUjaaAvgiXvt78r61iNKAaRJS2b8+8k1Hw7jzzW/y80M9Lg+6rOkV
qLt4q536G0jnq6bYIdbu5lXT75TriNpB2g1y1AW/ee3SKv5lBOqouzg5V09G
zzBnXK7ZBd/aRlOBw9iv+3EEvrcZhXImsDMimYp5nppE7ZZelTT1akmDIF8M
efqc7mWXds+VusT9lXoG6he3SHFIoDD9y8haldMOwLXGlwwzRNcZ9QrGcsdP
EFq7aacneQgusjVfp0/5N0RaRQrXuxEuUfHlsNJke0KC6yHhFj8KYEKtRFpM
+LNt/RuBhaxoGf2Mh9SDfVNHuMXBxqK5feZLl92L0dQs4rrhZIO9mxEkBr7B
IoDGQEMpqD9cjIhCVn/QalzznScWB0cWSuoVgzZKxunBzMjWQ6/IiNpQ3IlR
2j+iztchILKZCZH8Iu2axNT9lZFt4V/5gOa8mDjNO56cTTa1Lo2KaKvGuedg
66Hg8eXDB/8E87gW6vhOAAA=

-->

</rfc>
