<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.3.24 -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-gundogan-core-icncoap-00" category="info" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.5.0 -->
  <front>
    <title abbrev="Data-centric CoAP">A Data-centric Deployment Option for CoAP</title>
    <seriesInfo name="Internet-Draft" value="draft-gundogan-core-icncoap-00"/>
    <author initials="C." surname="Gündoğan" fullname="Cenk Gündoğan">
      <organization>HAW Hamburg</organization>
      <address>
        <email>cenk.guendogan@haw-hamburg.de</email>
      </address>
    </author>
    <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
      <organization/>
      <address>
        <email>christian@amsuess.com</email>
      </address>
    </author>
    <author initials="TC." surname="Schmidt" fullname="Thomas C. Schmidt">
      <organization>HAW Hamburg</organization>
      <address>
        <email>t.schmidt@haw-hamburg.de</email>
      </address>
    </author>
    <author initials="M." surname="Waehlisch" fullname="Matthias Waehlisch">
      <organization>link-lab &amp; FU Berlin</organization>
      <address>
        <email>m.waehlisch@haw-hamburg.de</email>
      </address>
    </author>
    <date year="2021" month="February" day="22"/>
    <area>General</area>
    <workgroup>TODO Working Group</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <t>The information-centric networking (ICN) paradigm offers replication of autonomously verifiable content throughout a network, in which content is bound to names instead of hosts.
This has proven beneficial in particular for the constrained IoT.
Several approaches, the most prominent of which being Content-Centric Networking (CCNx) and Named-Data Networking (NDN), propose access to named content directly on the network layer.
Independently, the CoRe WG developed mechanisms that support autonomous content processing, on-path caching, and content object security using CoAP proxies and OSCORE.</t>
      <t>This document describes a data-centric deployment option using standard CoAP features to replicate information-centric properties and benefits to the host-centric IoT world.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
  Constrained RESTful Environments Working Group mailing list (core@ietf.org),
  which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/core/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
  <eref target="https://github.com/inetrg/draft-core-icncoap"/>.</t>
    </note>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>Information-Centric Networking (ICN) introduced the idea to turn named content objects into first class citizens of the Internet ecosystem.
This paradigm gave rise to (i) a decoupling of content from hosts and the ability of ubiquitous content caching without content delivery networks (CDNs), and (ii) serverless routing on names without the DNS infrastructure;
(iii) Named Data Networking (NDN) additionally abandoned network endpoint addresses in favor of a stateful forwarding fabric.
These properties enable an asynchronous, hop-wise content fetching, which prevents forwarding of unsolicited data.
The latter significantly reduces the attack surface of (Distributed) Denial-of-Service (DDoS).</t>
      <t>All three constituents make ICN appealing to the (constrained) Internet of Things (IoT) as infrastructural burdens and common DDoS threats stand in the way of a lean and efficient inter-networking for embedded devices.
Early experimental work <xref target="NDN-IOT" format="default"/> shows that NDN can successfully operate on very constrained nodes with noticeable resource savings compared to IP.
In addition, short-term in-network caching proved valuable for increasing reliability in low-power lossy networks with nodes frequently at sleep as common at the IoT edge.</t>
      <t>The deployment option described in this document replicates these information-centric properties using standard CoAP features.
Recent experimental evaluations <xref target="OBJECTSEC" format="default"/><xref target="ICN-COAP" format="default"/> in a testbed with real IoT hardware demonstrate promising results.</t>
    </section>
    <section anchor="requirements-language" numbered="true" toc="default">
      <name>Requirements Language</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default"/> <xref target="RFC8174" format="default"/>
when, and only when, they appear in all capitals, as shown here.</t>
    </section>
    <section anchor="data-centric-deployment-option-for-coap" numbered="true" toc="default">
      <name>Data-centric Deployment Option for CoAP</name>
      <section anchor="stateful-forwarding" numbered="true" toc="default">
        <name>Stateful Forwarding</name>
        <t>In the data-centric deployment, all IoT devices act as CoAP proxies with enabled caching functionality.
A forwarding information base (FIB) on the application-layer describes a mapping of resource names to next-hop CoAP proxies.
This mapping list is compiled statically, or is dynamically discovered in the network; future document iterations will further elaborate on this topic.</t>
        <t>Within the IoT stub network, requests traverse multiple proxies, install forwarding state, and build return paths for corresponding responses.
The use of IPv6 link-local addresses between each proxy hop is encouraged for a better 6LoWPAN compressibility.
Responses return on symmetrical request paths, which consequently consumes existing forwarding state.</t>
      </section>
      <section anchor="content-caching" numbered="true" toc="default">
        <name>Content Caching</name>
        <t>A deployment of proxy nodes on each hop enables a hop-wise caching just as performed by CCNx <xref target="RFC8569" format="default"/> and NDN.
Responses replicate on a request path following a cache decision and cache replacement strategy.
A simple and lightweight approach is to <em>cache everywhere</em> and replace <em>least recently used</em> (LRU) content.</t>
        <t>OSCORE enables content object security for CoAP and allows for transmitting autonomously verifiable content similar to CCNx and NDN.
Further details on cachable OSCORE messages is recorded in <xref target="I-D.draft-amsuess-core-cachable-oscore-00" format="default"/>.</t>
      </section>
      <section anchor="corrective-actions" numbered="true" toc="default">
        <name>Corrective Actions</name>
        <t>In contrast to end-to-end retransmissions for standard CoAP deployments, the data-centric setup performs hop-wise retransmissions in the event of message timeouts.
Confirmable messages arm message timers on each proxy node.</t>
        <t><xref target="fig-eeretrans" format="default"/> illustrates the default retransmission behavior: each subsequent packet traverses the full request path to recover a lost message.</t>
        <figure anchor="fig-eeretrans">
          <name>End-to-end recovery of lost packets.</name>
          <artwork align="center" name="" type="" alt=""><![CDATA[
Initial request:

,-------,  Request   ,-------,  Request   ,-------,
|client |------------|router |----------->|server |
|       |  x---------|       |------------|       |
'-------'  Response  '-------'  Response  '-------'



Request retransmission:

,-------,  Request   ,-------,  Request   ,-------,
|client |------------|router |----------->|server |
|       |<-----------|       |------------|       |
'-------'  Response  '-------'  Response  '-------'
]]></artwork>
        </figure>
        <t><xref target="fig-retrans" format="default"/> demonstrates the shortening of request paths for subsequent request retransmissions due to the on-path caching functionality.</t>
        <figure anchor="fig-retrans">
          <name>Hop-wise recovery of lost packets with on-path caching.</name>
          <artwork align="center" name="" type="" alt=""><![CDATA[
Initial request:

,-------,  Request   ,-------,  Request   ,-------,
| Proxy |----------->| Proxy |----------->| Proxy |
|(cache)|  x---------|(cache)|<-----------|(cache)|
'-------'  Response  '-------'  Response  '-------'



Request retransmission:

,-------,  Request   ,-------,            ,-------,
| Proxy |----------->| Proxy |            | Proxy |
|(cache)|<-----------|(cache)|            |(cache)|
'-------'  Response  '-------'            '-------'
]]></artwork>
        </figure>
        <t>Proxy nodes aggregate requests and suppress the forwarding procedure, if they already maintain an on-going request with the same cache key.</t>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>TODO Security</t>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization/>
            </author>
            <date year="1997" month="March"/>
            <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" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba">
              <organization/>
            </author>
            <date year="2017" month="May"/>
            <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="I-D.draft-amsuess-core-cachable-oscore-00" target="http://www.ietf.org/internet-drafts/draft-amsuess-core-cachable-oscore-00.txt">
          <front>
            <title>Cachable OSCORE</title>
            <author initials="C" surname="Amsuess" fullname="Christian Amsuess">
              <organization/>
            </author>
            <author initials="M" surname="Tiloca" fullname="Marco Tiloca">
              <organization/>
            </author>
            <date month="July" day="13" year="2020"/>
            <abstract>
              <t>OSCORE group communication can secure CoAP group communication across untrusted proxies, but in doing so sidesteps the proxies' caching abilities.  This restores cachability of requests by introducing consensus requests which any client in a group can send.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-amsuess-core-cachable-oscore-00"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="NDN-IOT" target="https://dl.acm.org/doi/10.1145/3267955.3267967">
          <front>
            <title>NDN, CoAP, and MQTT: a comparative measurement study in the IoT</title>
            <author initials="C." surname="Gündoğan" fullname="Cenk Gündoğan">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="P." surname="Kietzmann" fullname="Peter Kietzmann">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="M." surname="Lenders" fullname="Martine Lenders">
              <organization>FU Berlin</organization>
            </author>
            <author initials="H." surname="Petersen" fullname="Hauke Petersen">
              <organization>FU Berlin</organization>
            </author>
            <author initials="TC." surname="Schmidt" fullname="Thomas C. Schmidt">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="M." surname="Waehlisch" fullname="Matthias Waehlisch">
              <organization>FU Berlin</organization>
            </author>
            <date year="2018"/>
          </front>
          <seriesInfo name="Proceedings of" value="5th ACM ICN"/>
          <seriesInfo name="DOI" value="10.1145/3267955.3267967"/>
        </reference>
        <reference anchor="OBJECTSEC" target="https://ieeexplore.ieee.org/document/9142731">
          <front>
            <title>IoT Content Object Security with OSCORE and NDN: A First Experimental Comparison</title>
            <author initials="C." surname="Gündoğan" fullname="Cenk Gündoğan">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
              <organization>n/a</organization>
            </author>
            <author initials="TC." surname="Schmidt" fullname="Thomas C. Schmidt">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="M." surname="Waehlisch" fullname="Matthias Waehlisch">
              <organization>FU Berlin</organization>
            </author>
            <date year="2020"/>
          </front>
          <seriesInfo name="Proceedings of" value="19th IFIP Networking"/>
        </reference>
        <reference anchor="ICN-COAP" target="https://dl.acm.org/doi/10.1145/3405656.3418718">
          <front>
            <title>Toward a RESTful Information-Centric Web of Things: A Deeper Look at Data Orientation in CoAP</title>
            <author initials="C." surname="Gündoğan" fullname="Cenk Gündoğan">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
              <organization>n/a</organization>
            </author>
            <author initials="TC." surname="Schmidt" fullname="Thomas C. Schmidt">
              <organization>HAW Hamburg</organization>
            </author>
            <author initials="M." surname="Waehlisch" fullname="Matthias Waehlisch">
              <organization>FU Berlin</organization>
            </author>
            <date year="2020"/>
          </front>
          <seriesInfo name="Proceedings of" value="7th ACM ICN"/>
          <seriesInfo name="DOI" value="10.1145/3405656.3418718"/>
        </reference>
        <reference anchor="RFC8569" target="https://www.rfc-editor.org/info/rfc8569">
          <front>
            <title>Content-Centric Networking (CCNx) Semantics</title>
            <author initials="M." surname="Mosko" fullname="M. Mosko">
              <organization/>
            </author>
            <author initials="I." surname="Solis" fullname="I. Solis">
              <organization/>
            </author>
            <author initials="C." surname="Wood" fullname="C. Wood">
              <organization/>
            </author>
            <date year="2019" month="July"/>
            <abstract>
              <t>This document describes the core concepts of the Content-Centric Networking (CCNx) architecture and presents a network protocol based on two messages: Interests and Content Objects.  It specifies the set of mandatory and optional fields within those messages and describes their behavior and interpretation.  This architecture and protocol specification is independent of a specific wire encoding.</t>
              <t>The protocol also uses a control message called an Interest Return, whereby one system can return an Interest message to the previous hop due to an error condition.  This indicates to the previous hop that the current system will not respond to the Interest.</t>
              <t>This document is a product of the Information-Centric Networking Research Group (ICNRG).  The document received wide review among ICNRG participants.  Two full implementations are in active use and have informed the technical maturity of the protocol specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8569"/>
          <seriesInfo name="DOI" value="10.17487/RFC8569"/>
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgments" toc="default">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIADM2NGAAA+1a3XLbuBW+51OgzkxrZ0zFzsbORtttV5Gd2K1teW1nMp1O
ZwciIQlrkuACoGWt7b5KX2Tvtg/W7wAgRSq2k3T6M50uL2KJBHH+vu/8QInj
OLLSZqLPBmyPWx4norBaJmxPlJla5PjGRqWVqmATpdlQDU4jPh5rcdXvrndP
UpUUPMdmqeYTG0+rIlVTXsSJ0iKWSZEoXsZbW1HCrZgqvegzWUxUFMlS95nV
lbHPt7ZebT2PuBa8z96KQmieRXOlL6daVWWfXYz2Ruw9vstiyt7SvehSLLAg
7bPDwgpdCBvvkfQoMpYX6Xc8UwU0WggTmZxr+90PlbLC9FmholL22Z+tSjaZ
UdpqMTH4tMjpw1+iiFd2pnQ/YnHEcMkCLw177O3PP8Gsv/+NF+62N3goisvV
J0rDdvkjJ+/12cHgPTvg+bjSU/dU5FxmfQb/XfamlfCe+mbG5/HMr+qlYlX0
IDc//2RMW+5MS2MlLzrPOpI70url3/DcVMKYXqLyjpQLiDlPZrlMbUvMxUzl
3LCVZ59koO0Z/8pjth332HsuZpnE2pbYY27tTEJw92FXbiaLyzjjY/Zr9uYd
ey00brQVyHvz+u1VFaJC6RzbXAny0tmb4fPt7Vd94BGobD1g7GTvJD4cXfgv
dFmup8L22cza0vSfPUuzHk/yHjR7lir5bHurt739YufZF893X77a2em5v7sv
l697zq1h301HnU0GrLLjby8u+owzBKXk2slnueCm0sIx0dgqXcBjzM4EO1QX
a82GDVZbV9z59iCAl9fDUF5esPDDUD8q8bTH/iiF/THnxf0CTwV4++CazxcI
MB2BT0Kbe8UdIwnIQjywxonr4uhRYQc9r78R9xt3wKtL8dCSzxW2Ss5VYffT
dEXe5/qyy71VkQ9Q9KM2pigBffZ8a/vL5pYRWgpD3OvieO1Uq0SIFCnfMDVZ
A2927IwNhsfscHiy1lm7Nzrss8fYN3r9h/3hxfn+8GEuSyHENaqfFj36GEid
VETBZ6+2Xzx/+cX2B0wGG0FkVCAqmOPvRWLZuUgqLe2CzSXUHZ0PR2f7juZg
PdXbN1Iby/avS9hNe/MMOxDxpVHF/wS1V0rSB+LuLU4rAotn/P8S+M+3/hng
b78ClA7fHJ6yE2Hnvg/yUAEV4uFocPr5NerF1s7uzm7vixfbX75s0bFG9oWa
c52iKp3tn19Mqgx9VqiOqoiHof17L8bQEHEgXV0zKQRwzY6UumTcul6RjWAm
YO66SRQxqnu/wLwt6BeYB5i//LT8voLcKIrjmPGxsZonGAAu0CXJFljrWaVo
qMPWIWGDUbOVymkO6RPUaaYx/MjEAxWoBjRVoXJVmWzBrmDFRPJxJtCm+Xxv
ZxhEpjNVWbAkbL5JCJ/PZDJrlknDxgojEbPKOddQCKzgKcmYKWNNDypj1Qzu
LrW6EgUbYwSayESiNmC/klqXpMq4dtMYdYHYnMxFQ5NSR9iLzsUVDU2Ml9iC
JzOBmYYW5hBAu+ZYCmUg0ms3FuSHULoaPp+0XDQcnlxv+MIFrdPYcbm9APVs
Y5P2LpURjCcJBovayLQxP5UaVREeVL5/DY5iGV8I3YsO0Y2V1JIVWONVHqoz
wd6/ZSlMylSJvXKRzND6mxz7z5BWTFWWmNxaEWrElQQqA7hNNyExLjkglcAf
7gYZUy9UvlqbulpXxjtkcEp7XAOybrmv373Ih6juB6CbSbQc0yLC/HIgTpcD
tPIDtN/YTaWUUJ2EieAW3b1zV426+0FL7hUIf1DHA8O6F8lXhJ9mLTUj8G2W
9jwlkCrSDOPOE5qRtUqrhLaOovsy+ckqOWR4Be4nQTIV3AmtdLESYe9JgjWe
T1x3k2QcWEiklT+KgtjtR5cwqTORKLMAB/KA/IaIU47RB2lVkKh1uUHexeIK
HoJi2KaWOQGiPXmcW2h3PpYZBRKrqrH8oZK2jYuAAdeUEWMbeIoM45Ze1Lg0
AP7eidnwYFmX0AEJDCsyQjcIb50mRaByvR0psHdyTiHUHMyEqxHfryJsgB0c
gdi9BGI8TSVFgmfgCB9DqiJS1zQBNUoFz9I6AMa49MEm/AqJgHIUAcsKqs+I
KVVs2nnCx4gpOVfAlS0IicJlMNQsbhZFggRWwEmb8GQZz8ntjX+FDZzx6aLU
IGMBb7ekkKMLowBeaaEx0cCJBLUtjXZGTgvkzIQTtQFzApPxobKWJ5egsZ7w
RNBG63uopSBUhZ020EUUSH2xmsTn8L3EkvW9PXW+AVwPsowSrwgpUNrKqZVz
jFvALeU/wR1aAkPWW6lyYwnBpmsB3NUFwmC6sUMqRSlNCb0+a+Q5gk5aOPEc
Mh2l67F8zhc+Hpkg7+KBmFAGdxWAhMat8kNZXORjkabkN0EWogjscw0/ifZg
4CBwcxPOIe7umJmpeUiCuAlUF/Ciy7yAACVZvEypBLo6VLfrRKHSgFh8REER
DgsAlao0XGz4lfOHP4UQrl4dnlKGbjC6SfK1jWFODqtqkxpyueqVsiueVW5v
slMWCdzlcqAG12qWwm2ZmselmgMpmTKmxcCgImk70eKHytUGaidNhvaSQhXC
wW19JMJEOhU9X/s/TMF1tg7RaifyJvs6ZJqPJuHHsnkvOhP0SjeGwrmD9jMI
ZTOI3t3d3NTNOwILxZBfhbGkpXMAvJY502YQBM6RYbkPpxW+pAevmiqjJoIS
/RncJf2xkWFHvJhWfCq8Wy7FgvCUGrZ2/O78Ym3T/2UnI/f5bP/bd4dn+3v0
+fxgcHTUfKhXnB+M3h3heRQ+Ld8cjo6P90/2/Mu4y1ZuHQ/+tOYT6tro9OJw
dDI4WqtDETWhIBOBubHwhEHKobSCaHfC93p4yrZfwJPh3A6+u7n5Fb58uf3y
xd1dNJ+JwstSBVDjvyK0C58atPM0kkjCS4nwIPlBAtGqYDOhCUNPPvlIPHry
hJ3X+fdNkxmpwjpgPtAZbDoFKLSB+2ieLKnR6T4cCHzCThuGTaoi8dUCJOpF
g3Y+biGXjTmgvP7m8PVG3XfB+rq5jV3v1elhcjwOOb1JCL7CUUMnrm2MEtHR
L5Tu+kXMCK7VpewhSWOqS5CXUVdHaQBhXGBHfwtdoUmQK7RoEmhg/1cwkci0
ZCiKiw70mUv4bVJprEcCzfhY1cnOkdqqkqpe9B6eW56W0vHpeNmfu4RCfQN4
dEWncywHfWSZidqyTdegU4haznVl1uNqXMksxT6uFaIG01VFWK7hulIVaWAl
PhrvJ4G04crc4enVbji5Vgl1601RH0M/gc5fcFdt1fWCijK5TRRogDRonDox
nJZSed09Uu9PByfO47SJ9JmVklAQXesI/5hFnguCIYQGD3jVN5fTimlSLX2p
KPjimkZcX7E6nug57NcnX0OPTlTnTvKdBEN8KlfBODLLw5qAt+w8AsK/r4zj
AjIowRlWjxeMZhHQ/PdE851d4nw4UOtaWzfSVBo6ZkL/DOWG9udOEiXTBPlT
+Vrtb9EG6EfCmTtBa+o4ZmReuq4pReymMwSK/m1GLeagx576TWgOW8wplTx1
b4RN2VM0BobqTeJ9DESkT9n60dm7jbrrglPDcWHtn4eGlToDOQmcTPMYhNKF
yaV1MfvY/AqzJM2U0N35t3Hpm8CwVFguMxc5ss29HBQEOAwgach2mISy4pmM
VHwY7/X8D4Hhxyb/O2C9Q6yM+761dXdXo0jTiEi/egxccjMugZKa1I+RfuiC
Y6ti4fwZjDTG5QQyu1uOlxAMM3AnDRtwoqzRZZb4W903JBDX9hKUg8XMoq6j
4wevgX5MO7lzS+MPjs6ovVQvgb8kA+y+uZnIaSxEEEsdQJZVHnW+SU7FhCMz
rSgG9s/QqCnd95uaahx4C6Anl+hs67zmd6G2sEsFN3K65EvdKh0PBH2h1V+b
CxFAy7fMFv0o2oz9tclcm0EbMvb4zeg2yVwLfBu3rlsaoyC+ffN3t37MYrfR
bTj0wd/r5Tv1zc5G9c3oN+HOb0gNnxAYe/wm+qWoVrnr4/+Grb+9z6x/na2t
wN702ZMO9vyR79dr+22SOYC4kcZBxGPL9Nbu6H2uXTGN0YVMi6/XiFpC41FA
9RLTrY7Vw9HND5ju6lajVYk8k5dw1vfGBm1EJerZbuWAZ7U7+jfAmZ06Enej
+ejN6HbdFYaNLpzrm5241zf/43BeXp9qa/ude2y916zOO59s6/J6FM4rYD5Y
5vX7oez76xUEfQzfp61+hk+nWkyp3WhaSqqgdDap3UnoTLTbJncwmaKzRXs5
CQNJhhkvXaCHxsDDaS6hXi2eKt9A+jg5NR110I6HRgWjnJtTmp8aUYqMTOs+
GfMe/X+Z+qk7ABycDD5c1ZmE6fi5UH4l93U4nCOO4THaZJBcFmqO5n7qiis8
VVT5mJr4r9cmGKUEuciJ5s1KVJV/ALeHefNuJAAA

-->

</rfc>
