<?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.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-netconf-quic-call-home-02" category="std" consensus="true" submissionType="IETF" updates="8071" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="NC/RC Call Home Using QUIC">NETCONF Call Home and RESTCONF Call Home Using QUIC</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-netconf-quic-call-home-02"/>
    <author fullname="Kent Watsen">
      <organization>Watsen Networks</organization>
      <address>
        <email>kent+ietf@watsen.net</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <area>Operations and Management</area>
    <workgroup>Network Configuration</workgroup>
    <abstract>
      <?line 54?>

<t>This RFC extends NETCONF Call Home and RESTCONF Call Home
[RFC 8071] to support the QUIC protocol [RFC 9000].</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://netconf-wg.github.io/quic-call-home/draft-ietf-netconf-quic-call-home.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-netconf-quic-call-home/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Network Configuration Working Group mailing list (<eref target="mailto:netconf@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/netconf/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/netconf/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/netconf-wg/quic-call-home"/>.</t>
    </note>
  </front>
  <middle>
    <?line 61?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>This RFC extends NETCONF Call Home and RESTCONF Call Home
<xref target="RFC8071"/> to support the QUIC protocol <xref target="RFC9000"/> using
TLS <xref target="RFC9001"/>.</t>
      <t>RESTCONF <xref target="RFC8040"/> supports QUIC with its implicit
support for HTTP/3 <xref target="RFC9114"/>.  NETCONF <xref target="RFC6241"/>
supports QUIC with <xref target="I-D.ietf-netconf-over-quic"/>. But
neither transport mapping supports Call Home using QUIC.</t>
      <t>The QUIC-based call home solution presented in this
document is nearly identical to the TLS-based solution
defined in RFC 8071, with the primary difference being
the use of UDP instead of TCP.</t>
      <t>RFC 8071 provides a full description and motivation for
call home.  This document merely maps the solution to
the QUIC protocol.</t>
      <section anchor="applicability-statement">
        <name>Applicability Statement</name>
        <t>The techniques described in this document are suitable for network
  management scenarios such as the ones described in <xref section="1.1" sectionFormat="of" target="RFC8071"/>.  However, these techniques are only defined for NETCONF
  Call Home and RESTCONF Call Home, as described in this document.</t>
        <t>The reason for this restriction is that different protocols have
  different security assumptions.  The NETCONF and RESTCONF protocols
  require clients and servers to verify the identity of the other
  party.  This requirement is specified for the NETCONF protocol
  in <xref section="2.2" sectionFormat="of" target="RFC6241"/>, and for the RESTCONF protocol in
  Sections <xref target="RFC8040" section="2.4" sectionFormat="bare"/> and <xref target="RFC8040" section="2.5" sectionFormat="bare"/> of <xref target="RFC8040"/>.</t>
        <t>This contrasts with the base QUIC protocol, which does not require
  programmatic verification of the other party, e.g., in <xref section="2.1" sectionFormat="of" target="RFC9001"/> says "the server is optionally able to learn and
  authenticate an identity for the client."  In such circumstances,
  allowing the QUIC server to contact the QUIC client would open new
  vulnerabilities.  Any use of call home with QUIC for purposes other
  than NETCONF or RESTCONF will need a thorough contextual risk
  assessment.  A risk assessment for this RFC is in the Security
  Considerations <xref target="sec-con"/>.</t>
      </section>
      <section anchor="the-netconfrestconf-convention">
        <name>The NETCONF/RESTCONF Convention</name>
        <t>Throughout the remainder of this document, the term "NETCONF/
  RESTCONF" is used as an abbreviation in place of the text "the
  NETCONF or the RESTCONF".  The NETCONF/RESTCONF abbreviation is not
  intended to require or to imply that a client or server must
  implement both the NETCONF standard and the RESTCONF standard.</t>
      </section>
      <section anchor="requirements-terminology">
        <name>Requirements Terminology</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?>

</section>
      <section removeInRFC="true" anchor="editorial-note-to-be-removed-by-rfc-editor">
        <name>Editorial Note (To be removed by RFC Editor)</name>
        <t>This document contains placeholder values that need to be replaced with
finalized values at the time of publication.  This note summarizes all
of the substitutions that are needed.  No other RFC Editor instructions
are specified elsewhere in this document.</t>
        <t>Please apply the following replacements:</t>
        <ul spacing="normal">
          <li>
            <t>XXXX --&gt; the assigned RFC number for this draft</t>
          </li>
          <li>
            <t>PORT-X --&gt; the IANA-assigned port number for NETCONF Call Home (QUIC)</t>
          </li>
          <li>
            <t>PORT-Y --&gt; the IANA-assigned port number for RESTCONF Call Home (QUIC)</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="solution-overview">
      <name>Solution Overview</name>
      <t>The diagram below illustrates call home from a protocol layering
  perspective:</t>
      <artwork><![CDATA[
         NETCONF/RESTCONF                    NETCONF/RESTCONF
              Server                              Client
                |                                    |
                |         1. UDP                     |
                |----------------------------------->|
                |                                    |
                |                                    |
                |         2. QUIC                    |
                |<-----------------------------------|
                |                                    |
                |                                    |
                |         3. NETCONF/RESTCONF        |
                |<-----------------------------------|
                |                                    |

               Note: arrows point from the "client" to
                 the "server" at each protocol layer
]]></artwork>
      <t>This diagram makes the following points:</t>
      <ol spacing="normal" type="1"><li>
          <t>The NETCONF/RESTCONF server begins by sending a UDP containing
the TLS certificate it will present during the QUIC handshake.</t>
        </li>
        <li>
          <t>Using this source IP address of the UDP datagram, the
NETCONF/RESTCONF client initiates a QUIC session to the
NETCONF/RESTCONF server.</t>
        </li>
        <li>
          <t>Using this QUIC session, the NETCONF/RESTCONF client initates
a NETCONF/RESTCONF session to the NETCONF/RESTCONF server.</t>
        </li>
      </ol>
    </section>
    <section anchor="the-netconf-or-restconf-client">
      <name>The NETCONF or RESTCONF Client</name>
      <t>The term "client" is defined in <xref section="1.1" sectionFormat="of" target="RFC6241"/> and
<xref section="1.1.5" sectionFormat="of" target="RFC8040"/>.  In the context of network management,
the NETCONF/RESTCONF client might be a controller, orchestrator, or
network management system.</t>
      <section anchor="protocol-operation">
        <name>Protocol Operation</name>
        <!--{:type C%d}-->
<!-- <list style="format C%d"> -->
<t>C1. The NETCONF/RESTCONF client listens for UDP datagrams from
    NETCONF/RESTCONF servers.  The client <bcp14>MUST</bcp14> support receiving
    UDP datagrams on the IANA-assigned ports defined in <xref target="iana-con"/>,
    but <bcp14>MAY</bcp14> be configured to listen to a different port.</t>
        <t>C2. Upon receiving a UDP datagram, the NETCONF/RESTCONF client <bcp14>MUST</bcp14>
    ensure that the datagram contains at least 1200 bytes and <bcp14>SHOULD</bcp14>
    monitor the use of the datagram's source IP address and port for
    excessive connection attempts (see <xref target="sec-con"/> for details).</t>
        <t>C3. The NETCONF/RESTCONF client extracts the NETCONF/RESTCONF server's
    TLS certificate from the UDP datagram.  The NETCONF/RESTCONF client
    <bcp14>SHOULD</bcp14> monitor the use of the TLS certificate for excessive connection
    attempts (this can be done before certificate validation), <bcp14>MUST</bcp14>
    validate the server's certificate, and <bcp14>MUST</bcp14> ensure that the
    certificate belongs to a server that the client is willing to
    connect with (see <xref target="sec-con"/> for details).</t>
        <artwork><![CDATA[
To validate the certificate, the client MUST either use certificate
path validation to a preconfigured issuer certificate or compare
the certificate to a previously trusted or "pinned" value.  If the
certificate contains revocation checking information, the
NETCONF/RESTCONF client SHOULD check the revocation status of
the certificate.

To ensure that the certificate belongs to a server that the client
is willing to connect with, the client asserts the certificate
encodes an "identifier" {{RFC6125}} that the client had awareness
of prior to the connection attempt.  How identifiers are encoded
in certificates MAY be determined by a policy associated with
the certificate's issuer.  For instance, a given issuer may be
known to only sign IDevID certificates {{Std-802.1AR-2009}}
having a unique identifier (e.g., serial number) in the X.509
certificate's "CommonName" field.
]]></artwork>
        <t>C4. The NETCONF/RESTCONF client initiates the standard QUIC client
    <xref target="RFC9000"/> protocol to the IP address and port extracted from
    the received UDP datagram.  As part of establishing the QUIC
    connection, the NETCONF/RESTCONF client <bcp14>MUST</bcp14> assert that the
    server's presented certificate is the same as extracted in step
    C3.  Since the certificate was validated before, it does not
    need to be validated again here.  After the server's certificate
    is validated, the QUIC protocol proceeds as normal to establish
    a QUIC connection.</t>
        <t>C5. Once the QUIC connection is established, the NETCONF/RESTCONF
    client starts either the NETCONF-client <xref target="RFC6241"/> or RESTCONF-client
    <xref target="RFC8040"/> protocol.  Assuming the use of the IANA-assigned ports,
    the NETCONF-client protocol is started when the UDP datagram is
    received on port PORT-X and the RESTCONF-client protocol is
    started when the the UDP datagram is received on port PORT-Y.</t>
      </section>
      <section anchor="configuration-data-model">
        <name>Configuration Data Model</name>
        <t>How a NETCONF or RESTCONF client is configured is outside the scope
of this document.  This includes configuration that might be used to
enable listening for call home connections, configuring trusted
certificate issuers, and configuring identifiers for expected
connections.  That said, YANG <xref target="RFC7950"/> modules for configuring
NETCONF and RESTCONF clients, including call home, are provided in
{{RFC10010}} and {{RFC10011}} respectively.</t>
      </section>
    </section>
    <section anchor="the-netconf-or-restconf-server">
      <name>The NETCONF or RESTCONF Server</name>
      <t>The term "server" is defined in <xref section="1.1" sectionFormat="of" target="RFC6241"/> and
<xref section="1.1.5" sectionFormat="of" target="RFC8040"/>.  In the context of network management,
the NETCONF/RESTCONF server might be a network element or a device.</t>
      <section anchor="protocol-operation-1">
        <name>Protocol Operation</name>
        <!--{:type S%d}-->
<!-- <list style="format S%d"> -->
<t>S1. The NETCONF/RESTCONF server sends a UDP datagram containing the
    TLS certificate intended to be used for the QUIC connection,
    padded out to at least 1200 bytes.  The server <bcp14>MUST</bcp14>
    support connecting to one of the IANA-assigned ports defined in
    <xref target="iana-con"/>, but <bcp14>MAY</bcp14> be configured to connect to a different port.
    Using the IANA-assigned ports, the server connects to port PORT-X
    for NETCONF over QUIC, port PORT-Y for RESTCONF over QUIC.</t>
        <t>S2. The NETCONF/RESTCONF server listens for incoming QUIC connections
    on the UDP address and port used when it sent the initial UDP
    datagram to the NETCONF/RESTCONF client.</t>
        <t>S3. As part of establishing the QUIC connection, the NETCONF/RESTCONF
    server will send its certificate to the NETCONF/RESTCONF client.
    The server <bcp14>MUST</bcp14> also send all intermediate certificates leading
    up to a well known and trusted issuer.  How to send a list of
    certificates is defined in <xref section="4.5.1." sectionFormat="of" target="RFC9846"/>.</t>
        <t>S4. Establishing a QUIC session requires server authentication
    of client credentials in all cases except with RESTCONF, where
    some client authentication schemes occur after the TLS
    connection has been established.  If TLS-level client
    authentication is required, and the client is unable to
    successfully authenticate itself to the server in an amount
    of time defined by local policy, or 30 seconds if unspecified,
    the server <bcp14>MUST</bcp14> close the connection.</t>
        <t>S5. Once the QUIC connection is established, depending on how the
    NETCONF/RESTCONF server is configured, it starts either the
    NETCONF-server or RESTCONF-server over QUIC protocol, per
    <xref target="I-D.ietf-netconf-over-quic"/> and <xref target="RFC8040"/> respectively.
    Assuming the use of the IANA-assigned ports, the NETCONF-server
    over QUIC protocol is used after connecting to remote port
    PORT-X and the RESTCONF-server protocol is used after
    connecting to remote port PORT-Y.</t>
        <t>S6. If a persistent connection is desired, the NETCONF/RESTCONF
    server, as the connection initiator, <bcp14>SHOULD</bcp14> actively test the
    aliveness of the connection using a keep-alive mechanism.  The
    NETCONF/RESTCONF server <bcp14>SHOULD</bcp14> send PING Frame <xref section="19.2" sectionFormat="of" target="RFC9000"/>, and ensure an ACK Frame <xref section="19.3" sectionFormat="of" target="RFC9000"/>
    in received in an amount of time set by local policy, or 30 seconds
    if unspecified.  If the connection is deemed lost, the NETCONF/RESTCONF
    server <bcp14>SHOULD</bcp14> initiate a new connection by going back to S1.</t>
      </section>
      <section anchor="configuration-data-model-1">
        <name>Configuration Data Model</name>
        <t>How a NETCONF or RESTCONF server is configured is outside the scope
of this document.  This includes configuration that might be used to
specify hostnames, IP addresses, ports, algorithms, or other relevant
parameters.  That said, YANG <xref target="RFC7950"/> modules for configuring
NETCONF and RESTCONF servers, including call home, are provided in
{{RFC10010}} and {{RFC10011}} respectively.</t>
      </section>
    </section>
    <section anchor="sec-con">
      <name>Security Considerations</name>
      <t>The solution in this document extends <xref target="RFC8071"/> to support call
home using QUIC <xref target="RFC9000"/> with TLS <xref target="RFC9001"/> for the NETCONF
and RESTCONF protocols, <xref target="I-D.ietf-netconf-over-quic"/> and <xref target="RFC8040"/>
respectively.  The security considerations described in those documents
apply here as well.</t>
      <t>The solution in this document introduces a protocol interaction that
occurs before a standard QUIC-client-initated connection.  Thus the
security analysis in this section focuses on this protocol interaction.</t>
      <t>In step C2, ensuring the datagram packet is at least 1200 bytes thwarts
the amplication attack described in <xref section="14.1" sectionFormat="of" target="RFC9000"/>.</t>
      <t>In steps C2 and C3, monitoring for source IP address/port and server
certificates for excessive use can thwart denial of service (DoS) attacks.
Precautions mitigating DoS attacks are recommended, such as temporarily
blacklisting the source IP address/port or server certificate after a set
number of unsuccessful connection attempts.</t>
      <t>In step C3, ensuring that the server certificate belongs to a server that
the client is willing to connect with thwarts additional possible
denial-of-service (DoS) attacks.  Note that, in some cases, the client
may not be aware of the server's identity before the first connection,
and yet still be "willing" to connect so long as the server certificate
is valid.</t>
      <t>Step S6 recommends the NETCONF/RESTCONF server, as the
connection initiator, to actively test the aliveness of the
QUIC connection by sending a QUIC PING Frame and expecting an QUIC ACK
frame in an amount of time set by local policy.  The PING
and ACK frames are cryptographically protected, after mutual
authentication, and therefore do not introduce an attack vector.</t>
    </section>
    <section anchor="op-con">
      <name>Operational Considerations</name>
      <t>This solution has a dependency on middleboxes recognizing and
using the server's initial UDP datagram to allow the
client-initiated QUIC connection.  For instance, firewalls
<bcp14>SHOULD</bcp14> create impicit rules to allow the client's QUIC
connection to reach the server.  This differs from <xref target="RFC8071"/>
could rely on the full-duplex nature of TCP to tunnel through
middleboxes.</t>
      <t>Steps C2, C3, and C4 describe conditions that, if not met, the
client <bcp14>MUST</bcp14> drop the connection attempt.  Clients <bcp14>SHOULD</bcp14> log
such errors so that Operators can diagnose errors.</t>
      <t>Steps S4 and S6 regard servers timing out connection
attempts if needed.  Servers <bcp14>SHOULD</bcp14> log such errors so that
Operators can diagnose errors.</t>
      <t>Additionally, note that the last paragraph in <xref section="10.1.2" sectionFormat="of" target="RFC9000"/> says:</t>
      <t><tt>A connection will time out if no packets are sent or received for a period longer than the time negotiated using the max_idle_timeout transport parameter; see Section 10. However, state in middleboxes might time out earlier than that. Though REQ-5 in [RFC4787] recommends a 2-minute timeout interval, experience shows that sending packets every 30 seconds is necessary to prevent the majority of middleboxes from losing state for UDP flows.</tt></t>
    </section>
    <section anchor="iana-con">
      <name>IANA Considerations</name>
      <t>IANA has assigned two UDP port numbers in the "User Ports" range
   with the service names "netconf-ch-quic" and "restconf-ch-quic".
   These ports will be the default ports for NETCONF Call Home and
   RESTCONF Call Home when using QUIC.  Below is the registration
   template following the rules in <xref target="RFC6335"/>.</t>
      <t>Service Name:           netconf-ch-quic
   Port Number:            PORT-X
   Transport Protocol(s):  UDP
   Description:            NETCONF Call Home (QUIC)
   Assignee:               IESG <eref target="mailto:iesg@ietf.org">iesg@ietf.org</eref>
   Contact:                IETF Chair <eref target="mailto:chair@ietf.org">chair@ietf.org</eref>
   Reference:              RFC XXXX</t>
      <t>Service Name:           restconf-ch-quic
   Port Number:            PORT-Y
   Transport Protocol(s):  UDP
   Description:            RESTCONF Call Home (QUIC)
   Assignee:               IESG <eref target="mailto:iesg@ietf.org">iesg@ietf.org</eref>
   Contact:                IETF Chair <eref target="mailto:chair@ietf.org">chair@ietf.org</eref>
   Reference:              RFC XXXX</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC6125">
          <front>
            <title>Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <author fullname="J. Hodges" initials="J." surname="Hodges"/>
            <date month="March" year="2011"/>
            <abstract>
              <t>Many application technologies enable secure communication between two entities by means of Internet Public Key Infrastructure Using X.509 (PKIX) certificates in the context of Transport Layer Security (TLS). This document specifies procedures for representing and verifying the identity of application services in such interactions. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6125"/>
          <seriesInfo name="DOI" value="10.17487/RFC6125"/>
        </reference>
        <reference anchor="RFC8071">
          <front>
            <title>NETCONF Call Home and RESTCONF Call Home</title>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="February" year="2017"/>
            <abstract>
              <t>This RFC presents NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8071"/>
          <seriesInfo name="DOI" value="10.17487/RFC8071"/>
        </reference>
        <reference anchor="RFC9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="RFC9001">
          <front>
            <title>Using TLS to Secure QUIC</title>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <author fullname="S. Turner" initials="S." role="editor" surname="Turner"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document describes how Transport Layer Security (TLS) is used to secure QUIC.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9001"/>
          <seriesInfo name="DOI" value="10.17487/RFC9001"/>
        </reference>
        <reference anchor="RFC9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="July" year="2026"/>
            <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 obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9846"/>
          <seriesInfo name="DOI" value="10.17487/RFC9846"/>
        </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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.ietf-netconf-over-quic">
          <front>
            <title>NETCONF over QUIC</title>
            <author fullname="Jinyou Dai" initials="J." surname="Dai">
              <organization>Fiberhome Telecom LTD./CICT.</organization>
            </author>
            <author fullname="Shaohua Yu" initials="S." surname="Yu">
              <organization>China PCL.</organization>
            </author>
            <author fullname="Weiqiang Cheng" initials="W." surname="Cheng">
              <organization>China Mobile</organization>
            </author>
            <author fullname="Marc Blanchet" initials="M." surname="Blanchet">
              <organization>Viagenie</organization>
            </author>
            <author fullname="Per Andersson" initials="P." surname="Andersson">
              <organization>Ionio Systems</organization>
            </author>
            <date day="25" month="October" year="2026"/>
            <abstract>
              <t>   This document specifies how to use QUIC as a secure transport for
   exchanging Network Configuration Protocol (NETCONF) messages.
   NETCONF over QUIC allows implementations to take advantage of QUIC
   streams, for example, to eliminate some TCP head-of-line blocking
   issues.  NETCONF over QUIC provides security properties similar to
   NETCONF over TLS.

   This document also defines a YANG module which augments the ietf-
   netconf-client and ietf-netconf-server YANG modules.

Editorial note (to be removed by the RFC Editor)

   This draft contains placeholder values that need to be replaced with
   finalized values at the time of publication.  This note summarizes
   all of the substitutions that are needed.  No other RFC Editor
   instructions are specified elsewhere in this document.

   Artwork in this document contains shorthand references to drafts in
   progress.  Please apply the following replacements:

   *  AAAA --&gt; the assigned RFC value for this draft

   *  BBBB --&gt; the assigned RFC value for draft-ietf-netconf-netconf-
      client-server

   *  CCCC --&gt; the assigned RFC value for draft-ietf-netconf-quic-
      client-server

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-netconf-over-quic-13"/>
        </reference>
        <reference anchor="RFC6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/>
            <date month="June" year="2011"/>
            <abstract>
              <t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6241"/>
          <seriesInfo name="DOI" value="10.17487/RFC6241"/>
        </reference>
        <reference anchor="RFC7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="August" year="2016"/>
            <abstract>
              <t>YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7950"/>
          <seriesInfo name="DOI" value="10.17487/RFC7950"/>
        </reference>
        <reference anchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </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="Std-802.1AR-2009" target="http://standards.ieee.org/findstds/standard/802.1AR-2009.html">
          <front>
            <title>IEEE Standard for Local and metropolitan area networks - Secure Device Identity</title>
            <author>
              <organization>IEEE SA-Standards Board</organization>
            </author>
            <date year="2009" month="December"/>
          </front>
        </reference>
        <reference anchor="RFC6335">
          <front>
            <title>Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="L. Eggert" initials="L." surname="Eggert"/>
            <author fullname="J. Touch" initials="J." surname="Touch"/>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <date month="August" year="2011"/>
            <abstract>
              <t>This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry.</t>
              <t>This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol (SCTP). It also updates the DNS SRV specification to clarify what a service name is and how it is registered. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="165"/>
          <seriesInfo name="RFC" value="6335"/>
          <seriesInfo name="DOI" value="10.17487/RFC6335"/>
        </reference>
      </references>
    </references>
    <?line 422?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author would like to thank the following for lively discussions
on list and in the halls (ordered by first name):
  Bo Wu,
  Lucas Pardu,
  and Mirja Kühlewind.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81c63bbRpL+j6fooc+e2LMkdbGc2FqPMzItxzrxRWPJJ+Mz
zpm0gCaJMYjmoAEpjMZ5ln2Q/bX7YvtV9QUNkJSczM6e+EcEAt3V1XWv6uqM
RqOkzutCHYrB6+PzyZvXz8VEFoV4oRdKyDITb4/P+q/fmbyciT+9O5kMEnlx
UalLmj3ZeTvZMiiVtZrpanUoTJ0lzTLDb3MoHu5+tZckmU5LuQACWSWn9ShX
9XRUqjrV5XT09yZPRylgjuaAOdrdT0xzsciNyXVZr5aYdHJ8/lyIO0IWRgOL
vMzUUuE/ZT0YioHK8lpXuSzox8nRU/zRFZ7enj8fJGWzuFDVYULYHCZYz6jS
NMCrrhqVYE/3E1kpCahvlqqSNdY0TJJXspQztaA1kitdfZxVulkSCVRNP8UE
qOezxk4ZJB/VCq+zw+RSlQ1WEuKWCULYvQ2+w0ei4jc0nt4vZF7gvSPPH4lW
Y13N6JOs0jk+zet6aQ53dmgkvcov1dgP26EXOxeVvjJqx8HYobmzvJ43Fy3g
0dVsp0t6GlUQ1+pojXb02EIY57o3b+dWpo7n9aIYJIls6rkGN8QISwkxbYrC
isXgWxBafCdrsGfA37AVWeY/MbWISvxJOGIaO0Y5Un3E5H+n5f94xcPGwAKr
lbpaYP4ls+Pt88mXe/sP3CNJpXt8tLu72z6Gtw8PvjxMkiQvpzGUk9GzcWef
+lJVvFm/xv6BB/HVowe7YbmDsMbe3gE93sHzHtbbjZ738HxWZ6OHu/vjvaO3
o/3d3UeHvNNaVjMFthBXwBRTQ0RllRkgoxSzfQqtgOKZ8G0nhsIMsJCcITg5
Pj7GYnaswCbFSw1+sewvVF3ppS5yfBakHqJ0dBcjcabSplLimbrMUyVOSAvz
emUZwlomaMHR3j6/CRwXjqmkzbTy0cgvbsRTjT/JeDxOktFoJOSFqSuZ1kly
Ps8NEU2oH2sovBGfa76SD3+hacTmD9+LWgvTLJe6qkU9V2yvxLLStU51IexI
koIP3wMBi8Iiz7JC4ccdcVKCGFmTkiD+MxhdXzu5+/TpZoR4IOGDgQ0Z2OT8
5Vl4i+nAMsB3UA9osANpLLwraKvI8StfLIs8zevEL0nMfnF+frpz30GFSAKq
CHvhtyTJnz4lG4BeX29XA4LztKmTUmGkqmBmZWl41YVcLsnOBYAtxZrgRsZE
YUuQ0YU0KhNkQwTZEGF00RATQCkFJa/xMS9Bv9yQe2nIVAswp1SyKlYiZ8Ek
iQaxicggogPpASWZgtZYMF5ahnaLNGFZ5QtZrUSWT6eqUiWk/UIRO+hjY5TQ
U/Hu2Slmm1rJjH6eT06JOQ4WsfQSeMChsKkTeEyrfMmbYD3TsCts4YgnSdgq
WMFyFra1wPrYE0hoGLVAilonawJEQnznjhBHS+K7vMihxytS9ZrdWZIQdCVq
lc7L/O8N0LN4XbQEbVeG9oNjMAQXhWLBcZaA/ZT3kMKkqpRVrg3GpnMhLZa6
7MO+vob1YMT3xnsgWGuMWf5e6CsFQRrSbNPBkNDQJUjgWUaoOHEFkNuUb0go
bd/l2NMEps5YZtgBELS6yi3GOW1K1kEc6kBwI+byUgFE+8mQkSSyS2OaBXPc
jO0aXsk6mAZQgFIpKBL2mxY5QNloxKgKhDEky/ibT1dM4NwZXxI9JjipHCAs
ZVWvvBA5cF49zFKl+TR3JKwjhDwOANBh1f54nxYIJmHIGPnZa1vAZEAI0w3m
H/CM/fEDB8faK0d14AQTAjthsNegfKSpXbGGZs5zCFemIQ+lrv3GaL+VnlVy
QW46tfSB3DPuMWEsWYZCjWfjYWeLALHP8iiCjRVGrowYsLIx7Yl2mhkJoQJf
SR/AjQLWhpU5sb7OGp2aBLFlj6eV5eh4gDiitJqS5hVEkFx2qsyQYBSFviJr
GNTaLY+1iExwi+0nC09c6aaA+UFIDO28ApDLpigRzLLm54oE76hceZPVGlQm
NgMiBJdNtdQGtPVSBGkvg3BgQOD0VQ4IpYIISUHeXTezOSMHn9jA4Fa5IfsA
0VfGsH4BAX4bvWuVjMwl/rBSKhtegGik1ZAe0NBH5dfX0KoR1mHRgYWLtGmn
1XldXhLZyVmTeDF2urFUqyhiROJQWcGITADbHFicahFypB2yTg7sgDBsyHlI
UkhhM6LcChkwXxYyVV7aiA4sOomI6Rdry6BrDFr0u4BZ0FkfKdjA6pACbx40
ywQ595U1TNLLA744oVk0hqdjkDUAF9rpl8fLR4usoR199l8srd+2VsSIc5Ap
L3WhZyvrr5H9CEp/oDGv3p2dUyJGf8XrN/z89hhS9vb4GT2fvTh6+TI8JG7E
2Ys3714+a5/amZM3r14dv35mJ+Ot6LxKBq+O3g+sRRq8OT0/efP66OVgsxsD
tS4Uk7JCBFEzL5OOU3g6Of3v/9w7gKT9DkK5v7f3CIbA/ni49xViJJggVdrV
2BvZnyDbKkF0A1NAUEi/UrmEzywMOx4z11elgFIp0PL3fyHKfH8oHl+ky72D
J+4Fbbjz0tOs85Jptv5mbbIl4oZXG5YJ1Oy871G6i+/R+85vT/fo5eOvC7hp
Mdp7+PUTG44c+yxdvNYwj3fPmRuQKISOmbhYsRmwg+4l14f2Q15W0/STi7oD
M9kOIuqyWjfXBSn0pSwoUGBNYNtUuwV4UMbGLkHsIIv8J/x0w6W1C3W+YO1d
NheFcx3efZaELXw4QkFMNMTdxOm5aZCo5HVjzZPVQcgZra4yCqe1czzt1jhY
rGwyYRIOroI/VoVRVyQlm+KTUzga2G9IWWF9/1R7T+G2yKp5SEbv9+LP+CdG
oyc8EjY3n1HMRGjYekhrfDl15zmnb96ej9pZJ0evj0ZhKkfw0dz1rOcuOZJ7
LaT3nwlpQ+nJgeLs68xHum9gzy5zuDcXqmW5JJ8PHoMMAh6poaSxBodaBzet
9AJmMUQmhVwhOEAEj5AB0dSSvD/l9cnPP//sMlQh1m3yhn/9MUn385k1vzf+
m7CxTvqv/3HzLDfohml7Y85KPnPa6PZ/T25a7Vci+Sun7Y9tvPJ50x5/xuZ+
O3u7P94qef/fe+vPI4t9CNtGRUUocE7RG6kWaffABh0DSkXXQPEAG4sMyNYq
iZi3q46se97CO51eyI/K9KwcL0v2bW9b6ORings1I98Aj2IQM9FUyQrhvIZV
f+FLAiJVVW3zBdjd2sa2rsAgsqbqhOIIiDMzB3IwyBBFV/5mO2p0U1E57FTI
LMN044NBWjqTNW+MQwVefQ15F7oBvzpnKyZ99M91cFfE2DzXbhw43e/iFAMY
xlHfxmVpVVuy27RCjMUNGCSdqLyTNTh7l5yHONtLDnG+rcT0awRt4slpVudz
P6PkxIozLZuN0FdXsIjKFcPkJlos8tm8ptBB2rwUEkglCV2lc8UuRvOvZB2u
MCtTq4UNmE+9lIdzhSR5/LvR6PqQ6v5i8m/ZJ5hWfiUeF7nB7HpVqD8MbL2Z
BgyekA9NJpD4jQLvEKbJChJP3jSWNsNKepPI+JKEA8RxqC8SVipV+aXXli5c
XW5x7D1G5iCNTdiGDOUCaRiCRyJu6k5DbKBmt0BPMq6vACKIOYGqvVtizYCS
0+iOWm0lD+3KnhaUhgrXHKfRBD+9jSfxgcKsWuzt7+7CgrAeIta3sTMDWeiS
47ioBhjD+mKTJSAQvvBqMfkxJYW6ZDKUTpxlDdlZgoR3jVJxssuMzRRQLMw9
osf9m+UBck/Vc3OTqn5hVb1vAINVj8m7zd6mbQDjkostxFlbBUM2kcBan0AG
tmEpkm2IS6ZLqr5ipuqAQhifZ6xd94Ytp91bJdryDRgTzbMpHMt7Typ4frwC
xZflzFjZ9LUYL0LefBr2G2x4rRd0m7IlltsYypzQXaw7yNY9HXW1dSJxNI7h
LCUWbKli0YY/i/QtN6bB7HiTwCfVi6WsVPCN8WcP5DLXjaH8o0KwDUh0zLrM
sdNsYBMqMsDTjWQMOgYo2hXnYFBTPvoMh2zOT93oIp2s8WRX1AkQDbxYY2xh
eW0bLaX7luAX8pvBdHje4XeHX1Twqpwu9nmlylTz6UApBrZWiDwQgZI9ftnb
f0AnRT1Rm8tMyCswqoT62IPSKZ1U2GqQc309k2Ir66JdwtbT7fKZ3U0ZY2e8
lYaQcqnHZuiQAY30mIvaOqUwxaXVG4gNfbNyhsWfu7yXipzQPDGD2pdeDBdy
hZUYxMeS6iTYBtdWyK2Ik2fq8uRZFzdEAL0z0k+feP5cOufQ8KlBtGFx1xZ9
wQuqQNj0854vOf55/GD3UV9isYHBRC9g0l7LhRoIgCmoFjY5uNn6thEcGx9f
XovqtbxSfMgXAmLHwU2uwxl1Ktt7p25ln1wi3vYM9pHhajcJB4IWeQEHO49D
2dhI3Rodss2xgty1k8G0tidynXDa0UDSuYyJtpCTpqolwyBvJs5yOl3rq+IV
JnmjmDnrP6Qg3R8BMICo2NMOljMYG1tyAzGmtaq2+gKvzWHycMOZLB5SrGNo
H9xWwMwKpHVxs2VyoCpJy4OxeOP31vtMiwYIftmNhQXHB4wlU+JPVtvRIzcg
OreNQ+9RX+7ceXE4MCR5Mc3CC0jkujeEeMMgfL3V2wMgY1El8zBX5VpAgQEM
IwgvnemSkLsSVL8UvWEBK379RTYstGWR9+6QtNOUI55hnngFo1gkCVlMuTGR
aZ1+x6kK3dR0XGEFLdVLlfQPGXxNEdJeNGT5087yrFsh/eDTBoQTquSzJhsi
E4soemhrXK08mWGAx5y0TjrpaiTZXGPDn3hw7BtseEbFMZrdgmfsgaGROYT1
/dHrb6w0UZ8LpGmhs6ZQdnoEOtl43unONoeOFIRC2NKQvZM7OydjkXy4/nDt
22U+fPrAiaCIXu7xS9ggV9ErVuPkxlzU1ufiXNQXKX4juag/v2lzUT9VuZMc
bAe5Ejfh2ITztozz7LaM8yxknGfbMk6HluHOl24SFtVXgn9Yq69Ex1hewv3Z
aM84Dl00m9FwPr7Tm9Izl5s4vEIC4JNYD88GaZRDbLdrEd+dpYzS1+2pq4/8
NuaunDobb1c3GdPILXlQHHtG9tC2ykVFd2q2YXoNY4vWraaHMRCOs/2b2RkX
EKCPeuG7cWLjYmPN1pivRSjMTTbFOfU/lDZsteFQQVN8h5gVl22lJHdGDqwR
GNwWxtwawkRhii3tkehyV1Qvv7kRF5blrphxL6qFRnaLTxUXKss514mjVUhs
5qsozdKKyZXCFBvtsq9z6VQImMn31B46s8enNB3Q22zVwfgBzJFvZ3h48CUf
mJ8hcD2OidirMLpzZeN3GXUz+Nycuges80sh/fQRVGiPPKl5gPL6pct7PR2p
c0O51NKwz3K5UWcF+Mw5TBv8aJo2WD4EbbAivXAVkb6BJkLUovjJ5p7U5VUo
uIA42O4t1DbFZMMQbLRevSldc4czJSlVKqh/a9Xt8IAUqWLqhcd3iZTcHrDQ
jVubDA6dLnpOIY8quNHS5lLcq3x/lxqGNBnVfIr1w5lgG2vFopcW2qherkcM
/iWxpu2gJjEgcpK83Vxd7oY7HIWvhaPx/JGbFoeh/pU3TVFrz1JVzuje1FrI
zIoj2K7LJwC/JJDtBLEWOcuyNQTb7g+Wyq5boaNqiAPB5Onboli3/c0wOxK+
BrcNWs++HJOYSz7AZLtd99iMuNJK9i32cOjb9OLpNnmlCrcrs0hHXUFt4YHJ
SJUuuQLhyRvBsM2cUnxUajnigWKh0rksc+NKiTfKmVuXbd/pCWLM5xXlj1Go
9Wi87zUr5NBWj11dBwp4NPl208T7nUm+8hFShFh5g+IaVd+itBZOR3FDIWyN
OTBxGYCZ+naH5UjhKwocBF7FAIHWTBO1LyTVwrRA4Par05pNev4vTGssqVaw
PaamOwBQx7buQb+cjspipiuYmIVhqtuGigpR8KWEhUV0gLm1P8r4P8pO3OnI
vzQ7uRM63db63O74SrFNUEKz71pXk+9B39JaTjgn826DdafwxF6611zebwtN
NvepDn+hqU46+/fhlCNA2iVAr1GXnJ3fsklsBwy3ycB+USQ1vo1Muevg51PV
qE0VYiPTIKIJxx3GnzLIbu3O1SBG7qQ0i10v7aZhW5q0fb+lLFbGtzVSRcTp
7BRYcZele78JH+zoxJbIxGR/aM2a92khgF5C5xUHLJuOrer5FXlnzi4lXwCQ
viRMtmJbV/ZB3AZre3QdJgaoMFMn94f+oMdXI9aOvHZY/trG5aQTt3bPf/gU
Q5YOY2BWUr4AJGgqXTG5+0yf3XOIm3FyCnMtXc/VApZxJtlhYpAfwxpKRx6L
Baebw7YrXS2AmazyYpVcFBhLsbWn7JZdtN2UccpgAwE6IajdHTNCGR4ghIub
zvZixt7vMNZV+TestO1AItl2ANU9fHKCQHvKbfcyLCsojxA3sbQe6eloM61t
5wevxg3TNniXbJ6j4xAq4VNDNtUprrhTf9qttoZGaKdb3NmRV6buJPwkLitF
cSUlagA2cHsaxJtC1kX08MHLOsESX8ulaIkoffZlKww3Hor6iCjZHBERA/rR
0FoklPQD704fCn+MohoOWrjUxt9LOwDBSzLl758bkDiDSpCZjBT+MASrC2m1
WtbUIr+c040Y4E9Whwt8QyfJi4Zat5NuphSyo8ryLdPM52BPGTlrUC4BTVMH
yJ22/AT01lybXgbPxl0zzmZTQieFv9aZrsg82jtYF/pHxVVcPSvznyyZsqQJ
RZVWyNpKQ6fKwB31lq2tCbeHV/16ff+oCjKqrjDfJP7QsVKc+S2WdKFKVBxS
xGs4lfjCNt/EgsQBPbU/tUiHaz5cNbLtGrEvx3Rq7OerP67yQmnoKGuWhfpR
lLJurLKdT045DW2wWoFx3POeRPRzqmDYnZDlYUN+ENwAEcGaB+O1fcqsRmw1
jGhn88+s0svtR40Td23FkazQs4TNr6oqXRHLrbWzUkJvyPhT51dJjt6OCvie
2asjrMIz8sXhIkzOWR5VBqMGgtA8QOj7NtwzN6VFSGxAKLkNoSQ5Cia0QApQ
etPIpCjI/1I0ylrW86q7471wh8aFXnS95DBJfvjhh6OYjFyjst3I2BkzwTl6
q8nGlX5DyjLlOjBQz3XGhtF6B3ceQoBKNdNO3lutWcgf/5pDOv5KQ7i8Gu7p
hZD6PwT1LUSbaO9n0Tk7W6dYR22IH5Cna3h5i42sqQjJV0XeHv9p9IBm083L
g68efvV9bKCl2B+Bt01t8Wc6UGgEmz5kY1nlfBePuupd17U3sJ5ShOSqU1Wh
a4Hkl+k+H1VXK3XpK5QL+TdduUtU8XZYG5Go8Z3F2vetkHWZQtnNGKyzhwxU
Wlg3dKF4zF0HPIaNnC9B1FeagUX90OEOzOAdxFycUgI0EGDMjFPmcDfKO2tO
m9r73OmcY++BvQxBV9c6r7k+cs4X62y9+8q5WY4q1VQ2Re2+bO7wtpecNjVs
c9U3usQpxFPblW3cIfUs5845V0ckHS0sQePbTtaasuZ8Tecs9+8/cJfEWIVp
x6/5snj7r7d1GkpUE6/trf9oZFRLPw+i7k9M7pp7h8KXqJ+1lzQ7AG5oeaeq
E3G1gxv9Ozk++0Y8zpWZhWv8T2j8xN7k6g+3/6ODyVzmlXic0p/utLfKXUTt
TaTGfmr5v5FWfYG4lVjv/wlibe/q/y1Ry971puIJ6fFRSiX5QmUzm2leH1q1
VNkfBlNZGDVwCbm90+6u3RX5R3eAIEvbj9RKNelRYQPGLDfI+wyfpMCack2f
9NRp/JyiDHFXVxmtR+GdjY9Jxe/R7fmnWnzXUDn4ZYMAXJzCF/JP7mPLq79J
8e3//Ne8UFiXAt/kfwHjrjPL9EMAAA==

-->

</rfc>
