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

<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://brentzundel.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/brentzundel/draft-ietf-spice-use-cases"/>.</t>
    </note>
  </front>
  <middle>
    <?line 47?>

<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>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:
- Device identity and authentication ensuring only authorized IoT devices can
  connect to a network or control system.
- Restricting access to critical systems, such as industrial control systems,
  SCADA networks, and energy grid controllers, to only authorized personnel and
  devices.
- Role-based access control (RBAC) and attribute-based access control (ABAC)
  policies using digital credentials.
- Encrypted and authenticated data exchange between industrial sensors,
  actuators, and control systems.
- Verifying software updates and firmware integrity using signed credentials to
  prevent unauthorized modifications.
- Tamper-resistant logging and auditing: digitally signed operational logs and
  sensor data to enable post-incident forensic analysis.
- Temporary access credentials for emergency personnel and automated response
  systems during critical incidents.</t>
      </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="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>TODO Security</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 263?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
    <section numbered="false" anchor="document-history">
      <name>Document History</name>
      <t>-01</t>
      <ul spacing="normal">
        <li>
          <t>Added offline use case</t>
        </li>
        <li>
          <t>Added IoT use case</t>
        </li>
        <li>
          <t>Added microcredentials use case</t>
        </li>
        <li>
          <t>Changed author affiliations</t>
        </li>
      </ul>
      <t>-00</t>
      <ul spacing="normal">
        <li>
          <t>Initial individual draft</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61aXXPcxpV9x6/oHb9IWwRlrb2VhJVNQpF0xCpJpEUqTnZr
H3qAnpkOATSMBoYeu/xf8lv2l+059zYwGHLkiqvyInGA/rh97te5t5Hnedb7
vnJnZvEpOnNho4tmFTpzd3t9cbXICtu7deh2Z8Y3q5BlZSgaW2N42dlVn3vX
r/LY+sLlQ3R5wen5l6+zOCxrH6MPTb9rMfr66v4bY74wtooBW/mmdK3DP02/
ODELV/o+dN5W/HF9/gb/QYLF9cf7bxZZM9RL151lJSQ5y4rQRNfEIZ6Zvhtc
tj0zX2W2cxar3rli6Hy/W2SPoXtYd2Fox6fO3Nq+d12jh7tu+LfrzUV3RSGw
dVxkD26HieVZZnI9frZ1zYBNjfn1ixmjJ198B1l8szZ/5hJ8Xltf4bmg9icC
eBq6NV/Yrtjgxabv23j26hXH8ZHfutNx2Cs+eLXswmN0r2SFV5y59v1mWGLu
soMAPw5Atnr1eQ1xSgU4Yz/bbjb1VNc79eEXFvmFV6ebvq4WWWaHfhM64okN
jVkNVaXGs3jvi411lbntQheKh4W8x/ls43+0PcwGY+47W7qt6/xqV+oAl6Cr
W532p3425LQINfZ8vtcbHsz8t5zsV24kmJwqKMc2a0JXY5UtbCSjf+x/ZXme
G7uMmFT0WXa/8dHAd4aaspQuFp1fwtO2tvNhiAbQGYHOdI6aKU0fTNG5ZE/G
/QC8mrWDFxqb9ZvOOdPart+ZOkA28wLONrjuxGxCVfJ/kdO77uWpud84rL7f
wfqSy/Qbl3lZf+ULgcKElXncQDPmnzVz80L85CVM12V1iD0XbhzEx1KxdcVs
7Q7H7gErXo5AyJvTBFbty7JyWfYFd+pCORR8S+gcRAF8VlcGMHXAk6Jytqt2
M1Q9zBZY7WGLOKTtzdD7yv/o9MSCU64w5SNKCUVbdCHulcIoYjCfwevEXN/d
nJjvvro4MbbB+bBYl91d3kQCDOlENqrEF0MlgmEVwg1E9tgTSN3ULiv3TFSE
V9MEorgN1daZzVDbJvdNjt3yKoQWb6AFK9DEExjL94MHFjCzgBAzqtN1slO2
HKJvHE7Ex713mFHYqhIpsKJZusatfB+prYs3Nx8xrgglgpXE34rGbteKW9Ht
2j6sO9vCQIxdA1EYH/ywdR1XliVu7q4SGpNSirClNPVQ9b6txAyzfwoKs3FV
a9SpzBJwi8TpwKXESt+7ooedZlQIHLINDVbAIS1053BO/A9rWXWIA6If3XQy
HJy9wVI1EOIx1X0jjx6Htg04FzCtHT3Pxzqe0jYvQrOlmIBf7OCSi3j5LaZq
kERoONhr8f7T3T0zGv83H27k749X3366/nh1yb/v3p6/ezf9kaURd29vPr27
3P+1n3lx8/791YdLnYyn5uBRtnh//reFWufi5vb++ubD+buFevpcI3BVorJ0
aktt5xhubMzGqCTR4c3F7f/94/XX5qef/u3jNxf/8fr1737+Of347evffI0f
jxvXJF9ogKb+hI52mW1bICyhCkoobEu3VLXETXhsDD0aaP77/xCZ/z0zv18W
7euv/5Ae8MAHD0fMDh4KZs+fPJusIB55dGSbCc2D50+QPpT3/G8Hv0fcZw9/
/8cKZmby17/94x8ympCETBhSXSMsjiE2y75DzgVk+raXoEdVWbNyj7Rujm7H
gCweAi4EEx0Acgo2yDtgLq6CWyALISDGogqRkfwRi6uLL+F85WccD7Mvjvp5
8gez9Va8/ATKLaqBoWJ6R9e6/VbDI9lPMAgNte8l+iE60H0jPTH6dWPptzAP
UEtIVkcVUNw8jvJjkdkJZj7N3L4b3+Ewhye401hIw6zwR15hqTKFRolUgl1t
d3SBInRjwhUJ2mFZ4dxwYiFqAJvZdx+qUjLj4ul0S3BZwoDzXn64Y/BwP/go
oeOH//zyd1imYISUqe4wNiF6br1MBn8tocOiYLAmcpMYGsjN4faa0Djx7f39
7d6mJgY/Zk0aUJQwTgrRWhV1RgU0cD43rTpAAxA4o9YeE4MVEixzQEDBhTqZ
OyD87WYGIUYIfgeCttfLyWFqhJ07JHg5DUZfMnMnPkZTaTe7iLNWYlsYjgiM
GWMEk5Q6JhRA83eQ/lh6zYkk67la+tws+PCtX29y5NWBNriLvavzPuT6155g
YfunEz+6NeRGhQKjs71VBFJqzcsO9tWYif3JgS5myWxG6K7D/QkzCCy0Mney
cdQQegE3kBNfN0hXSOeDZrbPLkVqzccF3VPMEcbkGtsU7sQ4oV4SF8JK3EiZ
UY1Cy2LNm9VKYtJ06BdAFPYcQ/PyCQB7b9nYLRmDa7CgH7mg0KkSS16hSCvF
uuaTsawQJcUtJdhR4RDoO8iIVa6ZQYU5RxrzaMYYFotBqkg8/sJ8DBUHnDco
IIXGSbZTcrMzL/QAJ8jrW08U5ixfCE0Mq/5RYuoac15OQVThhiai0N6kkrjB
0HiMVSJ1naNuEgr5LxAhizAtEkXB8gA/9U+xF2rC+W4WElWMkcL+KwTpXOGo
hKl8SFBsbeVZfsdZ0D2OC7T01PVpBFeTs2fPXmsUlERXIXQyJcme+wz1COuD
yUO6sG5I5OODrxBTMgsOiOhWJ9aXWCD4TFN4Zd5TlDk1n5rKP4D6oIoTvgbZ
S7dGIUXGl+2DtDLr+qmYYbWCHVtWCgxi6nPIeyKhWnYyKKhhicCJUid06qxj
JWTIPBs6SRh6iOqkeABhhONymcqvHHPWNI58HRJ2mS23dG2eVA+KrDPAbnc5
VLMmixVMRk0xjqKSI5RVFR79uCSpeB/A9Gqxeqg0WdUcSSFuc/x1P3g8yb48
QVWCtaDvxGKmjHI0+Ev+nASewFAtIsaj4EQ2hF0NqsCB2fOEmXO3hMSpqyNm
m+KvrXYIfVCTAMfjzcRN60Ksv4cl2yrIIXvFvvPNgyuvG9rdCghFXTdZM/xw
oFoyRn01N67OHA8jHWjvcwuD2BOuWA/WxPy9QZ5c40z6yNY8itbVog0CDILQ
D/sqwtVtFXaqHT3K7lAlUvFirUYT6KnwHFs8qDae4i12KHvN1U5+MdTMZG70
FZAXZtBnC0DbGG6w1xpG/z3OPfkGt2ZLK6dFrDvJR5NZc1nA3UlmcnHj23g2
6uOZe64tyy9SxQSYZhWZdfJ0GdFS0EIYaqUbe/WQ0QQycwijhNOjTQGaIzlN
W9nC7YUHQQLyEO5A/yMnSQm+mvvmyH5yJdVTsBFhG0irAQaSJUsQwUbCvDcq
pb+ICTMKOI9TGzAX6GEfzCTQ3o4s6U5Z0oWwpBlfyLLbY0RqH3JHaohDfA+s
YgEsOx9UV6nUVvsjCfVAV34SYCByLAOYWbcmNSXqoEaMQyHhlFn5K8le8hxW
rbuWAzFmJC6sPbPWQm+S0wqGJYTlciURGTuWSB1kaox/a1vsxKwCXIs6vgtk
gr1r457cmN4+8F+Rdcz+c3GPS5npJn99/44tuEfiqmX3JvF8JwwN3kqOWBh2
RUwjlIcVhAW1HNsP5cD6XIg33YU5kcEvIvGlbCwUVlQAI2liarTjdy9EVFpH
5ZHgLIZ/FO6Y6LtWkE/5Lip4LdcYqUbKKOXSmudopJVXoXor4dYyf2Y5Fr5N
z5c1pF4c4z/742pI3GRWP5BzXzccJ6DPqTVf3UrhpdT8ggh5pkZzkMHNC6kl
u/1JlCNLUfNSpt538H671AJ3tse8tp3VBIm1c5m1CxHlEgxemsVFCB1Gkx/h
8LdTUUcNjusT+a+61CB04uALFXi3mG+OCQgDTFqNEmdb9JI8tXyeqezUuNP1
6Yn5i2tKjDgXn2vUvrcSVmU0m5vcnEDZZmf+ShFtFGsdoV+6/pGmPzXpJBBL
sdAJB1y6FfPP0on+oFYKKESFXWqk9YDIRiIpcZ0tNiQ20hKNpO+BCD2Q2cTY
GvagLceozEVzetw1SEJNGGK1Uztf+ryEGRUaBCtW5OI27AP30pulehpXYYtr
7XzuJAkRssRiDrxVWgJI/0k5tdowAwMVmajz3NoYZX91zXYYgdkSLB3TksTA
42GTsmodIikxVad7akQZstEC41yGYpTBH8rgmq0HmiOf0346dAMgUHHBpqEY
vRcY99LoIQyvl2uGgyUEKSyPKtvsCRmpRFOourIZQ1SbnyeQ06nkO6D+FcKz
NThV2jFKiMi0DkvFy9i64TaaHRMSigCOHPvRiqbolExahcL4Bma0B/ZYbJwC
IKrTw32V1Yz1trrpKKr2PvWeCwG6pKqS3JGVAEms7i4EbLJc9ZGZPpVxKMJq
xCMRmFQ8KX40i0SpvbDSQ+PAvncX55fn44bJXByo4HoHIumnurJCNj/hPk9P
oiVk46rU0EunEkGhsMR5DlViXnx8c37xUhHrIdpy6D838pwjSY0C2DnjhqbQ
o3Vlbq4auYHgOofa+Jzq5+jwxhghgaggOAxMCFO9eIAbd/qL0G+JdGONPLRa
/XLGyne1PFT+S/tQwVM0O+DhQaif440BSNYMXFSR+2qTu95bMOMuRwHhY28x
vArr9USpB1JBpMYRHWgqbacOqzQRU2JSlp5YkYFuU33ZhtiDtxdi2UwLGMUu
L+sp7CtygEOHjnxk1NcT4gx/7hjpd4cGQpWEWtSBM7S8pacYKbiU6iyzaKUy
pJbBZ3pc5097XLdTjyvLLoUmaZHFurmbGNr5db6mocsyoUtYO1W2FND9RFIZ
IXBCMdDxdnFkx/P8TQwja30f9SJq326bxfRs7Bgj3plvB8yQCg8DnrXruEbt
rL6lBMpa5MJPf7vyBOuhCGzY/I6eD8z4II14KR9UCGloylMkohTMHrX72wCL
caje4o0ItAcsRW8/5zRkpgUOSHgmgKVXlJYiiktUSrWWyYIl/mSPt5b2SNP/
YrSVcEu2IdUcBVfaY1IvCnHIOwVZCAn3OwQpwWl7qSSdmQk2czi5+APhsnod
K7Z+nKpp7VW4qcSc7gHUAd69e6+RIPqaH2iwfiZ+EqxB3lrwt9x8akq4R586
7n6U/tHGSSHLnRA2lbHXWoAXs0xoiNn9hownhqGjucNLnnVtn7Sqs/ckeFi8
yjG9Kmf13HhPfBiceAEyNfSmnp8imo09v3KqTdN1E2/GSUlrORF7CVOqQgqh
gNF1mir0Ljg1xLSumTJgBfT6sSkjxBwhBVsUbAFotT8LbRM7EjqTHXITMfaU
ZlFRk8TFxGF9L7aA1RB+t/ygBnHw1EjlNzrt7DMLuSqWfEmX40VBOtLB9cv+
SvgkVafsj/PeHseMg596gmwacnqOpBF7c0Tq6VKqhtLHzs9cqal4DVL35tMR
9hcRhxfzPUSTYv6XOc7EmIHVwdFY08IiJsI0F3lPPEDqQs/L+LWoTzpI8B1m
jUlpY18tgpXCodm8xU4o3VcAptdc06Hq1uyxRAmFUXtqmZQ6s9dx8y2XhLXC
7Fh0aVXI5VGva+NlNJrry4Tr0k3GzRMSTY3MWgDQEjVVNEzYU3UxsyiKe35I
YLBQ4qkrW/D4Uiod4WYM3fKtRnT8agGseSmYsRjXgtQIQxBMEvd8QjdZvPgu
X/NmvZyTlVsH0tCHvHW8jdsbMi8vYDiaXvd3M4elyc3lDdL5sXub0WRk+uFl
zThx5GmPeoUzm2HG7/BYNkVk0mQQaeL4Vu7Cr88/nD8fdvC9AjsoTdCR6cOX
8ZOhpS0euMp58dCEx8qVa23G/HSmHw268r8WK5zHLX5Om9tppJPPOS7HXd56
3sLsMNUcmctPGmkBZSmfNmkcno48viD3f/bwWW91NuIiNbE0Bxi7WsGORhTy
L78UP5W7sWregpYP77L/B0aG98O7KQAA

-->

</rfc>
