<?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.3.8) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-john-scion-svcb-00" category="info" submissionType="independent" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="SCION SvcParamKey">Publishing SCION Endpoint Addresses in DNS Service Binding (SVCB) Records</title>
    <seriesInfo name="Internet-Draft" value="draft-john-scion-svcb-00"/>
    <author initials="T." surname="John" fullname="Tony John">
      <organization>OVGU Magdeburg</organization>
      <address>
        <email>tony.john@ovgu.de</email>
      </address>
    </author>
    <author initials="J." surname="van Bommel" fullname="Jelte van Bommel">
      <organization>ETH Zurich</organization>
      <address>
        <email>jelte.vanbommel@inf.ethz.ch</email>
      </address>
    </author>
    <author initials="T." surname="Zäschke" fullname="Tilmann Zäschke" asciiSurname="Zaeschke" asciiFullname="Tilmann Zaeschke">
      <organization>ETH Zurich</organization>
      <address>
        <email>tilmann.zaeschke@inf.ethz.ch</email>
      </address>
    </author>
    <author initials="L." surname="Schulz" fullname="Lars-Christian Schulz">
      <organization>OVGU Magdeburg</organization>
      <address>
        <email>lschulz@ovgu.de</email>
      </address>
    </author>
    <author initials="N." surname="Rustignoli" fullname="Nicola Rustignoli">
      <organization>SCION Association</organization>
      <address>
        <email>nic@scion.org</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <keyword>SVCB</keyword>
    <keyword>HTTPS RR</keyword>
    <keyword>SCION</keyword>
    <keyword>path-aware networking</keyword>
    <abstract>
      <?line 72?>

<t>This document defines "scion", a Service Parameter Key (SvcParamKey) for the Service Binding (SVCB) and HTTPS DNS resource records. Its value lists the addresses at which a service endpoint is reachable over SCION (Scalability, Control, and Isolation On Next-generation networks), a path-aware inter-domain network architecture. This document specifies the wire format, presentation format, and semantics of the key and requests its registration with IANA.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-john-scion-svcb/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/netsys-lab/draft-scion-svcb"/>.</t>
    </note>
  </front>
  <middle>
    <?line 76?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>SCION (Scalability, Control, and Isolation On Next-generation networks) <xref target="I-D.dekater-scion-controlplane"/> <xref target="I-D.dekater-scion-dataplane"/> is a path-aware inter-domain network architecture <xref target="RFC9217"/>. A SCION endpoint is identified by a SCION address, which consists of an Isolation Domain (ISD) number, a SCION Autonomous System (AS) number, and a host address.</t>
      <t>No interoperable way exists to publish SCION addresses in the DNS. Current deployments use TXT records of the form "scion=ISD-AS,host" (Section 3.3 of <xref target="I-D.meynell-panrg-scion-research-questions"/>), which cannot be associated with the protocols, port, Encrypted ClientHello (ECH) configuration <xref target="RFC9848"/>, and priority that SVCB and HTTPS records <xref target="RFC9460"/> carry for an endpoint.</t>
      <t>This document defines the "scion" SvcParamKey, which lists the SCION addresses of the alternative endpoint of a ServiceMode record.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>This document uses the following terms:</t>
      <dl>
        <dt>ISD number:</dt>
        <dd>
          <t>A 16-bit number identifying a SCION Isolation Domain (Section 1.5.1 of <xref target="I-D.dekater-scion-controlplane"/>).</t>
        </dd>
        <dt>SCION AS number:</dt>
        <dd>
          <t>A 48-bit number identifying a SCION Autonomous System (AS) (Section 1.5.2 of <xref target="I-D.dekater-scion-controlplane"/>). SCION AS numbers are distinct from BGP AS numbers, although some SCION ASes reuse their BGP AS number as their SCION AS number. In this document, "AS" and "AS number" always refer to a SCION AS and a SCION AS number.</t>
        </dd>
        <dt>Host address:</dt>
        <dd>
          <t>The address of an endpoint within its SCION AS, interpreted only within that AS; the SCION specifications call it the endpoint address. SCION carries IPv4 (4-octet), IPv6 (16-octet), and other host address types (Section 2.1.2 of <xref target="I-D.dekater-scion-dataplane"/>); this document covers IPv4 and IPv6 host addresses only.</t>
        </dd>
        <dt>SCION address:</dt>
        <dd>
          <t>The combination of an ISD number, a SCION AS number, and a host address (Section 1.5 of <xref target="I-D.dekater-scion-controlplane"/>).</t>
        </dd>
      </dl>
    </section>
    <section anchor="key">
      <name>The "scion" SvcParamKey</name>
      <section anchor="wire">
        <name>Wire Format</name>
        <t>The SvcParamValue is a sequence of one or more 24-octet blocks, each holding one SCION address:</t>
        <figure>
          <name>One SCION address block</name>
          <artwork type="ascii-art"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          ISD number           |                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
|                        SCION AS number                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                                                               +
|                                                               |
+                         Host address                          +
|                                                               |
+                                                               +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
        <dl>
          <dt>ISD number:</dt>
          <dd>
            <t>2 octets, in network byte order.</t>
          </dd>
          <dt>SCION AS number:</dt>
          <dd>
            <t>6 octets, in network byte order.</t>
          </dd>
          <dt>Host address:</dt>
          <dd>
            <t>16 octets. An IPv6 host address is carried as is. An IPv4 host address is carried as an IPv4-mapped IPv6 address (Section 2.5.5.2 of <xref target="RFC4291"/>).</t>
          </dd>
        </dl>
        <t>A SvcParamValue whose length is zero or not a multiple of 24 octets does not have the expected format, so the RR is malformed and a client that implements this key <bcp14>MUST</bcp14> reject the entire RRset (Section 2.2 of <xref target="RFC9460"/>). A value of any other length is well-formed, even if it contains unusable addresses (<xref target="unusable"/>).</t>
      </section>
      <section anchor="presentation">
        <name>Presentation Format</name>
        <t>The presentation value is a comma-separated list (Appendix A.1 of <xref target="RFC9460"/>) of one or more SCION addresses. To enable simpler parsing, this SvcParamValue <bcp14>MUST NOT</bcp14> contain escape sequences. Each item matches the <tt>scion-address</tt> rule of the following ABNF <xref target="RFC5234"/>. <tt>DIGIT</tt> and <tt>HEXDIG</tt> are defined in Appendix B.1 of <xref target="RFC5234"/>; <tt>IPv4address</tt> and <tt>IPv6address</tt> are defined in Section 3.2.2 of <xref target="RFC3986"/>.</t>
        <sourcecode type="abnf"><![CDATA[
scion-address = isd "-" as "_" host
isd           = 1*5DIGIT              ; decimal, 0-65535
as            = as-dec / as-hex
as-dec        = 1*10DIGIT             ; decimal, 0-4294967295
as-hex        = 1*4HEXDIG ":" 1*4HEXDIG ":" 1*4HEXDIG
host          = IPv4address / IPv6address
]]></sourcecode>
        <t>The part before the "_" is the "ISD-AS" text representation of the ISD number and SCION AS number (Section 1.5.3 of <xref target="I-D.dekater-scion-controlplane"/>). The <tt>isd</tt> and <tt>as-dec</tt> values are decimal; leading zeros do not change the value. The <tt>as-hex</tt> form gives the SCION AS number as three 16-bit groups in network byte order (Section 1.5.3.2 of <xref target="I-D.dekater-scion-controlplane"/>). An IPv4 host address can be written in IPv4 form ("192.0.2.1") or in IPv4-mapped IPv6 form ("::ffff:192.0.2.1"); both produce the same wire encoding.</t>
        <t>A presentation-format parser <bcp14>MUST</bcp14> reject a value in which any item does not match <tt>scion-address</tt>, has an ISD number above 65535, or has an <tt>as-dec</tt> value of 2^32 or more. Zone-file implementations <bcp14>SHOULD</bcp14> also reject a value that contains an unusable address (<xref target="unusable"/>).</t>
        <t>SCION tools write a SCION address as "ISD-AS,host". This document uses "_" in place of the "," so that values need no escaping.</t>
        <section anchor="rendering">
          <name>Canonical Rendering</name>
          <t>When converting a wire-format value to presentation format, an implementation <bcp14>MUST</bcp14> render each SCION address as follows:</t>
          <ul spacing="normal">
            <li>
              <t>the ISD number in decimal without leading zeros (Section 1.5.3.1 of <xref target="I-D.dekater-scion-controlplane"/>);</t>
            </li>
            <li>
              <t>the SCION AS number in decimal without leading zeros if it is below 2^32, and otherwise in the <tt>as-hex</tt> form with lowercase hexadecimal digits, no leading zeros within a group, and "0" for a zero group (Section 1.5.3.2 of <xref target="I-D.dekater-scion-controlplane"/>);</t>
            </li>
            <li>
              <t>an IPv4-mapped host address in dotted-decimal IPv4 form, and any other host address in the form of Section 4 of <xref target="RFC5952"/>, without the mixed notation of Section 5 of <xref target="RFC5952"/>.</t>
            </li>
          </ul>
          <t>An unusable address is rendered like any other, so a zone-file implementation that follows <xref target="presentation"/> rejects the rendered text. Zone transfers carry wire format and are not affected. A round trip through wire format preserves the value but not necessarily the text (<xref target="rendering-vectors"/>). Two SCION addresses are the same address if their wire encodings are equal.</t>
        </section>
      </section>
      <section anchor="semantics">
        <name>Semantics</name>
        <t>The "scion" SvcParamKey applies to HTTPS records and to SVCB records of any protocol mapping, unless that mapping specifies otherwise (Section 7 of <xref target="RFC9460"/>).</t>
        <t>The key indicates that the alternative endpoint named by the record's TargetName is reachable over SCION at each listed address. The listed addresses are equivalent; their order carries no preference, and duplicates have no effect. Clients <bcp14>SHOULD</bcp14> pick addresses to use in a random order, as for "ipv4hint" and "ipv6hint".</t>
        <t>Unlike "ipv4hint" and "ipv6hint", the value is not a hint: clients use the listed addresses directly. This document does not specify how clients order connection attempts to SCION addresses relative to IP addresses.</t>
        <t>The other SvcParams of the record apply to connections to the listed SCION addresses as they apply to IP connections to the endpoint. In particular:</t>
        <ul spacing="normal">
          <li>
            <t>"port" gives the transport port at the SCION host address. If it is absent, the port is determined as for IP (Section 7.2 of <xref target="RFC9460"/>).</t>
          </li>
          <li>
            <t>"alpn" and "no-default-alpn" determine the SVCB ALPN set for connections to the SCION addresses exactly as for IP connections (Section 7.1 of <xref target="RFC9460"/>). A protocol that runs over TCP uses TCP/SCION, and one that runs over UDP uses UDP/SCION (SCION protocol numbers 6 and 17, Appendix A of <xref target="I-D.dekater-scion-dataplane"/>). A client that cannot use the required transport over SCION does not use the SCION addresses for that protocol.</t>
          </li>
          <li>
            <t>"ech" applies to TLS handshakes over SCION.</t>
          </li>
        </ul>
        <t>A client <bcp14>MUST</bcp14> authenticate the server of a connection to a SCION address as it would over IP, with the same server name and certificate validation.</t>
        <t>An IPv4-mapped host address denotes a SCION IPv4 host address, which a client <bcp14>MUST</bcp14> use as a 4-octet host address in the SCION header (address type 0, length 0; Section 2.1.2 of <xref target="I-D.dekater-scion-dataplane"/>). Any other value denotes a 16-octet IPv6 host address (address type 0, length 3). The encoding therefore cannot express IPv6 host addresses that are themselves IPv4-mapped.</t>
        <t>A client <bcp14>MUST NOT</bcp14> use the host address of a SCION address as an IP address of the endpoint. IP addresses come from A and AAAA records or from "ipv4hint" and "ipv6hint".</t>
        <section anchor="unusable">
          <name>Unusable Addresses</name>
          <t>A SCION address is unusable if its ISD number is 0 or its AS number is 0 (wildcards, Sections 1.5.1 and 1.5.2.1 of <xref target="I-D.dekater-scion-controlplane"/>), if its AS number is ffff:ffff:ffff (reserved, Section 1.5.2.2 of <xref target="I-D.dekater-scion-controlplane"/>), or if its host address is unspecified (0.0.0.0 or ::) or multicast (224.0.0.0/4, or ff00::/8 per Section 2.7 of <xref target="RFC4291"/>).</t>
          <t>Operators <bcp14>MUST NOT</bcp14> publish unusable addresses. A client <bcp14>MUST</bcp14> ignore unusable addresses and <bcp14>MAY</bcp14> use the others in the value. If no address remains, the client <bcp14>MUST</bcp14> proceed as if the key were absent; if the key is mandatory, the record is incompatible (<xref target="mandatory"/>).</t>
          <t>ISD numbers 16-63 and AS numbers ffaa:0:0 to ffaa:ff:ffff are reserved for private use (Sections 1.5.1 and 1.5.2.2 of <xref target="I-D.dekater-scion-controlplane"/>). Operators <bcp14>SHOULD NOT</bcp14> publish addresses from these ranges in zones intended for use on the Internet.</t>
        </section>
        <section anchor="mandatory">
          <name>The "mandatory" Key</name>
          <t>When "scion" is listed in "mandatory", the record is compatible (Section 8 of <xref target="RFC9460"/>) for a client only if it implements the key, at least one listed address is usable (<xref target="unusable"/>), and the client has SCION connectivity; otherwise the client ignores the record. A path lookup or connection attempt that fails later does not make the record incompatible. <xref target="scion-only"/> gives guidance for operators.</t>
        </section>
      </section>
    </section>
    <section anchor="ops">
      <name>Operational Considerations</name>
      <section anchor="scion-only">
        <name>Endpoints Reachable Only over SCION</name>
        <t>For an endpoint reachable only over SCION, operators <bcp14>SHOULD</bcp14> list "scion" in "mandatory" and publish no A or AAAA records for its TargetName. For an endpoint also reachable over IP, operators <bcp14>SHOULD NOT</bcp14> list "scion" in "mandatory", because clients that do not implement the key would discard the record. In the following example, clients that can use SCION use the first record and other clients the second, over IP:</t>
        <sourcecode type="dns-rr"><![CDATA[
example.com.  3600 IN HTTPS 1 sc.example.com. (
                       mandatory=scion alpn=h3
                       scion=1-ff00:0:110_192.0.2.10 )
example.com.  3600 IN HTTPS 2 . alpn=h3,h2
example.com.  3600 IN A     198.51.100.1
example.com.  3600 IN AAAA  2001:db8::1
]]></sourcecode>
      </section>
      <section anchor="codepoint-used-before-assignment">
        <name>Codepoint Used Before Assignment</name>
        <t>Prototype implementations used the Private Use value 65280 for this key. Clients <bcp14>SHOULD NOT</bcp14> interpret 65280 as "scion" unless configured to do so.</t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>The security considerations of <xref target="RFC9460"/> apply. The security of the SCION control and data planes is specified in <xref target="I-D.dekater-scion-controlplane"/> and <xref target="I-D.dekater-scion-dataplane"/>.</t>
      <section anchor="endpoint-authentication">
        <name>Endpoint Authentication</name>
        <t>An attacker that can modify DNS answers can already redirect clients by changing A, AAAA, or SVCB data, and clients rely on endpoint authentication to detect such redirection (Section 12 of <xref target="RFC9460"/>). A forged "scion" value also lets the attacker choose the destination ISD and AS, and with them the paths available to the client. SCION path authorization validates the path, not that the host serves the requested name; it does not replace endpoint authentication (<xref target="semantics"/>).</t>
        <t>Because clients use the value directly rather than as a hint, no A or AAAA lookup can confirm it. The DNSSEC validation policy of Section 3.1 of <xref target="RFC9460"/> applies to it as to the rest of the record <xref target="RFC9364"/>.</t>
      </section>
      <section anchor="internal-targets">
        <name>Internal Targets</name>
        <t>A "scion" value can name any AS, including the client's own, and any host within it. This is the SCION form of the attack on local-network addresses described in Section 12 of <xref target="RFC9460"/>. Host addresses are interpreted only within their AS and are often private-use IP addresses, so a client cannot identify internal targets by host address alone. Clients that restrict connections to local-network IP addresses <bcp14>SHOULD</bcp14> apply the same policy to SCION addresses in their own AS and in private-use ISDs and ASes.</t>
      </section>
      <section anchor="removal-of-the-key">
        <name>Removal of the Key</name>
        <t>An attacker that removes the "scion" key or the record causes clients to connect over IP instead. DNSSEC detects modification of a signed record; blocking of the response is addressed by Section 3.1 of <xref target="RFC9460"/>. Whether a client treats missing SCION addresses as a failure is a local policy matter.</t>
      </section>
      <section anchor="resource-consumption">
        <name>Resource Consumption</name>
        <t>Each distinct destination ISD and AS a client uses can trigger path lookups, which load the client's control service and, for uncached paths, those of core ASes in the client's ISD and in the destination ISD. Clients <bcp14>SHOULD</bcp14> limit the number of distinct destination ASes for which they look up paths when connecting to a service.</t>
      </section>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>A path lookup reveals the destination ISD and AS to the client's SCION control service. Unless the answer is cached, that service may query core ASes in its own ISD, which learn the querying AS and the destination ISD, and core ASes in the destination ISD, which learn the destination AS and the querying AS (Section 4.1 of <xref target="I-D.dekater-scion-controlplane"/>). These parties can differ from the client's IP access provider.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>IANA is requested to add the following entry to the "DNS SVCB Service Parameter Keys (SvcParamKeys)" registry in the "DNS Service Bindings (SVCB)" registry group <xref target="RFC9460"/>:</t>
      <dl>
        <dt>Number:</dt>
        <dd>
          <t>TBD (13 suggested)</t>
        </dd>
        <dt>Name:</dt>
        <dd>
          <t>scion</t>
        </dd>
        <dt>Meaning:</dt>
        <dd>
          <t>SCION addresses</t>
        </dd>
        <dt>Change Controller:</dt>
        <dd>
          <t>Tony John (tony.john@ovgu.de)</t>
        </dd>
        <dt>Reference:</dt>
        <dd>
          <t>This document (<xref target="key"/>)</t>
        </dd>
      </dl>
      <t><xref target="presentation"/> and <xref target="wire"/> specify the presentation-to-wire conversion required by Section 14.3.1 of <xref target="RFC9460"/>; <xref target="test-vectors"/> provides test vectors.</t>
      <t>(RFC Editor: replace TBD with the assigned value throughout and remove this note.)</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>
        <reference anchor="RFC3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC4291">
          <front>
            <title>IP Version 6 Addressing Architecture</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <date month="February" year="2006"/>
            <abstract>
              <t>This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.</t>
              <t>This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4291"/>
          <seriesInfo name="DOI" value="10.17487/RFC4291"/>
        </reference>
        <reference anchor="RFC5234">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC5952">
          <front>
            <title>A Recommendation for IPv6 Address Text Representation</title>
            <author fullname="S. Kawamura" initials="S." surname="Kawamura"/>
            <author fullname="M. Kawashima" initials="M." surname="Kawashima"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5952"/>
          <seriesInfo name="DOI" value="10.17487/RFC5952"/>
        </reference>
        <reference anchor="RFC9460">
          <front>
            <title>Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)</title>
            <author fullname="B. Schwartz" initials="B." surname="Schwartz"/>
            <author fullname="M. Bishop" initials="M." surname="Bishop"/>
            <author fullname="E. Nygren" initials="E." surname="Nygren"/>
            <date month="November" year="2023"/>
            <abstract>
              <t>This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9460"/>
          <seriesInfo name="DOI" value="10.17487/RFC9460"/>
        </reference>
        <reference anchor="I-D.dekater-scion-dataplane">
          <front>
            <title>SCION Data Plane</title>
            <author fullname="Corine de Kater" initials="C." surname="de Kater">
              <organization>Independent</organization>
            </author>
            <author fullname="Nicola Rustignoli" initials="N." surname="Rustignoli">
              <organization>SCION Association</organization>
            </author>
            <author fullname="Jean-Christophe Hugly" initials="J." surname="Hugly">
              <organization>Independent</organization>
            </author>
            <author fullname="Samuel Hitz" initials="S." surname="Hitz">
              <organization>Anapaya Systems</organization>
            </author>
            <date day="24" month="June" year="2026"/>
            <abstract>
              <t>   This document describes the Data Plane of SCION (Scalability,
   Control, and Isolation On Next-generation networks), a path-aware,
   inter-domain network architecture.

   Unlike IP-based forwarding, SCION embeds inter-domain forwarding
   directives in the packet header, enabling endpoints to construct and
   select end-to-end paths from segments discovered by the Control
   Plane.  The role of the Data Plane is to combine such segments into
   end-to-end paths, and to forward data according to the specified
   path.

   This document describes the SCION packet format, header structure,
   and extension headers.  It also describes the cryptographic
   mechanisms used for path authorization, processing at routers
   including a life of a packet example.

   This document contains new approaches to secure path aware
   networking.  It is not an Internet Standard, has not received any
   formal review of the IETF, nor was the work developed through the
   rough consensus process.  The approaches offered in this work are
   offered to the community for its consideration in the further
   evolution of the Internet.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-dekater-scion-dataplane-15"/>
        </reference>
        <reference anchor="I-D.dekater-scion-controlplane">
          <front>
            <title>SCION Control Plane</title>
            <author fullname="Corine de Kater" initials="C." surname="de Kater">
              <organization>SCION Association</organization>
            </author>
            <author fullname="Nicola Rustignoli" initials="N." surname="Rustignoli">
              <organization>SCION Association</organization>
            </author>
            <author fullname="Samuel Hitz" initials="S." surname="Hitz">
              <organization>Anapaya Systems</organization>
            </author>
            <date day="30" month="April" year="2026"/>
            <abstract>
              <t>   This document describes the Control Plane of the path-aware, inter-
   domain network architecture SCION (Scalability, Control, and
   Isolation On Next-generation networks).  A fundamental characteristic
   of SCION is that it gives path control to SCION-capable endpoints
   that can choose between multiple path options, thereby enabling the
   optimization of network paths.  The SCION Control Plane is
   responsible for discovering these paths and making them available to
   the endpoints.

   The SCION Control Plane creates and securely disseminates path
   segments between SCION Autonomous Systems (AS) which can then be
   combined into forwarding paths to transmit packets in the data plane.
   This document describes mechanisms of path exploration through
   beaconing and path registration.  In addition, it describes how
   Endpoints construct end-to-end paths by combining path segments
   obtained through a path lookup process.

   This document contains new approaches to secure path aware
   networking.  It is not an Internet Standard, has not received any
   formal review of the IETF, nor was the work developed through the
   rough consensus process.  The approaches in this work are offered to
   the community for its consideration in the further evolution of the
   Internet.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-dekater-scion-controlplane-18"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
        <reference anchor="RFC9217">
          <front>
            <title>Current Open Questions in Path-Aware Networking</title>
            <author fullname="B. Trammell" initials="B." surname="Trammell"/>
            <date month="March" year="2022"/>
            <abstract>
              <t>In contrast to the present Internet architecture, a path-aware internetworking architecture has two important properties: it exposes the properties of available Internet paths to endpoints, and it provides for endpoints and applications to use these properties to select paths through the Internet for their traffic. While this property of "path awareness" already exists in many Internet-connected networks within single domains and via administrative interfaces to the network layer, a fully path-aware internetwork expands these concepts across layers and across the Internet.</t>
              <t>This document poses questions in path-aware networking, open as of 2021, that must be answered in the design, development, and deployment of path-aware internetworks. It was originally written to frame discussions in the Path Aware Networking Research Group (PANRG), and has been published to snapshot current thinking in this space.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9217"/>
          <seriesInfo name="DOI" value="10.17487/RFC9217"/>
        </reference>
        <reference anchor="RFC9364">
          <front>
            <title>DNS Security Extensions (DNSSEC)</title>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="February" year="2023"/>
            <abstract>
              <t>This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of those RFCs. A second purpose is to state that using DNSSEC for origin authentication of DNS data is the best current practice. A third purpose is to provide a single reference for other documents that want to refer to DNSSEC.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="237"/>
          <seriesInfo name="RFC" value="9364"/>
          <seriesInfo name="DOI" value="10.17487/RFC9364"/>
        </reference>
        <reference anchor="RFC9848">
          <front>
            <title>Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings</title>
            <author fullname="B. Schwartz" initials="B." surname="Schwartz"/>
            <author fullname="M. Bishop" initials="M." surname="Bishop"/>
            <author fullname="E. Nygren" initials="E." surname="Nygren"/>
            <date month="March" year="2026"/>
            <abstract>
              <t>To use TLS Encrypted ClientHello (ECH), the client needs to learn the ECH configuration for a server before it attempts a connection to the server. This specification provides a mechanism for conveying the ECH configuration information via DNS, using a SVCB or HTTPS resource record (RR).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9848"/>
          <seriesInfo name="DOI" value="10.17487/RFC9848"/>
        </reference>
        <reference anchor="RFC5398">
          <front>
            <title>Autonomous System (AS) Number Reservation for Documentation Use</title>
            <author fullname="G. Huston" initials="G." surname="Huston"/>
            <date month="December" year="2008"/>
            <abstract>
              <t>To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, two blocks of Autonomous System numbers (ASNs) are reserved for use in examples in RFCs, books, documentation, and the like. This document describes the reservation of two blocks of ASNs as reserved numbers for use in documentation. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5398"/>
          <seriesInfo name="DOI" value="10.17487/RFC5398"/>
        </reference>
        <reference anchor="I-D.meynell-panrg-scion-research-questions">
          <front>
            <title>SCION Research Questions</title>
            <author fullname="Kevin Meynell" initials="K." surname="Meynell">
              <organization>SCION Association</organization>
            </author>
            <author fullname="Juan A. García Pardo Giménez de los Galanes" initials="J. A." surname="de los Galanes">
              <organization>ETH Zürich</organization>
            </author>
            <author fullname="Tilmann Zäschke" initials="T." surname="Zäschke">
              <organization>ETH Zürich</organization>
            </author>
            <author fullname="Nicola Rustignoli" initials="N." surname="Rustignoli">
              <organization>SCION Association</organization>
            </author>
            <date day="24" month="July" year="2024"/>
            <abstract>
              <t>   This draft intends to summarize all SCION related questions which are
   deemed important to be answered for SCION to properly work at
   Internet scale.  The set of questions is at the moment not
   comprehensive, but we intend them to initiate a discussion to
   determine which questions should remain here, and which ones are
   missing.

   When appropriate, some example solutions can be provided for the
   community to determine whether said solutions are adequate or not.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-meynell-panrg-scion-research-questions-01"/>
        </reference>
        <reference anchor="DNS-SCION-SVCB" target="https://github.com/netsys-lab/dns-scion-svcb/tree/69d4ec790b666da7ede7cbd088fdd059ad7b4d7e">
          <front>
            <title>dns-scion-svcb: miekg/dns with the scion SvcParamKey</title>
            <author>
              <organization>netsys-lab</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 291?>

<section anchor="examples">
      <name>Examples</name>
      <t>The examples use ISD and AS numbers reserved for documentation (ISDs 1-15 and AS numbers ff00:0:0 to ff00:0:ffff, Sections 1.5.1 and 1.5.2.2 of <xref target="I-D.dekater-scion-controlplane"/>). SCION has no documentation AS numbers below 2^32, so the test vectors also use AS 64496, a value reserved for documentation as a BGP AS number <xref target="RFC5398"/>, and values around 2^32 to show the decimal AS form and canonical rendering.</t>
      <t>An HTTPS service reachable over IPv4, IPv6, and SCION:</t>
      <sourcecode type="dns-rr"><![CDATA[
$ORIGIN example.com.
web  3600 IN A      192.0.2.80
web  3600 IN AAAA   2001:db8::80
web  3600 IN HTTPS  1 . alpn=h3,h2 scion=1-ff00:0:110_192.0.2.81
]]></sourcecode>
    </section>
    <section anchor="test-vectors">
      <name>Test Vectors</name>
      <section anchor="wire-vectors">
        <name>Wire Format</name>
        <t>Each vector gives a presentation value and the SvcParamValue in hexadecimal, one 24-octet block per line, split into ISD, AS, and host. Whitespace is for readability only.</t>
        <artwork><![CDATA[
1. 1-ff00:0:110_192.0.2.1
   0001 ff0000000110 00000000000000000000ffffc0000201

2. 1-ff00:0:110_2001:db8::1
   0001 ff0000000110 20010db8000000000000000000000001

3. 15-64496_198.51.100.7
   000f 00000000fbf0 00000000000000000000ffffc6336407

4. 1-ff00:0:110_192.0.2.1,2-ff00:0:220_2001:db8:220::7
   0001 ff0000000110 00000000000000000000ffffc0000201
   0002 ff0000000220 20010db8022000000000000000000007
]]></artwork>
      </section>
      <section anchor="rendering-vectors">
        <name>Canonical Rendering</name>
        <t>Each line gives a presentation value and the canonical rendering of its wire value (<xref target="rendering"/>).</t>
        <artwork><![CDATA[
1-FF00:0000:0110_2001:DB8:0:0::1  ->  1-ff00:0:110_2001:db8::1
01-0:0:fbf0_::ffff:192.0.2.1      ->  1-64496_192.0.2.1
1-0:ffff:ffff_192.0.2.1           ->  1-4294967295_192.0.2.1
1-1:0:0_192.0.2.1                 ->  1-1:0:0_192.0.2.1
1-ff00:0:110_::c000:201           ->  1-ff00:0:110_::c000:201
]]></artwork>
      </section>
      <section anchor="invalid-vectors">
        <name>Invalid and Unusable Values</name>
        <t>Zone-file implementations <bcp14>SHOULD</bcp14> reject a value with an unusable address; clients ignore the address (<xref target="presentation"/>, <xref target="unusable"/>).</t>
        <artwork><![CDATA[
Presentation: 1-ff00:0:110,192.0.2.1
Result:       invalid: "," separates list items

Presentation: 1-ff00:0:110\_192.0.2.1
Result:       invalid: escape sequence

Presentation: 1-4294967296_192.0.2.1
Result:       invalid: decimal AS number not below 2^32

Presentation: 70000-ff00:0:110_192.0.2.1
Result:       invalid: ISD number above 65535

Presentation: 1-ff00:0:01100_192.0.2.1
Result:       invalid: hexadecimal group longer than 4 digits

Presentation: scion (no value)
Result:       invalid: empty value

Presentation: 0-ff00:0:110_192.0.2.1
Result:       unusable: wildcard ISD number

Presentation: 1-0_192.0.2.1
Result:       unusable: wildcard AS number

Presentation: 1-ffff:ffff:ffff_192.0.2.1
Result:       unusable: reserved AS number

Presentation: 1-ff00:0:110_::
Result:       unusable: unspecified host address

Wire:         SvcParamValue of 0, 23, or 25 octets
Result:       malformed: the RRset is rejected
]]></artwork>
      </section>
    </section>
    <section anchor="design-rationale">
      <name>Design Rationale</name>
      <dl>
        <dt>SvcParamKey rather than a new RR type:</dt>
        <dd>
          <t>A new RR type would need an additional query and support in DNS software before deployment. A SvcParamKey needs only registration and is ignored by software that does not implement it.</t>
        </dd>
        <dt>Fixed-length binary encoding:</dt>
        <dd>
          <t>Carrying every host address in 16 octets costs 12 octets per IPv4 host address, in exchange for exactly one encoding per address and comparison octet by octet, as with "ipv4hint" and "ipv6hint".</t>
        </dd>
      </dl>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>(RFC Editor: please remove this section, and the references cited only in it, before publication.)</t>
      <t>Implementation status as of November 2026 (<xref target="RFC7942"/>):</t>
      <dl>
        <dt>dns-scion-svcb <xref target="DNS-SCION-SVCB"/>:</dt>
        <dd>
          <t>A fork of the miekg/dns Go library that parses, serializes, and presents the key using the Private Use value 65280, deployed in a CoreDNS instance on a SCION testbed. It differs from this document in that it fails the whole DNS message on a malformed value. License: BSD-3-Clause. Contact: Tony John.</t>
        </dd>
      </dl>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The idea of a SCION SvcParamKey was first raised in <xref target="I-D.meynell-panrg-scion-research-questions"/>. The authors thank the participants of the SCION research meetings and of the SCION Association Technical Committee for their feedback.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8U863baSJr/9RQ1ZM9pexYIYHzDk5kmdtJxb+J4jdNz2Uun
kApQW0isSpjQGc+z7I99kt0X2+9SVSoJcJzu2bPuc9Ig1eWr734rWq1WUMRF
ogaicb0cJ7GexelUjM4v31+JV2m0yOK0EMMoypXWSos4FRdXIzFS+X0cKvEy
TiMcvzf64fzlvrhRYZZHuhHI8ThX97AmLzS6D69lLuf/pNaNIJSFmmb5egCL
TbIgysJUzmH/KJeTovVTNktbOowz+Pc+HLc6nUAvx/NYa3hUrBcKp0VqoeCf
tAjS5Xys8kEQwaKDAHY8CO7UegVQDAIhWgLhog9vbm+vR+Lmhp8iVPRpIYtZ
S65krkSqCph3B8cJ7lW6VLjANC5myzGcA17qtW4lcvyc4SxBhNMui1mW84aT
ZZLweW6zdC2+h+PAcwFAx0UsEw3P2/RAL3Me54Zk+VSm8c+ygJUH4v0P330Q
7+Q0UuNlPqUBai7jZCAKWLiNePo2u58u25Gqbfy9Sgol7mUqXmbzuUpq+39f
2782sArFq9s34i/LPA5nPgQ/4Q5tmDimed8CIduqmP3cpmEVJMTJXKap+Mv/
/JcOZ3eKVpGAvPj15hipyjG78bW51Mi98ld4ykEK3rr9s5n4yEneyly3zmd5
rAGuVIzC2TL5uQbq2xqo3qCnEjfRNGcHaa/iMEukuFkCENM0S+IaAFc1AGoD
q0CwbA61zsKYHvlwpHH4LfF4GyYFQZrlcxhzT1Jx8/q81+2emo8n3eO++Xhw
enJkPvZ7p13z8bB3YAccnh72zMfT/lEHP162LuCcdyC/uREqkGW5SGSqtr8O
QQ/kWWJGBKhEqrAdn/bdJr3usf14cGShOD3pn1iAAGS7zVytU5UkrYVM86nZ
DNSeknk4a/3HUmnEkcbRoAJbhL0W6pcB4c1q0SjVnnIYiHms7qbP4alYgTIR
xUwJel1VirSCzKeqGIhZUSz04PlzVj7tMJs/99VPZf3nRa7U86PTqK/C49PO
+OjoKJLHKlLH4TjqnJxMoqhzeCqj43E/OjYi47QV/rWQKQai3ICekzoVvU7v
KAiCVqsl5FgXuQyLILidxVqA0l7OQf+KSE3iFOxCg0BqNIV0toEOp4BuAk4I
FqI87r4AkhEmdtgRmUZGYaOxARpkyxxG5Wxe2uKy0KC2kqUSYLDgMy4lnY2S
hVjNQNABFm3WV9aSAey5kuFMjhMlsnsAjqVgbxRKOHycxMW6Kc6ZxZoEyKUG
kUPSi/epuFKfitZUpSrnR8Zo6H08uWdMYC9g2CgDYXKDBDJSXKiwWOaqLaqI
1AsVxpNY8WFWMazBfN0UC2TCtOAN7UOETIOspkUcapFNaBqYPnqRK2JXMNcF
nncaI/FoOvHg5fBq2Ga6zuMoSlQQPBOXeORoGZIiCP5OWBGfPz8uwA8PW4c4
FQDvAUtfh1pY0Yj+w0NbDA2FfRaI0XdAbEdivEaWpRGGg5qGewBMTdwFyAWF
Xx74grfeuxxd7At2QJpukeESzHM2z5ZajNa6UHOxNxx5wwB1UswyXdjtgBBX
GR8qWwACkTFXci3UJ2btTCzYL6tCyb4YEh1EpC3Ol3nO8rhIsjVylBZLrcTt
n26t2FgmQQ4y8voCjtAajpoITwOorYj64qB9gIOZME/Tig8P+w5vYFCzQoxB
JI1pATQ73bfIsyIDIwZoXmQ5MPKrNMzXCxxznsQA9xvYLBN7r87f7CMJJvF0
abiKyQq6++GBEbnI4ywH1oSFQeZRdXiaw56aZ4GxAVYKZZ6vSfkAQS1DtHfp
NATX6DVfWdtzlqqnThiDaAlOEthhtEwl9yEzWbX3LousUmujCIKA3SNjAj7p
IBcISEzfEUaW7xWdqvHuw+gW1C39X1y9p883r/75w+XNqwv8PHozfPvWfQjM
iNGb9x/eXpSfypnn79+9e3V1wZPhqag8Chrvhn9uMNYb769v4bzDtw3mQB91
KJ/AsWMjpaC5kLBSBxH4V3k8hi8w5+X59X//Z7cPpPmNcSVIDfzGOBPwZTVT
Ke+WpcnafAWcrgO5WADr4SoySYCgi7iQyExSCz3LVqmYKVCuQfDbf0HM/NtA
/G4cLrr935sHeODKQ4uzykPC2eaTjcmMxC2PtmzjsFl5XsN0Fd7hnyvfLd69
h7/7QwKsKlrdkz/8Pqjz8VIbJp5kIFIrtK9Akzl4MAHIvbCh0wBUZPeoNY4L
88iqxzXOsHptU/1ZbdFtH7a7pb54TNfvt61lGY4q+/dPvrT/Dr1agaL3VChE
DQhNjBuha5+GhZjk2Vy8/O7aG9BEaZ5ly+lM6Gyu3AIK7SsqWsBznFcnIU/y
49p24MDUBAdkbjhqsHi5YfA9AUuAO0xgNZArWa7EhqS+cBC88UwL4va2dI2M
IXOqCHUyEBJ9BLtOsyK3LHs8ilTscHTmKTzjsoSSNVaIAglExAFuD2vkzBRU
wOjjXF7f98Vev5WFhSrAcsD3I7EHXGgfkOjDSnnFVgpMAOiS6L12dzfRPR9i
/6ymp0J0/QwY5M3g/v5OqMXh9I5faxgFn3wcpywPxj1wEtXcpMs2u19h3aeL
zzPaf4tZEp+fgXl4gBHPxB/RfXxNniI8RmfygQ2IHf8DOc/kWWn0FVPwkQGE
DHQJGMd5BtN7hjpinGThHQgAus1wgoQcdRxZw0zwt7/9jePxlsyLQHTE5l93
y7PelmcHOL0Lrw5EXxyKI3EsTsTp1zwL/rH1K/8L/lrCU1LXA/KvG2BX//76
ZRi+sEIFhupfjcN+BQxfg4df9Acw/MoV/m9h8FXm/xcMT/v7u8Dwq/kB5Dz4
POCEx4vG+7omYIXReKh7GaCoUZ9otDEubhuvC1Q5EdmuLa7B0Rcn1Q1e106B
0C/dVOyo9NgKoV8K3+yw/mPDJA9pzdH9NOZiQ4/3wAVxTohJgbHSHtYU7wq2
UiJR6RSiItjpZ4j9UPFi3CTFfJkU8SIhjdzrm9OA7QKbhANm8l6xkf0EBhjt
tM0J6Iye39zgmnOZ4HOEn2xPSNEV2/F4DstzkEh2EeMK8o5z9RMsaUx4gVbk
5kaDDfDOWJ6Pg6p9DLE5GUOWcG3sdnm6FYaPDAtYEYhwRDxBRwGNG3iSEKim
S01xb2l89z5/tk+N3Xsmrv08iLNufnbEWLlKwuS+NHVgteeypdUCKIF4wwgO
3MgFFhPiT2Jo3djybHWjWIv02uI2A0QR7JqQmgtYXIOFbDJmq3S3EYg9uoCo
SC6Us8Gw4Cu0sjH6t3C8cGY8+I/sDpiNP4p8yexR9e6HL69eM/iYcsXkx8eL
y+8ubz8SC3x88+pP8PUj+7oU41I05s7/0js/L3AmPiLbu21pGWT+8kl1rTKD
4DMKpoUBGuMhjNNJUDmOeAHkAce31UBRa/zYIEkM8Fn590J0f3tIp6kqtDPY
PoyB2Zui0zo6PDw4DGRFi7+ARVswRjzHDzP1KTDfvYW7nc2VKwuDKPdPj457
p7g6LuLP7jNiRWPQ2PUtIN3iweShFQDzUEralbkYvCiIpCfId5SKAMTEJivB
eZsGxHOfChDaCsMbtvBcFiRb3V+oBE4HTw6cELCPQBnDC4zKjyxkJopirJ2B
ApDkKqJyQ/VFyiucyXTK56E5ZkVG6kfOTU3je+UnVmoBVa6UjVenebZc6O2m
oXbCrwgOt9qDEEzAGDR3HhcFajAzhgDea3RPe+0O8Hy3sY+6It5iLszIwWAC
fwNvwpkYg8bExFi0DBk1Ws5NDhi0QoZYJCPik7nFSp/UDRzW197S6rzU5sFB
KZNKcTaEdEtdqzTBtOhqLAPSCpGSILlq4snMiCrhyVD9+0HPqsm2+AsozdYk
BiXlTI2JEk1+RCZgrGrwkmlyRgF2qduFTavADFJkWaKJNKqezCWN4mc563l3
SpKQaKUCWCB0arXRbLBBBaAMe6cKiJlmrLWZKM/ALp3LNEshDE7EDValc2T6
z89y+xmM0h9nwDIhZvfygpMaSFxLQnP6bFeiv4ZDS2tcnoOyjROzScCY7Ld1
XQDHNBJKkX22LGqCWhObp2Z2zuxedZn94obsDABNxgqAJkby4v9VrJXNdFfV
BKWUYYbKQwlj4IW0G0XxNEafEWhV3cskMyRrDpPP7DQ4JcxuGL35pcqDsFBz
FqtuJWAjAw0StSysTo2YJIFzoOrzXO4eQLHQ9UuDfXrYw7y4xTGOnsefiGFL
w2DnHdbmoXrZIm9ULUM+I2fpTpXQkbMJGNsh5yw2hg1ho4qT9mAEn3W82wBt
GWsOUeQy1RPM0HDG3iuHMZKwXQN95cmEPGB0QYFs8KbI4wXaCMrU+dMIgtwa
Fha5MeAJl0kVuF5a5nGyprdkVUHXOBFu3cM2Wa7ZBK6yjYy/zD3F7bA3Mem/
iibnweDwyYTd2pGr4n1+5ip6xpPdlucBrkqoTpjVKh2IGXhIdRCv5oM0s1UX
gTxJ3ukyTSihhnQyD70aZCl6ThCON/z+siaB1Vts6zHr7Sx+YFMCldyY8Aji
N1rcUt37ClG3qzwLi5KmQ48dIxqbVUQAqs+Uw28MRAaeOzNEYKfAJiBT0rbA
Yuh2s+RFS8Arn4JCLFT0xF9tU5lyxmsRh3fefoDzJSspKYBxo2zOmzVZFeei
ES/u+6B3CpPhha9H9BVQ+CElwdo5pOnxa6xNhIhvBiai4zpfsQ0REfBdWCTr
us1zbgATfA2qZuVWM3jK0tQQXoK6mi+4FFnn+1wlTGJ4d3ntBUbMG6zILPO6
whhTnhh5jTPLzWgT7ywbckbiuy6nwqZbZrvSHiba0Y+Ow2Uic7KHDSw7Njwn
k5QNPqSCpDD8yztXCrXi0loqOdaUtKeCJk5C7GKrw5wCIUN2gK2Uni1xM0Ej
k0VqaJ5mYBQmEqL/Fj91SzJEKNfDt9dXAiNy3GDLyesIA6OIHOCB5E/ywNsI
fVGnOrVBYp0vYQoJ5e35NTtO8OE5bWmLdao+9MOFGQofntuuAvqfW9zWYI5o
je5xswxJh09J7iOkfnbDFKCtWGAzREwGxhHa0yxOFuzwOga5VYUsCMPLdFPh
rOGr4tu3I1AbaaRn8k5pbwfy3A145Llh/w0mV1DVsNFAu5RzZdiTO6/e47l2
wICrbJlEvMPlddNrK0INahZLyRABOkN0OSe8GWiROCIbzPZ+p5cSKcAIipst
/tXDoabrsPFPhijE+EDY0sE2F8YIFrhlGKP5hR3RadqsUedMfHWNBwM36zux
viyPYStLW/KBu0A4MNGutdsIfM7RuGEw9WlBE7cVj4hjjFcw1yq5N0Uvg+4N
psCkkOXACnjcL1DnAnIx/TE1reepYsx6KS5pDokjhvBX+gc5v3rMRGGM88G6
hmUr8OdnLhajDGcFxtjL6pGDrytBiBYdipPhsRcp4NO9VZxEYKUj4LGR1VNc
YibtgBnWJwclTbt3ZRMKwN0/Ys94hpHb0OzyVKefAmOzUT2HDHrQOFWR2Ou0
6T8cPhhQooBSvRC+gLvZ6/X59fM+LTiZdDqDwfMTsUBN4oTheEt6+T32DaF/
WvKS7RnaTK162pJGY3so8OmWHCzi+93wz44vSbScHJv0DdhEcJTsiXPsHk01
W0Z/F1CeoTIp97JXDWI3ZYzpmf+c0tdphGdaN32XAXu3QB7nC9BiCCw46W4g
46LkMo1Sf3TAPF9W+icTKQedQQf1K322fIDSalmBtP4iBxcS1ObSc4M3efHp
eaWSTGWTiCOUZ3BQHuHMsGuOyTLCOAZamorzEJIweAhWxrS4xKJ9qgojrBQ5
OLw0BFeHS0SZhIQNLgCpxt2Cjbx5dcz7eLcMebKRMedQ2tCeOghMgO/XHIjM
TfS1ID7XBTkOVfeVhIc5spr1YU/D4y9MSZnuAmM87+NifebFMN5g5nbtnYz8
HEmphOwOIv9sm/Nr4lkZJ4ArpLGfSrtTFUR5/NkG1DAzICIg8GWvc7oEM4wl
d8RVZrmCivvMIzBDJtgOpuPIfEd9my001/ftxQwtbly09B5R7Tk2EEyWOwfB
62rTmx9mVSc2S4gsn1KdxHFLhUe4D8/wMCiCIeKvYmEmRs+XUV5b1IEx2cBK
4IeuzQYkKDGPQNMUYxVKFAwbzRDdTO7ZcWCpf8iTimKNBqfCE5c232JrK+BI
4/RmdWXMCuN2jHKrKCdxrgsX5bhOlnImumnAZGBxzFFN9wT2dud5YPbCzu+2
EAdHnY64vDLBflfosF0ZsBfsqPU6vLzghnMMKl7MDnYN547QbosMT2fQ7XZ+
dFnqjth/FKqeaNvlm7PejqFD2qZ7etI+7MKSnXZ310DkH9HrdLqDaHwyGHS5
KIKp1ixSzDIfNOiKl+yPDbUGuUbKBsE1eunkytUzz0ucgbi/NnodljCO4tFh
76RjPH0uh27E/Mh5rjfKTJCu792mU2zDqqJMDPCdzkisQV0uqVN1Q6a1eWMS
PvYrdx+XA6taluNf9k/dDOMFOlWIxocTG+AkCzJDpFVLhyROn9KfjUt8wfdu
V7QS9urZCIeayYekR2V4p/JSbObgVU/W1OAPYdmKk33IpKAHojVID2cvnNSM
11w8okJnk3iE/CQKixEWNgx2eK5Qq/k6pgIUkUdhw7jQSwhk7Hb4qsz9bq11
A5tMAXmW8sxBpMESZe8i2NOGsywzSiHCTmnTMoZOCrslDLQN4eacUQBrBN7X
PVgbUocmtOeT2U46Mll8lcNc6LHhnbFuOKBJes/l5Mg59bKg5poA5ohBLZ+h
lXZmLVdcDdmFPzDKZbKSPK+XNdVrtaGJxUwuCnwaUoYAVMrBIoYZzartMKYY
+YEkKp8DbMzuwC+jV+deKCsWWRKHaz+7fbCRzfAjdTildPkS8AWKWlqKpx0c
9S1fs3cFBplNmMZop0p9BNRE3GvTRRkmSxs1Gox8A1K8SsssP1HD9WCaHF3s
Fz5ttr9kKeToJAtl0nIXH8psn99ivZOF25V2J5Mt3d30iZlT222aY20Mi5/G
MW4hhf1Q0xQFjKtlomTbzMubIBr5nhNJdCVckgm4gaXi5UQS0CePw6Ke66oi
oRLv2gojpwhtXsRwyZYcpjsndo+bs8a1Q44utBFYym0CU9yoeQbEt+QBF3uL
nstxUO0mAfod5vaTYTgSG126By4har0DAAekVIJbYrifNZdmHWolkjIFaAhV
ZFY+41Ys6te0LK4XgEHuhzEYoIT8btFpCwgWSGTLHiJQ0bg7Xsp1l4UrSVpJ
vjLexaHGG6KWJcEcfercYtFc7UK7uARHm+wF9cC4buztirOEhpEHEgiMMp1S
B47z5l2iKslkVJVFayHtFTGJ7hjFVWkI+wNaSA9jEIQqHJASkq8xKm/euLUs
WOZ5DeINXyKJ56ZP2iQlYPGtx6XNECY+BKW+8WAClCNbiZWpLJNsoLrJyltv
5HmQsxPWHQ/qJvCCnlzdKzBhjxiqqhX6Rtf8DLul+GDrSsqYde6kQ4Q2WSgs
wudyLcD+5OsqYjFWQEmErR3xlMwZszSePICRCwNr8Bo3oE6rjVH1pat4d6v7
OzrHoP/0Cw9otDQ388SGT0FmsZ/fxvkeG4EaC7EUiemS+5j7G5/Rdb1NxzGW
qcQeS3xJZTNrywtKx9TDF4BqbWnYoCv86DdtvaupK5c19X7DXiFcW2Q2tvwG
gDaXN73RXEr3dAmEOVeutfP25YXY6x6A/wVSi5Dvw1u8tQzvCJdB8E7JFJbG
JzUlEwTn3ElkLiUmZk17517sbdySh+VvbMWP+/j9mhj4M9g+/wCjNsrV7AFT
G/2Dq5kVtUbDVpG1qNDLfR74cwVl6cHTsN1+e1PJnsEXcNyKstBsWQBECV0U
8xz4YQ8miVdRDF8HzktDXLo6gNTGCti2GqqGY1MA3w1Fm8SBDqbH2/t8E3QM
dgu57RWHZMhiJjqzxWj7VRiTWM+sVZJnFrHGWyQL2m11DzfTcRRtmnQcfcZs
3CPJ36+95YP5oTSrAeRB4LedmA5aH+Xs2uORYc5Rv3961HQdS4+cmIxg9ToQ
91scnLr7i65rjloXqIMKsIDX2IxG4g4RWIE8QdJrrtfINSdwLYfjcKtbN3Ip
932+ZNMsmwGrOYd/eH9z+R3E3n5EHqzUuB6+C5sTOOnUXlPQ7kXt9QEMoehW
UgWPZR1ObNwvbpEePxh6fH5WkZQdF1689+RO8FeTgJPbWoStxq/dkUn9zqIm
ZSqrV2MoQY/X8IB9IMgo0NHN2MbY+A7dXPSjYoB8gfIas1nHUNdcr7bXjfDE
3bbYnobB1E0HEEySQn/wWnS2/KEMhfih1+kGQa+2oJ9a2bokDujAgG1L45Ag
OIAlD1skDz96KZ1js97EQTUZTx4B8egAAq3OcRD0d5252bOPez0PcvgyGBz/
QoTwrF45C1Yrzwxftvwdl0mox/v96pxHNzSfwHdbRBs1HfpDZFd4tN+WxHE3
cUzr9WvEUQf/cRS+eHmCqhWoLETr92I3D3S6LVK8QKof6w2qLPU83ZLbsiNO
c4W0H2tTvHll+3Rlcheh2zrNn1wbFVROMRggUQdA1I15W0c5Il6mlEIg7Lvi
5g+skMG54rceKb/Y0VprZiVrvKWH9czFeabwVswq/a1V16Mp6h2vCL9/EWJQ
OWmzRBOEVsukGBiUmAMNuK3V3IDgug+1BuvgkVX/9ccvLlu7yLC5mmOBoy8v
5hk+Yzr5BwWsna6vfox8v11h7thhe4fzThygSD1hVb8FlX3fJEunNtnVN22p
9V04Ob8HLgpxzv5OFEN4vOYx9SWedHjLRwNhS+weGjaP/lULOUptQ6FfbX/C
os6penRRT7Z3ruQX3/1MUxCgv2DHi5rFB53baYreAWWXe4fm/lVtE3e7akAC
zLekKAz7iTpSredyodAXFzempgeU81s5K7lQkaoV3t2iHzmjW/HeA1Oqog50
HBxFsakScghNPwezXHAzGv9Gm84mBf1girlDUv40CP0oigcGrsr3nas/FkMp
DauoKIhxa5q6mkkWl5W1GGvQr7HvuGX6aPCeNABo22jwZOfY1EtR6T3CXu8S
cjf4IJTCn9jo2puD5Glt6UXCi1SfzM0SdKts0xv6aq59B+e6TCNlCOagBWON
mTN25tb8gdo2SX0/2hQjLqsdzyP4/5JsR+V5S9Pzh1rgtsC6t6oEY5oDnrK+
7fpTARGxS81SiqRpiUqlV04AYiBXg4n3xvMAU1/BTqTx8Ged0NSYn8oCuwKh
QPVnpcDsVH/jCmP3ARc/7mwysfxlq+8ysCTjHOnMrXJ4KQXTweCmgPL6GT/z
D7aQGLsOAAirbI58R1GuadiWs9oSwv1cIXNjRpRK6MimJtDDsGCMzeCXhcmx
uGYKP9K3P2YQ24I+br+aZQkVF8QcW8GnZuHyEqVpd3kL0VWqQXe8HF20Dlrn
CeZu25SFAJ7zEhDEIsPwLs1WiYqm1PgQfB6wQlPRi8YE4krVMKE1BPrSb/Xy
pXOFvZtcUZax9st2T/1pHq6ccLGI8urpnSkRYWdsDNMLXS0f2lUAG6rgpnUs
Y/tDvN+Ng/gsnLHrep7N53hDStmf+IpzMQH1gtmFdvC/2uHSr25SAAA=

-->

</rfc>
