<?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.29 (Ruby 3.4.4) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-spice-use-cases-02" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.29.0 -->
  <front>
    <title>Use Cases for SPICE</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-spice-use-cases-02"/>
    <author fullname="Brent Zundel">
      <organization>Tradeverifyd</organization>
      <address>
        <email>brent.zundel@gmail.com</email>
      </address>
    </author>
    <author fullname="Michael Prorock">
      <organization>Tradeverifyd</organization>
      <address>
        <email>mprorock@tradeverifyd.com</email>
      </address>
    </author>
    <date year="2025" month="July" day="07"/>
    <area>Security</area>
    <workgroup>Secure Patterns for Internet CrEdentials</workgroup>
    <keyword>SPICE</keyword>
    <abstract>
      <?line 58?>

<t>This document describes various use cases related to credential exchange in a
three party model (issuer, holder, verifier). These use cases aid in the
identification of which Secure Patterns for Internet CrEdentials (SPICE) are
most in need of specification or detailed documentation.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://ietf-wg-spice.github.io/draft-ietf-spice-use-cases/draft-ietf-spice-use-cases.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-spice-use-cases/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Secure Patterns for Internet CrEdentials Working Group mailing list (<eref target="mailto:spice@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/spice/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/spice/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ietf-wg-spice/draft-ietf-spice-use-cases"/>.</t>
    </note>
  </front>
  <middle>
    <?line 66?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>There is a need to more clearly document digital credentials that utilize the
issuer-holder-verifier model across various work at IETF, ISO, W3C, and other
SDOs. This need particularly arises in use cases for verifiable credentials that
do not involve human-in-the-loop interactions, require strong identifiers for
business entities, call for the benefits of CBOR encoding, or leverage the
cryptographic agility properties of COSE. This document covers multiple use
cases for verifiable credentials that help inform both the required architecture
and components, as well as to frame needs for clearly defined message formats or supporting mechanisms.</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?>

</section>
    <section anchor="spice-common-patterns">
      <name>SPICE Common Patterns</name>
      <t>Within SPICE there are a few common patterns that continually arise:</t>
      <ul spacing="normal">
        <li>
          <t>Selective disclosure with CBOR based verifiable credentials</t>
        </li>
        <li>
          <t>Cryptographic agility support via COSE, including support for PQC, and
to permit use of the same signature algorithms with both selective
disclosure as well as fully disclosed credentials</t>
        </li>
        <li>
          <t>Strong and long-lived identities that may be correlated with public key
material for verification and permit binding to DNS or existing x509
certificates, as well as providing ready access to public keys for
verification utilizing HTTP</t>
        </li>
      </ul>
    </section>
    <section anchor="spice-use-cases">
      <name>SPICE Use Cases</name>
      <t>There are several expanding use cases and common patterns that motivate
the working group and broader community, including:</t>
      <ul spacing="normal">
        <li>
          <t>Microcredentials, particularly in education</t>
        </li>
        <li>
          <t>Digitization of physical supply chain documents in multiple
jurisdictions:
          </t>
          <ul spacing="normal">
            <li>
              <t>CBOR credentials</t>
            </li>
            <li>
              <t>High-volume system-to-system exchange of credentials</t>
            </li>
            <li>
              <t>Regulatory data and business-driven information</t>
            </li>
          </ul>
        </li>
        <li>
          <t>Credentials related to IoT, Control Systems, and Critical Infrastructure</t>
        </li>
        <li>
          <t>Credentials related to authenticity and provenance, especially of
digital media</t>
        </li>
        <li>
          <t>Offline exchange (in person) of credentials that may have been
internet issued</t>
        </li>
        <li>
          <t>Attribute sharing for trusted telephone interactions</t>
        </li>
        <li>
          <t>Embedding credentials in other data formats</t>
        </li>
        <li>
          <t>Digital Wallet Initiatives</t>
        </li>
      </ul>
    </section>
    <section anchor="use-case-discussion">
      <name>Use Case Discussion</name>
      <section anchor="roles">
        <name>Roles</name>
        <t>An "issuer", an entity (person, device, organization, or software agent) that constructs, secures, and shares digital credentials.</t>
        <t>A "holder", an entity (person, device, organization, or software agent) that
stores issued credentials and controls their disclosure.</t>
        <t>A "verifier", an entity (person, device, organization, or software agent) that
receives, verifies, and validates disclosed digital credentials.</t>
      </section>
      <section anchor="microcredentials-in-education">
        <name>Microcredentials in Education</name>
        <t>Microcredentials provide a flexible and verifiable way to recognize skills,
achievements, and competencies in education. Unlike traditional degrees or
certifications, microcredentials offer a modular and portable format that can be
tailored to specific learning outcomes. They enable lifelong learning, career
advancement, and industry-aligned skill validation while allowing learners to
demonstrate their achievements in a verifiable and interoperable manner.</t>
        <t>Common use cases:</t>
        <ul spacing="normal">
          <li>
            <t>Microcredentials for industry-specific skills such as cloud computing,
cybersecurity, or data analytics, enabling verifiable skills on job
applications, LinkedIn profiles, or digital resumes.</t>
          </li>
          <li>
            <t>Recognizing individual competencies as learners progress through a program,
which allows institutions and employers to verify achievements more granularly.</t>
          </li>
          <li>
            <t>Stackable microcredentials that allow learners to accumulate and combine
microcredentials into a larger qualification.</t>
          </li>
          <li>
            <t>Work-integrated learning and apprenticeships: skills and competencies gained
through internships, apprenticeships, or on-the-job training, enabling
employers to issue digital credentials for workplace learning experiences.</t>
          </li>
          <li>
            <t>Recognition of informal learning, community-based education, or non-degree
programs to support individuals without access to traditional higher education.</t>
          </li>
        </ul>
      </section>
      <section anchor="physical-supply-chain-credentials">
        <name>Physical Supply Chain Credentials</name>
        <t>Physical supply chains provide several unique scenarios and requirements for
implementers of digital credentials. There is a strong movement toward
digitization of physical supply chain documents which are typically exchanged on
paper or scanned pdf form today using legacy approaches.
Some steps have been taken towards digitatization of supply chain documents
using XML, however this has proved problematic over native binary formats due to
the complexity, size, and volumes of transmission often involved.</t>
        <t>Common use cases for physical supply chains include:</t>
        <ul spacing="normal">
          <li>
            <t>Regulatory data capture and exchange with governmental bodies</t>
          </li>
          <li>
            <t>Requirements around capturing specific types of data including:
            </t>
            <ul spacing="normal">
              <li>
                <t>Inspection information</t>
              </li>
              <li>
                <t>Permits</t>
              </li>
              <li>
                <t>Compliance certification (both regulatory and private)</t>
              </li>
              <li>
                <t>Traceability information, including change of control and geospatial
coordinates</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Providing the ability for 3rd parties to "certify" information about
another actor in the supply chain. e.g., Vendor A is an approved
supplier for Company X</t>
          </li>
          <li>
            <t>Passing of data between multiple intermediaries, before being sent
along to customs agencies or consignees.</t>
          </li>
          <li>
            <t>Moving large amounts of signed data asyncronously, and bi-directionally
over a network channel</t>
          </li>
          <li>
            <t>Identifying actors in a supply chain and linking them with legal
entity information</t>
          </li>
        </ul>
      </section>
      <section anchor="iot-control-systems-and-critical-infrastructure-credentials">
        <name>IoT, Control Systems, and Critical Infrastructure Credentials</name>
        <t>The deployment of digital credentials in constrained systems such as IoT,
control systems, and critical infrastructure environments introduces challenges.
These systems often operate in environments with strict security, latency, and
interoperability requirements. Digital credentials play a role in ensuring
secure device identity, access control, and trusted data exchange between
interconnected systems.</t>
        <t>Common use cases include:</t>
        <ul spacing="normal">
          <li>
            <t>Device identity and authentication ensuring only authorized IoT devices can
connect to a network or control system.</t>
          </li>
          <li>
            <t>Restricting access to critical systems, such as industrial control systems,
SCADA networks, and energy grid controllers, to only authorized personnel and
devices.</t>
          </li>
          <li>
            <t>Role-based access control (RBAC) and attribute-based access control (ABAC)
policies using digital credentials.</t>
          </li>
          <li>
            <t>Encrypted and authenticated data exchange between industrial sensors,
actuators, and control systems.</t>
          </li>
          <li>
            <t>Verifying software updates and firmware integrity using signed credentials to
prevent unauthorized modifications.</t>
          </li>
          <li>
            <t>Tamper-resistant logging and auditing: digitally signed operational logs and
sensor data to enable post-incident forensic analysis.</t>
          </li>
          <li>
            <t>Temporary access credentials for emergency personnel and automated response
systems during critical incidents.</t>
          </li>
        </ul>
      </section>
      <section anchor="credentials-related-to-authenticity-and-provenance">
        <name>Credentials related to Authenticity and Provenance</name>
        <t>Due to a proliferation of AI-generated or modified content, there is an
increased need to provide the ability to establish the provenance of digital
materials.  Questions of authenticity and the means of creation (human created,
machine assited, machine created) also abound. In cases where an AI created the
content, providing the model information related to the generation of that
content is becoming increasingly important.</t>
        <t>Common use cases include:</t>
        <ul spacing="normal">
          <li>
            <t>Determining whether a received piece of media is human created, and that
the content is authorized for certain uses.</t>
          </li>
          <li>
            <t>Providing the ability to trace training materials for LLMs and similar
models to output</t>
          </li>
          <li>
            <t>Understanding if media was created by an authoritative or trustworthy
source</t>
          </li>
        </ul>
      </section>
      <section anchor="offline-exchange-of-credentials">
        <name>Offline exchange of credentials</name>
        <t>Many real-world scenarios require credentials to be disclosed, verified, and
validated without continuous or immediate access to online services. This can be
due to network limitations, privacy concerns, or operational constraints in
environments where connectivity is intermittent or unavailable. Some digital
credential frameworks assume online verification mechanisms, which may not be
suitable for offline-first environments where entities must verify credentials
using locally-available data and cryptographic techniques.</t>
        <t>Common use cases include:</t>
        <ul spacing="normal">
          <li>
            <t>Identity verification in disconnected environments, such as remote regions,
military operations, or disaster recovery efforts.</t>
          </li>
          <li>
            <t>Travel and border security, where credentials such as visas, vaccination
records, or national IDs must be verified in locations with limited or no
network connectivity.</t>
          </li>
          <li>
            <t>Access control in secure facilities, such as industrial sites, research labs,
or private events.</t>
          </li>
          <li>
            <t>Device authentication in air-gapped systems.</t>
          </li>
          <li>
            <t>Peer-to-peer credential sharing.</t>
          </li>
        </ul>
      </section>
      <section anchor="attribute-sharing-for-trusted-telephone-interactions">
        <name>Attribute Sharing for Trusted Telephone Interactions</name>
        <t>When a user subscribes to a telecom operator, a subscription identifier is
issued that enables the operator to identify the user. However, the subscription
information is limited. Operators or Over-the-Top (OTT) providers with the
capability to verify user VCs, which serve as reliable proofs of users'
attributes, enable a user to share those attributes over a telecom network.</t>
        <t>Common use cases include:</t>
        <ul spacing="normal">
          <li>
            <t>Bank employees taking calls from customers can receive digitally signed
account information, which enables a smoother experience for the customer and a
higher level of assurance for the bank.</t>
          </li>
          <li>
            <t>Identification of the user across network domains supports mobility in a
larger area (e.g., cross-border traveling, studying abroad) by endorsing
attributes (e.g. , “subscriber of a legal operator”).</t>
          </li>
          <li>
            <t>Disclosure of a user’s role or affiliation to other parties during a phone
call by presenting the attributes endorsed by the operator or OTT providers.</t>
          </li>
          <li>
            <t>Operator or OTT provider service provisioning by verifying user attributes
(e.g., subscription status)</t>
          </li>
        </ul>
      </section>
      <section anchor="embedding-credentials">
        <name>Embedding Credentials</name>
        <t>TODO embedding credentials use case</t>
      </section>
      <section anchor="digital-wallets">
        <name>Digital Wallets</name>
        <t>TODO digital wallet use case</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>There are no security considerations for this document.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <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>
    </references>
    <?line 304?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors would like to thank the following individuals for their
contributions to this specification:
Yurong Song, Lun Li, Donghui Wang, Fei Liu</t>
    </section>
    <section numbered="false" anchor="document-history">
      <name>Document History</name>
      <t>-02
   * Added telecom use case
   * added contributors
   * added acknowledgements
   * added security considerations</t>
      <t>-01
   *  Added offline use case
   *  Added IoT use case
   *  Added microcredentials use case
   *  Changed author affiliations</t>
      <t>-00
   *  Initial individual draft</t>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact fullname="Yurong Song">
        <organization>Huawei</organization>
        <address>
          <email>songyurong1@huawei.com</email>
        </address>
      </contact>
      <contact fullname="Lun Li">
        <organization>Huawei</organization>
        <address>
          <email>lilun20@huawei.com</email>
        </address>
      </contact>
      <contact fullname="Donghui Wang">
        <organization>Huawei</organization>
        <address>
          <email>wangdonghui124@huawei.com</email>
        </address>
      </contact>
      <contact fullname="Fei Liu">
        <organization>Huawei</organization>
        <address>
          <email>liufei19@huawei.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61a227kRpJ951fklh+2Naiqdtte7FiYnbFakqcFqFtyS+0e
72IfssisqhyRTJpJVrlsGPBvLLAL7Lfsp/hL9kREJpmUqn0B5qVbReYlMi4n
TkRysVhkne1Kc6pm77xR59obr9auVXe3V+eXsyzXndm49nCqbL12WVa4vNYV
hhetXncLa7r1wjc2N4vem0VO0xcff5L5flVZ762ru0OD0VeX918q9ZHSpXfY
ytaFaQz+qbvZXM1MYTvXWl3Sj6uzl/gPEsyu3t5/OcvqvlqZ9jQrIMlplrva
m9r3/lR1bW+y3an6NNOt0Vj1zuR9a7vDLNu79mHTur6JT4261V1n2loOd1XT
36ZT5+0lCYGt/Sx7MAdMLE4ztZDjZztT99hUqd+/mFJy8tl7yGLrjforLUHP
K21LPGetfUEKXLp2Qy90m2/xYtt1jT99/pzG0SO7M8s47Dk9eL5q3d6b57zC
c5q5sd22X5FiyR77jZjk+YdtRJNKKNR3yYaTyUtZc2ndLyzzC6+W264qZ1mm
+27rWtIptlRq3ZelONDsZQtlqX/v4QbljF/igLq23+sOfoMB960uzM60dn0o
ZIAR3a1o5vJ7nvnFhp4tc1dlR/Z4bfOtNqW6bV3r8offt82samTaF10yhLbC
ucgTu9au+o5P92Trb/rWwep3+OfIpq96vTc23cxj4IHnvPhiy2/5TE8Xvu5r
dW1/05qlLfv6k49/eb0LbLntrXqvf6OkewwsZNKLTz775cW/NBbC9r9R2n5t
7IvP0xWz2rUVZuwQhRkh0PBrAeSif5ReeZgn77Lsfmu9AkD1FTlWYXwO+wDO
drq1rvcKvqnYN1VryPkL1TmVtyYErTLfwVnqjQHUKZ1129YY1ei2O6jKwdPU
MyBab9q52rqyoP/ZI6xpT5bqfmuw+riDtgUt021NZnn9tc355Mqt1X4Lt1S/
FUvUMwajE+CDySrnO1q4NhAfS/nG5MnaLY7dQZt4GRXBb5aZKKuyRVGaLPuI
dmpd0ef0llRnIArUp2VlKKZyeJKXRrflIdGqBS5AV6PaPA6pO9V3trTfGzkx
62khalpELQUt6rx1fjQKQbXCfMoQc3V1dzNX7z89nytd43xYrM3uLm48KRjS
sWxkEpv3JQuGVUjd0Mioe1KkbKpXpXkiKnKYqh1pcefKnVHbvtL1wtYL7LYo
nWvwBlbQrBo/h7N821voAm5GER3NaVreKVv13tYGJ6LHnTWYkeuyZCmwolqZ
2qxt58la5y9v3mJc7gpkBE5yJcGK3oje8vbQdG7T6gYOovQGGoXzAYQa09LK
vMTN3WXQxmCU3O1ImqovO9uU7IbZb1KF2pqyURJXagV1s8ThwAUnJNuZvIOf
ZmQQhGTjaqyAQ2rYzuCc+B/esm4R72wf2XRwHJy9xlIVNETHlAj2dHTfN43D
uaDTylDkWV/5Jfnmuat3JCbUz35wQYtY/s2uqpCpyXGw1+z1u7t7og30v3pz
w3+/vfzq3dXbywv6++7V2fX18EcWRty9unl3fTH+Nc48v3n9+vLNhUzGUzV5
lM1en30zE++c3dzeX928ObueSaSnFkGoklZWRnypaQ3BjfZZRCVGh5fnt//3
vy8+Uz/88E9vvzz/5MWLz3/8Mfz444t//Qw/9ltTh1iooU35CRsdMt000DBD
FYyQ64bCUszit25fK4poaPMP/0Ga+c9T9adV3rz47M/hAR148jDqbPKQdfb0
yZPJosQjj45sM2hz8vyRpqfynn0z+R31njz8019KuJlavPjjX/6ckQsxZMKR
qgqwGCE2y96D1EBl8rZj0CNTabU2e/JuGt1EQOYIoTRv6x5KDmCDRAR6aEqE
BRIRANHnpfOE5HssLiG+QvAVHwg8zD4/GuchHtTOao7yOYyblz1BxfCOQuv2
K4FHophOARoq2zH6AR0ofD1ForebWlPcwj3A3yFZ5UVADnMf5cciyQmSmKYc
fojvcJjpCe4EC8kxS/yxKLFUEaCRkYp1V+kDhUDu2phwWYKmX5U4N4KY2TCU
Tdl3hKqQzGjxcLoVCgZSA8578eaOwMN8Zz1Dx3f/8vHnWCYnhOSpZopNQM+d
5ckoEgrYMM8JrElzgxgC5Gq6vSQ0mvjq/v529KmhTIpZkxzIM4wThWi0iJpQ
AQHOp65VOVgAAmdktX0oE7jS4Dlg+WCdLc/tAX+HxCHYCUFuwU5Hu8ynqRF+
bpDg+TQYfUGZO9AvcpVme/A4a8m+heFAYMyICMYpNSYUqObvqKx8YSUnMt8V
T0/dgh6+spvtAnm1Jx88+M5Ui84t5K+RYGH7xxPfmg3kBpmG0+lOiwZCal0U
LfyrVgMB5AOdJ8ksIXRX7n5OGQQeWqo73tgLhJ4jDPjEVzXSFdJ5L5ntg0tR
7UKPcwpPdkc4k6l1nZu5Mky9GBfcmsNImFGFalZjzZv1mjFpOPQzaBT+DKJ/
8kgBY7Rs9Y4Yg6mxoI1ckOlUgSXPOqk4oNotsAjewiSj7T0LjJhutkjPE/6C
aZcooAt2ynRPSMP8StQd8nL0E5zjPY6Gza8o8TLn9hQD0fsxzOc9V/h4/JF6
60oacFajBmX2x0lSONFBPZNzz0EHdpaUl9YCzIO8W3d7huIN5pwM2CtWggE9
s+VgSTo+IusIGUXGO0NFy8zzHyBC5uGRxC/ZBBP9SVizm5EBjW0TJBUxIvP9
RwjSmtyQEYaqI6hip0tLrRGfYPVxvcBKjxGDnOBywIjsyWsBT86PJRCXMhnv
OSa2PZwWkQLp3KYm/u8fbAkoyjSoI0CxCmQxkEfQoDq3QtgHcFqqd3VpH8CY
UGYzzYPshdmg/iKimI3YLoS8eiymW6/hx5oKDMI+CVWkS5ZQPDs4FMywAt6i
QnKtxHgsoBQR1pqCxPUdRDVcc4BnIt5pmdKuDaW6YRzRfEjYZrrYESLQSeWg
SFaIyPawgGk2RH5ZJ9FSBL8oAEmVZen2Ni5JDL5zIIgVez1MGrwq1STzvVT/
sh/CnWoEfoJiBmvB3oH8DInoaM5gBBkEHpQhVkRqQJ2KJAq/6sWAPSXdOSXc
wwoSh44bu22AbV0egJgwEyuOjpeIG9aFWH93K2p5IfWMhr229YMprmryuzU0
5GXd4M2Iw57MklGyEHej1YkawEl78vfUwyD2oFesB2+itL9Fet3gTPJIV3QU
KcfZGqRg8IquH4sPUzWlO4h15CiHqUm4UMZateTdJdMjnT+INR7rm/2Q90rN
TrSkrygBmhgr4DyUeJ8sAGtjuMJeGzj9tzj3EBu0NbUbF+QRm5bT2ODWtCzU
3XJCM35rG38a7fEkPDeaqjZimEFhkox41vzxMmwlJ/UzzEphbCVCogtkaqpG
htOjvQRyR6JCTalzMwoPXgXNQ7iJ/SOVCbygTGMzkqaFcPEBbFjYGtIKwECy
4AksWOTZo1MJawYmJMwxxaktCA/sMIIZA+1tJFd3Qq7OmVwlNCPLbo/xrxFy
I6PEIb6FrnwOXbbWia1ChS7+R9zVQrv8kxQMjRzLACpp8oReRuXEiXEoJJwi
K34nRwyRQ8XuoaGBGBP5DpWsWaNhN85pOcESYLlYMyJjxwKpgwge4d9G5wd2
K4fQIhvfOSKQnWn8yIlUpx/oX5Y1Zv9U3ONSZrLJ315fU+duT3qVan0bygPD
xA7RStQyV9RMUTVTHio8NBhp7FoUPZX1zNcpXCgnEvh5JL6QjZn5sgngJLUP
lyD43TF/5Y5TcQSc2fGPqtsH1i+F52OajMJfqjxCqsg0ucra0Dlq7gCWKPoK
hDXPTzxHI7Yp8nkNLjMj/tPdhTgSbZKUHUTVr2oax0pPGTm9uuV6TRj9OWnI
UmpUkwyunnEJ2o4nEWrNtdAJT70HezV6JXVxskdaEielRCD7tMzGOI8qCw7P
reXcuRajiR/h8LdDLUgWjOuT5j9tQ1/RcIDPRODDLN0cEwADlLRqIc5g2Jw8
pepOTLZUZrlZztXXpi4w4oxjrhb/3jGs8mjqidLmpChdH9TfSETt2Vuj6lem
25PrD709BmKuMVrmgCuzpvyzMmw/mJUEZKJCzW2kdQdkIyLJuE6dOSQ2oiWC
pK+hEYpAyiZKV/AH6VR6YS6S0/2hRhKqXe/Lg/j5yi4KuFEuIFhSIc9hQ+3j
jlu6ZJ7alNjiShqmB05CpLLAYibRyp0EpP9gnEp8mICBDBmoc+pthLK/u9Sb
IjB1EgtDaYkx8DhskqxSh3BKDEXtSI1Ihix6oE9lyKMMdiqDqXcW2ox8Ttrw
sA0UgYoLPg3DyHVC3EvQgxlex7cTkyVYU1gexbkaCRlRiToXc2UJQxSfTxPI
cij5JtS/BDxrhVOFHT1DRCZ1WCheYseHtpHsGDQhGoiVKXvRgE7BpUUojK/h
RqNij2FjCoAX042F1sQ6XeI0yio9U7mABEIXZKsguKdSgFisbM8MbHBdCZLE
oEI5RMXixZEJDDYeLB/9InBqy7R06h3Y9+787OIsbhj8xYALbg5gknYoLEuk
8znt8/gkUkPWpgyNwHAqFhQWC6RnahP17O3Ls/MT0VjsJHxg5BmNJG7kQM8J
OCSHHi0sF+qy5psLWmdqjQ/ZPtUOXecDE0grQIeeMsJQME70Rjt9zfyboS4W
yX0j5S/NWNu24odCgMk/RPAAZxMi7pj7GbppAMtKlIsyciw3add7DWrcLlBB
WN9pDC/dZjNw6p64IHJj1A4sFbaTiBWeiCk+GEtOLJqBbUOB2Tjfgbjn7NmU
FzCKusNUUGFflgMk2rVESKK9HjFnBHRLUH+YOgiZxFVsDpyhoU8oSIyALoUE
SwJXIkPoGXygN3b2uDd2O/TGsuyCeZJUWVQ4twNFO7tabMjReRnXBl0bMTZX
0N3AUgkicEJ20HgrGelxmsBJh56KfevlAmts0yWgnsVOMwBPfdVjBpd4GPCk
zUdrVEbLW5JAaAtfFMpvU8yxHqrAmprm3tIDFR+EESf8tQuzhrpYIhMFNNtL
17iGLuJQuf2LGmgmNEVuTVMekliBBgR9BgVzsygsRVpcoVSqpE5mXeJP6g1X
3B+pu1+HW6IbXM6R4MJ7VGhGAYesESUzI6H9pkoK6tQdl5JGJYIlAccXhmBc
Wq5x2dePczUpvnIz1JjD/YEEwPX1a0ECbyv6eoYKaNIfgzXYWwMCt1Dv6gLh
0YVOvY3S77UfDLI6MGMTGTspBmKvFZjdbYnyeNe35O6Ikifd3kct7uw1MTws
Xi4wvSySgi7eL0/BiS5Oho7e0PQTjWax6VcMxWm4pqIbdeKkFZ+ImglDqkIK
IQG9aSVVyB1y6IhJYTNkwBLa62JXhpk5IAVb5NQDkHI/gbaBHjGfyabkhJ09
pFmU1MTifCCxtmNfwGqA3x197QQcXCou/WLQJp9n8BUz50sKObpgCEeaXNuM
V8nzUJ5SX53u+3FM39uhKUhdQ5q+QNLwnToi9XCZVcHosfWTGjVUr44L38Vw
hPECY3qh30E0ruZ/leRcRXYzORoVtfCIgTGlIo/EA6zOdXSJv2HzcQsJsUNZ
YzBabKx50FIENHVvsRNq9zUU00muaVF2S/ZYoYbCqJFbBqMm/ho339GS8Fa4
HVVdUhbS8ijYpfMSnebqIuh1ZQbnphOSNgWZpQIgT5RUUVPCHsqLxKNI3LMp
gcFCgaiudU7H51rpCDcj6OZvPLyhrx1Am1esM6rGpSJVzBBYJ4F7PqKbVL3Y
drGhG/kiJSu3BqShc4vG0C3e6Mjh8kbS63inc5fc6dwH5nw/3OlcpXc62XsI
AByG99B3FKv4pRPnXLoHAuYHa7t2zrUWj2lE4OELFsRiFq42uC8pVISvM4bp
3K8LJRy/oE2X6pV0Uuah+B2Xz9JUhVgPFlyqm7AgI9TNjnSzNYt716hnN/f3
JzG1t8HynBJ1kyB/iEA+9NfnQ3wTohnx/FK6zFjJrTl501j/z9lAd2Nb2kTl
Uc9vyw2sLYB25MU+1rNRm8Hxfi1yX+r6IfY6SZGaK1oCCCSoFutISU6nJOgN
ifQJdcwQQFSLT5sfct5oJFi1ctKJGNujw2dHcR/hf1loU9LnRiVzHli91emE
FSRfjuV68rlaNHr8dCvGYAFOSf2p0DSlTvjQssGWoUNNH+eqZ9IQ4fmLgCcd
Iwx3a33XF9If4EvvE0q/3DshgE2sJ+uoufr5p/8e3L7l80ivYPDan3/6nxMO
2fHjBh5F5/j5p//yUtji6Hq9hsxyVsqSrM/YCgrUGDyWYjDj77pW9EWWoU7L
QE5G+URo4Q+TICKXv78ffZxku/nAy5ij5QH1D2mnVcgGh/B1QZvsmwX9TsIc
BKfr/QmjzHgFPO2A3FzcwFuPXQ9H9+bp0zvhODFWg3u5KU5mqPgpNnVnPJ1J
j19vhU8majdkFOlJDaOCSybfU/FXYVdnb86OrJd+dkUdXazLIwNWxi8fVzp/
oFXO8ofa7UtTbKQ5/MOpfGBuin+brXFwM/tROkPC/egDxb6k3tSDEcJNAU6m
Xbt4fZdeFoRosu34fTAfiadC1Mn3mqdZ8pXwPHzZO598kTsfPqGF7BfxnK8s
3UsfILw6Ir1Sir7Bx39/UGdFET4NIBAbTMTvNL9LvmP26XM9KEraROm7Dxgu
bP1Choa9A816tHd4SR2Zoy+eXHs9GnUe7hjESmkURyk+DiPlA4YyvSfkr9az
/weFTsAG/DAAAA==

-->

</rfc>
