<?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-amsuess-core-accept-any-01" category="std" consensus="true" updates="7641" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>Accept-Any option for CoAP</title>
    <seriesInfo name="Internet-Draft" value="draft-amsuess-core-accept-any-01"/>
    <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
      <organization/>
      <address>
        <postal>
          <country>Austria</country>
        </postal>
        <email>christian@amsuess.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <workgroup>CoRE</workgroup>
    <keyword>CoAP</keyword>
    <keyword>observe</keyword>
    <abstract>
      <?line 22?>

<t>This memo defines the Accept-Any option,
which provides a more flexible content negotiation than the one originally specified
for the Constrained Application Protocol (CoAP) in <xref target="RFC7252"/>.
As this is particularly useful with, but ruled out in, CoAP observation (<xref target="RFC7641"/>),
that is updated to allow it.</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-amsuess-core-accept-any/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Constrained RESTful Environments Working Group mailing list (<eref target="mailto:core@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/core/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/core/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/chrysn/accept-any"/>.</t>
    </note>
  </front>
  <middle>
    <?line 30?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>[ This document is document has been revised from the original 2019 version
after pub-sub moved away from desiring non-crated states,
and moved back to that during AD review in 2026. ]</t>
      <t>When CoAP content format defined in <xref target="RFC7252"/>,
the choice was made to have the initial content negotiation allow the client to only pick zero or one content format.
This is a good choice for many situations
and ensures that proxies can cache as much as possible without added complexity.
A client that does not know a usable content format would either leave the request field absent,
indicating it would accept any response,
or try several acceptble values in a series of requests.</t>
      <t>In line with that choice,
observation (<xref target="RFC7641"/>) required notification responses
to carry the same content format in the notification as in the original response.</t>
      <t>For applications that expect a representation to change its representability to change during an observation's lifetime,
<xref target="I-D.ietf-core-multipart-ct"/> introduces a way of wrapping responses in an application/multipart-core response.
That approach is convenient for bags of representations,
but lacks actual content negotiation
and produces representations that are not directly usable
but need to be processed from inside the multipart representation.</t>
      <t>This document introduces an additional way for the client to indicate its set of acceptable content formats,
and removes the same-content-format limitation during observation.</t>
    </section>
    <section anchor="the-accept-any-option">
      <name>The Accept-Any option</name>
      <t>A new option Accept-Any is defined. It is critical [ I don't fully see
why but follow Accept here ], safe-to-foward and part of the cache key.
Its format is uint up to 2 long (indicating content types), it is Class
E in OSCORE, usable in requests only, and repeatable.</t>
      <t>Repeatability is the only aspect in which it differs from Accept in
terms of option properties.</t>
      <t>Its values indicate a list of acceptable representations in order of
decreasing preference. A server MUST answer with the first format it can
represent the requested state in, or 4.06 (Not Acceptable) if it could
answer successfully but the response would not match any of the option
values.</t>
      <t>The Accept-Any option MUST NOT be used exactly once;
that request's meaning would be identical to that of a single Accept option.
Instead, a single Accept option is used.</t>
      <section anchor="proxy-behavior">
        <name>Proxy behavior</name>
        <t>A proxy MAY ignore this option per its properties
(and serve a cached response if the cache key matches),
but can implement additional behavior to enhance its cache.</t>
        <t>A proxy is allowed to serve a cached representation to a request with a different
sequence of Accept-Any options, provided the second request has an
Accept value of the cached representation, or all the content formats
that precede the available content format in the second request's
Accept-Any options also preceded the available representation in any
earlier (fresh) request's list.</t>
        <t>When a request that carries Accept-Any is answered 4.06 (or with any
but the first format requested by Accept-Any in its Content-Format), a proxy SHOULD [ we
can't have a MUST here w/o making it non-safe-to-forward, but I think
it's sufficient ] invalidate all known representations in any of the
requested formats (or the formats preceeding the returned one,
respectively).</t>
      </section>
    </section>
    <section anchor="update-to-rfc7641">
      <name>Update to RFC7641</name>
      <section anchor="changed-behavior">
        <name>Changed behavior</name>
        <t>The requirement that subsequent notifications carry the same
Content-Format option as the original response (<xref target="RFC7641"/> Section 3.2) is lifted.</t>
      </section>
      <section anchor="rationale">
        <name>Rationale</name>
        <t>Observing resources whose available representations changed is a key feature of Accept-Any,
and necessary to implement pub-sub topics that have no initial value
(but a "null" representation with a dedicated content format)
without losing content negotiation and direct usability of the response.</t>
        <t>The requirement was introduced initially before such content negotiation was thought of,
and is not a necessary part to the remainder of the observation document.</t>
        <t>As long as the limitation is in place,
the origin server has no clear action guidance
when its resource changes the available content formats
(see below).</t>
      </section>
      <section anchor="impact">
        <name>Impact</name>
        <t>Changes to the returned media type can either happen when</t>
        <ul spacing="normal">
          <li>
            <t>Accept-Any was sent in the request -- in which case both server and
client know the updated rules, or</t>
          </li>
          <li>
            <t>no Accept header was sent -- in which case the server whose
representation changes to require a new content format has no clear
way of indicating that under <xref target="RFC7641"/> (ending with 4.06 Not Acceptable
would be close but isn't the expected response to a repeated request);
if the server changes the content format in a notification to an
unaware client, the client would catch it as a bad response (probably
similar to a response with a Content-Format not matching the sent
Accept). The client might regard the observation as being aborted while the
server does not, and will terminate the observation with a RST on the
next notification (or close the connection in TCP).  </t>
            <t>
Applications are still free to require constant content formats;
clients would treat what could previously be treated as a protocol error
would now treat it as an application error.</t>
          </li>
        </ul>
        <t>Impact on proxies: A proxy that enforces the previous rule on
Content-Format staying constant would close observations (probably with
something like 5.02 Bad Gateway), and the client would need to
re-establish. No proxy implementations are known that implement that
behavior.</t>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC7252">
          <front>
            <title>The Constrained Application Protocol (CoAP)</title>
            <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
            <author fullname="K. Hartke" initials="K." surname="Hartke"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.</t>
              <t>CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7252"/>
          <seriesInfo name="DOI" value="10.17487/RFC7252"/>
        </reference>
        <reference anchor="RFC7641">
          <front>
            <title>Observing Resources in the Constrained Application Protocol (CoAP)</title>
            <author fullname="K. Hartke" initials="K." surname="Hartke"/>
            <date month="September" year="2015"/>
            <abstract>
              <t>The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks. The state of a resource on a CoAP server can change over time. This document specifies a simple protocol extension for CoAP that enables CoAP clients to "observe" resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time. The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7641"/>
          <seriesInfo name="DOI" value="10.17487/RFC7641"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.ietf-core-multipart-ct">
          <front>
            <title>Multipart Content-Format for the Constrained Application Protocol (CoAP)</title>
            <author fullname="Thomas Fossati" initials="T." surname="Fossati">
              <organization>ARM</organization>
            </author>
            <author fullname="Klaus Hartke" initials="K." surname="Hartke">
              <organization>Ericsson</organization>
            </author>
            <author fullname="Carsten Bormann" initials="C." surname="Bormann">
              <organization>Universitaet Bremen TZI</organization>
            </author>
            <date day="21" month="August" year="2019"/>
            <abstract>
              <t>This memo defines application/multipart-core, an application-independent media type that can be used to combine representations of zero or more different media types (each with a Constrained Application Protocol (CoAP) Content-Format identifier) into a single representation, with minimal framing overhead.
              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-core-multipart-ct-04"/>
        </reference>
        <reference anchor="I-D.jimenez-core-coap-no-content-00">
          <front>
            <title>The 2.06 (No Content) Response Code for the Constrained Application Protocol (CoAP)</title>
            <author fullname="Jaime Jimenez" initials="J." surname="Jimenez">
              <organization>Ericsson</organization>
            </author>
            <author fullname="Carsten Bormann" initials="C." surname="Bormann">
              <organization>Universität Bremen TZI</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This document defines the 2.06 (No Content) response code for the
   Constrained Application Protocol (CoAP).  The code indicates that the
   target resource exists but has no current representation to transfer.
   It allows a client to retrieve or observe a resource before that
   resource has any content, without the server signaling an error.
   This document updates RFC 7641 to allow 2.06 (No Content)
   notifications, and specifies how cross-proxies map the code to and
   from the HTTP 204 (No Content) status code.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-jimenez-core-coap-no-content-00"/>
        </reference>
        <reference anchor="I-D.ietf-core-coap-pubsub">
          <front>
            <title>A publish-subscribe architecture for the Constrained Application Protocol (CoAP)</title>
            <author fullname="Jaime Jimenez" initials="J." surname="Jimenez">
              <organization>Ericsson</organization>
            </author>
            <author fullname="Michael Koster" initials="M." surname="Koster">
              <organization>Dogtiger Labs</organization>
            </author>
            <author fullname="Ari Keränen" initials="A." surname="Keränen">
              <organization>Ericsson</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This document describes a publish-subscribe architecture for the
   Constrained Application Protocol (CoAP), extending the capabilities
   of CoAP communications for supporting endpoints with long breaks in
   connectivity and/or up-time.  CoAP clients publish on and subscribe
   to a topic via a corresponding topic resource at a CoAP server acting
   as broker.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-core-coap-pubsub-22"/>
        </reference>
      </references>
    </references>
    <?line 157?>

<section anchor="open-questions">
      <name>Open questions</name>
      <ul spacing="normal">
        <li>
          <t>We could just as well make Accept repeatable with the same semantics as Accept-Any.</t>
        </li>
        <li>
          <t>Is there any value in having an Accept-All option in parallel to this option
that asks for a multipart response that contains all the representations?</t>
        </li>
      </ul>
    </section>
    <section anchor="comaparison-with-206-no-content">
      <name>Comaparison with 2.06 No Content</name>
      <t>This document was revived with minimal modifications (mostly the addition of this appendix)
as a response to <xref target="I-D.jimenez-core-coap-no-content-00"/>.</t>
      <t>To serve the same purpose as that document for the current <xref target="I-D.ietf-core-coap-pubsub"/>:</t>
      <ul spacing="normal">
        <li>
          <t>Only the relaxation of <xref target="RFC7641"/> is needed, not the added Accept-Any option: A pubsub resource only has a single topic-content-format anyway.
(Accept-Any would become relevant if pub-sub were extended to cater for multiple media types;
if relevant, this document might be changed to give it <tt>,*/*;q=0.1</tt> semantics).</t>
        </li>
        <li>
          <t>The null media type hinted at (and the corresponding content format) would need to be added to this document;
the next section gives a possible definition.</t>
        </li>
      </ul>
      <t>It is the author's impression that this document's approach can solve the same issue as no-content,
but with less impact on the REST model underlying CoAP
(in that "exists but has no value" does not become a new state).
More convenient aspects of this approach are that a null media type can easily be PUT into a resource
(as opposed to introducing a variant of DELETE that just affects the content but not the resource as a whole),
and that it opens for additional states that can be represented in new media types
(e.g. a generic "tombstone" type that can be placed in a resource to indicate that there is no fresh representation, but possibly tells a bit about the history).</t>
      <section anchor="suggested-media-type">
        <name>Suggested media type</name>
        <t>The multipart/empty media type indicates an empty set of available alternatives.</t>
        <ul spacing="normal">
          <li>
            <t>Type name: multipart</t>
          </li>
          <li>
            <t>Subtype name: empty</t>
          </li>
          <li>
            <t>Required parameters: N/A</t>
          </li>
          <li>
            <t>Optional parameters: N/A</t>
          </li>
          <li>
            <t>Encoding considerations: This media type only describes empty representations.</t>
          </li>
          <li>
            <t>Applications that use this media type: <xref target="I-D.ietf-core-coap-pubsub"/> (if applied)</t>
          </li>
          <li>
            <t>Intended usage: limited use -- in applications where the absence of content in a resource is distinct from the resource not existing at all.</t>
          </li>
        </ul>
      </section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA4VZbW8bNxL+vr+Cl36IXEiK477hHBStz3F7Bto6sB0Uh7ZA
qV1KYr1LquSuZTXwP7tv98fumRlydyU7d0GLxF4uOZx55plnZmezWXF/qj4r
WtvW5lSdlaXZtLMzt1N+01rv1NIHde7P3hWVL51usKYKetnOdBM7E+Os9MHM
tLym3W52/LoodWtWPuxOVWyrYuvD3Sr4bnOKfa4vim5T4Xk8VV99+fnr4s7s
sKA6Vb/QIVPlF9GEe/NbcW9cZ04Lpfp3XWyDts5U6vri5nbZ1erC3dvgXWNc
G7Gy0bY+VWTQt9a0y7kPK3rftutugd+vwy66V4Ophe7atQ+nxQyrrINF53N1
1sT//DvSbnLZ83WwsbXajZ6UvnMtXe+sg0lW41cmnZ1Xf5vcMy99UzgfGt3a
e1zHuuXwQzGbzZRe0LXKtihu1zaqxjReVWaJe0bVrs3TiEyL7dqWa7UJ/t5W
WKVVgyurZW0e7KI2MM+18IhyCAJs4Si2a+14O+/wf7Ar63Rd71TcmNIurakK
ijMtGPv5bLOpbSk7vAu+9aWv1YQCdQSHqQ8f/nb93flXJ1+cPD7OizOyFzfA
fxsdWlt2tQ44oouGYrVFGKZq0bUqdDX29viXdVPGVoq6HDRJ2wIdj49H0wKm
t7Sp4KZSrVcw3W+VbefiwsZWVW2K4hN1ibj4qitpo6L49RfFPgVyO8KIGv97
raNaGONUMPc2Yt9l8I24KLlHnRy//ru6NyHSbsC8CWrTLWaxW8Dj93hFb/VO
3kMcbLBupZx3szKwobElnE8L7aq0fqHLO7Kfr1R1/MLZW7bAbMmjJ8cnX87V
r78Vxc9rmMa+yeEU4CRsVIf+Jz8h9GtvS6O2uFujK0NnrfW94WtZZ4GG+ll4
iEN5h9rSQ7zoHYK3sbD4LxPwY2Ds7FszF9BaAuHK+yobQGBqkGIq2rbjIyK7
wbjYBQY2bgIAP1j8UAKapS5xOJndAdr4e+NjZDQTbggruqpwa6TThnDe7gC4
3lh2p8dWzrfqzuEqGrDT42RI3tv6roYZ2BPBrE32TTB/Iluxyho8RkrilSmS
tWL0I0o2vyr0oehuuMgGFzPTglIn4LIGYIGHZQ2dfq9r7Eux0nga6LZ+mU+L
gO+lUzXCybeUe4gHsedHU4LftwHewHWRvClBszmxQPBKHWAQXS2Cxg69YIUL
9l7XMf+6x3/eEXZ+hyvqgQ1SBM0D6APOwMoNFuOExDYwAISzAujaOHq4sDUi
N3qccgAAGF33ZYRPlqa1Ddzw4cM3l7O3c+JzKTVNV7eWCGZWto+PsFkynnmQ
0hH+3QaYSvv2LuEIuPENXo32IfYc7npLN8PK4IFJgjach2Jkk/+QxKsUxfGd
kefEbTUyHJaUQP2zmcZZsMkWH2whTtWBI6MqhLhsmUAJyby9M0KAC0ObYIue
uFC/bCVg7m92sP88lZiBDke+c5RglpbBcKa1VA8GQkjpIEGNpiUnCNSfybTE
e8EQ88UeibO0apaQWNvGJtAkLIyAAINh8TMlsPj6I38KkIIDlSbtMnqR7i3M
OVeXXAnKgOuWuC3KxCWc4l7C9o6LojGosTsuVkvP1Cg7KbCGAT1PcZelmbUe
19jqAFagqJLH4RJ2GtMZtM28uISzctqhiMHnqGTkzhNVe9x3MmKZ7MJ2tzHx
aEqsg3fOaw3ZcUEYvro5v7q+mGZys67nEqbrqRKfb4zmmMCB1+kHyTwbkwjA
LXXk5MUeoicsQW65RLkTRKUrW1eg8DUM+eRWQG9jUOENMxjO7mkuAUQjrvEQ
H4dgx8EQfqBhvywqUwajI/kAi2CDcaWBGFMsBoP68f3NLe4Wt/h3okoUGRvi
QGkt1ZGiP2RM67kWs94ArD+fH3+pJj8hx8568yBolrwJsXyRjopdSTkmqCA0
yKbCFKkgUKrCAKpabpfjn2Aqfpl/BMVyq5+ubimdO8pk86A54z1u/0aET7rC
S1KG2pGD5Fi8gnx3guAsKcjhirxY5+PSUYAhVJ3R1fQjCxibMAG2Qug94LYG
wsH6QAJr9IcSbMMLfjz7l7IrR9zJsi9jA24jfhgwUkwIlBxIHM6ZUQ1OtAcJ
I74k9DPhkTawVPKZsEYUle2juxuHalIKL/FG88FMkiaUwcKbT6w4LFu6lwIM
M51SAkuKSA/oGHj5SSzjNOvxSrjOIJerfjMSm0BncjnDYo8qDk1hmMJuWbFP
rEUST6Y0ifD1PZqP59ROKuj7xryMxVPzcVj0edPqYNcDN3Et3RUG6t4i2pMl
Hq6PRkil5J8nCTs4VNQNdAmpoH1mlnTDuZKZPiU5nZKzbi/Zh7xe7Pa2coyB
81RjvuPVR4R5AcPNP6/e//CWCH9r0KUS47M81pKKzO7bVx4YvEuij+T8wPWB
yF6amEtCvbsrLF04dkvoKK6Tv/4GKxBgWzERIoSkR91z7DfwRTFcKAWZncD3
Tj9zaExFZgkJtV2gNgCafFpQNoHL0VTWuyOqmu+5VyJAJ9n4tGIWxTlrsOpj
qU7JfptIFFKk6ZU2+h/JhXZPQcYD0VnshyEThI7Pi8x9katuDDdx6rP5yRFB
BIqwZXq61sIAphjZecWiIUk+3wWSNNu1jx9HcUwStJLmhZhniUKJ7mQ/v0XG
OEN1QAfWrgMf5W6w9eiTknxjQDnft1uc7MWEMKPVC4dS8uIwoTLVGCmf1UEa
HxW5B6p9HMuEvQ4OVopiZHEg5T5RzEjHHwZ0y7I/ycAqG03VziyJ2iO1Y8+d
t+U4+m61prIjXrLSgOmRu1gUcXmicxsNicAVXzAwanGyKCXqjqKMElJGEtFy
3mwgso30u4KirBKIZeH5En1dIA1Or6w6ZCJYG4LOuNSOCEISAOL/pFBUL6hB
eAMlhDLrstnQrCbj7jxv4fezskEoNcs4rmCp31yjqzAkt4wrik/HxEXejCLJ
9/rR2WzQZ6UGnBceUEnXhctpGCX6nLteejWPSWjKEqmO4CQ4pRewmgLQn/fk
AKkXvD8nEE44QGs53DkhiSO+PSw+42hgl9SbjdQup0vHgNhL/YlxzHOcFlwR
9qUabZY1UFlTklNy2Uh0TuZLVzoWGamwkxI2fR08ekNjv+X4xmNEPC2ler9h
pk0dtuic3lLPJoGYjpsmMbNkdYhiQiIA7ePIsAnq0gJ32mGfCJzXOmRjs8gU
bjjg0l505npA4cEe4qSjubodjGgs5WgwK2pUDtOOh2Dcgi98IOcACjWjgCwS
r+TJinQXW0uyBB0B2Ls1TzZM9l6jnPLYkfZx5mG/VHB1k9AlV7tE93Dz7fk7
yjQ1nj5G7opjS2dDbpgx+EoaWGrXHmbumz45YgpEix4DQWEdwr/Y0OTNd5H5
Th7TVC+KYJBxpwnBhx5ynGW8TYrn3lBBFvc0oaRXoiHXqcqCVAYnNAYuE9Ky
FZyyeOewcOJ2u0T7ctEEK/bfyPdxgBOHoYi+MS1DpLZ3Rn0xPz5R/wD8vsc1
kY5HEtAneE1DBqiKGdIE29m4niMHs6LO5W8UGdE4MqntqyP9WGRxkUa1NAGl
Qe0VESGnIc8GwVE/mxSUP7rIrt0aBBtKrO9Uhr526AF5uhVRWKgTivTawKpz
2vaSfUwcBZoV4Q2MkU0yd8rLcVbuhBxVLRRBkxqrvrkBCmRCE++4p6fJ+2jW
kslG8AX/WNbVdWL0PfXxDTnh3Dca79qY8+ZEyC5n++G8hlibsEKjZF6PHLQN
NEbjq5EMmzQ+UhfJdS11TFJySepQCarsw1HBMB9TZBq1/WFxmPlLpm2l15uZ
8/3Y5viYRv3FbW6l+hhsurBhvRXzODYZ3c+RukBtlHoy0OMjoKQgpB4f6aOI
unLJ+mBq/aCz/R8+DDWCpIahVmXKXJiuSp8sDlsbzjzefaj8PP/gniw3w6zg
DodTgAzSZI6wT8a1OtWeEtlFFpp7ykkUkqwGqZVBEcJOlXSdJOqCzMQZLjhv
EAgxlaG801Ti1PtP6Hther2KDVeAABHQ79NPX3365s+vj+evfx+yAOw54wJA
YnMsRUAFzG+tmvSJ74NAoBoLy6Q79/mAbBAf56zINr7hxDDC8zExOdnIRJoH
+Tx+s2muJyM4Dht/hEMTBeKAKTF9rWr3j3gZh5EsKaro6zH6bIwdY2+AqswP
OE0ghHj7RMn0Fn1BpLRBjrMCqZlh+TvnxCYDXpgHS5M12ieJGSaQF8O3hoQC
0T88Y4Lzf/RSlfLQWAZtcZyCchEdElvoJ6Fi1aijlcr07v0tqfQkDBjDxUQT
LVHOVTKcFRHPtAY7gyVU4si3Fz9c3F7IOUKtyyWbMxY5PFv2/XxLsoTzAyKw
Nkei74XfqZMzLhHgMJCRr125y3dkds958rmKfDTCfTEx89WcPhyBboIt1YvW
N4vYoqN9IU4Y78WivxIZ1ls4HkonzFDucR+ieCzxZK5CN02QBMegxLAmo2K+
8GnUgBi1PnAj/ckn6qZbraQ1H2yXPqrn/lem2aDbGoUvW8UCQZ7mgXnfaOga
rOD4U3DkUnVLb8pX535r/PqmW7TDE94Mv73O34CoVqHMmwCN8dOrMzy62qSQ
PH104UqfM52+FwQpGacqfXvuL8AMWZlYBrvALeQKBzVsTj3Mk29CXUwDwWG3
0/9D+moC/mMZZaojqtkucSc62RXe5g6QfzSpYdn7FLXloDOX0Ic7mdBlZO8D
hhiFPtA7MEH/vbd/ShnAOc9J1FLtnhf/BdU/dXoiIQAA

-->

</rfc>
