<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.4 (Ruby 2.6.10) --><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-httpbis-alias-proxy-status-07" submissionType="IETF" number="9532" updates="" obsoletes="" xml:lang="en" category="std" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.18.2 --> <front> <titleabbrev="DNSabbrev="Next-Hop AliasesProxy-Status">HTTPProxy-Status Parameter">HTTP Proxy-Status Parameter for Next-Hop Aliases</title> <seriesInfoname="Internet-Draft" value="draft-ietf-httpbis-alias-proxy-status-07"/>name="RFC" value="9532"/> <author initials="T." surname="Pauly" fullname="Tommy Pauly"> <organization>Apple, Inc.</organization> <address> <email>tpauly@apple.com</email> </address> </author><date/><date month="January" year="2024"/> <area>Applications and Real-Time</area> <workgroup>HTTP</workgroup> <keyword>proxy status</keyword><abstract> <?line 43?> <t>This<abstract><t>This document defines the <tt>next-hop-aliases</tt> HTTP Proxy-Status Parameter. This parameter carries the list of aliases and canonical names an intermediary received during DNS resolution as part of establishing a connection to the next hop.</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-ietf-httpbis-alias-proxy-status/"/>. </t> <t> Discussion of this document takes place on the HTTP Working Group mailing list (<eref target="mailto:ietf-http-wg@w3.org"/>), which is archived at <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>. Working Group information can be found at <eref target="https://httpwg.org/"/>. </t> <t>Source for this draft and an issue tracker can be found at <eref target="https://github.com/httpwg/http-extensions/labels/alias-proxy-status"/>.</t> </note></front> <middle><?line 49?><section anchor="introduction"> <name>Introduction</name> <t>The Proxy-Status HTTP response field <xreftarget="PROXY-STATUS"/>target="RFC9209"/> allows intermediaries to convey information about how they handled the request in HTTP responses sent to clients. It defines a set of parameters that provide information, such as the name of the next hop.</t> <t><xreftarget="PROXY-STATUS"/>target="RFC9209"/> defines a <tt>next-hop</tt> parameter, which can contain a hostname, IP address, or alias of the next hop. This parameter can contain only one such item, so it cannot be used to communicate a chain of aliases encountered during DNS resolution when connecting to the next hop.</t> <t>Knowing the full chain of names that were used during DNS resolution via CNAME records <xreftarget="DNS"/>target="RFC1034"/> is particularly useful for clients of forward proxies, in which the client is requesting to connect to a specific target hostname using the CONNECT method <xreftarget="HTTP"/>target="RFC9110"/> or UDP proxying <xreftarget="CONNECT-UDP"/>.target="RFC9298"/>. CNAME records can be used to "cloak" hosts that perform tracking or malicious activity behind more innocuous hostnames, and clients such as web browsers use the chain of DNS names to influence behavior like cookie usage policies <xreftarget="COOKIES"/>target="RFC6265"/> or the blocking of malicious hosts.</t> <t>This document allows clients to receive the CNAME chain of DNS names for the next hop by including the list of names in a new <tt>next-hop-aliases</tt> Proxy-Status parameter.</t> <section anchor="requirements"> <name>Requirements</name><t>The<t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<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"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.<?line -6?></t> </section> </section> <section anchor="parameter"> <name>next-hop-aliases Parameter</name> <t>The<tt>next-hop-aliases</tt> parameter'svalue of the <tt>next-hop-aliases</tt> parameter is a String <xreftarget="STRUCTURED-FIELDS"/>target="RFC8941"/> that contains one or more DNS names in a comma-separated list. The items in the list include all alias names and canonical names received in CNAME records <xreftarget="DNS"/>target="RFC1034"/> during the course of resolving the next hop's hostname usingDNS,DNS andMAY<bcp14>MAY</bcp14> include the original requested hostname itself. The names ought to appear in the order in which they were received in DNS, for the sake of consistency. If there are multiple CNAME records in the chain, the first name in the <tt>next-hop-aliases</tt> list would be the value in the CNAME record for the original hostname, and the final name in the <tt>next-hop-aliases</tt> list would be the name that ultimately resolved to one or more addresses.</t> <t>The list of DNS names in <tt>next-hop-aliases</tt> parameter uses a comma (",") as a separator between names. Note that if a comma is included in a name itself, the comma must be encoded as described in <xref target="encoding"/>.</t> <t>For example, consider a proxy "proxy.example.net" that receives the following records when performing DNS resolution for the next hop "host.example.com":</t> <sourcecodetype="dns-example"><![CDATA[type=""><![CDATA[ host.example.com. CNAME tracker.example.com. tracker.example.com. CNAME service1.example.com. service1.example.com. AAAA 2001:db8::1 ]]></sourcecode> <t>The proxy could include the following proxy status in its response:</t> <sourcecode type="http-message"><![CDATA[ Proxy-Status: proxy.example.net; next-hop="2001:db8::1"; next-hop-aliases="tracker.example.com,service1.example.com" ]]></sourcecode> <t>This indicates thatproxy.example.net,"proxy.example.net", which used the IP address "2001:db8::1" as the next hop for this request, encountered the names "tracker.example.com" and "service1.example.com" in the DNS resolution chain. Note that while this example includes both the <tt>next-hop</tt> and <tt>next-hop-aliases</tt> parameters, <tt>next-hop-aliases</tt> can be included without including <tt>next-hop</tt>.</t> <t>The proxy can also include the name of the next hop as the first item in the list. This is particularly useful for reverse proxies when clients would not otherwise know the name of the next hop, and the <tt>next-hop</tt> header is used to convey an IP address.</t> <t>For example, consider a proxy "reverseproxy.example.net" that receives the following records when performing DNS resolution for the next hop "host.example.com":</t> <sourcecodetype="dns-example"><![CDATA[type=""><![CDATA[ host2.example.com. CNAME service2.example.com. service2.example.com. AAAA 2001:db8::2 ]]></sourcecode> <t>The proxy could include the following proxy status in its response:</t> <sourcecode type="http-message"><![CDATA[ Proxy-Status: reverseproxy.example.net; next-hop="2001:db8::2"; next-hop-aliases="host2.example.com,service2.example.com" ]]></sourcecode> <t>The <tt>next-hop-aliases</tt> parameter only applies when DNS was used to resolve the next hop's name, and it does not apply in all situations. Clients can use the information in this parameter to determine how to use the connection established through the proxy, but they need to gracefully handle situations in which this parameter is not present.</t> <t>The proxyMAY<bcp14>MAY</bcp14> send the empty string ("") as the value of <tt>next-hop-aliases</tt> parameter to indicate that no CNAME records were encountered when resolving the next hop's name.</t> <section anchor="encoding"> <name>Encodingspecial characters</name>Special Characters</name> <t>DNS names commonlyjustcontain just alphanumeric characters and hyphens ("-"), although they are allowed to contain any character (<xref section="3.1" sectionFormat="comma" target="RFC1035"/>), including a comma. To prevent commas or other special characters in names leading to incorrect parsing, any characters that appear in names in this list that do not belong to the set of URIUnreserved Charactersunreserved characters (<xref section="2.3" sectionFormat="comma" target="RFC3986"/>)MUST<bcp14>MUST</bcp14> be percent-encoded as defined in <xref section="2.1" sectionFormat="comma" target="RFC3986"/>.</t> <t>For example, consider the DNS name<tt>comma,name.example.com</tt>."comma,name.example.com". This name would be encoded within a <tt>next-hop-aliases</tt> parameter as follows:</t> <sourcecode type="http-message"><![CDATA[ Proxy-Status: proxy.example.net; next-hop="2001:db8::1"; next-hop-aliases="comma%2Cname.example.com,service1.example.com" ]]></sourcecode> <t>It is also possible for a DNS name to include a period character (".") within alabel,label instead of as a label separator. In this case, the period characterMUST be<bcp14>MUST</bcp14> first be escaped as "\.". Since the "\" character itself will be percent-encoded, the name "dot\.label.example.com" would be encoded within a <tt>next-hop-aliases</tt> parameter as follows:</t> <sourcecode type="http-message"><![CDATA[ Proxy-Status: proxy.example.net; next-hop="2001:db8::1"; next-hop-aliases="dot%5C.label.example.com,service1.example.com" ]]></sourcecode> <t>Upon parsing this name, "dot%5C.label"MUST<bcp14>MUST</bcp14> be treated as a single label.</t><t>Similarly<t>Similarly, the "\" character in a labelMUST<bcp14>MUST</bcp14> be escaped as "\\" and then percent-encoded. Other uses of "\"MUST NOT<bcp14>MUST NOT</bcp14> appear in the label after percent-decoding. For example, if there is a DNS name "backslash\name.example.com", it would first be escaped as"backslash\\name.example.com","backslash\\name.example.com" and then percent-encoded as follows:</t> <sourcecode type="http-message"><![CDATA[ Proxy-Status: proxy.example.net; next-hop="2001:db8::1";next-hop-aliases="backslash%5C%5Cname.example.com,service1.example.com"next-hop-aliases="backslash%5C%5Cname.example.com,s1.example.com" ]]></sourcecode> </section> </section> <section anchor="implementation-considerations"> <name>Implementation Considerations</name> <t>In order to include the <tt>next-hop-aliases</tt> parameter, a proxy needs to have access to the chain of alias names and canonical names received in CNAME records.</t> <t>Implementations ought to note that the full chain of names might not be available in common DNS resolution APIs, such as <tt>getaddrinfo</tt> <xref target="POSIX"/>. <tt>getaddrinfo</tt> does have an option for <tt>AI_CANONNAME</tt> (<xref section="6.1"sectionFormat="of"sectionFormat="comma" target="RFC3493"/>), but this will only return the last name in the chain (the canonical name), not the alias names.</t> <t>An implementationMAY<bcp14>MAY</bcp14> include incomplete information in the <tt>next-hop-aliases</tt> parameter to accommodate cases where it is unable to include the full chain, such as only including the canonical name if the implementation can only use <tt>getaddrinfo</tt> as described above.</t> </section> <section anchor="sec-considerations"> <name>Security Considerations</name> <t>The <tt>next-hop-aliases</tt> parameter does not include any DNSSEC information or imply that DNSSEC was used. The information included in the parameter can only be trusted to be valid insofar as the client trusts the proxy to provide accurate information. This information is intended to be used as ahint,hint andSHOULD NOT<bcp14>SHOULD NOT</bcp14> be used for making security decisions about the identity of a resource accessed through the proxy.</t> <t>Inspecting CNAME chains can be used to detect cloaking of trackers or malicious hosts. However, the CNAME records could be omitted by a recursive or authoritative resolver that is trying to hide this form of cloaking. In particular, recursive or authoritative resolvers can omit these records for both clients directly performing DNS name resolution and proxies performing DNS name resolution on behalf of a client. A malicious proxy could also choose to not report these CNAME chains in order to hide the cloaking. In general, clients can trust information included (or not included) in the <tt>next-hop-aliases</tt> parameter to the degree that the proxy and any resolvers used by the proxy are trusted.</t> </section> <section anchor="iana-considerations"> <name>IANA Considerations</name> <t>This document registers the"next-hop-aliases"<tt>next-hop-aliases</tt> parameter in the "HTTP Proxy-Status Parameters" registry<<eref target="https://www.iana.org/assignments/http-proxy-status"/>>.</t> <dl> <dt>Name:</dt> <dd> <t>next-hop-aliases</t> </dd> <dt>Description:</dt> <dd> <t>A<eref target="https://www.iana.org/assignments/http-proxy-status" brackets="angle"/> as shown in <xref target="table_1"/>.</t> <table anchor="table_1"> <name>HTTP Proxy-Status Parameters Registry</name> <thead> <tr> <th>Name</th> <th>Description</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td>next&nbhy;hop&nbhy;aliases</td> <td>A string containing one or more DNS aliases or canonical names used to establish a proxied connection to the nexthop.</t> </dd> <dt>Reference:</dt> <dd> <t>This document</t> </dd> </dl>hop.</td> <td>RFC 9532</td> </tr> </tbody> </table> </section> </middle> <back> <displayreference target="RFC9209" to="PROXY-STATUS"/> <displayreference target="RFC1034" to="DNS"/> <displayreference target="RFC9110" to="HTTP"/> <displayreference target="RFC9298" to="CONNECT-UDP"/> <displayreference target="RFC8941" to="STRUCTURED-FIELDS"/> <displayreference target="RFC6265" to="COOKIES"/> <references> <name>References</name> <references anchor="sec-normative-references"> <name>Normative References</name><reference anchor="PROXY-STATUS"> <front> <title>The Proxy-Status HTTP Response Header Field</title> <author fullname="M. Nottingham" initials="M." surname="Nottingham"/> <author fullname="P. Sikora" initials="P." surname="Sikora"/> <date month="June" year="2022"/> <abstract> <t>This document defines the Proxy-Status HTTP response field to convey the details of an intermediary's response handling, including generated errors.</t> </abstract> </front> <seriesInfo name="RFC" value="9209"/> <seriesInfo name="DOI" value="10.17487/RFC9209"/> </reference> <reference anchor="DNS"> <front> <title>Domain names - concepts and facilities</title> <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/> <date month="November" year="1987"/> <abstract> <t>This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them.</t> </abstract> </front> <seriesInfo name="STD" value="13"/> <seriesInfo name="RFC" value="1034"/> <seriesInfo name="DOI" value="10.17487/RFC1034"/> </reference> <reference anchor="HTTP"> <front> <title>HTTP Semantics</title> <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/> <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/> <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/> <date month="June" year="2022"/> <abstract> <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t> <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t> </abstract> </front> <seriesInfo name="STD" value="97"/> <seriesInfo name="RFC" value="9110"/> <seriesInfo name="DOI" value="10.17487/RFC9110"/> </reference> <reference anchor="CONNECT-UDP"> <front> <title>Proxying UDP in HTTP</title> <author fullname="D. Schinazi" initials="D." surname="Schinazi"/> <date month="August" year="2022"/> <abstract> <t>This document describes how to proxy UDP in HTTP, similar to how the HTTP CONNECT method allows proxying TCP in HTTP. More specifically, this document defines a protocol that allows an HTTP client to create a tunnel for UDP communications through an HTTP server that acts as a proxy.</t> </abstract> </front> <seriesInfo name="RFC" value="9298"/> <seriesInfo name="DOI" value="10.17487/RFC9298"/> </reference> <reference anchor="RFC2119"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="March" year="1997"/> <abstract> <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/> </reference> <reference anchor="RFC8174"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <author fullname="B. Leiba" initials="B." surname="Leiba"/> <date month="May" year="2017"/> <abstract> <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="8174"/> <seriesInfo name="DOI" value="10.17487/RFC8174"/> </reference> <reference anchor="STRUCTURED-FIELDS"> <front> <title>Structured Field Values for HTTP</title> <author fullname="M. Nottingham" initials="M." surname="Nottingham"/> <author fullname="P-H. Kamp" surname="P-H. Kamp"/> <date month="February" year="2021"/> <abstract> <t>This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields that wish to use a common syntax that is more restrictive than traditional HTTP field values.</t> </abstract> </front> <seriesInfo name="RFC" value="8941"/> <seriesInfo name="DOI" value="10.17487/RFC8941"/> </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><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9209.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1034.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9298.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8941.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/> </references> <references anchor="sec-informative-references"> <name>Informative References</name> <reference anchor="POSIX"target="http://ieeexplore.ieee.org/servlet/opac?punumber=6506089">target="https://ieeexplore.ieee.org/document/8277153"> <front><title>Standard<title>IEEE Standard for InformationTechnology PortableTechnology--Portable Operating System Interface(POSIX(R))(POSIX(TM)) Base Specifications, Issue 7</title> <author> <organization>IEEE</organization> </author> <dateyear="2013" month="April"/>year="2018" month="January"/> </front> <seriesInfoname="DOI" value="10.1109/ieeestd.2013.6506091"/> </reference> <reference anchor="COOKIES"> <front> <title>HTTP State Management Mechanism</title> <author fullname="A. Barth" initials="A." surname="Barth"/> <date month="April" year="2011"/> <abstract> <t>This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 2965. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6265"/> <seriesInfo name="DOI" value="10.17487/RFC6265"/> </reference> <reference anchor="RFC1035"> <front> <title>Domain names - implementation and specification</title> <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/> <date month="November" year="1987"/> <abstract> <t>This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication.</t> </abstract> </front> <seriesInfo name="STD" value="13"/> <seriesInfo name="RFC" value="1035"/>name="IEEE Std" value="1003.1-2017"/> <seriesInfo name="DOI"value="10.17487/RFC1035"/> </reference> <reference anchor="RFC3493"> <front> <title>Basic Socket Interface Extensions for IPv6</title> <author fullname="R. Gilligan" initials="R." surname="Gilligan"/> <author fullname="S. Thomson" initials="S." surname="Thomson"/> <author fullname="J. Bound" initials="J." surname="Bound"/> <author fullname="J. McCann" initials="J." surname="McCann"/> <author fullname="W. Stevens" initials="W." surname="Stevens"/> <date month="February" year="2003"/> <abstract> <t>The de facto standard Application Program Interface (API) for TCP/IP applications is the "sockets" interface. Although this API was developed for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="3493"/> <seriesInfo name="DOI" value="10.17487/RFC3493"/>value="10.1109/IEEESTD.2018.8277153"/> </reference> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6265.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1035.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3493.xml"/> </references> </references> </back><!-- ##markdown-source: H4sIACnXeWUAA81a/W4bNxL/n0/B26CoA0hry07SWG2aqrZ7EZrYPsvGtWiK mtqlJF5Wyy3JlSIY6bPcs9yT3cyQ+yXLbu+AKy4oKnmXH/Pxm9/MkOr3+8wp l8khf3N9fckvjf646U+ccKXll8KIpXTS8Jk2/Fx+dP03uuCjTAkrLRPTqZGr IT89n1TPOvNZqpMcFhjy1IiZ6yvpZv2Fc8VU2b7ACf2Chlsa3j/4gqXCwfC7 09H12SeWwB9zbTZDbl3KhJFiyEdFkSl4oXRuuchTfiVF1r9WS8nW2nyYG10W XhXGVGGG3JnSusODg+ODQ/ZBbmBQOmS8z2ln7ndmDD7z9BeR6Ry234BuhRry n5xOetxq44ycWfi2WeKXnxlbybyUsAxv78e52xQw/e8gh8rn/K/4Dp4uNJoA 9bbD/X38XM9jbeb78G4pVDbktWH66/k36yN8Ce+ESRbNvExZZ2P/cn8Er9RK 2v3Lcgrm2G8vgMsaWehm6ly5RTmNE70Mu9NHH9wpc4uG3M/EVGZ2/75PmJ/b V9aWsk/DhnzHMCZKt9AGLQvbc65yO+TXMSCozDb0xAPhWi+Xm9ZTUMb7VPb4 OE9ieii9VVyBw74R+BaFB4fmgMMlOH9Fxuf88mIy/sF/Bet7GEcT9KUwKYF2 XE3ROb+WySLXmZ6DBOBUMc0kvyikgbfgrsnGOrmECYD3mUgk36PV966ePuXf Arb5pJCJmlXgA3nRJvyLKGxfWyD8I9XGZ2dnlXjCzKXzXgGnKCnlxyLTRsb4 ldxqpVll0u3rQiSvizIvl1NpXr14fvDi4OVxWMZHyKgwKuOHB4Oj8BimKmnR QI0EpxfjIR8cxIPBwTHtB2EU45yYljweMNbv97mYWmdE4hi7XijLIWjLpcwd T+VM5RDSbiH5bY7Bv9CFj1tpbx+ji5jTSkVNH4kwKB7DpRDIXM94WIiCOBG5 zsGyGcEEnwGCYOJSpkqYDeA5keD0lKelQV8h4xhpdVaSYwXt5RisCjqCX5Vd 4DDBE53nMqFBTpMmqAiEZBF75ZcqTTPJ2BN0vNFpSYPRFLKrHKkLexbge8ln SmYpv7v7y+XVxQ8/9ifXo+ubyaur706ODw+OP30C5TK9tm0lFFpSo0AruWmQ jNJPdYkirVG+DV+AQTJQFYU18tcSNIJ1uvtb8Dd4CNfLFHyzMRs3DhPwlkxc OwCdKBxy3kqlkrd2B1YrkwVakIwDw3FiZSjmDfWwns2WNUJum217fL1QsDq4 FxV3AvQQoKl1uFGPjS+5SFNQCqIJYpUQ0d6e/HQfS81iOs828D/plVAQvz1m NXzBUbl2fCp5adGYaPnlskSQOYnAWND8BoYyT3SJ7noIZWy9kHkNKHh9H1Df 53pNb+DxrMyyZhcPa3LCGrbwQu0G80oJfnI+eneGqIdsZdH8MAatPjg4egZW 9/ZwKikzYcACsBpsR3wX8IB7wp9rpEEkakBfD1Hk/QHyMT8QlwogCyoFBfEr 4ChQXiCv2nWwY6XnycX5+dnJNQfnLHSKsiJSCSLAOyAsCHVzeunzLU6CEWFO H557LB2//PQp7mpNfm7cx6Ik0+JDRCJUcAaiBhxzZC/KuLDVEvyZKA0BC4ym VsptYBEgg5QvgWrBBDnQG76uVLE9RgwU7FZFw1pO+dRADGPwgAyka+1OdFlw qcZoykqAj8SdxEqBFJn6AKO1/qAkK62YS15olAsm3N29Prm4+H58Rg59cfji ubfRNNNBiVlLCdI23mbmwC6VzCBDIEjvETLjDlkRH23EsukGhE+yMq2cWXGz H0/Rmsv1LvbvcGMdnCDpkydQkv1aKiNRVOuZFAovviavRu9uJtdRz3/y8wv6 fnX2t5vx1dkpfp+8Gb19W39hYcTkzcXN29PmWzPz5OLdu7PzUz8ZnvLOIxa9 G/0Ib9DF0cXl9fjifPQ2Qs1c16KADTDjVHrKLgxokwIOWCptYtQU/oA5355c /uufg2cIYfDd4WCAFOj/eDn4AiMTOcLvRtTk/0RaZ1DGSGHIpkgMolBOZBCU gDUL3J/zBfBCzL56nQGh8v6L118zzErblm/V5HdPart/8mbe4ad6yOeWrwTg FCNe8IkzIRYn11c3J9c3YP3+d+Ozt6cEy5fHzwagDUVZ4FrLkGcxwjCOGlAR SJBbRd9K3A0NhzhC4pbEydbbO8DLI06SGTzjVzk/Zdt1QJ33YYEuO9zdgQiY gDyHUnTq0lhKX8Smq+p5BffPLdviL1jCOwtAUsuFU7RRc5WDGIEbQYJ6qnJW ZjOvnZdSl/MFEmbLx36RVJoO6W48+be1IhGqwLTiA8kPJrdgKuCUTczHlA+N xAaIL8vMKaiHt6wRdqSY7/n0owzY2gucP1TCkT/WusxSNvWKB4jkLSLxe9Qy 1qap0zhZ0O+ZB8+FFdije/KwJ00gqKFyUJbIbBNc6DN3G3ihXpCeFBvG6gBy x7YllZoeqHwv6kVPMfKwUiLMIgFLt5aQ4WmVmJ1rF6RSs3qishVM0sCODSJ6 AYQ4bgk9J6qHRUVKRMLbRAJZkt4ABiHvMfYdbC8/iiW1QeR8RI4IPWpEH3EY EOfSRV6wgCNfus00JgVEdQUKJB8WcuSOOmM7G/AIPVpvA4pEQ8Z+++03nua2 Hx6z7TExb/55vHCfjyEZtIexXQ+3J2L/oxI56M7c+TTMHME//IQGfzBMpy+H wwGK7LHhzZcQ1trR3ZiqfQiADgVP1jV2UJ5aZUAEZnHWznpDfs8vX9Z0/Spq SRR96TvgLVC+inbYpLdL26jSifCXUg3blPRdGaqa29dNoG1TZPOOUHXNX1UD HhBNQdjr1MSuprtdYkc+w+4WPtDJFv6IrGLexBnInUkvQZheec3yqXaLLovd UsJ4LONBct3xOpSVdRivFdStpWsVQs0WcQdHAlM3dhctKG03TBRIwbCegjEB tvNf6GeUZQ+V8EauJCayULdz33eEWs8zJ7Y2GrPCWsHAD7nvHdvSsEqahp5b pltIQbnJtroj7Eux8W7w8vvMFET97wjKN1T/C4I6fIChtnjmcCfP7Jx8n2cO /zyeecjKu+nm8EG6uWea3i6Vo0axx6LLF7h4OFdjFP23Fg2mQg7fKsJ4XTSw VMNUxDIus6lqY6tc6c/YoCUMsMfgq7qw9tlJVcg3YsG+KX4BRCEY1vig7t+a 06D6nIiozWAJR0PIyD0+BUbIpVdjDnSHwZlVZzMtCVmrvOuIobxi0EjgSU2H SLDYhIc+KOWycIgMqmL3Il+WNJUYBPMOJ1DT6dMABRrL9VZBSHVmm77JQQ/V xeQS37udhbrEt/6CjjDwcBDb4LsnddXCWFNwYclDYPgHVj31OU9WgLWguzIq aS+CbLTYFCCOBX370VOAQoYU7B2woTKXGtyamPx6+aZZhu9BG+3PQ573+CT4 9CiGpuVpr0XloW4DztWswDDKnX9isaAkBt2lqApVIM+AJ8O5CCyqjcGTEXAy dg94brBpzyLKa1qAuholZFCdSiNSzf3JVKabQ6RwYHdzNWY3OWLGYO170iy+ 59vMo+OXLxqFD+MjUJhTKw05Dag0AQ37TdXJ/PkcFau7Fxg8UoBWSZvSyi3Z rUdIabHFbchnNKYu64MEDJMr1cmPMomwgSrtn1BzkRqfHZ5sK/JY4TWmczJK /oW2VuHFAWYn0ZjHNXWBQEconbbhGsUQ2bU16B6lB9wBPZ5I6RTSVo+bjgRa vwCeBET37cW9lSvf+2IDegxRgN1huej9+ziK+UThwRROhQdRa6JvWkAmYNz7 2OnV9QSLUu1gLRKuW/Jtu5v/H7obhP/s+cl96R9z9w3k5SrKvQN8yuosFtWm d0YKf1qE/STMAXT4/RibqKXyBd4uF9RYqNcKDuTegTg8VG/5todidkH0RY0t IIjWrg7VePckwu8hZrhptUwqPZXHvB38TIXTBn9MVMM7mkLJbzNhF+/fb0dO 1MMDdw8GD8OOIqw9d+fsh1T8c5FSSwkuhv/+E354wsf4BE8SfVlyEig0FAkM AtmfBrlu+/BYnPTqMhsLETrlXQiopkSSYC8XEgd1Uay6x2iO0u5dqT14lAYo 7UrfHGhhogrN2UNXGkuFQ8NVi1gJQPuUGrdQFiCEWKuoH12ObXPndDuXDpsN LOluIUPRjSteBXRfUJ3olYeti7o7uB2NfzkZnV+coz63DHJkldhexAOUEWuE o2fHR1QWYE1H0UycRxWLka40VYxsnZd5y+7R144tYSnUF1+0jA5mHEE92sVB +1wRCwh863ZUsL9TauNdTEL2xNtfSgdUcmOYUmoqc7L6FroafzUWJ7W7h/5d 7bhngG1NsACnuVhLd73TOdwSU72iUhJrjNLg/Us3GKCKtDLpJ52Hf+D8mtfN Qp1nofwCdE3OTjoGBVyg7BuP2zCgakti2qdr/+Y8jzJs56KRVCaOL+kU2N8R QG2ucILVM2Gqgt136IxG2qaXwCnVvSs4scQD8rYA1XlAWyR/cZyn9YbUUQGV Cg751XnGbC5C6hEzugCjWyRbWR94Xln/axm6ZybfpiApvkTeoK6gBOINzALl w72GCDkix0KZbglbF0zb13TUe0GNTJd14TYrHBfZ7vWcv9nib6DOXyHZ4ZnF 1gVgVV7opXJo/OmGpAXFLN51YQFGv7lQjn4SUvWbJhzbghPMJlTvC5WGoyW6 McQz9iBhjOTcHMX0/sgGXmsUC8W2shYZHUBHVdVxTaqwZQAMbR1zUGXV/gVD Xt/T7hraPhbROd0zQu1GWuA+MR+1LNs6jmBUsyYLra0MfE6/DTKV4B1XqlaW CgaTjZ2wGp3LHEI269X6gR084nfH1B7YoxWy6dM/Snc4JpVzIyWr04/XCy2F kd/4gqA33bTHmDpiiYrGo/PRvZzcvVI1co43LsZHbrQtXtSIVx1nRo/8AAbG +wXNhn3108971S+x1ut1rEQu6Nc+AjqJeU63pP4HWe1fVD39GiQ/x99MseG9 YgW6byJcyoQ4YFSdIIRumSJv67quukDU5l5tUAVvfSjCBfNoTB//Bc2VnEES gg4DhegYlP0bEDGZMlkoAAA= --></rfc>