<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.11) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-ietf-ocm-open-cloud-mesh-08" category="std" consensus="true" submissionType="IETF">
  <front>
    <title>Open Cloud Mesh</title>

    <author initials="G." surname="Lo Presti" fullname="Giuseppe Lo Presti">
      <organization>CERN</organization>
      <address>
        <email>giuseppe.lopresti@cern.ch</email>
        <uri>https://cern.ch/lopresti</uri>
      </address>
    </author>
    <author initials="M. B." surname="de Jong" fullname="Michiel de Jong">
      <organization>Ponder Source</organization>
      <address>
        <email>michiel@pondersource.org</email>
        <uri>https://pondersource.com</uri>
      </address>
    </author>
    <author initials="M." surname="Baghbani" fullname="Mahdi Baghbani">
      <organization>Ponder Source</organization>
      <address>
        <email>mahdi@pondersource.org</email>
        <uri>https://pondersource.com</uri>
      </address>
    </author>
    <author initials="M." surname="Nordin" fullname="Micke Nordin">
      <organization>SUNET</organization>
      <address>
        <email>kano@sunet.se</email>
        <uri>https://code.smolnet.org/micke</uri>
      </address>
    </author>

    <date year="2026" month="November" day="16"/>

    <area>Applications and Real-Time</area>
    
    <keyword>Internet-Draft</keyword>

    <abstract>


<?line 38?>

<t>Open Cloud Mesh (OCM) is a server federation protocol that is used to
notify a Receiving Party that they have been granted access to some
Resource.  It has similarities with authorization flows such as
OAuth, as well as with social internet protocols such as ActivityPub
and email.</t>

<t>A core use case of OCM is when a user (e.g., Alice on System A) wishes
to share a resource (e.g., a file) with another user (e.g., Bob on
System B) without transferring the resource itself or requiring Bob to
log in to System A.</t>

<t>While this scenario is illustrative, OCM is designed to support a
broader range of interactions, including but not limited to file
transfers.</t>

<t>Open Cloud Mesh handles interactions only up to the point where the
Receiving Party is informed of their access to the Resource.  Actual
Resource access is subsequently managed by other protocols, such as
WebDAV.</t>



    </abstract>



  </front>

  <middle>


<?line 60?>

<section anchor="introduction"><name>Introduction</name>

<t>Open Cloud Mesh was initially conceived of in 2015 and has been deployed
since 2016.  OCM has been implemented by several platforms, including
CERNBox, Nextcloud, OpenCloud, ownCloud, and Seafile.</t>

<t>The goal of OCM is to provide a secure, scalable, and flexible
infrastructure for securely sharing and collaborating on resources and
has seen wide adoption, not least in the academic sector.</t>

<t>The core idea of OCM is to make it simple for users to do the right
thing.  This is achieved by providing a protocol that abstracts away
security and authentication details from the users to the servers acting
on behalf of the users.  Another important point of the protocol is the
invitation mechanism that lets users connect over established human
relationships and use those connections to establish contact between
their respective OCM servers.</t>

</section>
<section anchor="terms"><name>Terms</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 [RFC2119] [RFC8174] when, and only when,
they appear in all capitals, as shown here.</t>

<t>We define the following concepts, with some non-normative references to
related concepts from OAuth [RFC6749] and elsewhere:</t>

<t><list style="symbols">
  <t><strong>Collection</strong> - A grouping of one or more Resources whose membership
and semantics are defined by the Sending Server.  The Resources MAY
be at different locations and have different Resource types.</t>
  <t><strong>Discoverable Server</strong> - A server that tries to supply information in
OCM API Discovery.</t>
  <t><strong>Discovering Server</strong> - A server that tries to obtain information in
OCM API Discovery.</t>
  <t><strong>Federation</strong> - A group of OCM Providers that have established
mutual trust and agree on certain policies for interaction.  A
Federation MAY be facilitated by a Directory Service.</t>
  <t><strong>FQDN</strong> - Fully Qualified Domain Name, such as <spanx style="verb">"cloud.example.org"</spanx>.</t>
  <t><strong>Invite Acceptance Gesture</strong> - Gesture from the Invite Receiver to
the Invite Receiver OCM Server, supplying the Invite Token as well as
the OCM Address of the Invite Sender, effectively allowlisting the
Invite Sender OCM Server for sending Share Creation Notifications to
the Invite Receiver OCM Server.</t>
  <t><strong>Invite Acceptance Request</strong> - API call from the Invite Receiver OCM
Server to the Invite Sender OCM Server, supplying the Invite Token as
well as the OCM Address of the Invite Receiver, effectively
allowlisting the Invite Sender OCM Server for sending Share Creation
Notifications to the Invite Receiver OCM Server.</t>
  <t><strong>Invite Acceptance Response</strong> - HTTP response to the Invite
Acceptance Request.</t>
  <t><strong>Invite Creation Gesture</strong> - Gesture from the Invite Sender to the
Invite Sender OCM Server, resulting in the creation of an Invite
Token.</t>
  <t><strong>Invite Message</strong> - Out-of-band message used to establish contact
between parties and servers in the Invite Flow, containing an Invite
Token (see below) and the Invite Sender's OCM Address.</t>
  <t><strong>Invite Receiver</strong> - The party receiving an Invite, identified by its
OCM Address.</t>
  <t><strong>Invite Receiver OCM Server</strong> - The server holding an address book
used by the Invite Receiver, to which details of the Invite Sender are
to be added.</t>
  <t><strong>Invite Sender</strong> - The party sending an Invite, identified by its
OCM Address.</t>
  <t><strong>Invite Sender OCM Server</strong> - The server holding an address book
used by the Invite Sender, to which details of the Invite Receiver are
to be added.</t>
  <t><strong>Invite String</strong> - An Invite Token and the FQDN of an Invite Sender
OCM Server joined by an <spanx style="verb">@</spanx>-sign, then encoded using base64url (the
URL- and filename-safe alphabet defined in [RFC4648], Section 5) with
padding omitted.</t>
  <t><strong>Invite Token</strong> - A hard-to-guess string used in the Invite Flow,
generated by the Invite Sender OCM Server and linked uniquely to the
Invite Sender's OCM Address.</t>
  <t><strong>OCM Address</strong> - identifies a user or group "at" an OCM Server.
The OCM Address contains a server specific Party identifier, a host
locating the OCM Server and an optional port.  The OCM Address is not
a URI as it does not have scheme and the identifier may contain
reserved characters:  <vspace blankLines='1'/>
    <figure><artwork><![CDATA[
ocm-address = identifier "@" host [ ":" port]
]]></artwork></figure>
  <vspace blankLines='1'/>
"identifier" is an opaque, case-sensitive UTF-8 string.  It is
separated from the host by the last "@" in the OCM Address.  It is
possible to have multiple @-signs in a OCM-address, e.g. when an
email address is the local part of the address like
<spanx style="verb">nomen.nescio@example.org@cloud.example.org</spanx>.
"host" is an IP literal encapsulated within square brackets, an IPv4
address in dotted decimal form, or a registered name as described in
[RFC3986]:  <vspace blankLines='1'/>
    <figure><artwork><![CDATA[
host = IP-literal / IPv4address / reg-name
]]></artwork></figure>
  <vspace blankLines='1'/>
The optional port subcomponent can be used to specify a port to use
for discovery (see Discovery Process).
The OCM Server MUST be discoverable at the given host and optional
port via the Well-Known [RFC8615] path <spanx style="verb">/.well-known/ocm</spanx>.  The OCM
Address MUST NOT contain a path.</t>
  <t><strong>OCM API Discovery</strong> - Process of evaluating properties of a Remote
Resource, after establishing contact with an OCM Server.</t>
  <t><strong>OCM Notification</strong> - A message from the Receiving Server to the
Sending Server or vice versa, using the OCM Notifications endpoint.</t>
  <t><strong>OCM Server</strong> - A server that has the OCM Provider function.</t>
  <t><strong>Receiving Party</strong> - A person, group or party who is granted access
to the Resource through the Share; similar to "Requesting Party / RqP"
in OAuth-UMA, identified by its OCM Address.</t>
  <t><strong>Receiving Server</strong> - The server that:
  <list style="symbols">
      <t>receives Share Creation Notifications (see below),</t>
      <t>actively or passively notifies the receiving user or group of any
incoming Share Creation Notification,</t>
      <t>acts as an API client, allowing the receiving user to access the
Resource through an API (e.g., WebDAV [RFC4918]) of the sending
server.</t>
    </list></t>
  <t><strong>Remote Resource</strong> - A Resource provided by the Sending Server.</t>
  <t><strong>Resource</strong> - The piece of data or interaction to which access is
being granted, including but not limited to: a file or folder, a video
call, a contact, a printer queue, etc.</t>
  <t><strong>Sending Gesture</strong> - A user interface interaction from the Sending
Party to the Sending Server, conveying the intention to create a
Share.</t>
  <t><strong>Sending Party</strong> - A person or party who is authorized to create
Shares; similar to "Resource Owner" in OAuth [RFC6749], identified by
its OCM Address.</t>
  <t><strong>Sending Server</strong> - The server that:
  <list style="symbols">
      <t>holds the Resource ("file server" or "Entreprise File Sync and Share
(EFSS) server" role),</t>
      <t>provides access to it (by exposing at least one "API"),</t>
      <t>takes the decision to create the Share based on user interface
gestures from the Sending Party (the "Authorization Server" role in
OAuth [RFC6749]),</t>
      <t>takes the decision about authorizing attempts to access the Resource
(the "Resource Server" role in OAuth [RFC6749]),</t>
      <t>sends out Share Creation Notifications when appropriate (see below).</t>
    </list></t>
  <t><strong>Share</strong> - A policy rule stating that certain actors have specific
access rights to a Resource; it MAY also refer to a record in a
database representing this rule.</t>
  <t><strong>Share Creation</strong> - The addition of a Share to the database state of
the Sending Server, in response to a successful Sending Gesture or for
another reason.</t>
  <t><strong>Share Creation Notification</strong> - A server-to-server request from the
sending server to the receiving server, notifying the receiving server
that a Share has been created.</t>
  <t><strong>Share Name</strong> - A human-readable string, provided by the Sending
Party or the Sending Server, to help the Receiving Party understand
which Resource the Share grants access to.</t>
  <t><strong>Share Permissions</strong> - protocol-specific allowances granted to the
Receiving Party on the modes of accessing the Resource.</t>
  <t><strong>Share Requirements</strong> - Protocol-specific restrictions on the modes
of accessing the Resource.</t>
  <t><strong>Shared Resource</strong> - A Resource shared by an OCM Server, becoming a
Remote Resource if accepted by the Invite Receiver OCM Server.</t>
  <t><strong>Sharing User</strong> - A user providing access to a Resource through a
Share.</t>
  <t><strong>Trusted Server</strong> - An OCM Server that is considered trustworthy by
another OCM Server, based on out-of-band information, federation
membership or prior interactions, SHOULD be recorded in an internal
registry of trusted servers, that SHOULD be updated over time based
on new information.  The registry SHOULD include the FQDN of the
trusted server and the public keys (JWK Set [RFC7517]) used for
HTTP Message Signatures.  It MAY
also include additional metadata such as the inviteAcceptDialog URL
or supported capabilities.</t>
  <t><strong>WAYF Page</strong> - A Where-Are-You-From page is a discovery service used
to identify the OCM Server of an Invite Receiver.</t>
</list></t>

<section anchor="functions"><name>Functions</name>

<t>Open Cloud Mesh defines distinct functions.  It is not necessary for an
implementation to provide all of them.  In fact, it may be useful to
have separate implementations for different functions.</t>

<section anchor="ocm-provider"><name>OCM Provider</name>

<t>An OCM Provider is an entity that can take on the two <em>roles</em> of a
<em>Sending Server</em> and a <em>Receiving Server</em>.  An OCM Provider MUST be a
<em>Discoverable Server</em> and SHOULD be able to receive <em>Notifications</em>.</t>

</section>
<section anchor="ocm-directory-service"><name>OCM Directory Service</name>

<t>An OCM Directory Service is an entity that exposes information about a
<em>Federation</em> of OCM Providers.</t>

</section>
</section>
<section anchor="roles"><name>Roles</name>

<t>Open Cloud Mesh defines two distinct roles that an OCM Provider MUST
take on: the <em>Sending Server</em> role and the <em>Receiving Server</em> role.</t>

<section anchor="sending-server"><name>Sending Server</name>

<t>A Sending Server is an OCM Provider that holds Resources and exposes
APIs to allow access to them.  It allows its users to create <em>Shares</em>
to give other users access to those Resources.  A Sending Server MAY
provide its users with the ability to generate <em>Invites</em> to establish
contact with other users on other OCM Providers.  When doing so it MAY
provide a <em>WAYF Page</em> to facilitate the Invite Flow.  The WAYF page MAY
be limited to a set of trusted OCM Providers, for instance those in the
same <em>Federation</em>.</t>

</section>
<section anchor="receiving-server"><name>Receiving Server</name>

<t>A Receiving Server is an OCM Provider that receives <em>Share</em> Creation
Notifications from Sending Servers, notifies its users about incoming
<em>Shares</em>, and acts as an API client to allow its users to access Remote
Resources.  It MAY provide its users with an <em>Address Book</em> of
<em>Contacts</em> and the ability to accept <em>Invites</em>.</t>

<t>In Appendix D, an object model is presented as a non-normative guide for
implementers to understand the relationships between these terms.</t>

</section>
</section>
</section>
<section anchor="general-flow"><name>General Flow</name>

<t>The lifecycle of an Open Cloud Mesh Share starts with prerequisites such
as establishing trust, establishing contact, and discovery of the remote
OCM Server.</t>

<t>The share creation involves the Sending Party making a Sending Gesture
to the Sending Server, and the Sending Server preparing the Share and
sending a Share Creation Notification to the Receiving Server.</t>

<t>After this, the Receiving Server MAY notify the Receiving Party and/or
the Sending Server, and will act as an API client through which the
Receiving Party can access the Resource.  The Receiving Party or
the Sending Party MAY then update or delete the Share: the respective
Server MAY send a Notification to the other party about the change.</t>

<t>In what follows all the related flows are detailed.  [OpenAPI] contains
a description of the whole protocol in OpenAPI format.</t>

</section>
<section anchor="establishing-contact"><name>Establishing Contact</name>

<t>Before the Sending Server can send a Share Creation Notification to the
Receiving Server, it MUST establish the Receiving Party's OCM
Address (containing the Receiving Server's FQDN, and the Receiving
Party's identifier), among other things.  Some steps may preceed the
Sending Gesture, allowing the Sending Party to establish (with some
level of trust) the OCM Address of the Receiving Party.  In other cases,
establishing the OCM Address of the Receiving Party happens as part of
the Sending Gesture.</t>

<section anchor="direct-entry"><name>Direct Entry</name>

<t>The simplest way for this is if the Receiving Party shares their OCM
Address with the Sending Party through some out-of-band means, and the
Sending Party enters this string into the user interface of the Sending
Server, by means of typing or pasting into an HTML form, or clicking a
link to a URL that includes the string in some form.</t>

</section>
<section anchor="public-link-flow"><name>Public Link Flow</name>

<t>An interface for anonymously viewing a Resource on the Sending Server
MAY allow any internet user to type or paste an OCM address into an HTML
form, as a Sending Gesture.  This means that the Sending Party and the
Receiving Party could be the same person, so contact between them does
not need to be explicitly established.</t>

</section>
<section anchor="public-invite-flow"><name>Public Invite Flow</name>

<t>Similarly, an interface on the Sending Server MAY allow any internet
user to type or paste an OCM address into an HTML form, as a Sending
Gesture for a given Resource, without itself providing a way to access
that particular Resource.  A link to this interface could then for
instance be shared on a mailing list, allowing all subscribers to
effectively request access to the Resource by making a Sending Gesture
to the Sending Server with their own OCM Address.</t>

</section>
<section anchor="invite-flow"><name>Invite Flow</name>

<section anchor="rationale"><name>Rationale</name>

<t>Many methods for establishing contact allow unsolicited contact with the
prospective Receiving Party whenever that party's OCM Address is known.
The Invite Flow requires the Receiving Party to explicitly accept it
before it can be used, which establishes bidirectional trust between the
two parties involved.</t>

<t>OCM Servers MAY enforce a policy to only accept Shares between such
trusted contacts, or MAY display a warning to the Receiving Party when a
Share Creation Notification from an unknown Sending Party is received</t>

</section>
<section anchor="steps"><name>Steps</name>

<t><list style="symbols">
  <t>the Invite Sender OCM Server generates a unique Invite Token and helps
the Invite Sender to create the Invite Message</t>
  <t>the Invite Sender uses some out-of-band communication to send the
Invite Message, containing the Invite Token and the Invite Sender OCM
Server FQDN, to the Invite Receiver</t>
  <t>the Invite Receiver navigates to the Invite Receiver OCM Server and
makes the Invite Acceptance Gesture.  This step MAY be facilitated if
the Invite Sender OCM Server implements a WAYF Page, such that the
Invite Message would include a link to it for the Invite Receiver to
navigate to: the Invite Receiver would then be able to indicate their
OCM Server and proceed with the Invite Acceptance Gsture without
manually copying the Invite Token.</t>
  <t>the Invite Receiver OCM Server discovers the OCM API of the Invite
Sender OCM Server using generic OCM API Discovery (see section below)</t>
  <t>the Invite Receiver OCM Server sends the Invite Acceptance Request to
the Invite Sender OCM Server</t>
</list></t>

</section>
<section anchor="invite-acceptance-request-details"><name>Invite Acceptance Request Details</name>

<t>Whereas the precise syntax of the Invite Message and the Invite
Acceptance Gesture will differ between implementations, the Invite
Acceptance Request MUST be a HTTP POST request:</t>

<t><list style="symbols">
  <t>to the <spanx style="verb">/invite-accepted</spanx> path in the Invite Sender OCM Server's OCM
API</t>
  <t>using <spanx style="verb">application/json</spanx> as the <spanx style="verb">Content-Type</spanx> HTTP request header</t>
  <t>its request body containing a JSON document representing an object
with the following string fields:
  <list style="symbols">
      <t>REQUIRED: <spanx style="verb">recipientProvider</spanx> - FQDN of the Invite Receiver OCM
Server.</t>
      <t>REQUIRED: <spanx style="verb">token</spanx> - The Invite Token.  The Invite Sender OCM Server
SHOULD recall which Invite Sender OCM Address this token was linked
to.</t>
      <t>REQUIRED: <spanx style="verb">userID</spanx> - The Invite Receiver's identifier at their OCM
Server.</t>
      <t>REQUIRED: <spanx style="verb">email</spanx> - Non-normative / informational; an email address
for the Invite Receiver.  Not necessarily at the same FQDN as their
OCM Server.</t>
      <t>REQUIRED: <spanx style="verb">name</spanx> - Human-readable name of the Invite Receiver, as a
suggestion for display in the Invite Sender's address book</t>
    </list></t>
  <t>using TLS</t>
</list></t>

<t>When HTTP Message Signatures are available, the Invite Acceptance
Request MUST be signed and verified as described in <xref target="http-message-signatures">HTTP Message
Signatures</xref>.  As the Invite flow establishes
the trust that later exchanges rely on, implementations SHOULD NOT use
it unless signing is available.</t>

<t>The Invite Receiver OCM Server SHOULD apply its own policies for
trusting the Invite Sender OCM Server before making the Invite
Acceptance Request.</t>

<t>Since the Invite Flow does not require either Party to type or remember
the <spanx style="verb">userID</spanx>, this string does not need to be human-memorable.  Even if
the Invite Receiver has a memorable username at the Invite Receiver OCM
Server, this <spanx style="verb">userID</spanx> that forms part of their OCM Address does not need
to match it.</t>

<t>Also, a different <spanx style="verb">userID</spanx> could be given out to each contact, to avoid
correlation of identities.</t>

<t>If the Invite Sender OCM Server implements a WAYF Page, such a page MAY
include a fixed list of servers, in addition to, or instead of, a
free-text input where any OCM Server can be entered.  This is especially
useful if the Invite Sender is part of a federation of associated OCM
Servers.  In order to populate the list of associated OCM Servers, the
Invite Sender's server MAY make use of a Directory Service, which is
expected to follow the specification detailed in Appendix C.</t>

<t>Implementors that provide a WAYF Page SHOULD make the URL for the API
endpoint of such a Directory Service configurable, allowing the OCM
Server to be part of a network of associated OCM Servers.  The
configuration mechanism MAY allow an OCM Server to be part of multiple
networks, thus displaying a union of multiple lists in its WAYF Page.</t>

</section>
<section anchor="invite-acceptance-response-details"><name>Invite Acceptance Response Details</name>

<t>The Invite Acceptance Response SHOULD be a HTTP response:</t>

<t><list style="symbols">
  <t>in response to the Invite Acceptance Request</t>
  <t>using <spanx style="verb">application/json</spanx> as the <spanx style="verb">Content-Type</spanx> HTTP response header</t>
  <t>its response body containing a JSON document representing an object
with the following string fields:
  <list style="symbols">
      <t>REQUIRED: <spanx style="verb">userID</spanx> - the Invite Sender's identifier at their OCM
Server</t>
      <t>REQUIRED: <spanx style="verb">email</spanx> - non-normative / informational; an email address
for the Invite Sender.  Not necessarily at the same FQDN as their
OCM Server</t>
      <t>REQUIRED: <spanx style="verb">name</spanx> - human-readable name of the Invite Sender, as a
suggestion for display in the Invite Receiver's address book</t>
    </list></t>
</list></t>

<t>A 200 response status means the Invite Acceptance Request was
successful.
A 400 response status means the Invite Token is invalid or does not
exist.
A 403 response status means the Invite Receiver OCM Server is not
trusted to accept this Invite.
A 409 response status means the Invite was already accepted.</t>

<t>Before processing the Invite Acceptance Request and sending the Invite
Acceptance Response, the Invite Sender OCM Server SHOULD apply its own
policies for trusting the Invite Receiver OCM Server.  Any HTTP
Signature on the request is verified as described in <xref target="http-message-signatures">HTTP Message
Signatures</xref>.</t>

<t>As with the <spanx style="verb">userID</spanx> in the Invite Acceptance Request, the one in the
Response also doesn't need to be human-memorable, doesn't need to match
the Invite Sender's username at their OCM Server.</t>

</section>
<section anchor="addition-into-address-books"><name>Addition into address books</name>

<t>Following these step, both servers MAY display the <spanx style="verb">name</spanx> of the other
party as a trusted or allowlisted contact, and enable selecting them as
a Receiving Party.  OCM Servers MAY enforce a policy to only accept
Share Creation Notifications from such trusted contacts, or MAY display
a warning to users when a Share Creation Notification from an unknown
party is received.</t>

<t>Both servers MAY also allowlist each other as a server with which at
least one of their users wishes to interact.</t>

<t>In addition, if the identity provider of either server supports the
registration of external users, it may happen that the just received
email contact from the other party matches an external user already
known in the local identity provider, and therefore already present
in the address book.  In such a case, implementers MAY support linking
of the two identities belonging to that same user, so that when a Share
Creation gesture is made to that recipient, both a regular share and an
OCM Share Creation Notification are issued.</t>

<t>Note that Invites act symmetrically, so once contact has been
established, both the Invite Sender and the Invite Receiver MAY take on
either the Sending Party or the Receiving Party role in subsequent
Share Creation events.</t>

<t>Both parties MAY delete the other party from their address book at any
time without notifying them.</t>

</section>
<section anchor="invite-format"><name>Invite format</name>
<t>To accept an invite, two pieces of information are required: a <spanx style="verb">token</spanx>
and a <spanx style="verb">provider</spanx>.  There are two recognized formats:</t>

<t><list style="symbols">
  <t><strong>Invite string format:</strong>
The token and the provider’s FQDN, joined by an <spanx style="verb">@</spanx> sign and then
encoded using base64url (the URL- and filename-safe alphabet defined
in [RFC4648], Section 5) with padding omitted.  Example:  <vspace blankLines='1'/>
If the <spanx style="verb">token</spanx> is <spanx style="verb">a55a966e-15c1-4cb9-a39d-4e4c54399baf</spanx> and the
<spanx style="verb">provider</spanx> is <spanx style="verb">cloud.example.org</spanx>, the combined string is
<spanx style="verb">a55a966e-15c1-4cb9-a39d-4e4c54399baf@cloud.example.org</spanx>,
which when base64url-encoded becomes
<spanx style="verb">YTU1YTk2NmUtMTVjMS00Y2I5LWEzOWQtNGU0YzU0Mzk5YmFmQGNsb3VkLmV4YW1wbGUu
b3Jn</spanx>.  <vspace blankLines='1'/>
When parsing an invite string, implementors MUST base64url-decode it
(accepting the string whether or not padding is present), then split
on the last <spanx style="verb">@</spanx> sign, taking care to allow multiple <spanx style="verb">@</spanx> characters in
the token part.</t>
  <t><strong>Link format:</strong>
If the inviting OCM Server supports a WAYF page, the invite may be
provided as a link with the token as a request parameter.  Example:  <vspace blankLines='1'/>
<spanx style="verb">https://cloud.example.org/wayf?token=
a55a966e-15c1-4cb9-a39d-4e4c54399baf</spanx></t>
</list></t>

<t>Implementations MUST be able to accept invites in the invite string
format.  This format is considered canonical.  The link format is only
useful if the Receiving OCM Server exposes the <spanx style="verb">inviteAcceptDialog</spanx>
in its Discovery endpoint.  Implmentations SHOULD support the link
format when they implement a WAYF Page that leverages those
<spanx style="verb">inviteAcceptDialog</spanx> targets.</t>

</section>
<section anchor="security-advantages"><name>Security Advantages</name>

<t>It is important to underscore the value of the Invite in this scenario,
as it provides four important security advantages.  First of all, if the
Receiving Server blocks Share Creation Notifications from Sending
Parties who are not in the address book of the Receiving Party, then
this protects the Receiving Party from receiving unsolicited Shares.  An
attacker could still send the Receiving Party an unsolicited Share, but
they would first need to convince the Receiving Party through an
out-of-band communication channel to accept their invite.  In many use
cases, the Receiving Party has had other forms of contact with the
Sending Party (e.g., in-person or email back-and-forth).  The
out-of-band Invite Message thus leverages the filters and context which
the Receiving Party may already benefit from in that out-of-band
communication.  For instance, a careful Receiving Party MAY choose to
only accept Invites that reach them via a private or moderated
messaging platform.</t>

<t>Second, when the Receiving Party accepts the Invite, the Receiving
Server knows that the Sending Server they are about to interact with is
trusted by the Sending Party, which in turn is trusted by the Receiving
Party, which in turn is trusted by them.  In other words, one of their
users is requesting the allowlisting of a server they wish to interact
with, in order to interact with a party they know out-of-band.  This
gives the Receiving Server reason to put more trust in the Sending
Server than it would put into an arbitrary internet-hosted server.</t>

<t>Third, equivalently, the Sending Server knows it is essentially
registering the Receiving Server as an API client at the request of the
Receiving Party, to whom the right to request this has been traceably
delegated by the Sending Party, which is one of its registered users.</t>

<t>Fourth, related to the second one, it removes the partial 'open relay'
problem that exists when the Sending Server is allowed to include any
Receiving Server FQDN in the Sending Gesture.  Without the use of
Invites, a Distributed Denial of Service attack could be organised if
many internet users collude to flood a given OCM Server with Share
Creation Notifications which will be hard to distinguish from
legitimate requests without human interaction.  An unsolicited (invalid)
Invite Acceptance Request is much easier to filter out than an
unsolicited (possibly valid, possibly invalid) Share Creation
Notification Request, since the Invite Acceptance Request needs to
contain an Invite Token that was previously uniquely generated at the
Invite Sender OCM server.</t>

</section>
</section>
</section>
<section anchor="ocm-api-discovery"><name>OCM API Discovery</name>

<section anchor="introduction-1"><name>Introduction</name>

<t>After establishing contact as discussed in the previous section, the
Sharing User MAY send the Share Creation Gesture to the Sending Server.
The Sharing User MUST provide the following information:</t>

<t><list style="symbols">
  <t>Resource to be shared</t>
  <t>Protocol to be offered for access</t>
  <t>Sending Party's identifier</t>
  <t>Receiving Party's identifier</t>
  <t>Receiving Server FQDN</t>
  <t>OPTIONAL: Share Requirements</t>
  <t>OPTIONAL: Share Name</t>
  <t>OPTIONAL: Share Permissions</t>
</list></t>

<t>The next step is for the Sending Server to additionally discover:</t>

<t><list style="symbols">
  <t>if the Receiving Server is trusted</t>
  <t>if the Receiving Server supports OCM</t>
  <t>if so, which version and with which optional functionality</t>
  <t>at which URL</t>
  <t>the public keys the Receiving Server will use for HTTP Message
Signatures (if any), published as a JWK Set at the URL given by the
<spanx style="verb">jwksUri</spanx> field</t>
</list></t>

<t>The Sending Server MAY first perform denylist and allowlist checks on
the FQDN.</t>

<t>If a finite allowlist of Receiving Servers exists on the Sending Server
side, then this list MAY already contain all necessary information.</t>

<t>If the FQDN passes the denylist and/or allowlist checks, but no details
about its OCM API are known, the Sending Server can use the following
process to try to fetch this information from the Receiving Server.</t>

<t>This process MAY be influenced by a VPN connection and/or IP
allowlisting.</t>

<t>When OCM API Discovery can occur in preparation of a Share Creation
Notification, the Sending Server takes on the 'Discovering Server' role
and the Receiving Server plays the role of 'Discoverable Server'.
For a navigation index of discovery fields, capabilities, and related
informative aids, see <xref target="appendix-e-navigation-index">Appendix E: Navigation
Index</xref>.</t>

</section>
<section anchor="process"><name>Process</name>

<t>At the start of the process, the Discovering Server has either an OCM
Address, or just an FQDN from for instance the <spanx style="verb">recipientProvider</spanx>
field of an Invite Acceptance Request.</t>

<t>Step 1: In case it has an OCM Address, it SHOULD first extract <spanx style="verb">&lt;fqdn&gt;</spanx>
from it (the part after the last <spanx style="verb">@</spanx> sign).
Step 2: The Discovering Server SHOULD attempt OCM API Discovery via a
HTTP GET request to <spanx style="verb">https://&lt;fqdn&gt;/.well-known/ocm</spanx>.
Step 3: If that results in a valid HTTP response with a valid JSON
response body within reasonable time, go to step 5.
Step 4: If not, fail.  Implementations MAY fallback to HTTP instead
of HTTPS in testing setups and retry steps 2-3, in particular when
an optional port is given in the address.
Step 5: The JSON response body is the data that was discovered.</t>

</section>
<section anchor="fields"><name>Fields</name>

<t>The JSON response body offered by the Discoverable Server SHOULD
contain the following information about its OCM API:</t>

<t><list style="symbols">
  <t>REQUIRED: enabled (boolean) - Whether the OCM service is enabled at
this endpoint</t>
  <t>REQUIRED: apiVersion (string) - The OCM API version this endpoint
supports.  Example: <spanx style="verb">"1.5.0"</spanx></t>
  <t>REQUIRED: endPoint (string) - The URI of the OCM API available at
this endpoint.  Example: <spanx style="verb">"https://cloud.example.org/ocm"</spanx></t>
  <t>OPTIONAL: provider (string) - A friendly branding name of this
endpoint.  Example: <spanx style="verb">"MyCloudStorage"</spanx></t>
  <t>REQUIRED: resourceTypes (array) - A list of all resource types this
server supports in both the Sending Server role and the Receiving
Server role, with their access protocols.  Each item in this list
MUST itself be an object containing the following fields:
  <list style="symbols">
      <t>name (string) - A supported resource type, such as file, calendar,
contact, etc.  Implementations MUST offer support for at least one
resource type: <spanx style="verb">file</spanx> is the commonly supported one, and
other values are to be registered in the "OCM Resource Types"
registry (see <xref target="iana-considerations">IANA Considerations</xref>).
Each resource type is identified by its <spanx style="verb">name</spanx>: the list MUST NOT
contain more than one resource type object per given <spanx style="verb">name</spanx>.</t>
      <t>shareTypes (array of string) -
The supported recipient share types.  MUST contain
<spanx style="verb">"user"</spanx> at a minimum, plus optionally <spanx style="verb">"group"</spanx> or any
other value registered in the "OCM Share Types" registry
(see <xref target="iana-considerations">IANA Considerations</xref>).
Example: <spanx style="verb">["user"]</spanx></t>
      <t>protocols (object) - The supported protocols for accessing Shared
Resources of this type.  Implementations that offer <spanx style="verb">file</spanx>
Resources MUST support at least <spanx style="verb">webdav</spanx>, any other combination
of Resources and protocols is optional.  Example:      <vspace blankLines='1'/>
        <figure type="json"><artwork><![CDATA[
        {
          "webdav": "/remote/dav/ocm/",
          "webdav-receive": { "uri": "absolute" },
          "webapp": {},
          "webapp-receive": { "targets": ["blank", "iframe"] },
          "talk": "/apps/spreed/api/"
        }
]]></artwork></figure>
      <vspace blankLines='1'/>
The <spanx style="verb">protocols</spanx> object distinguishes a server's role for each
protocol: a property named after the protocol (e.g. <spanx style="verb">webdav</spanx>,
<spanx style="verb">webapp</spanx>, <spanx style="verb">ssh</spanx>) advertises support for acting as a Sending
Server, while a property suffixed with <spanx style="verb">-receive</spanx> (e.g.
<spanx style="verb">webdav-receive</spanx>, <spanx style="verb">webapp-receive</spanx>, <spanx style="verb">ssh-receive</spanx>) advertises
support for acting as a Receiving Server.      <vspace blankLines='1'/>
Fields:
- webdav (string) - The top-level WebDAV [RFC4918] path at this
  endpoint.  In order to access a Remote Resource, implementations
  SHOULD use this path as a prefix (see sharing examples).
- webdav-receive (object) - Advertised by implementations that
  support receiving WebDAV shares.  It contains a <spanx style="verb">uri</spanx> property
  whose value MUST be either <spanx style="verb">"absolute"</spanx> or <spanx style="verb">"relative"</spanx>,
  signalling the URI format this endpoint accepts.  Note that
  older implementations MAY not support this property.
- webapp (object) - Advertised, as an empty object, by
  implementations that support sending WebApp shares.
- webapp-receive (object) - Advertised by implementations that
  support receiving WebApp shares.  It contains a <spanx style="verb">targets</spanx>
  array listing the ways this endpoint is able to present a
  WebApp share to the user.  A subset of:
  - <spanx style="verb">blank</spanx> - the endpoint can open the URI in a top-level
    browsing context, such as a new window or tab, or a full page
    navigation in the current window.
  - <spanx style="verb">iframe</spanx> - the endpoint can embed the URI in an iframe
    within its own UI, when the Sending Server allows framing
    by this receiver.
- ssh (string) - The top-level address in the form <spanx style="verb">host:port</spanx>
  of an endpoint that supports ssh and scp with a public/private
  key based authentication.
- ssh-receive (object) - Advertised, as an empty object, by
  implementations that support receiving SSH shares.
- Any additional protocol supported for this Resource type SHOULD be
  advertised here, where the value MAY correspond to a top-level
  URI to be used for that protocol.  Similarly, additional receiving
  capabilities for custom protocols SHOULD be advertised using a
  <spanx style="verb">-receive</spanx> suffixed property.  Additional protocols are to be
  registered in the "OCM Protocols" registry (see
  <xref target="iana-considerations">IANA Considerations</xref>).</t>
    </list></t>
  <t>OPTIONAL: capabilities (array of string) - The optional capabilities
supported by this OCM Server.
As implementations MUST accept Share Creation Notifications
to be compliant, it is not necessary to expose that as a
capability.
Example: <spanx style="verb">["exchange-token", "protocol-object"]</spanx>.  The array MAY
include one or more of the following items:
  <list style="symbols">
      <t><spanx style="verb">"enforce-mfa"</spanx> - to indicate that this OCM Server can apply a
Sending Server's MFA requirements for a Share on their behalf.</t>
      <t><spanx style="verb">"exchange-token"</spanx> - to indicate that this OCM Server supports the
OCM code flow via an [RFC6749]-compliant token endpoint.  When this
OCM Server acts as Sending Server, it hosts <spanx style="verb">tokenEndPoint</spanx>.  When it
acts as Receiving Server, it can honor inbound shares that require
token exchange.</t>
      <t><spanx style="verb">"http-sig"</spanx> - to indicate that this OCM Server supports
[RFC9421] HTTP Message Signatures and advertises the public keys
for signature verification, in the format specified by [RFC7517],
at the URL given by the <spanx style="verb">jwksUri</spanx> field.</t>
      <t><spanx style="verb">"invites"</spanx> - to indicate the server would support acting as an
Invite Sender or Invite Receiver OCM Server.  This might be useful
for suggesting to a user that existing contacts might be upgraded
to the more secure (and possibly required) invite flow.</t>
      <t><spanx style="verb">"notifications"</spanx> - to indicate that this OCM Server handles
notifications to exchange updates on shares and invites.</t>
      <t><spanx style="verb">"invite-wayf"</spanx> - to indicate that this OCM Server exposes a WAYF
Page to facilitate the Invite flow.</t>
      <t><spanx style="verb">"protocol-object"</spanx> - to indicate that this OCM Server can
receive a Share Creation Notification whose <spanx style="verb">protocol</spanx> object
contains one property per supported protocol instead of containing
the standard <spanx style="verb">name</spanx> and <spanx style="verb">options</spanx> properties.</t>
    </list></t>
  <t>OPTIONAL: criteria (array of string) - The criteria for accepting a
Share Creation Notification.
As all Receiving Servers SHOULD require the use of TLS in API
calls, it is not necessary to expose that as a criterium.
Example: <spanx style="verb">["must-use-http-sig"]</spanx>.  The array MAY include
for instance:
  <list style="symbols">
      <t><spanx style="verb">"must-use-http-sig"</spanx> - to indicate that API requests
without http signatures will be rejected.</t>
      <t><spanx style="verb">"must-exchange-token"</spanx> - to indicate that when this OCM Server
acts as Receiving Server, it requires the code flow for all inbound
shares.  Shares that do not include <spanx style="verb">must-exchange-token</spanx> in
the requirements of each protocol offered for access will be
rejected.  An
OCM Server advertising this criterium MUST also expose the
<spanx style="verb">exchange-token</spanx> capability.  See the <xref target="code-flow">Code Flow</xref>
section.
Informative: The string <spanx style="verb">must-exchange-token</spanx> also appears in
<spanx style="verb">protocol.*.requirements[]</spanx> on outbound shares.  The binding between
receiver <spanx style="verb">criteria[]</spanx> and sender <spanx style="verb">requirements[]</spanx> is defined in
<xref target="share-creation-notification">Share Creation Notification</xref>.</t>
      <t><spanx style="verb">"denylist"</spanx> - some servers MAY be blocked based on their IP
address</t>
      <t><spanx style="verb">"allowlist"</spanx> - unknown servers MAY be blocked based on their IP
address</t>
      <t><spanx style="verb">"must-invite"</spanx> - an invite MUST have been exchanged between the
sender and the receiver before a Share Creation Notification can be
sent</t>
    </list></t>
  <t>OPTIONAL: inviteAcceptDialog (string) - URL path of a web page where
a user can accept an invite, when query parameters <spanx style="verb">"token"</spanx> and
<spanx style="verb">"providerDomain"</spanx> are provided.  Implementations that offer the
<spanx style="verb">"invites"</spanx> capability SHOULD provide this URL as well in order to
enhance the UX of the Invite Flow.  If for example
<spanx style="verb">"/index.php/apps/sciencemesh/accept"</spanx> is specified here then a WAYF
Page SHOULD redirect the end-user to <spanx style="verb">/index.php/apps/sciencemesh/
accept?token=zi5kooKu3ivohr9a&amp;providerDomain=cloud.example.org</spanx>.</t>
  <t>OPTIONAL: jwksUri (string) - URL of a JWK Set document [RFC7517]
containing the public keys this OCM Server uses for HTTP Message
Signatures.  The URL MUST use HTTPS and is discovered from this field.
It MAY refer to a different host, not necessarily to the same OCM
Server; it is not a fixed path in the OCM API.  Implementations that
advertise the <spanx style="verb">"http-sig"</spanx> capability MUST provide this URL as well.
As with the Discovery Process, implementations MAY fallback to HTTP
instead of HTTPS in testing setups.
Example: <spanx style="verb">"https://cloud.example.org/ocm/jwks"</spanx>.</t>
  <t>OPTIONAL: tokenEndPoint (string) - URL of the token endpoint hosted by
this OCM Server.  When this OCM Server acts as Sending Server, the
Receiving Server POSTs here to exchange a <spanx style="verb">sharedSecret</spanx> for a
short-lived bearer token.
Implementations that offer the <spanx style="verb">"exchange-token"</spanx> capability MUST
provide this URL as well.
Example: <spanx style="verb">"https://cloud.example.org/ocm/token"</spanx>.</t>
</list></t>

</section>
</section>
<section anchor="http-message-signatures"><name>HTTP Message Signatures</name>

<t>A number of OCM API requests are signed "using httpsig [RFC9421]", as
described in the respective sections.  This section specifies the
normative requirements for producing and verifying those signatures.
Appendix B contains a complete example.</t>

<t>Public keys for signature verification are distributed as follows:
an OCM Server that advertises the <spanx style="verb">http-sig</spanx> capability MUST
publish its public keys as a JWK Set [RFC7517] at the URL
advertised in the <spanx style="verb">jwksUri</spanx> field of its
<xref target="ocm-api-discovery">Discovery</xref> response.</t>

<section anchor="applicability"><name>Applicability</name>

<t>Support for HTTP Message Signatures is negotiated through the
<spanx style="verb">http-sig</spanx> capability in the <xref target="ocm-api-discovery">Discovery</xref> response.
The following rules let deployments adopt signing incrementally while
remaining interoperable:</t>

<t><list style="symbols">
  <t>A Server that implements HTTP Message Signatures MUST use them when
interacting with another Server that advertises the <spanx style="verb">http-sig</spanx>
capability.</t>
  <t>Such a Server MAY nonetheless continue to interact, without signing,
with a Server that does not advertise the <spanx style="verb">http-sig</spanx> capability, for
backwards compatibility.</t>
  <t>A Server that implements HTTP Message Signatures MUST verify any
signature present on a request it receives, as specified below.</t>
  <t>A Server MAY accept an unsigned request from a Server that does not
advertise the <spanx style="verb">http-sig</spanx> capability; a Server that advertises the
<spanx style="verb">must-use-http-sig</spanx> criterion MUST reject unsigned requests.</t>
  <t>A Server that does not implement HTTP Message Signatures operates
without them.</t>
</list></t>

<t>Because the <xref target="invite-acceptance-request-details">Invite Acceptance
Request</xref> and the <xref target="notifications">Request_Share
Notification</xref> establish the trust that later exchanges
rely on, implementations SHOULD NOT use those features unless HTTP
Message Signatures are available.</t>

</section>
<section anchor="signing-requirements"><name>Signing Requirements</name>

<t>A signed request MUST cover at least the following Signature-Input
components:</t>

<t><list style="symbols">
  <t>"@method"             - HTTP method</t>
  <t>"@target-uri"         - full request URI (scheme, authority,
                        path, query)</t>
  <t>"content-digest"      - [RFC9530] digest of the body</t>
  <t>"content-length"      - message size</t>
</list></t>

<t>The signature parameters MUST include <spanx style="verb">created</spanx> and <spanx style="verb">keyid</spanx>.
Freshness is anchored on <spanx style="verb">created</spanx> (see Verification Requirements);
<spanx style="verb">created</spanx> bounds how long a captured signature stays acceptable, but
does not by itself detect replay within that window (see Section
7.2.2 of [RFC9421]).  The <spanx style="verb">keyid</spanx> value MUST be equal to the
<spanx style="verb">kid</spanx> value of the corresponding key in the signer's JWK Set (see
<xref target="keys-and-algorithms">Keys and Algorithms</xref>).</t>

<t>The <spanx style="verb">Date</spanx> header is deliberately not covered by the signature:
intermediaries sometimes rewrite it (see Section 6.6.1 of [RFC9110]),
which would make signatures fragile, and the <spanx style="verb">created</spanx> signature
parameter already conveys the message's creation time (see
Section 7.2.4 of [RFC9421]).</t>

<t>The <spanx style="verb">content-digest</spanx> component binds the request body to the signature,
protecting it against modification in transit.  Its value MUST use a
hash algorithm from the IANA "Hash Algorithms for HTTP Digest Fields"
registry [IANA-DIGEST-ALG]; implementations MUST support <spanx style="verb">sha-256</spanx>.</t>

<t>A request signed in the context of OCM MUST carry the signature
parameter <spanx style="verb">tag="ocm"</spanx> (see Section 2.3 of [RFC9421]).  Unlike the
signature label, which is a dictionary key that is not covered by the
signature and MAY be rewritten in transit, the <spanx style="verb">tag</spanx> parameter is part
of the signature base and is therefore integrity-protected.</t>

<t>A request MUST include one and only one signature carrying
<spanx style="verb">tag="ocm"</spanx>.  The signature label MAY be any value; it is not
significant to OCM processing.</t>

<t>The signature algorithm is determined by the signing key material;
see <xref target="keys-and-algorithms">Keys and Algorithms</xref>.</t>

</section>
<section anchor="keys-and-algorithms"><name>Keys and Algorithms</name>

<t>Each key published in the signer's JWK Set MUST include the <spanx style="verb">kid</spanx>
and <spanx style="verb">alg</spanx> parameters [RFC7517].  The JWK <spanx style="verb">alg</spanx> value MUST identify
an asymmetric signature algorithm registered in the IANA "JSON Web
Signature and Encryption Algorithms" registry [RFC7518], and SHOULD
be a fully-specified algorithm [RFC9864]; <spanx style="verb">Ed25519</spanx> ([RFC8032],
[RFC9864]) is RECOMMENDED.</t>

<t>The signature algorithm is derived from the key material rather
than declared by the message: signers and verifiers MUST determine
the algorithm from the <spanx style="verb">alg</spanx> parameter of the JWK identified by the
<spanx style="verb">keyid</spanx> signature parameter, and apply it to the signature base as
specified in Section 3.3.7 of [RFC9421].</t>

<t>This way, implementations are neither restricted to the algorithms
listed in the IANA "HTTP Signature Algorithms" registry
(Section 6.2 of [RFC9421]), nor is an update to this document
needed as new algorithms, for example post-quantum ones, are
registered for JOSE: as noted in that section, an application is
free to use any algorithm provided the signer and verifier can
agree on it in a secure and deterministic fashion, and the JWK
<spanx style="verb">alg</spanx> parameter provides that agreement.</t>

<t>The JWS algorithm <spanx style="verb">none</spanx> and symmetric MAC algorithms, such as
<spanx style="verb">HS256</spanx>, MUST NOT be used: the former provides no protection, while
the latter would require the verifier to have prior access to a
shared secret.</t>

<t>The <spanx style="verb">alg</spanx> signature parameter is OPTIONAL: the algorithm is always
determined by the JWK, as described above.  Note that this
parameter takes its values from a different registry than the JWK
<spanx style="verb">alg</spanx> value.  If the parameter is present, the algorithm it names
in the IANA "HTTP Signature Algorithms" registry [IANA-SIG-ALG]
MUST denote the same algorithm as the JWK <spanx style="verb">alg</spanx> value, for
example, <spanx style="verb">ed25519</spanx> for a JWK with <spanx style="verb">alg</spanx> <spanx style="verb">Ed25519</spanx>, and verifiers
MUST reject the signature otherwise
(see Section 7 of [RFC9421] on algorithm confusion and substitution
attacks).  When the JWK algorithm has no counterpart in that
registry, the <spanx style="verb">alg</spanx> signature parameter MUST be omitted.</t>

</section>
<section anchor="verification-requirements"><name>Verification Requirements</name>

<t>Verifiers MUST reject signatures that omit any of the mandatory
components listed under Signing Requirements or the <spanx style="verb">created</spanx> or
<spanx style="verb">keyid</spanx> parameters, and MUST reject signatures whose <spanx style="verb">created</spanx> value
is more
than a small implementation-defined skew tolerance in the future, or
older than the verifier's freshness window.</t>

<t>A <spanx style="verb">Content-Digest</spanx> header value carrying multiple algorithms MUST have
every recognised digest match the body; a single match alongside a
recognised mismatch MUST be treated as an integrity failure.</t>

<t>Verifiers MUST reject a signature if the signer's JWK Set contains
no key whose <spanx style="verb">kid</spanx> equals the <spanx style="verb">keyid</spanx> parameter, if the JWK
identified by <spanx style="verb">keyid</spanx> does not carry an acceptable <spanx style="verb">alg</spanx> value (see
<xref target="keys-and-algorithms">Keys and Algorithms</xref>), or if an <spanx style="verb">alg</spanx>
signature parameter is present and does not correspond to the
algorithm derived from that JWK.</t>

<t>Verifiers MUST identify the OCM signature by its <spanx style="verb">tag="ocm"</spanx>
parameter, examining the parameters of each member of the
<spanx style="verb">Signature-Input</spanx> field and disregarding the dictionary labels.
Verifiers MUST verify only that signature.  If more than one signature
carries <spanx style="verb">tag="ocm"</spanx>, the entire message MUST be rejected.  A request
that carries no signature with <spanx style="verb">tag="ocm"</spanx> is unsigned and is handled
as described in Applicability (accepted only at the receiver's
discretion, or rejected when the receiver advertises
<spanx style="verb">must-use-http-sig</spanx>).  Signatures without <spanx style="verb">tag="ocm"</spanx> MAY coexist (e.g.
proxy-attached signatures) but verifiers MUST NOT process them as part
of OCM signature processing.</t>

<t>After successful signature verification, the verifier SHOULD confirm
that the payload is consistent with the signer, i.e. that the
actions implied by the payload were initiated on behalf of the
origin of the request.</t>

</section>
<section anchor="signing-direction-index"><name>Signing Direction Index</name>

<t>This subsection is informative.  HTTP Message Signatures apply only
when the peer advertises the <spanx style="verb">http-sig</spanx> capability; a
<spanx style="verb">must-use-http-sig</spanx> criterion makes signing mandatory for inbound
traffic.  When signing is in play, the signer and verifier roles are:</t>

<t><list style="symbols">
  <t><strong>Share Creation Notification</strong> (<spanx style="verb">POST /shares</spanx>) - the Sending
Server signs; the Receiving Server verifies.  See
<xref target="share-creation-notification">Share Creation Notification</xref>,
<xref target="decision-to-discard">Decision to Discard</xref>, and <xref target="http-message-signatures">HTTP Message
Signatures</xref>.</t>
  <t><strong>Token Request</strong> (<spanx style="verb">POST {tokenEndPoint}</spanx>) - the Receiving Server
signs; the Sending Server verifies.  See <xref target="token-request">Token
Request</xref>, <xref target="token-response">Token Response</xref>, and
<xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>
  <t><strong>Invite Acceptance</strong> (<spanx style="verb">POST /invite-accepted</spanx>) - the Invite Receiver
signs; the Invite Sender verifies.  See <xref target="invite-flow">Invite Flow</xref>
and <xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>
  <t><strong>Share Acceptance Notification</strong> (<spanx style="verb">POST /notifications</spanx>) - the
Receiving Server signs; the Sending Server verifies.  See
<xref target="notifications"></xref> and
<xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>
  <t><strong>Sender-initiated Notification</strong> (<spanx style="verb">POST /notifications</spanx>) - the
Sending Server SHOULD sign; the Receiving Server verifies.  See
<xref target="notifications"></xref> and
<xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>
</list></t>

</section>
</section>
<section anchor="share-creation-notification"><name>Share Creation Notification</name>

<t>To create a Share, the Sending Server SHOULD make a HTTP POST request</t>

<t><list style="symbols">
  <t>to the <spanx style="verb">/shares</spanx> path in the Receiving Server's OCM API</t>
  <t>using <spanx style="verb">application/json</spanx> as the <spanx style="verb">Content-Type</spanx> HTTP request header</t>
  <t>its request body containing a JSON document representing an object
with the fields as described below</t>
  <t>using TLS</t>
  <t>using httpsig [RFC9421]</t>
</list></t>

<t>Before constructing the notification, the Sending Server MUST query
the Receiving Server's OCM API Discovery endpoint.  If the Receiving
Server advertises <spanx style="verb">must-exchange-token</spanx> in its <spanx style="verb">criteria</spanx> and the
Sending Server exposes the <spanx style="verb">exchange-token</spanx> capability with a
<spanx style="verb">tokenEndPoint</spanx>, the Sending Server MUST include <spanx style="verb">must-exchange-token</spanx>
in the requirements of each protocol offered for access and MUST NOT
fall back to legacy shared-secret access.  If the Receiving
Server advertises <spanx style="verb">must-exchange-token</spanx> but the Sending Server does
not expose the <spanx style="verb">exchange-token</spanx> capability or does not have a
<spanx style="verb">tokenEndPoint</spanx>, the Sending Server MUST NOT create the share, 
as the Receiving Server would reject any notification that lacks 
the code-flow requirement.
If the Receiving Server does not advertise <spanx style="verb">must-exchange-token</spanx> in its
<spanx style="verb">criteria</spanx>, the Sending Server MAY still include <spanx style="verb">must-exchange-token</spanx>
voluntarily.</t>

<t>The Sending Server SHOULD NOT create a share for a combination of
resource type, share type, and protocol that the Receiving Server does
not advertise in its Discovery response.  Specifically, for the
share's <spanx style="verb">resourceType</spanx> and <spanx style="verb">shareType</spanx>, and for each protocol offered
in the <spanx style="verb">protocol</spanx> object, the Receiving Server's <spanx style="verb">resourceTypes</spanx> array
SHOULD contain an entry whose <spanx style="verb">name</spanx> equals the <spanx style="verb">resourceType</spanx>, whose
<spanx style="verb">shareTypes</spanx> array contains the <spanx style="verb">shareType</spanx>, and whose <spanx style="verb">protocols</spanx>
object contains that protocol's <spanx style="verb">-receive</spanx> property.  Each such
combination corresponds to an entry in the "OCM Share Payloads"
registry (see <xref target="iana-considerations">IANA Considerations</xref>).
For backwards compatibility reasons, the Sending Server MAY still send
a share with the <spanx style="verb">file, user, webdav</spanx> combination if the Receiving
server does not advertise it, as it MAY be assumed to be supported.</t>

<t>When the notification includes <spanx style="verb">protocol.webapp</spanx>, the Sending Server
MUST expose the <spanx style="verb">exchange-token</spanx> capability and a <spanx style="verb">tokenEndPoint</spanx>,
because WebApp access requires the Receiving Server to exchange
<spanx style="verb">protocol.webapp.sharedSecret</spanx> before presenting the WebApp to the
browser.  If the Sending Server cannot offer this code flow, it MUST NOT
include <spanx style="verb">protocol.webapp</spanx> in the notification.  A Sending Server MAY
serve Web apps either from the same hosting infrastructure or from
external servers in the same organization: to facilitate the integration
of external servers, the RECOMMENDED reference implementation is
described in [OCM-IP].</t>

<section anchor="fields-1"><name>Fields</name>

<t><list style="symbols">
  <t>REQUIRED shareWith (string)
OCM Address of the user or group the provider wants to share the
Resource with.  This MUST be known in advance, either via a previous
Invitation or through other means.
Example: "51dc30ddc473d43a6011e9ebba6ca770@cloud.example.org"</t>
  <t>REQUIRED name (string)
Name of the Resource (file or folder).
Example: "resource.txt"</t>
  <t>OPTIONAL description (string)
Optional description of the Resource (file or folder).
Example: "This is the Open API Specification file (in YAML
format) of the Open Cloud Mesh API."</t>
  <t>REQUIRED providerId (string)
Opaque value to identify the Shared Resource at the provider side.
This MUST be unique per Resource and per share, such that multiple
shares of a given Resource are guaranteed to get different values.
Example: 7c084226-d9a1-11e6-bf26-cec0c932ce01</t>
  <t>OPTIONAL collectionId (string)
Opaque identifier of the Collection to which the Shared Resource
belongs.  Multiple Resources and Shares MAY carry the same value;
global uniqueness is not required.  This identifier MAY be advertised
out of band, for example in a catalog, and used in a <spanx style="verb">REQUEST_SHARE</spanx>
notification.  It MAY also be included in unsolicited Shares.
The Receiving Server MAY use it to associate incoming Shares with a
pending request for the Collection to the Sending Server.
It does not replace <spanx style="verb">providerId</spanx> or grant access to any Resource.
Example: "research-data-123"</t>
  <t>OPTIONAL collectionSize (integer)
Total number of distinct Shares representing the Collection for this
recipient, including this Share.  When <spanx style="verb">collectionId</spanx> is present and
the total is known, <spanx style="verb">collectionSize</spanx> SHOULD be included.  When
present, it MUST be at least 1 and MUST be accompanied by
<spanx style="verb">collectionId</spanx>.  If the total is unknown, <spanx style="verb">collectionSize</spanx> MUST be
omitted.  A Share offering multiple protocols counts as one Share.
When included in Shares fulfilling the same request, the values MUST
agree.  The Receiving Server MAY compare this value with the number
of distinct <spanx style="verb">providerId</spanx> values received for the Collection and
recipient from the Sending Server to determine whether receipt of the
Collection is complete.</t>
  <t>REQUIRED owner (string) -
OCM Address of the user who owns the
Resource.
Example: "6358b71804dfa8ab069cf05ed1b0ed2a@cloud.example.org"</t>
  <t>REQUIRED sender (string) -
OCM Address of the user that wants to share
the Resource.
Example: "527bd5b5d689e2c32ae974c6229ff785@cloud.example.org"</t>
  <t>OPTIONAL ownerDisplayName (string)
Display name of the owner of the Resource
Example: "Dimitri"</t>
  <t>OPTIONAL senderDisplayName (string)
Display name of the user that wants to share the Resource
Example: "John Doe"</t>
  <t>REQUIRED shareType (string)
SHOULD have a value of "user" or "group", to indicate that the first
part of the <spanx style="verb">shareWith</spanx> OCM Address refers to a Receiving Party who
is a single user of the Receiving Server, or a group of users at the
Receiving Server.  Other values MAY be used provided they are
registered in the "OCM Share Types" registry (see
<xref target="iana-considerations">IANA Considerations</xref>); for example, [OCM-MLS]
registers the "federation" share type for a group of users that
spans multiple OCM Servers.
The Sending Server SHOULD only use a <spanx style="verb">shareType</spanx> that the Receiving
Server advertises for the share's <spanx style="verb">resourceType</spanx> in its Discovery
response, i.e. one listed in the <spanx style="verb">shareTypes</spanx> array of the matching
<spanx style="verb">resourceTypes</spanx> entry (see
<xref target="share-creation-notification">Share Creation Notification</xref>).</t>
  <t>REQUIRED resourceType (string)
Resource type (file, folder, calendar, contact, ...).  If the
Resource is a folder, implementations SHOULD advertise it as
<spanx style="verb">folder</spanx> rather than <spanx style="verb">file</spanx>, in order to streamline the processing
by the Receiving Server.
Registered values are listed in the "OCM Resource Types" registry
(see <xref target="iana-considerations">IANA Considerations</xref>).</t>
  <t>OPTIONAL expiration (integer)
The expiration time for the OCM share, in seconds
of UTC time since Unix epoch.  If omitted, it is assumed that the
share does not expire.  A sender server MAY use it to signal that
the resource represents a cached copy of a dataset that was made
available for an efficient data transfer to the destination server.</t>
  <t>OPTIONAL encryption (object)
Optional JSON object with encryption information for the share.  If
omitted, it is assumed that the resource is not encrypted.  For
encrypted resources, the actual key material is to be exchanged out
of band, and this object MUST include:
  <list style="symbols">
      <t>REQUIRED resourceId (string) - a unique identifier of the
underlying resource.</t>
      <t>REQUIRED scheme (string) - an identifier of the encryption scheme
used to encrypt the resource, such as "ocm-pgp".  Registered values
are listed in the "OCM Encryption Schemes" registry (see
<xref target="iana-considerations">IANA Considerations</xref>).</t>
      <t>REQUIRED {schemeObject} (object) - an object keyed with the given
scheme, containing the details of the encryption used.
For the "ocm-gpg" scheme, it MUST contain:
      <list style="symbols">
          <t>fingerprints (array of strings) - one or more fingerprints of
the public keys used to encrypt the resource.
For the "ocm-mls" scheme, it MUST contain:</t>
          <t>cipher (string) - the encryption algorithm used to encrypt the
resource as in [RFC9180] Section 7.3.</t>
        </list></t>
    </list></t>
  <t>REQUIRED protocol (object)
JSON object with specific options for each protocol.
The supported protocols are:
  <list style="symbols">
      <t><spanx style="verb">webdav</spanx>, to access the data via HTTP WebDAV.</t>
      <t><spanx style="verb">webapp</spanx>, to access remote web applications.</t>
      <t><spanx style="verb">ssh</spanx>, to access the data via a public/private key pair.
Other custom protocols might be added in the future.
Registered protocol values are listed in the "OCM Protocols"
registry, and the valid resource-type/share-type/protocol
combinations in the "OCM Share Payloads" registry (see
<xref target="iana-considerations">IANA Considerations</xref>).
In case a single protocol is offered, there are three ways to
specify this object:
Option 1: Set the <spanx style="verb">name</spanx> field to the name of the protocol,
and put the protocol details in a field named <spanx style="verb">options</spanx>.
Option 2: Set the <spanx style="verb">name</spanx> field to the name of the protocol,
and put the protocol details in a field carrying the name of
the protocol.
Option 3: Set the <spanx style="verb">name</spanx> field to <spanx style="verb">multi</spanx>, and put the
protocol details in a field carrying the name of the protocol.
Option 1 using the <spanx style="verb">options</spanx> field is <em>deprecated</em>.
Implementations are encouraged to transition to the new
optional properties defined below, such that this field
may be removed in a future major version of the spec.
When specifying more than one protocol as different ways to
access the Share, the <spanx style="verb">name</spanx> field needs to be set to <spanx style="verb">multi</spanx>.
If <spanx style="verb">multi</spanx> is given, one or more protocol
endpoints are expected to be defined according to the
optional properties specified below.
Otherwise, at least <spanx style="verb">webdav</spanx> is expected to be
supported, and its options MAY be given in the opaque
<spanx style="verb">options</spanx> payload for compatibility with v1.0
implementations (see examples).  Note though that this
format is <em>deprecated</em>.
Warning: client implementers should be aware that v1.1+
servers MAY support both <spanx style="verb">webdav</spanx> and <spanx style="verb">multi</spanx>, but v1.0
servers MAY only support <spanx style="verb">webdav</spanx>.</t>
    </list></t>
  <t>Protocol details for <spanx style="verb">webdav</spanx> MAY contain:
  <list style="symbols">
      <t>OPTIONAL accessTypes (array of strings) - The type of access
being granted to the remote resource.  If omitted, it defaults to
<spanx style="verb">['remote']</spanx>.  A subset of:
      <list style="symbols">
          <t><spanx style="verb">remote</spanx> signals the recipient that the resource is available
for remote access and interactive browsing.</t>
          <t><spanx style="verb">datatx</spanx> signals the recipient that the resource is
available for data transfer.  If no expiration is given, the share
is suitable e.g. for sync use-cases, whereas if an expiration date
is set, the above clause MAY apply and the recipient SHOULD notify
the sender upon completing the data transfer, in order to ease
cache operations on the Sending Server.  The recipient MAY delegate
a third-party service to execute the data transfer on their behalf.</t>
        </list></t>
      <t>REQUIRED uri (string)
A URI to access the Remote Resource.  The URI MAY be relative,
such as a key or a UUID, in which case the prefix exposed by the
<spanx style="verb">/.well-known/ocm</spanx> endpoint MUST be used to access the Resource,
or it MAY be absolute, including a hostname.  In all cases, for a
<spanx style="verb">folder</spanx> Resource, the composed URI acts as the root path, such
that other files located within it MUST be accessible by
appending their relative path to that URI.</t>
      <t>REQUIRED sharedSecret (string)
A secret to be used to access the Resource, such as
a bearer token.  To prevent leaking it in logs it
MUST NOT appear in any URI.</t>
      <t>OPTIONAL permissions (array of strings) -
The permissions granted to the sharee.  A subset of:
      <list style="symbols">
          <t><spanx style="verb">read</spanx> allows read-only access including download of a copy.</t>
          <t><spanx style="verb">write</spanx> allows create, update, and delete rights on the Resource.</t>
          <t><spanx style="verb">share</spanx> allows re-share rights on the Resource.</t>
        </list></t>
      <t>OPTIONAL requirements (array of strings) -
The requirements that the sharee MUST fulfill to
access the Resource.  A subset of:
      <list style="symbols">
          <t><spanx style="verb">must-exchange-token</spanx> requires the recipient to
exchange the given <spanx style="verb">sharedSecret</spanx> via a signed HTTPS request
to the Sending Server's {tokenEndPoint} [RFC6749].
This MAY be used if the Sending Server exposes the
<spanx style="verb">exchange-token</spanx> capability and <spanx style="verb">tokenEndPoint</spanx>, and MUST be
included when the Receiving Server advertises <spanx style="verb">must-exchange-token</spanx>
in criteria.</t>
          <t><spanx style="verb">must-use-mfa</spanx> requires the consumer to be MFA-authenticated.
This MAY be used if the recipient provider exposes the
<spanx style="verb">enforce-mfa</spanx> capability.</t>
        </list></t>
      <t>OPTIONAL size (integer)
The size of the resource to be transferred, useful
especially in case of <spanx style="verb">datatx</spanx> access type.</t>
    </list></t>
  <t>Protocol details for <spanx style="verb">webapp</spanx> MAY contain:
  <list style="symbols">
      <t>REQUIRED uri (string)
A URI to a client-browsable view of the Shared Resource, such
that users MAY use a web application available at the Sending
Server.  The URI MUST be absolute, including a hostname.  In
case the underlying Resource is a folder, the URI MUST act as a
root path, such that files located within the folder are made
accessible in the web app by appending their relative path to
the URI.</t>
      <t>REQUIRED targets (array of strings) - How the recipient SHOULD
present the URI to the user.  The <spanx style="verb">targets</spanx> array MUST NOT be
empty.  A subset of:
      <list style="symbols">
          <t><spanx style="verb">blank</spanx> signals the recipient to open the URI in a top-level
browsing context chosen by the receiver, such as a new window or
tab, or a full page navigation in the current window.</t>
          <t><spanx style="verb">iframe</spanx> signals the recipient to embed the URI in an iframe
within its own UI, when the Sending Server allows framing by
this receiver.
A Sending Server MUST NOT offer a target that the recipient did
not advertise in its <spanx style="verb">webapp-receive</spanx> discovery property.</t>
        </list></t>
      <t>REQUIRED permissions (array of strings) -
The permissions granted to the sharee.  MUST NOT be empty.
A subset of:
      <list style="symbols">
          <t><spanx style="verb">view</spanx> allows access to the web app in view-only mode.</t>
          <t><spanx style="verb">read</spanx> allows read and download access via the web app.</t>
          <t><spanx style="verb">write</spanx> allows full editing rights via the web app.</t>
          <t><spanx style="verb">share</spanx> allows re-share rights on the Resource.  This only
applies to web apps that provide a mechanism for re-sharing.</t>
        </list></t>
      <t>REQUIRED requirements (array of strings) -
The requirements that the sharee MUST fulfill to
access the Resource.  The requirements MUST at least include
<spanx style="verb">must-exchange-token</spanx>.  If multiple protocols are present in the
share payload, the requirements for the different protocols MUST
agree.  For example, if a webapp share is sent in the same payload
as a webdav share, both protocols MUST carry the same
requirements, and both requirement arrays MUST include
<spanx style="verb">must-exchange-token</spanx>.</t>
      <t>REQUIRED sharedSecret (string)
A secret for accessing the remote web app.  To give access to the
remote app, the receiver MUST first exchange this value at the
Sending Server's {tokenEndPoint} using the Code Flow, then perform
an HTTP POST request to the given <spanx style="verb">uri</spanx> with the resulting bearer
token in a form field named <spanx style="verb">access_token</spanx> (see
<xref target="resource-access">Resource Access</xref>).  The shared secret MUST NOT
be exposed to the browser and MUST NOT appear in any URI.</t>
      <t>OPTIONAL apps (array of objects)
The web applications available at the Sending Server to access
the Shared Resource.  This is useful in particular when the
Resource is a folder, whose files can be opened by different web
applications depending on their format, and the OCM share payload
includes as well a transport protocol such as <spanx style="verb">webdav</spanx>: the
receiving OCM server MAY then implement a UI that allows users to
navigate the folder, and open the files on the offered web apps
according to the files' type.  If present, the array MUST NOT be
empty and MUST NOT contain more than one entry per given <spanx style="verb">name</spanx>.
Each entry contains:
      <list style="symbols">
          <t>REQUIRED name (string) - A human-friendly name of the web
application, to be used in user interfaces when referring to
this Share.</t>
          <t>REQUIRED mediaTypes (array of strings) - The media types (MIME
types) that this web application can handle.  The array MUST
NOT be empty.  This can be any media type entries from the IANA
Media Type registry.  The receiver MAY use this as a hint for UI
or routing decisions, e.g. to show which web application opens
a given file, and MAY ignore values it does not understand.
Unlike <spanx style="verb">appIconHint</spanx>, this describes formats the web
application can open rather than the share-level icon hint.
[RFC6838]</t>
        </list>
The order of the entries MAY be used by the Sending Server to
express a preference: when multiple web applications can handle
the same media type, the receiver SHOULD consider the first
matching entry as the default one.  All web applications listed
are accessed through the same <spanx style="verb">uri</spanx>, <spanx style="verb">sharedSecret</spanx>, <spanx style="verb">targets</spanx>,
<spanx style="verb">permissions</spanx> and <spanx style="verb">requirements</spanx>.  Example:      <vspace blankLines='1'/>
        <figure type="json"><artwork><![CDATA[
        "apps": [
          {
            "name": "HedgeDoc",
            "mediaTypes": ["text/markdown", "text/html"]
          },
          {
            "name": "Collabora",
            "mediaTypes": [
              "application/vnd.oasis.opendocument.text",
              "application/vnd.oasis.opendocument.spreadsheet"
            ]
          }
        ]
]]></artwork></figure>
      </t>
      <t>OPTIONAL appIconHint (string)
A string in the form of a media type (MIME type) that describes the
share as a whole, primarily intended as a way for the receiving
server to select an appropriate local icon for the share.  This is
display metadata and MUST NOT be interpreted as fetchable or
executable content.  It does not need to appear in any of the
<spanx style="verb">apps</spanx> media types, but SHOULD describe the primary shared
resource. [RFC6838]</t>
    </list></t>
  <t>Protocol details for <spanx style="verb">ssh</spanx> MAY contain:
  <list style="symbols">
      <t>OPTIONAL accessTypes (array of strings) - The type of access
being granted to the remote resource.  If omitted, it defaults to
<spanx style="verb">['remote']</spanx>.  A subset of:
      <list style="symbols">
          <t><spanx style="verb">remote</spanx> signals the recipient that
the resource is available for remote access, e.g. via sshfs.</t>
          <t><spanx style="verb">datatx</spanx> signals the recipient to transfer the resource
from the given URI via scp.  The recipient MAY delegate a
third-party service to execute the data transfer on their behalf.</t>
        </list></t>
      <t>REQUIRED uri (string)
The full address to be used for ssh or scp access, in the form
<spanx style="verb">username@host.fqdn:port/resource/path</spanx>, where the <spanx style="verb">username</spanx> is
chosen by the Sending Server and does not necessarily need to match
the recipient's OCM Address.  Authentication is expected to take
place via public/private key: the Receiving Server MUST reply to
such a Share Creation Notification by sending back their public
key, for the Sender Server to authorize access to the Resource.</t>
    </list></t>
</list></t>

</section>
<section anchor="response"><name>Response</name>

<t>The Share Creation Notification Response SHOULD be a HTTP response:</t>

<t><list style="symbols">
  <t>in response to the Share Creation Notification Request</t>
  <t>using <spanx style="verb">application/json</spanx> as the <spanx style="verb">Content-Type</spanx> HTTP response header</t>
</list></t>

<t>A 201 response status means the Share Creation Notification Request was
successful.  In this case, the response body MUST contain a JSON
document representing an object with the following string fields:
  - REQUIRED: <spanx style="verb">recipientDisplayName</spanx> - the Recipient's display name.
  - OPTIONAL: <spanx style="verb">recipientPublicKeys</spanx> - the Recipient's public key(s).
    This property MUST be returned when the protocol of the incoming
    share was <spanx style="verb">ssh</spanx>.
A 400 response status means some parameters were invalid or missing.
A 401 response status means the Sender cannot be authenticated as
a trusted service.
A 403 response status means the Sender is not authorized to create
shares.
A 501 response status means either the Receiver does not support
incoming external shares, or the share type or the resource type
are not supported.
A 503 response status means that the Receiver is temporary unavailable.</t>

</section>
<section anchor="decision-to-discard"><name>Decision to Discard</name>

<t>The Receiving Server MAY discard the notification if any of the
following hold true:</t>

<t><list style="symbols">
  <t>the HTTP Message Signature is missing but the Sending Server
advertises the <spanx style="verb">http-sig</spanx> capability in the Discovery response
obtained from the FQDN part of the <spanx style="verb">sender</spanx> field in the request
body</t>
  <t>the Sending Server advertises the <spanx style="verb">http-sig</spanx> capability but its
Discovery response carries no <spanx style="verb">jwksUri</spanx></t>
  <t>the HTTP Message Signature is missing</t>
  <t>the HTTP Message Signature is not valid (see <xref target="http-message-signatures">HTTP Message
Signatures</xref>)</t>
  <t>no trusted JWK Set can be obtained for the FQDN part of the
<spanx style="verb">sender</spanx> field in the request body, via the <spanx style="verb">jwksUri</spanx> field of its
Discovery response</t>
  <t>that JWK Set contains no key whose <spanx style="verb">kid</spanx> equals the <spanx style="verb">keyid</spanx>
signature parameter (see <xref target="http-message-signatures">HTTP Message
Signatures</xref>)</t>
  <t>the Sending Server is denylisted</t>
  <t>the Sending Server is not allowlisted</t>
  <t>the Sending Party is not trusted by the Receiving Party (e.g., no
Invite was exchanged and/or the Sending Party's OCM Address does not
appear in the Receiving Party's address book)</t>
  <t>the Receiving Server is unable to act as an API client for (any of)
the protocol(s) listed for accessing the Resource</t>
  <t>an initial check shows that the Resource cannot successfully be
accessed through (any of) the protocol(s) listed</t>
</list></t>

</section>
<section anchor="receiving-party-notification"><name>Receiving Party Notification</name>

<t>If the Share Creation Notification is not discarded by the Receiving
Server, they MAY notify the Receiving Party passively by adding the
Share to some inbox list, and MAY also notify them actively through for
instance a push notification or an email message.</t>

<t>They could give the Receiving Party the option to accept or reject the
share, or add the share automatically and only send an informational
notification that this happened.</t>

</section>
</section>
<section anchor="notifications"><name>Notifications</name>

<t>This optional endpoint is used to inform the other party about a change
that concerns a previously known entity, such as a Resource or a
trusted Share type (e.g. a user).</t>

<t>A Server that intends to send a notification SHOULD make a HTTP POST
request:</t>

<t><list style="symbols">
  <t>to the <spanx style="verb">/notifications</spanx> path in the Receiving Server's OCM API</t>
  <t>using <spanx style="verb">application/json</spanx> as the <spanx style="verb">Content-Type</spanx> HTTP request header</t>
  <t>its request body containing a JSON document representing an object
with the fields as described below</t>
  <t>using TLS</t>
  <t>using httpsig [RFC9421]</t>
</list></t>

<section anchor="fields-2"><name>Fields</name>

<t><list style="symbols">
  <t>REQUIRED notificationType (string) - it MUST be one of the
registered values listed in the "OCM Notification Types"
registry (see <xref target="iana-considerations">IANA Considerations</xref>).</t>
  <t>REQUIRED senderDomain (string) - the host and optional port of the
sender's OCM Server, using the <spanx style="verb">host [ ":" port ]</spanx> syntax defined for
OCM Addresses.  A Receiving Server SHOULD use this information to
verify the HTTP message signature on the request, and it SHOULD also
use it to validate the underlying share or resource the notification
is about.</t>
  <t>OPTIONAL resourceType (string) - the type of the resource this
notification is about (e.g., <spanx style="verb">file</spanx>).</t>
  <t>OPTIONAL shareType (string) - the type of recipient this notification
is about (e.g., <spanx style="verb">user</spanx>).</t>
  <t>OPTIONAL providerId (string) - the identifier assigned by the
Sending Server to the underlying share, if applicable. This
field is <em>deprecated</em> and SHOULD NOT be used.</t>
  <t>OPTIONAL collectionId (string) - the identifier of the Collection.
It is REQUIRED for <spanx style="verb">REQUEST_SHARE</spanx> and for a <spanx style="verb">SHARE_DECLINED</spanx>
notification declining such a request.</t>
  <t>OPTIONAL notification (object) - optional additional parameters,
depending on the notification and the resource type.</t>
</list></t>

<t>A Notification payload MUST include either the <spanx style="verb">resourceType</spanx> or the
<spanx style="verb">shareType</spanx>, or both when relevant.  Collection-scoped notifications
MUST set <spanx style="verb">resourceType</spanx> to <spanx style="verb">collection</spanx> and MUST include <spanx style="verb">collectionId</spanx>.
<spanx style="verb">REQUEST_SHARE</spanx> MUST also include <spanx style="verb">shareType</spanx>.
Multiple Notification types are defined for different purposes, and
additional types MAY be defined by implementers and registered in the
"OCM Notification Types" IANA Registry.  For each notification type,
a specific format MAY be defined for the optional notification object.
In the sections below, the base Notification types are detailed along
with their specific payload.</t>

</section>
<section anchor="share-acceptance-and-updating"><name>Share Acceptance and Updating</name>

<t>A notification MAY be sent by a recipient to let the provider know that
the recipient accepted or declined a share, in response to a Share
Creation Notification.  Similarly, it MAY be sent by a provider to let
the recipient know that the provider updated or removed a given share,
such that the recipient MAY clean it up from its database.  In all such
cases, the <spanx style="verb">resourceType</spanx> MUST match the <spanx style="verb">resourceType</spanx> of the
underlying share (e.g., <spanx style="verb">file</spanx>), the <spanx style="verb">shareType</spanx> MAY be omitted but if
present it MUST match the <spanx style="verb">shareType</spanx> of the underlying share, and the
<spanx style="verb">notificationType</spanx> MUST be one of:
- "SHARE_ACCEPTED", to inform about the acceptance of a share.
- "SHARE_DECLINED", to inform that a share was not accepted.
- "SHARE_UNSHARED", to inform the Receiving Server that the share
  was removed and is not accessible any longer.
- "SHARE_CHANGE_PERMISSION", to inform the Receiving Server that
  the permissions of a share were updated.
Further, the <spanx style="verb">notification</spanx> object MUST include the following fields:
* OPTIONAL message (string) - an optional human-readable message that
  describes the event.
* REQUIRED file (object) - an object containing the details of the
  event, including:
  * REQUIRED providerId (string) - the unique identifier assigned
    by the Sending Server to the underlying share in a previous Share
    Creation Notification.
  * OPTIONAL permissions (array of strings) - The permissions granted
    to the sharee, in case they have changed in the context of a
    <spanx style="verb">SHARE_CHANGE_PERMISSION</spanx> notification.  The allowed values match
    the <spanx style="verb">permissions</spanx> values specified in the <spanx style="verb">webdav</spanx> protocol of a
    <xref target="share-creation-notification">Share Creation Notification</xref>.</t>

<t><spanx style="verb">SHARE_UNSHARED</spanx> and <spanx style="verb">SHARE_CHANGE_PERMISSION</spanx> MUST identify the
individual Share by <spanx style="verb">providerId</spanx> and carry its <spanx style="verb">resourceType</spanx>, including
when that Share carries a <spanx style="verb">collectionId</spanx>.  The <spanx style="verb">collectionId</spanx> MUST NOT
be used as the target identifier of these notifications.</t>

<t>The same notifications identically apply to resources of type <spanx style="verb">folder</spanx>.
For other resources with a different <spanx style="verb">resourceType</spanx> attribute, a
Sending Server MAY implement the same notifications, provided that
they get registered in the related IANA Registry.  Note that the
Sending Server MAY at any time revoke access to a Resource (effectively
undoing or deleting the Share) without notifying the Receiving Server.</t>

</section>
<section anchor="resharing-and-request-to-share"><name>Resharing and Request to Share</name>

<t>The "REQUEST_RESHARE" notification type MAY be used by the Receiving
Server to ask the Sending Server to share a given, previously shared
Resource, with another third Receiving Party.  The Sending Server MAY
discard this request, e.g. in case the third party is not trusted, or
the share was originally granted without a <spanx style="verb">share</spanx> permission.  If
the Sending Server accepts the request, it MUST create a new share to
the third party: in this case, all necessary exchanges and access
requests MUST take place between the third party and the Sending
Server, without further including the Receiving Server in the process.</t>

<t>For a "REQUEST_RESHARE" notification, the <spanx style="verb">resourceType</spanx> MUST match the
<spanx style="verb">resourceType</spanx> of the original share (e.g., <spanx style="verb">file</spanx>, <spanx style="verb">folder</spanx>, ...), the
<spanx style="verb">shareType</spanx> MAY be omitted but if present it MUST match the <spanx style="verb">shareType</spanx>
of the original share, and the the <spanx style="verb">notification</spanx> object MUST include
the following fields:
* OPTIONAL message (string) - an optional human-readable message that
  describes the request.
* REQUIRED file (object) - an object containing the details of the
  request, including:
  * REQUIRED providerId (string) - the unique identifier assigned
    by the Sending Server to the underlying share in a previous Share
    Creation Notification.
  * REQUIRED shareWith (string) - the OCM Address of the third party
    the underlying share should be reshared with.
  * OPTIONAL permissions (array of strings) - The permissions to be
    granted to the third party.  The allowed values match the
    <spanx style="verb">permissions</spanx> values specified in the <spanx style="verb">webdav</spanx> protocol of a
    <xref target="share-creation-notification">Share Creation Notification</xref>.</t>

<t>The Receiving Server SHOULD receive a response whether the reshare
request was fulfilled or not.  In any case, a Receiving Server MUST
NOT directly reshare a Resource, even when a <spanx style="verb">share</spanx> permission was
granted, and MUST always send a <spanx style="verb">"REQUEST_RESHARE"</spanx> Notification
to the Sending Server.</t>

<t>Similarly, the <spanx style="verb">"REQUEST_SHARE"</spanx> notification type MAY be used by a
given Recipient OCM Server, to ask a remote OCM Server to share and
grant access to a Collection, previously made known to the Recipient
Server out of band, for example through a catalog.  The <spanx style="verb">resourceType</spanx>
MUST be <spanx style="verb">collection</spanx>.  The <spanx style="verb">collectionSize</spanx> field applies only to Share
Creation Notifications and MUST NOT be included in the request.  The
request has the following top-level fields:</t>

<t><list style="symbols">
  <t>REQUIRED collectionId (string) - Opaque identifier of the requested
Collection.  Example: "research-data-123".</t>
  <t>REQUIRED shareType (string) - Type of the recipient identified by
<spanx style="verb">notification.collection.shareWith</spanx>, according to the "OCM Share
Types" registry, for example <spanx style="verb">user</spanx>, <spanx style="verb">group</spanx>, or <spanx style="verb">federation</spanx>.
Each resulting Share Creation Notification MUST use this <spanx style="verb">shareType</spanx>.</t>
  <t>REQUIRED notification (object) - an object containing:
  <list style="symbols">
      <t>OPTIONAL message (string) - an optional human-readable message that
describes the request.</t>
      <t>REQUIRED collection (object) - an object containing the details of
the request, including:
      <list style="symbols">
          <t>REQUIRED owner (string) - OCM Address of the user who will be
requested to share the Collection's Resources.</t>
          <t>REQUIRED shareWith (string) - OCM Address of the recipient that
wishes to receive Shares of the Collection's Resources.
Example: "51dc30ddc473d43a6011e9ebba6ca770@cloud.example.org"</t>
          <t>REQUIRED permissions (array of strings) - The permissions to be
granted to the requesting party.  The allowed values match the
<spanx style="verb">permissions</spanx> values specified in the <spanx style="verb">webdav</spanx> protocol of a
<xref target="share-creation-notification">Share Creation Notification</xref>.</t>
        </list></t>
    </list></t>
</list></t>

<t>The remote OCM Server MAY choose to fulfill the request, according
to its trust policies: in that case, it MUST respond with HTTP 201
to the caller, and asynchronously ask for permission to the <spanx style="verb">owner</spanx>
user.  If the owner agrees, it MUST send one or more
<xref target="share-creation-notification">Share Creation Notifications</xref>, each
including the <spanx style="verb">shareWith</spanx> recipient and the requested <spanx style="verb">collectionId</spanx>
unchanged.  Each Share MUST have its own <spanx style="verb">providerId</spanx> and declare its
own <spanx style="verb">resourceType</spanx> and protocols.  The Sending Server determines the
number of Shares and MAY offer multiple protocols for a Resource in
one Share.</t>

<t>If the owner disagrees, the remote OCM Server MUST send back a
<spanx style="verb">"SHARE_DECLINED"</spanx> notification with the requested <spanx style="verb">collectionId</spanx> and
the requested recipient in <spanx style="verb">notification.collection.shareWith</spanx>.
This notification MUST set <spanx style="verb">resourceType</spanx> to <spanx style="verb">collection</spanx> and MAY echo
the request's <spanx style="verb">shareType</spanx>.  No <spanx style="verb">providerId</spanx> is required because no Share
has been created.
It MUST NOT be interpreted as removing or changing any existing Share.
The remote OCM Server MAY also decline such request because of its
policies, without even informing the <spanx style="verb">owner</spanx>: in this case, it MUST
respond to the <spanx style="verb">"REQUEST_SHARE"</spanx> notification with an appropriate HTTP
response type such as HTTP 404.</t>

</section>
<section anchor="recipient-removal"><name>Recipient Removal</name>

<t>A notification MAY report a single contact removal, a user leaving
the Sending Server's realm, or a group removal.</t>

<t>For "CONTACT_REMOVED", the Receiving Server MAY reciprocally remove
the contact between the two identified users. This notification alone
MUST NOT withdraw or reject existing Shares in either direction, or
affect other users' contacts. Each user MAY separately withdraw Shares
they issued or decline Shares they received, using the corresponding
per-share notifications.</t>

<t>For "USER_REMOVED" and "GROUP_REMOVED", the Receiving Server SHOULD
remove the departed recipient from its trusted users and related
shares. A single contact removal MUST NOT be reported as user departure.</t>

<t>For these cases, a notification payload is to be formed such that the
<spanx style="verb">resourceType</spanx> MUST be omitted, the <spanx style="verb">shareType</spanx> is set to the affected
shareType being removed, such as <spanx style="verb">user</spanx> or <spanx style="verb">group</spanx>, and the
<spanx style="verb">notificationType</spanx> MUST be one of:
- "CONTACT_REMOVED", to inform that a single user contact was removed
  from the list of trusted contacts by the peer user.
- "USER_REMOVED", to inform that a user left or was removed from the
  realm of the sending OCM Server, and is therefore no longer reachable
  as a contact.
- "GROUP_REMOVED", to inform about a removed group of users.
Further, the <spanx style="verb">notification</spanx> object MUST include the following fields:
* OPTIONAL message (string) - an optional human-readable message that
  describes the event.
* REQUIRED user or group (object) - an object containing the details
  of the recipient to be removed. In case of <spanx style="verb">user</spanx>, it MUST include:
  * REQUIRED userId (string) - OCM Address of the user that performed
    the removal, or that left.
  * REQUIRED targetUserId (string) - only for "CONTACT_REMOVED": OCM
    Address of the user, local at the target server, that was removed
    by the above peer contact.  It MUST be omitted for "USER_REMOVED",
    where all contacts and shares related to <spanx style="verb">userId</spanx> at the target
    server are to be removed.
  Whereas in case of <spanx style="verb">group</spanx>, it MUST include:
  * REQUIRED groupId (string) - identifier of the group to be removed
    from the target OCM Server.</t>

</section>
</section>
<section anchor="resource-access"><name>Resource Access</name>

<t>To access the Resource, the Receiving Server MAY use multiple ways,
depending on the body of the Share Creation Notification and the
protocol required for access.  The procedure is as follows:</t>

<t><list style="numbers" type="1">
  <t>The receiver MUST extract the OCM Server FQDN from the <spanx style="verb">sender</spanx>
field of the received share, and MUST query the
<xref target="ocm-api-discovery">Discovery</xref> endpoint at that address: let
<spanx style="verb">&lt;sender-ocm-path&gt;</spanx> be the <spanx style="verb">resourceTypes[0].protocols.webdav</spanx> value
to be used later, if defined.</t>
  <t>If <spanx style="verb">protocol.name</spanx> is <spanx style="verb">multi</spanx>, the receiver MUST inspect the
<spanx style="verb">protocol.{protocolName}</spanx> properties corresponding to the protocol
of concern, and act according to its semantics.  For the specific
case where <spanx style="verb">protocol.webdav</spanx> is available and the receiver wants
to use it, the following steps are to be followed.</t>
  <t>The <spanx style="verb">protocol.webdav.requirements</spanx> MUST be inspected:
3.1. If it includes <spanx style="verb">must-exchange-token</spanx>, the receiver MUST make a
 signed POST request to the path in the Sending Server’s
 {tokenEndPoint}, to exchange the <spanx style="verb">protocol.webdav.sharedSecret</spanx>
 token for a short-lived bearer token, and only use that bearer
 token to access the Resource (See the <xref target="code-flow">Code Flow</xref>
 section).  If the <spanx style="verb">must-exchange-token</spanx> requirement is not present
 and the discovery inspected at step 1 exposes the <spanx style="verb">exchange-token</spanx>
 capability with a <spanx style="verb">tokenEndPoint</spanx>, the receiver MAY attempt the
 token exchange as above, but it MUST fall back to the following
 steps should the process fail.
3.2. If it includes <spanx style="verb">must-use-mfa</spanx>, the Receiving Server MUST ensure
 that the Receiving Party has been authenticated with MFA, or prompt
 the consumer in order to elevate their session, if applicable.</t>
  <t>The <spanx style="verb">protocol.webdav.uri</spanx> property MUST now be inspected: if it's a
complete URI, the receiver MUST make a HTTP PROPFIND request against
it to access the Remote Resource, otherwise it is to be taken as an
identifier <spanx style="verb">&lt;id&gt;</spanx>, in which case the receiver MUST make a HTTP
PROPFIND request to: <spanx style="verb">https://&lt;sender-host&gt;&lt;sender-ocm-path&gt;/&lt;id&gt;</spanx>
in order to access to the Remote Resource.  The receiver MUST pass
an <spanx style="verb">Authorization: bearer</spanx> header with either the short-lived bearer
token obtained in step 3.1., if applicable, or the
<spanx style="verb">protocol.webdav.sharedSecret</spanx> value.</t>
  <t>Otherwise, if <spanx style="verb">protocol.name</spanx> is <spanx style="verb">webdav</spanx> the receiver SHOULD inspect
the <spanx style="verb">protocol.options</spanx> property: if <spanx style="verb">protocol.options.sharedSecret</spanx>
is defined, then the receiver SHOULD make a HTTP PROPFIND request to
<spanx style="verb">https://&lt;sharedSecret&gt;:@&lt;sender-host&gt;&lt;sender-ocm-path&gt;</spanx>.  Note that
this access method, based on Basic Auth, is <em>deprecated</em> and may be
removed in a future release of the Protocol.  If a secret cannot be
identified (e.g. because <spanx style="verb">protocol.options</spanx> is undefined), then
the receiver SHOULD discard the share as invalid.</t>
  <t>For the specific case where <spanx style="verb">protocol.webapp</spanx> is available and the
receiver wants to use it, the receiver MUST present the web app to
the user by opening <spanx style="verb">protocol.webapp.uri</spanx> using a target selected
from the intersection of <spanx style="verb">protocol.webapp.targets</spanx> and the targets
advertised in the receiver's <spanx style="verb">webapp-receive</spanx> discovery property.
If this intersection is empty, the receiver MUST treat the <spanx style="verb">webapp</spanx>
option as unusable for this Share.  If the selected target is
<spanx style="verb">blank</spanx>, the receiver MAY use <spanx style="verb">_blank</spanx> or <spanx style="verb">_top</spanx> according to its
local presentation policy.  The receiver MUST inspect
<spanx style="verb">protocol.webapp.requirements</spanx>: if it includes <spanx style="verb">must-use-mfa</spanx>, the
Receiving Server MUST ensure that the Receiving Party has been
authenticated with MFA, or prompt the consumer in order to elevate
their session, if applicable.  The receiver MUST NOT place the
<spanx style="verb">protocol.webapp.sharedSecret</spanx> in the URI and MUST NOT expose it to
the browser.  Instead, the receiver MUST first exchange it at the
Sending Server's {tokenEndPoint} using the Code Flow, then deliver
the resulting bearer token to the web app via an HTTP POST to
<spanx style="verb">protocol.webapp.uri</spanx> with the token carried in a form field named
<spanx style="verb">access_token</spanx> along with another form field named
<spanx style="verb">expired_session_redirect_uri</spanx>.  The
<spanx style="verb">expired_session_redirect_uri</spanx> value MUST be an absolute HTTPS URI
controlled by the Receiving Server.  The Sending WebApp MAY navigate
the browser to this URI when the posted session expires so that the
Receiving Server can restart access and obtain a fresh token; it
MUST NOT place the shared secret or access token in that URI.
Sending WebApps that do not support session refresh MAY ignore this
field.  This is typically achieved with an auto-submitting
HTML form whose <spanx style="verb">target</spanx> attribute selects the chosen
presentation (e.g. an iframe name, <spanx style="verb">_blank</spanx>, or <spanx style="verb">_top</spanx>).</t>
</list></t>

<t>In all cases, in case the Shared Resource is a folder and the Receiving
Server accesses a Resource within that shared folder, it SHOULD append
its relative path to that URL.  In other words, the Sending Server
SHOULD support requests to URLs such as
<spanx style="verb">https://&lt;sender-host&gt;&lt;sender-ocm-path&gt;/path/to/resource.txt</spanx>.</t>

</section>
<section anchor="code-flow"><name>Code Flow</name>

<t>This section defines the procedure for issuing short-lived bearer access
tokens for use by the Receiving Server when accessing a resource shared
through OCM.  The mechanism is aligned with the OAuth 2.0
<em>authorization_code</em> grant type but is performed entirely as a
server to server interaction between the Sending and Receiving Servers.
No user interaction or redirect is involved. [RFC6749]</t>

<section anchor="token-request"><name>Token Request</name>

<t>To obtain an access token, the Receiving Server MUST send an HTTP POST
request to the Sending Server’s {tokenEndPoint} as discovered in the
OCM provider metadata, following section 4.4.2 of [RFC6749].  The
request payload MUST be in <spanx style="verb">x-www-form-urlencoded</spanx> form, as shown
in the following example:</t>

<sourcecode type="http">
NOTE: '\' line wrapping per RFC 8792

POST {tokenEndPoint} HTTP/1.1
Host: cloud.example.org
Content-Type: application/x-www-form-urlencoded
Content-Digest: sha-256=:81kCnlO5UY/mZ8UgpxBWnq18GY3WhzJnDjOTvSvjbhw=:
Content-Length: 80
Signature-Input: sig1=("@method" "@target-uri" "content-digest" \
  "content-length");created=1730815200;\
  keyid="receiver.example.org#key1";alg="ed25519";tag="ocm"
Signature: sig1=:bM2sV2a4oM8pWc4Q8r9Zb8bQ7a2vH1kR9xT0yJ3uE4wO5lV6bZ\
  1cP2rN3qD4tR5hC=:

grant_type=authorization_code&amp;client_id=receiver.example.org&amp;code=\
  my_secret_code
</sourcecode>

<t>The request MUST be signed using an HTTP Message Signature
[RFC9421].  The <spanx style="verb">client_id</spanx> identifies the Receiving Server and MUST be
set to its fully qualified domain name.  The <spanx style="verb">code</spanx> parameter carries
the authorization secret that was issued by the Sending Server in the
Share Creation Notification.  It is allowed to send the additional
parameters defined in [RFC6749] for the <spanx style="verb">authorization_code</spanx> grant type,
but they MUST be ignored.</t>

</section>
<section anchor="token-response"><name>Token Response</name>

<t>If the request is valid and the code is accepted, the Sending Server
MUST respond with HTTP 200 OK and a OAuth-compliant JSON object
containing the issued token:</t>

<figure type="json"><artwork><![CDATA[
{
  "access_token": "8f3d3f26-f1e6-4b47-9e3e-9af6c0d4ad8b",
  "token_type": "Bearer",
  "expires_in": 300
}
]]></artwork></figure>

<t>The <spanx style="verb">access_token</spanx> is an opaque bearer credential with no internal
structure visible to the Receiving Server.  The token authorizes the
Receiving Server to access the shared resource using the appropriate
transport protocol (e.g., WebDAV).  The <spanx style="verb">expires_in</spanx> value indicates
the token lifetime in seconds.  No <spanx style="verb">refresh_token</spanx> is issued, instead
the same request to the {tokenEndPoint} MUST be repeated before the
<spanx style="verb">access_token</spanx> has expired, to recieve a new <spanx style="verb">access_token</spanx> that can
then be used in the same manner.</t>

</section>
<section anchor="error-responses"><name>Error Responses</name>

<t>If the request is invalid, the Sending Server MUST return an HTTP 400
response with a JSON object containing an OAuth 2.0 error code
[RFC6749]:</t>

<figure type="json"><artwork><![CDATA[
{ "error": "invalid_request" }
]]></artwork></figure>

<t>Permitted error codes are <spanx style="verb">invalid_request</spanx>, <spanx style="verb">invalid_client</spanx>,
<spanx style="verb">invalid_grant</spanx>, <spanx style="verb">unauthorized_client</spanx> and <spanx style="verb">unsupported_grant_type</spanx>.</t>

</section>
<section anchor="decision-table"><name>Decision Table</name>

<t>The directional contract depends first on whether the share is strict.
For strict shares, the Receiving Server's advertised behavior determines
whether the Sending Server can require code flow.  For non-strict
shares, the Sending Server's advertised behavior determines whether
token exchange is available in addition to legacy access.</t>

<t><list style="numbers" type="1">
  <t>If the Sending Server includes <spanx style="verb">must-exchange-token</spanx> in
<spanx style="verb">protocol.webdav.requirements</spanx> and the Receiving Server exposes the
<spanx style="verb">exchange-token</spanx> capability, strict token exchange is required
before the Resource is accessed.</t>
  <t>If the Sending Server includes <spanx style="verb">must-exchange-token</spanx> and the
Receiving Server does not expose the <spanx style="verb">exchange-token</spanx> capability,
the Sending Server SHOULD NOT include that requirement, because the
Receiving Server may be unable to complete the exchange.</t>
  <t>If the Sending Server omits <spanx style="verb">must-exchange-token</spanx> and exposes the
<spanx style="verb">exchange-token</spanx> capability with a <spanx style="verb">tokenEndPoint</spanx>, the Receiving
Server MAY attempt token exchange first and MUST fall back to legacy
shared-secret access if that exchange fails.</t>
  <t>If the Sending Server omits <spanx style="verb">must-exchange-token</spanx> and does not
expose the <spanx style="verb">exchange-token</spanx> capability, only legacy shared-secret
access is available.</t>
</list></t>

<t>The following examples illustrate typical end-to-end outcomes:</t>

<t><list style="numbers" type="1">
  <t>Strict required code flow: Provider A acts as Sending Server and
exposes the <spanx style="verb">exchange-token</spanx> capability with a <spanx style="verb">tokenEndPoint</spanx>.
Provider B acts as Receiving Server and advertises both
<spanx style="verb">exchange-token</spanx> and <spanx style="verb">must-exchange-token</spanx>.  After discovering B's
<spanx style="verb">must-exchange-token</spanx> criteria, A MUST include <spanx style="verb">must-exchange-token</spanx>
in <spanx style="verb">protocol.webdav.requirements</spanx>.  B MUST exchange the
<spanx style="verb">sharedSecret</spanx> at A's <spanx style="verb">tokenEndPoint</spanx> and then use only the bearer
token to access the Resource.</t>
  <t>Optional exchange with fallback: Provider A acts as Sending Server
and exposes the <spanx style="verb">exchange-token</spanx> capability with a <spanx style="verb">tokenEndPoint</spanx>.
Provider B does not advertise <spanx style="verb">must-exchange-token</spanx>, so A sends a
share without <spanx style="verb">must-exchange-token</spanx>.  When B later accesses the
Resource, it MAY attempt the token exchange at A's <spanx style="verb">tokenEndPoint</spanx>,
but if that exchange fails it MUST fall back to the legacy
<spanx style="verb">sharedSecret</spanx>.</t>
  <t>Legacy share to a code-flow-capable peer: Provider A does not
expose the <spanx style="verb">exchange-token</spanx> capability.  Provider B does expose
<spanx style="verb">exchange-token</spanx>, so B is capable of honoring strict inbound shares
from other peers.  Because A does not advertise a <spanx style="verb">tokenEndPoint</spanx>,
A can only send a legacy share and B can only use legacy
shared-secret access for that share.</t>
  <t>Asymmetric role behavior: Provider A exposes <spanx style="verb">exchange-token</spanx> and
<spanx style="verb">must-exchange-token</spanx>, so it can require code flow for inbound
shares when it acts as Receiving Server.  When A later acts as
Sending Server toward Provider B, and B does not advertise
<spanx style="verb">must-exchange-token</spanx>, A MAY omit <spanx style="verb">must-exchange-token</spanx>.  B may then
attempt token exchange against A's <spanx style="verb">tokenEndPoint</spanx> or fall back to
legacy access.  A therefore accepts strict inbound shares while
still choosing a legacy-compatible outbound share.</t>
</list></t>

</section>
</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>[RFC Editor: please replace all occurrences of "RFC XXXX" with the
RFC number assigned to this document and remove this note.]</t>

<section anchor="well-known-uri-for-the-discovery"><name>Well-Known URI for the Discovery</name>

<t>The following value is to be registered in the "Well-Known URIs"
registry (using the template from [RFC8615]):</t>

<dl>
  <dt>URI suffix:</dt>
  <dd>
    <t>ocm</t>
  </dd>
  <dt>Change controller:</dt>
  <dd>
    <t>IETF</t>
  </dd>
  <dt>Specification document(s):</dt>
  <dd>
    <t>RFC XXXX (this document)</t>
  </dd>
  <dt>Status:</dt>
  <dd>
    <t>permanent</t>
  </dd>
  <dt>Related information:</dt>
  <dd>
    <t>N/A</t>
  </dd>
</dl>

</section>
<section anchor="jscontact-types-registry"><name>JSContact Types Registry</name>

<t>The following entry is to be registered in the "JSContact Types"
registry (using the template from [RFC9553]):</t>

<dl>
  <dt>Type Name:</dt>
  <dd>
    <t>ocmAddress</t>
  </dd>
  <dt>Intended Usage:</dt>
  <dd>
    <t>common</t>
  </dd>
  <dt>Since Version:</dt>
  <dd>
    <t>1.0</t>
  </dd>
  <dt>Until Version:</dt>
  <dd>
    <t>N/A</t>
  </dd>
  <dt>Change Controller:</dt>
  <dd>
    <t>IETF</t>
  </dd>
  <dt>Reference or Description:</dt>
  <dd>
    <t>An object representing an OCM address.  The object contains:
</t>

    <t><list style="symbols">
      <t>"address" (String, required): The OCM federated address in
format "user@provider" where provider is the FQDN of an
OCM-capable server.</t>
      <t>"trusted" (Boolean, optional): Whether shares from this address
are automatically accepted.  Default: false.</t>
      <t>"source" (String, optional): How this address was established.
See "JSContact Enum Values" registry for allowed values.</t>
      <t>"label" (String, optional): Human-readable label for this
address.</t>
    </list></t>

    <t>See RFC XXXX, <xref target="jscontact-types-registry"></xref>.</t>
  </dd>
</dl>

</section>
<section anchor="jscontact-properties-registry"><name>JSContact Properties Registry</name>

<t>The following entry is to be registered in the "JSContact Properties"
registry (using the template from [RFC9553]):</t>

<dl>
  <dt>Property Name:</dt>
  <dd>
    <t>ietf.org:ocmAddresses</t>
  </dd>
  <dt>Property Type:</dt>
  <dd>
    <t>String[ocmAddress]</t>
  </dd>
  <dt>Property Context:</dt>
  <dd>
    <t>Card</t>
  </dd>
  <dt>Intended Usage:</dt>
  <dd>
    <t>common</t>
  </dd>
  <dt>Since Version:</dt>
  <dd>
    <t>1.0</t>
  </dd>
  <dt>Until Version:</dt>
  <dd>
    <t>N/A</t>
  </dd>
  <dt>Change Controller:</dt>
  <dd>
    <t>IETF</t>
  </dd>
  <dt>Reference or Description:</dt>
  <dd>
    <t>A map of OCM addresses for a contact.  The keys are arbitrary
identifiers (e.g., "primary", "work") and the values are
ocmAddress objects as defined in the JSContact Types Registry.
See RFC XXXX, <xref target="jscontact-properties-registry"></xref>.</t>
  </dd>
</dl>

</section>
<section anchor="jscontact-enum-values-registry"><name>JSContact Enum Values Registry</name>

<t>The following entry is to be registered in the "JSContact Enum
Values" registry (using the template from [RFC9553]):</t>

<dl>
  <dt>Property Name:</dt>
  <dd>
    <t>ietf.org:ocmAddresses/source</t>
  </dd>
  <dt>Context:</dt>
  <dd>
    <t>Card</t>
  </dd>
  <dt>Since Version:</dt>
  <dd>
    <t>1.0</t>
  </dd>
  <dt>Until Version:</dt>
  <dd>
    <t>N/A</t>
  </dd>
  <dt>Change Controller:</dt>
  <dd>
    <t>IETF</t>
  </dd>
  <dt>Reference or Description:</dt>
  <dd>
    <t>Values indicating how an OCM address was established.  See
RFC XXXX, <xref target="jscontact-enum-values-subregistry"></xref>.</t>
  </dd>
</dl>

<section anchor="jscontact-enum-values-subregistry"><name>JSContact Enum Values Subregistry</name>

<t>IANA will create a subregistry for "ietf.org:ocmAddresses/source"
(Context: Card) in accordance with [RFC9553], Section 3.7.2.  All
entries in the initial contents below have a Since Version of 1.0,
no Until Version, and IETF as the Change Controller.  Initial
contents:</t>

<figure><artwork><![CDATA[
   +==============+==========================================+
   | Enum Value   | Reference/Description                    |
   +==============+==========================================+
   | invite       | Address established via OCM invite flow  |
   |--------------|------------------------------------------|
   | share        | Address established by receiving a share |
   |--------------|------------------------------------------|
   | direct entry | Address added directly by the user       |
   |--------------|------------------------------------------|
]]></artwork></figure>

</section>
</section>
<section anchor="open-cloud-mesh-parameters-registry-group"><name>Open Cloud Mesh Parameters Registry Group</name>

<t>IANA is requested to create a new registry group titled "Open Cloud
Mesh (OCM) Parameters", containing the registries defined in the
following subsections.  Unless stated otherwise, the registration
policy for each registry in this group is "Specification Required"
[RFC8126].  The Designated Expert SHOULD verify that a requested entry
is documented in a stable, publicly available specification and that it
does not duplicate an existing entry.</t>

<section anchor="ocm-resource-types-registry"><name>OCM Resource Types Registry</name>

<t>IANA is requested to create the "OCM Resource Types" registry in the
"Open Cloud Mesh (OCM) Parameters" group.  This registry records the
resource type values used in the "resourceType" field of a
<xref target="share-creation-notification">Share Creation Notification</xref> or
<xref target="notifications">Notification</xref>, and in the "name" field of each entry
in the "resourceTypes" array advertised by the
<xref target="ocm-api-discovery">OCM API Discovery</xref> endpoint.  The <spanx style="verb">collection</spanx>
value is a meta resource type used only for collection-scoped
Notifications; it MUST NOT be used in Share Creation Notifications or
Discovery.</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +===============+============================+===============+
   | Resource Type | Description                | Reference     |
   +===============+============================+===============+
   | file          | A single file              | This document |
   | folder        | A folder/collection        | This document |
   | collection    | A Collection meta-resource | This document |
   +===============+============================+===============+
]]></artwork></figure>

</section>
<section anchor="ocm-protocols-registry"><name>OCM Protocols Registry</name>

<t>IANA is requested to create the "OCM Protocols" registry in the "Open
Cloud Mesh (OCM) Parameters" group.  Each entry records a protocol
property name that MAY appear in the "protocols" object advertised by
the <xref target="ocm-api-discovery">OCM API Discovery</xref> endpoint or in the
"protocol" object of a
<xref target="share-creation-notification">Share Creation Notification</xref>.</t>

<t>A property whose "Role" is "send" (e.g. "webdav") advertises support
for the Sending Server role in Discovery and is the value used in the
share "protocol" object.  Its "-receive" suffixed counterpart (e.g.
"webdav-receive"), whose "Role" is "receive", advertises support for
the Receiving Server role in Discovery.  Which protocols MAY be used
for a given resource type and share type is governed by the
<xref target="ocm-share-payloads-registry">OCM Share Payloads</xref> registry.</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +================+=========+===============+
   | Property       | Role    | Reference     |
   +================+=========+===============+
   | webdav         | send    | This document |
   | webdav-receive | receive | This document |
   | webapp         | send    | This document |
   | webapp-receive | receive | This document |
   | ssh            | send    | This document |
   | ssh-receive    | receive | This document |
   +================+=========+===============+
]]></artwork></figure>

</section>
<section anchor="ocm-share-types-registry"><name>OCM Share Types Registry</name>

<t>IANA is requested to create the "OCM Share Types" registry in the
"Open Cloud Mesh (OCM) Parameters" group.  Each entry records a share
type that MAY appear in the "shareTypes" array advertised by the
<xref target="ocm-api-discovery">OCM API Discovery</xref> endpoint or in the "shareType"
field of a <xref target="share-creation-notification">Share Creation Notification</xref>.
This document registers only the "user" and "group" share types; other
specifications MAY register additional share types in this registry.
The "federation" share type, for example, is registered by [OCM-MLS].</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +============+===============+
   | Share Type | Reference     |
   +============+===============+
   | user       | This document |
   | group      | This document |
   +============+===============+
]]></artwork></figure>

</section>
<section anchor="ocm-share-payloads-registry"><name>OCM Share Payloads Registry</name>

<t>IANA is requested to create the "OCM Share Payloads" registry in the
"Open Cloud Mesh (OCM) Parameters" group.  Whereas the "OCM Resource
Types", "OCM Share Types", and "OCM Protocols" registries record the
identifiers advertised in Discovery, this registry records the
wire format of the share payload itself: each entry binds a meaningful
combination of resource type, share type, and one or more protocols to
the document that completely specifies the wire format of the
<xref target="share-creation-notification">Share Creation Notification</xref> for that
combination.  Two implementations may agree on the Discovery
identifiers and still fail to interoperate if the fields and structure
of the payload are left unspecified; this registry is where that wire
format is pinned down.</t>

<t>Every value in the "Resource Type", "Share Type", and "Protocols"
columns MUST already appear in the corresponding "OCM Resource Types",
"OCM Share Types", or "OCM Protocols" registry.  For each entry,
the Designated Expert MUST verify that the referenced specification
completely specifies the wire format of the share payload for the
combination, including every required and optional field and the full
shape of the "protocol" details object.</t>

<t>The registered combinations are a constrained subset, not the full
Cartesian product of those three registries, even though for the
initial content the subset and the Cartesian product correspond.
However, in other cases beyond file sharing, a protocol may only be
meaningful for certain resource types.  A calendar event, for example,
is usually shared over CalDAV or JMAP, not over ssh.  Other
specifications MAY register additional combinations, including ones
that extend an already-registered protocol to a new resource type or
share type; doing so does not modify that protocol's own registration.
The federation combinations are registered in this way by [OCM-MLS].
If someone wants to specify how to share calendar events over ssh in an
interoperable way, they can do so using this very mechanism.</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +===============+============+=====================+===============+
   | Resource Type | Share Type | Protocols           | Reference     |
   +===============+============+=====================+===============+
   | file          | user       | webdav, webapp, ssh | This document |
   | file          | group      | webdav, webapp, ssh | This document |
   | folder        | user       | webdav, webapp, ssh | This document |
   | folder        | group      | webdav, webapp, ssh | This document |
   +===============+============+=====================+===============+
]]></artwork></figure>

</section>
<section anchor="ocm-notification-types-registry"><name>OCM Notification Types Registry</name>

<t>IANA is requested to create the "OCM Notification Types" registry in
the "Open Cloud Mesh (OCM) Parameters" group.  This registry records
the values that MAY appear in the "notificationType" field of an OCM
notification sent to the "/notifications" endpoint (see
<xref target="notifications"></xref>).</t>

<t>The "Scope" field indicates whether the notification refers to a
Resource, a Collection, or a Recipient.  Resource-scoped notifications
MUST include "providerId" in the payload.  Collection-scoped
notifications MUST set "resourceType" to "collection" and include
"collectionId"; this scope applies only to <spanx style="verb">REQUEST_SHARE</spanx> and a
<spanx style="verb">SHARE_DECLINED</spanx> response to that request.  It does not define recipient
membership for a Collection.  Recipient-scoped notifications refer to
the shareType in a
<xref target="share-creation-notification">Share Creation Notification</xref> and MUST
include a corresponding identifier such as "userId" in the payload.</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +=========================+======================+===============+
   | Notification Type       | Scope                | Reference     |
   +=========================+======================+===============+
   | SHARE_ACCEPTED          | Resource             | This document |
   | SHARE_DECLINED          | Resource, Collection | This document |
   | SHARE_UNSHARED          | Resource             | This document |
   | SHARE_CHANGE_PERMISSION | Resource             | This document |
   | REQUEST_RESHARE         | Resource             | This document |
   | REQUEST_SHARE           | Collection           | This document |
   | USER_REMOVED            | Recipient            | This document |
   | GROUP_REMOVED           | Recipient            | This document |
   | CONTACT_REMOVED         | Recipient            | This document |
   +=========================+======================+===============+
]]></artwork></figure>

</section>
<section anchor="ocm-encryption-schemes-registry"><name>OCM Encryption Schemes Registry</name>

<t>IANA is requested to create the "OCM Encryption Schemes" registry in
the "Open Cloud Mesh (OCM) Parameters" group.  This registry records
the values that MAY appear in the "encryption.scheme" field of a
<xref target="share-creation-notification">Share Creation Notification</xref>.</t>

<t>Registration Policy: Specification Required [RFC8126]</t>

<t>Initial Contents:</t>

<figure><artwork><![CDATA[
   +=========+============+===============+
   | Scheme  | Share Type | Reference     |
   +=========+============+===============+
   | ocm-pgp | user       | This document |
   | ocm-pgp | group      | This document |
   +=========+============+===============+
]]></artwork></figure>

</section>
</section>
</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<section anchor="threat-model"><name>Threat Model</name>

<t>The threat model follows the Internet threat model described in
[RFC3552].  It assumes that the Sending Server and Receiving Server
participating in an OCM exchange have not been compromised.  Their
administrative interfaces, host operating systems, private keys,
credentials, and underlying storage are part of the trusted endpoints.
Compromise of either endpoint or its trusted infrastructure is outside
the scope of this specification.</t>

<t>An attacker is assumed to have extensive control of the communication
channel and may observe, block, replay, insert, or modify traffic.  TLS
and, where used, HTTP Message Signatures provide the protections
described in this specification against such a network attacker.</t>

<t>An attacker may operate an OCM Server of their own, control a remote
user, send malformed or deceptive protocol messages, or steal bearer
credentials.  An attacker-controlled server can make arbitrary
assertions under its own identity, but must not thereby gain authority
for users or Resources outside its administrative domain.
Implementations are expected to authenticate peers where required,
enforce local authorization policies, validate protocol inputs, and
protect credentials.</t>

<t>Trust in one OCM Server does not imply trust in every OCM Server.  A
TLS and HTTP Message Signatures permit attribution to the server
controlling the relevant credentials, but do not establish that its
assertions are truthful or that supplied content is safe.  Resource
names, descriptions, URIs, metadata, and Resource contents received from
another server remain untrusted input and need to be handled according
to local security policy.</t>

<t>A malicious or unavailable peer can refuse to deliver notifications or
Resources and can attempt to exhaust network, processing, or storage
capacity.  The protocol cannot guarantee availability when a necessary
peer refuses service.  Implementations should nevertheless apply
appropriate timeouts, request and response size limits, rate limits,
quotas, and concurrency limits to contain such failures.</t>

</section>
<section anchor="trust"><name>Trust</name>

<t>There are several areas that are not covered by this specification.
Most importantly we do not provide a way of establishing trust between
servers, even though some features of the protocol rely on trust, such
as the <spanx style="verb">must-use-mfa</spanx> requirement.</t>

<t>Trust needs to be established out of band, but there are some features
of the protocol that <em>can</em> be used to assist operators in establishing
trust.  For instance, invite flow can be used to establish that users
know and have out of band connections with other users on an OCM server.</t>

<t>Further more the Directory Service feature can be used to establish a
trusted federation, where a central authority can be trusted to
implement measures for auditing and adding only trusted servers into the
discovery service.</t>

<section anchor="httpsig"><name>httpsig</name>

<t>It is RECOMMENDED to use signed messages, "httpsig" [RFC9421], to
verify that an OCM server is the server you expect it to be, and SHOULD
be done unless you have a niche use case.  Where signatures are used,
they MUST follow the requirements in
<xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>

</section>
</section>
<section anchor="legacy-shared-secrets"><name>Legacy shared secrets</name>

<t>The legacy format of an OCM Share Notification with shared secrets is
only provided for backwards compatibility with existing implementations.
Implementers SHOULD NOT use it and prefer short-lived tokens instead.</t>

</section>
<section anchor="code-flow-1"><name>Code Flow</name>

<t>All <spanx style="verb">{tokenEndPoint}</spanx> requests MUST be transmitted over HTTPS and
signed using HTTP Signatures.  As with the Discovery Process,
implementations MAY fallback to HTTP instead of HTTPS in testing
setups.  Bearer tokens MUST be treated as
confidential and never logged, persisted beyond their lifetime, or
transmitted over unsecured channels.</t>

</section>
<section anchor="underlying-security-specifications"><name>Underlying Security Specifications</name>

<t>This specification relies on HTTP Message Signatures [RFC9421], JSON
Web Keys and JWK Sets [RFC7517], and Digest Fields [RFC9530].  All
security considerations in those specifications apply to
implementations of OCM.  Implementers need to consider those
specifications together: a message signature is only as trustworthy as
the provenance and protection of its verification key, and signing a
<spanx style="verb">Content-Digest</spanx> field provides content integrity only when both the
signature and digest are correctly validated.</t>

</section>
</section>
<section anchor="copying-conditions"><name>Copying conditions</name>

<t>The author(s) agree to grant third parties the irrevocable right to
copy, use and distribute the work, with or without modification, in
any medium, without royalty, provided that, unless separate permission
is granted, redistributed modified works do not contain misleading
author, version, name of work, or endorsement information.</t>

</section>
<section anchor="references"><name>References</name>

<section anchor="normative-references"><name>Normative References</name>

<t>[OpenAPI] "<eref target="https://cs3org.github.io/OCM-API/docs.html?branch=develop&amp;repo=OCM-API&amp;user=cs3org">Open Cloud Mesh protocol specification in OpenAPI format</eref>".</t>

<t>[IANA-DIGEST-ALG] IANA, "<eref target="https://www.iana.org/assignments/http-digest-hash-alg/http-digest-hash-alg.xhtml">Hash Algorithms for HTTP Digest Fields</eref>".</t>

<t>[IANA-SIG-ALG] IANA, "<eref target="https://www.iana.org/assignments/http-message-signature/http-message-signature.xhtml#signature-algorithms">HTTP Signature Algorithms</eref>".</t>

<t>[RFC2119] Bradner, S. "<eref target="https://datatracker.ietf.org/doc/html/rfc2119">Key words for use in RFCs to Indicate
Requirement Levels</eref>",
March 1997.</t>

<t>[RFC3986] Berners-Lee, T., Fielding, R. and Masinter, L.
"<eref target="https://datatracker.ietf.org/doc/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax
</eref>", January 2005</t>

<t>[RFC4648] Josefsson, S. "<eref target="https://datatracker.ietf.org/doc/html/rfc4648">The Base16, Base32, and Base64 Data
Encodings</eref>", October
2006.</t>

<t>[RFC4918] Dusseault, L. M. "<eref target="https://datatracker.ietf.org/html/rfc4918/">HTTP Extensions for Web Distributed
Authoring and Versioning</eref>",
June 2007.</t>

<t>[RFC6749] Hardt, D. (ed), "<eref target="https://datatracker.ietf.org/html/rfc6749">The OAuth 2.0 Authorization Framework</eref>", October 2012.</t>

<t>[RFC6838] Freed, N., Klensin, J., Hansen, T. "<eref target="https://datatracker.ietf.org/html/rfc6838">Media Type
Specifications and Registration Procedures
</eref>", January 2013.</t>

<t>[RFC7515] Jones, M., Bradley, J., Sakimura, N., "<eref target="https://datatracker.ietf.org/doc/html/rfc7515">JSON Web Signature
(JWS)</eref>", May 2015.</t>

<t>[RFC7517] Jones, M., "<eref target="https://datatracker.ietf.org/doc/html/rfc7517">JSON Web Key (JWK)</eref>", May 2015.</t>

<t>[RFC7518] Jones, M., "<eref target="https://datatracker.ietf.org/doc/html/rfc7518">JSON Web Algorithms (JWA)</eref>", May 2015.</t>

<t>[RFC8032] Josefsson, S., Liusvaara, I., "<eref target="https://datatracker.ietf.org/doc/html/rfc8032">Edwards-Curve Digital
Signature Algorithm (EdDSA)</eref>", January 2017.</t>

<t>[RFC8126] Cotton, M., Leiba, B. and Narten, T. "<eref target="https://datatracker.ietf.org/doc/html/rfc8126">Guidelines for
Writing an IANA Considerations Section in RFCs</eref>", June 2017.</t>

<t>[RFC8174] Leiba, B. "<eref target="https://datatracker.ietf.org/html/rfc8174">Ambiguity of Uppercase vs Lowercase in RFC 2119
Key Words</eref>", May 2017.</t>

<t>[RFC8615] Nottingham, M. "<eref target="https://datatracker.ietf.org/doc/html/rfc8615">Well-Known Uniform Resource Identifiers
(URIs)</eref>", May 2019</t>

<t>[RFC9110] Fielding, R., Nottingham, M. and Reschke, J. "<eref target="https://datatracker.ietf.org/doc/html/rfc9110">HTTP
Semantics</eref>",
June 2022.</t>

<t>[RFC9421] Backman, A., Richer, J. and Sporny, M. "<eref target="https://tools.ietf.org/html/rfc9421">HTTP Message
Signatures</eref>", February 2024.</t>

<t>[RFC9530] Polli, R., Marwood, D., "<eref target="https://datatracker.ietf.org/doc/html/rfc9530">Digest Fields</eref>", February 2024.</t>

<t>[RFC9553] Stepanek, R., Loffredo, M., "<eref target="https://datatracker.ietf.org/doc/html/rfc9553">JSContact: A JSON
Representation of Contact Data</eref>, May 2024"</t>

<t>[RFC9864] Jones, M., Steele, O., "<eref target="https://datatracker.ietf.org/doc/html/rfc9864">Fully-Specified Algorithms for
JSON Object Signing and Encryption (JOSE) and CBOR Object Signing
and Encryption (COSE)</eref>",
October 2025.</t>

<t>[RFC9180] Barnes, R., Bhargavan, K., Lipp, B. and Wood, C. A.  "<eref target="https://datatracker.ietf.org/doc/html/rfc9180">Hybrid
Public Key Encryption</eref>",
February 2022.</t>

</section>
<section anchor="informative-references"><name>Informative References</name>

<t>[RFC3552] Rescorla, E. and Korver, B.  "<eref target="https://datatracker.ietf.org/doc/html/rfc3552">Guidelines for Writing RFC Text
on Security
Considerations</eref>", BCP 72,
July 2003.</t>

<t>[OCM-IP] Nordin, M., Lo Presti, G., and Baghbani, M. "<eref target="https://datatracker.ietf.org/doc/draft-ietf-ocm-integration-protocol/">Open Cloud Mesh
Integration
Protocol</eref>",
Work in Progress, Internet-Draft.</t>

<t>[OCM-MLS] Nordin, M., Lo Presti, G., and Baghbani, M. "<eref target="https://datatracker.ietf.org/doc/draft-ietf-ocm-mls-federated-groups/">Federated Groups
in Open Cloud Mesh using Messaging Layer
Security</eref>",
Work in Progress, Internet-Draft.</t>

<t>[RFC8792] Watsen, K., Auerswald, E., Farrel, A., Wu, Q., "<eref target="https://datatracker.ietf.org/doc/html/rfc8792">Handling
Long Lines in Content of Internet-Drafts and RFCs</eref>", June 2020.</t>

</section>
</section>
<section anchor="appendix-a-multi-factor-authentication"><name>Appendix A: Multi-factor Authentication</name>

<t>If a Receiving Server exposes the capability <spanx style="verb">enforce-mfa</spanx>, it
indicates that it will try and comply with a MFA requirement set on a
Share.  If the Sending Server trusts the Receiving Server, the Sending
Server MAY set the requirement <spanx style="verb">must-use-mfa</spanx> on a Share, which the
Receiving Server MUST honor.  A compliant Receiving Server that signals
that it is MFA-capable MUST NOT allow access to a Resource protected
with the <spanx style="verb">must-use-mfa</spanx> requirement, if the Receiving Party has not
provided a second factor to establish their identity with greater
confidence.</t>

<t>Since there is no way to guarantee that the Receiving Server will
actually enforce the MFA requirement, it is up to the Sending Server to
establish a trust with the Receiving Server such that it is reasonable
to assume that the Receiving Server will honor the MFA requirement.
This establishment of trust will inevitably be implementation
dependent, and can be done for example using a pre approved allow list
of trusted Receiving Servers.  The procedure of establishing trust is
out of scope for this specification: a mechanism similar to the
<eref target="https://sciencemesh.io">ScienceMesh</eref> integration for the
<xref target="invite-flow">Invite</xref> capability may be envisaged.</t>

</section>
<section anchor="appendix-b-jwks-and-http-signature-examples"><name>Appendix B: JWKS and HTTP Signature Examples</name>

<t>This appendix is informative.</t>

<section anchor="published-jwk-set"><name>Published JWK Set</name>

<t>An OCM Server that advertises the <spanx style="verb">http-sig</spanx> capability publishes
its public keys, in the format specified by [RFC7517], at the URL
advertised in the <spanx style="verb">jwksUri</spanx> field of its Discovery response (see
<xref target="http-message-signatures">HTTP Message Signatures</xref>).  Here is
an example response from <spanx style="verb">https://sender.example.org/ocm/jwks</spanx>:</t>

<figure type="json"><artwork><![CDATA[
{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "alg": "Ed25519",
      "kid": "sender.example.org#key1",
      "x": "AzeStPAdQ-vbi6bJVxcQjBPF2I7fDZdfDZ_XZ3J4Azs"
    }
  ]
}
]]></artwork></figure>

</section>
<section anchor="signing-a-request-sender"><name>Signing a Request (Sender)</name>

<t>Given a Share Creation Notification request:</t>

<sourcecode type="http">
POST /ocm/shares HTTP/1.1
Host: receiver.example.org
Content-Type: application/json
Content-Digest: sha-256=:/Uz47cfD1HOdMTIqcWjd84iMLQ4gVJdC7ZFACf1ViqU=:
Content-Length: 521

{
  "shareWith": "marie@receiver.example.org",
  "name": "spec.yaml",
  "providerId": "7c084226-d9a1-11e6-bf26-cec0c932ce01",
  "owner": "einstein@sender.example.org",
  "sender": "einstein@sender.example.org",
  "ownerDisplayName": "Albert Einstein",
  "senderDisplayName": "Albert Einstein",
  "shareType": "user",
  "resourceType": "file",
  "protocol": {
    "name": "multi",
    "webdav": {
      "uri": "spec.yaml",
      "sharedSecret": "hfiuhworzwnur98d3wjiwhr",
      "permissions": ["read", "write"]
    }
  }
}
</sourcecode>

<t>The signature base is constructed according to [RFC9421]:</t>

<sourcecode type="http">
NOTE: '\' line wrapping per RFC 8792

"@method": POST
"@target-uri": https://receiver.example.org/ocm/shares
"content-digest": sha-256=:/Uz47cfD1HOdMTIqcWjd84iMLQ4gVJdC7ZFACf1ViqU=:
"content-length": 521
"@signature-params": ("@method" "@target-uri" "content-digest" \
  "content-length");created=1785060500;\
  keyid="sender.example.org#key1";alg="ed25519";tag="ocm"
</sourcecode>

<t>Sign this base using for example Ed25519 ([RFC8032]) to produce the
signature, and then add headers.  Note that the dictionary label
(<spanx style="verb">sig1</spanx> below) is arbitrary; the signature is marked as belonging
to OCM by its <spanx style="verb">tag="ocm"</spanx> parameter, which is part of the signature
base above:</t>

<sourcecode type="http">
NOTE: '\' line wrapping per RFC 8792

Content-Digest: sha-256=:/Uz47cfD1HOdMTIqcWjd84iMLQ4gVJdC7ZFACf1ViqU=:
Content-Length: 521
Signature-Input: sig1=("@method" "@target-uri" "content-digest" \
  "content-length");created=1785060500;\
  keyid="sender.example.org#key1";alg="ed25519";tag="ocm"
Signature: sig1=:Epax4XFqvbrrDzQUAaNl+uECasEKbArgz8AlEkXspvYX2fSkQFlC\
  kaXImZnYU898C2t0IdmbFhjR8bkN0hZgCg==:
</sourcecode>

<t>See <xref target="http-message-signatures">HTTP Message Signatures</xref> for the
normative requirements illustrated by this example.</t>

</section>
<section anchor="verifying-a-signature-receiver"><name>Verifying a Signature (Receiver)</name>

<t>The normative verification requirements are specified in
<xref target="http-message-signatures">HTTP Message Signatures</xref>.  The following
illustrates the procedure to verify an incoming signed request:</t>

<t><list style="numbers" type="1">
  <t>Extract the provider domain from the <spanx style="verb">sender</spanx> field in the
request body</t>
  <t>Fetch the Discovery response from
<spanx style="verb">https://&lt;provider-domain&gt;/.well-known/ocm</spanx> and read its
<spanx style="verb">jwksUri</spanx> field.  If the Sending Server advertises the <spanx style="verb">http-sig</spanx>
capability but no <spanx style="verb">jwksUri</spanx> is present, the receiver can discard
the notification, as described in <xref target="decision-to-discard">Decision to
Discard</xref></t>
  <t>Fetch the public keys from the URL given by <spanx style="verb">jwksUri</spanx></t>
  <t>Locate the unique signature carrying the <spanx style="verb">tag="ocm"</spanx> parameter in
the <spanx style="verb">Signature-Input</spanx> header, disregarding its dictionary label
(here <spanx style="verb">sig1</spanx>)</t>
  <t>Extract <spanx style="verb">keyid</spanx> from <spanx style="verb">Signature-Input</spanx> header and find the key
matching the <spanx style="verb">kid</spanx> value in the [RFC7517] response</t>
  <t>Reconstruct the signature base from the request using the
components listed in <spanx style="verb">Signature-Input</spanx> as specified in [RFC9421]</t>
  <t>Verify the signature using the algorithm derived from the <spanx style="verb">alg</spanx>
value of that JWK (e.g., Ed25519 [RFC8032]), as described under
Keys and Algorithms in
<xref target="http-message-signatures">HTTP Message Signatures</xref></t>
</list></t>

</section>
<section anchor="validating-the-payload"><name>Validating the Payload</name>

<t>Following the validation of the signature, the host also confirms
the validity of the payload, as specified under Verification
Requirements in
<xref target="http-message-signatures">HTTP Message Signatures</xref>.</t>

<t>As an example, if the payload is about initiating a new share, the file
owner has to be an account from the instance at the origin of the
request.</t>

</section>
</section>
<section anchor="appendix-c-directory-service"><name>Appendix C: Directory Service</name>

<t>A third-party Directory Service is a back-end service used to federate
multiple OCM Servers and facilitate the Invite flow.  It is expected to
expose, via anonymous HTTPS GET, a signed JWS document [RFC7515], where
the signing key MUST be made available offline and the payload MUST
adhere to the following format:</t>

<t><list style="symbols">
  <t>REQUIRED: <spanx style="verb">federation</spanx> - a human-readable name for the list of OCM
Servers exposed by the Directory Service</t>
  <t>REQUIRED: <spanx style="verb">servers</spanx> - a JSON array of objects to describe the list
of OCM Servers with the following string fields:
  <list style="symbols">
      <t>REQUIRED: <spanx style="verb">url</spanx> - an absolute URL identifying the
OCM Server.  It MUST:
      <list style="symbols">
          <t>include scheme: either <spanx style="verb">https://</spanx> or
(for testing purposes) <spanx style="verb">http://</spanx></t>
          <t>include host (either a FQDN or an IP address)</t>
          <t>MAY include a non-default port</t>
          <t>MUST NOT include a base path (e.g., <spanx style="verb">/ocm</spanx>)</t>
          <t>MUST NOT include userinfo, query, or fragment</t>
        </list></t>
      <t>REQUIRED: <spanx style="verb">displayName</spanx> - a human-readable name
for the OCM Server
Example:</t>
    </list></t>
</list></t>

<figure type="json"><artwork><![CDATA[
{
  "payload": {
    "federation": "The ScienceMesh Directory",
    "servers": [
      {
        "url": "https://ocm-server.example.org",
        "displayName": "OCM Server 1"
      },
      {
        "url": "https://ocm-server.example.com:4443",
        "displayName": "OCM Server 2"
      },
      {
        "url": "http://192.168.1.1:8080",
        "displayName": "OCM Server 3"
      }
    ]
  },
  "protected": {"alg": "ES256"},
  "signature": "..."
}
]]></artwork></figure>

</section>
<section anchor="appendix-d-object-models"><name>Appendix D: Object models</name>

<t>An implementor of OCM MAY choose any internal object model to represent
an <em>Address Book</em>, a <em>Contact</em>, an <em>Invite</em>, a <em>Provider</em>, a <em>Share</em>,
and a <em>User</em>.  The following diagrams are provided to clarify
the concepts and their relationships, as a guide for implementors.</t>

<section anchor="address-book"><name>Address Book</name>

<t>An <em>OCM Provider</em> MAY offer its <em>Users</em> an address book tool, where OCM
Addresses can be stored over time in a labeled and/or searchable way.
This decouples the act by which the OCM Address string is passed into
the Sending Server's database from the selection of the <em>Receiving
Party</em> in preparation for Share Creation.</t>

<t>The Address Book entity maintains a collection of contacts for a user
within the OCM provider.  It serves as the primary mechanism for
managing federated relationships between users across different OCM
Servers. <em>Contacts</em> may be added to the Address Book through the Invite
flow or direct entry.  It provides a convenient way for users to
organize and access their federated contacts, and MAY allow users to
generate <em>Invites</em>.</t>

<figure><artwork><![CDATA[
+-----------------+
|  Address Book   |
|                 |
| - owner: User   |--------+
| - contacts: []  |        |
+-----------------+        |
       |                   |
       | contains          | generates
       | 0..*              |
       v                   v
+-----------------+  +----------------+
|    Contact      |  |    Invites     |
+-----------------+  +----------------+
]]></artwork></figure>

<section anchor="properties"><name>Properties</name>

<t><list style="symbols">
  <t><strong>owner</strong>: Reference to the User who owns this address book</t>
  <t><strong>contacts</strong>: Array of Contact objects stored in the address book</t>
</list></t>

</section>
<section anchor="relationships"><name>Relationships</name>

<t><list style="symbols">
  <t>An Address Book belongs one or more Users.</t>
  <t>An Address Book contains zero or more Contacts.</t>
  <t>An Address Book MAY allow its owner to generate Invites.</t>
</list></t>

</section>
</section>
<section anchor="contact"><name>Contact</name>
<t>A Contact represents a federated user relationship established through
the OCM protocol.  Contacts are stored in <em>Address Books</em> and may be
created through the Invite process or via direct entry.  A Contact MAY
of course contain much more detailed information about the referenced
user such as if it was added via <em>Invites</em> or direct entry.</t>

<figure><artwork><![CDATA[
+-----------------+
|    Contact      |
+-----------------+
| - addedDate     |
| - email         |
| - name          |
| - provider      |
| - userID        |
+-----------------+
       ^
       | referenced by
       |
+-----------------+
|  Address Book   |
+-----------------+
]]></artwork></figure>

<section anchor="properties-1"><name>Properties</name>

<t><list style="symbols">
  <t><strong>addedDate</strong>: Timestamp of when contact was added</t>
  <t><strong>email</strong>: Contact email address (informational)</t>
  <t><strong>name</strong>: Human-readable display name</t>
  <t><strong>userID</strong>: The identifier of the contact at their OCM Server</t>
  <t><strong>provider</strong>: The FQDN of the contact's OCM Server</t>
</list></t>

</section>
<section anchor="relationships-1"><name>Relationships</name>

<t><list style="symbols">
  <t>A Contact may be referenced by one or more Address Books.</t>
</list></t>

</section>
</section>
<section anchor="invite"><name>Invite</name>

<t>The Invite entity represents the bidirectional trust establishment
mechanism in OCM.  It facilitates secure contact exchange between users
on different OCM Servers.</t>

<figure><artwork><![CDATA[
+-----------------+
|     Invite      |
+-----------------+
| - acceptedTime  |
| - createdTime   |
| - sender: User  |
| - token         |
+-----------------+
       |
       | generated by
       v
+-----------------+
|   Address Book  |
+-----------------+

]]></artwork></figure>

<section anchor="properties-2"><name>Properties</name>

<t><list style="symbols">
  <t><strong>acceptedTime</strong>: Timestamp of invite acceptance (if accepted)</t>
  <t><strong>createdTime</strong>: Timestamp of invite creation</t>
  <t><strong>sender</strong>: Reference to the User who sent the Invite</t>
  <t><strong>token</strong>: Unique, hard-to-guess string generated by Invite Sender
           OCM Server</t>
</list></t>

</section>
<section anchor="relationships-2"><name>Relationships</name>

<t><list style="symbols">
  <t>An Invite is generated by an Address Book entry action.</t>
  <t>An Invite is associated with exactly one User as the sender.</t>
</list></t>

</section>
</section>
<section anchor="provider"><name>Provider</name>

<t>The Provider entity represents an OCM Server's capabilities and
configuration as discovered through the OCM API Discovery process.  It
represents both the Sending Server and Receiving Server roles, and an
implementor might find it useful to have a Provider object model to
store the discovered information about federation peers or other remote
OCM Providers.</t>

<t>The following diagram is illustrative and non-exhaustive.  The single
source of truth for Provider properties is the OCM API Discovery Fields
section; for the box contents below, see the Properties subsection and
the normative capability, criteria, and resource type definitions in
that section.</t>

<figure><artwork><![CDATA[
            +-----------------------+
            |      Provider         |
            |    (OCM Server)       |
            +-----------------------+
            | - apiVersion          |
            | - enabled             |
            | - endPoint            |
            | - inviteAcceptDialog  |
            | - provider            |
            | - tokenEndPoint       |
            | - ...                 |
            +-----------------------+
                   |
                   | exposes
                   |
         +---------+---------+----------------------+
         |                   |                      |
         v                   v                      |
+------------------+  +------------------+          |
| ResourceTypes[]  |  | Capabilities[]   |          |
+------------------+  +------------------+          |
| - name           |  | - enforce-mfa    |          |
| - shareTypes[]   |  | - exchange-token |          |
| - protocols{}    |  | - http-sig       |          |
| - ...            |  | - invites        |          |
+------------------+  | - notifications  |          |
       |              | - protocol-object|          |
       |              | - ...            |          |
       |              +------------------+          |
       |                                            |
       |                           +----------------+
       |                           |
       |                           v
       |              +--------------------------+
       |              |    Criteria[]            |
       |              +--------------------------+
       |              | - allowlist              |
       |              | - denylist               |
       |              | - must-use-http-sig      |
       |              | - must-invite            |
       |              | - must-exchange-token    |
       |              | - ...                    |
       |              +--------------------------+
       |
       | supports
       v
+------------------+
|   Protocols      |
+------------------+
| - ssh            |
| - ssh-receive    |
| - webapp         |
| - webapp-receive |
| - webdav         |
| - webdav-receive |
| - ...            |
+------------------+
]]></artwork></figure>

<section anchor="properties-3"><name>Properties</name>

<t><list style="symbols">
  <t><strong>apiVersion</strong>: Version string of supported OCM API</t>
  <t><strong>capabilities</strong>: Optional features supported</t>
  <t><strong>criteria</strong>: Criteria for accepting a Share Creation Notification</t>
  <t><strong>enabled</strong>: Boolean indicating if OCM service is active</t>
  <t><strong>endPoint</strong>: Base URI for OCM API endpoints</t>
  <t><strong>provider</strong>: Friendly branding name</t>
  <t><strong>resourceTypes</strong>: Array of supported resource types with protocols</t>
</list></t>

</section>
</section>
<section anchor="share"><name>Share</name>

<t>The Share entity represents a policy granting access to a <em>Resource</em>
from a Sending Party to a Receiving Party.</t>

<figure><artwork><![CDATA[
+-----------------+                      +------------------+
|  Sending Party  |                      | Receiving Party  |
+-----------------+                      +------------------+
       |                                        |
       | creates                                | accesses
       v                                        v
+------------------+     notification    +------------------+
|     Share        |-------------------->| Receiving Server |
+------------------+                     +------------------+
| - expiration     |                            |
| - name           |                            | mediates access to
| - owner          |                            v
| - protocol       |                     +------------------+
| - providerId     |                     | Resource (remote)|
| - requirements[] |                     +------------------+
| - resourceType   |
| - sender         |
| - shareType      |
| - shareWith      |
| - state          |
+------------------+
       |
       | governs access to
       v
+-----------------+
|    Resource     |
+-----------------+
]]></artwork></figure>

<section anchor="properties-4"><name>Properties</name>

<t><list style="symbols">
  <t><strong>expiration</strong>: Optional expiration timestamp</t>
  <t><strong>name</strong>: Human-readable name of the shared Resource</t>
  <t><strong>owner</strong>: OCM Address of the Resource owner</t>
  <t><strong>protocol</strong>: Access protocol name and details (webdav, ssh, webapp)</t>
  <t><strong>providerId</strong>: Unique identifier for the Share at the provider</t>
  <t><strong>requirements</strong>: Array of access requirements (must-use-mfa,
                  must-exchange-token)</t>
  <t><strong>resourceType</strong>: Type of resource (file, folder, calendar, etc.)</t>
  <t><strong>sender</strong>: OCM Address of the party creating the Share</t>
  <t><strong>shareType</strong>: Type of recipient (user, group, etc.)</t>
  <t><strong>shareWith</strong>: OCM Address of the Receiving Party</t>
  <t><strong>state</strong>: Current state of the Share (accepted, pending, deleted)</t>
</list></t>

<section anchor="share-states"><name>Share States</name>

<t><list style="symbols">
  <t><strong>Accepted</strong>: Share accepted, Resource accessible</t>
  <t><strong>Deleted</strong>: Share removed or expired</t>
  <t><strong>Pending</strong>: Awaiting acceptance by Receiving Party</t>
</list></t>

</section>
</section>
<section anchor="relationships-3"><name>Relationships</name>

<t><list style="symbols">
  <t>A Share is created by a User (local).</t>
  <t>A Share is received by a User (remote).</t>
  <t>A Share governs access to a Resource.</t>
</list></t>

</section>
</section>
<section anchor="user"><name>User</name>

<t>The User entity represents the party in OCM who can send and receive
Shares and Invites and manage Contacts, and interact with Resources.</t>

<figure><artwork><![CDATA[
                +-----------------------+
                |        User           |
                +-----------------------+
                | - email               |
                | - name                |
                | - ocmAddress          |
                | - uid                 |
                +-----------------------+
                            |
                  +---------+---------+
                  |                   |
                  | owns              | participates in
                  v                   v
         +------------------+  +------------------+
         |  Address Book    |  |    Shares        |
         +------------------+  +------------------+
         | - contacts[]     |  | - receiving[]    |
         +------------------+  | - sending[]      |
                  |            +------------------+
                  |
                  | issues
                  v
         +------------------+
         |    Invites       |
         +------------------+
         | - sent[]         |
         +------------------+
]]></artwork></figure>

<section anchor="properties-5"><name>Properties</name>

<t><list style="symbols">
  <t><strong>email</strong>: User's email address</t>
  <t><strong>name</strong>: Human-readable display name</t>
  <t><strong>ocmAddress</strong>: Full OCM Address</t>
  <t><strong>uid</strong>: Unique identifier within the OCM Provider</t>
</list></t>

</section>
<section anchor="relationships-4"><name>Relationships</name>

<t><list style="symbols">
  <t>A User owns one or more Address Book(s).</t>
  <t>A User issues zero or more Invites.</t>
  <t>A User participates in zero or more Shares as Sending or Receiving
Party.</t>
</list></t>

</section>
</section>
<section anchor="resource"><name>Resource</name>

<t>The Resource entity represents the data or service being shared between
OCM Providers.  It is the target of Shares and is accessed by the
Receiving Party through the Sending Server's API.  In general a Resource
is a much more complex entity, but for the purpose of OCM we only need
to model a few key properties.</t>

<figure><artwork><![CDATA[
+-----------------+
|    Resource     |
+-----------------+
| - location      |
| - owner: User   |
| - resourceID    |
| - type          |
+-----------------+
       ^
       |
       | accessed via
       |
       v
+------------------+
|     Share        |
+------------------+
]]></artwork></figure>

<section anchor="properties-6"><name>Properties</name>

<t><list style="symbols">
  <t><strong>location</strong>: URI or path to access the Resource</t>
  <t><strong>owner</strong>: Reference to the User who owns the Resource</t>
  <t><strong>resourceID</strong>: Unique identifier of the Resource</t>
  <t><strong>type</strong>: Type of Resource (file, folder, calendar, etc.)</t>
</list></t>

</section>
</section>
</section>
<section anchor="appendix-e-navigation-index"><name>Appendix E: Navigation Index</name>

<t>This appendix is informative.  It points to normative sections and
informative aids; it introduces no new rules.</t>

<t><list style="symbols">
  <t><strong>Discovery fields</strong> - <xref target="ocm-api-discovery">OCM API Discovery</xref>,
<xref target="fields"></xref></t>
  <t><strong>Capabilities</strong> - advertised in <spanx style="verb">capabilities[]</spanx>; see <xref target="ocm-api-discovery">OCM API
Discovery</xref></t>
  <t><strong>Criteria</strong> - advertised in <spanx style="verb">criteria[]</spanx> as inbound admission gates;
see <xref target="ocm-api-discovery">OCM API Discovery</xref></t>
  <t><strong>Per-share requirements</strong> - in <spanx style="verb">protocol.*.requirements[]</spanx>; see
<xref target="share-creation-notification">Share Creation Notification</xref></t>
  <t><strong>Per-share protocol shape</strong> - in <spanx style="verb">protocol.*</spanx> fields; see <xref target="share-creation-notification">Share
Creation Notification</xref></t>
  <t><strong>Same-string note</strong> - <spanx style="verb">must-exchange-token</spanx> in <xref target="ocm-api-discovery">OCM API
Discovery</xref> criteria and in share
<spanx style="verb">protocol.*.requirements[]</spanx></t>
  <t><strong>Signing</strong> - <xref target="http-message-signatures">HTTP Message Signatures</xref>,
<xref target="signing-direction-index">Signing Direction Index</xref></t>
  <t><strong>Object models</strong> - <xref target="appendix-d-object-models">Appendix D: Object
models</xref></t>
  <t><strong>Informative diagrams</strong> - in the OCM-API repository under <spanx style="verb">diagrams/</spanx></t>
</list></t>

</section>
<section anchor="changes"><name>Changes</name>

<t>This section collects the changes with respect to the previous
version in the IETF datatracker.  It is meant to ease the review
process and it shall be removed when going to RFC last call.
The complete changelog is updated in the OCM-API GitHub repository.</t>

<section anchor="version-08"><name>Version 08</name>
<t><list style="symbols">
  <t>Introduced an <spanx style="verb">apps</spanx> array in the <spanx style="verb">webapp</spanx> protocol payload, listing
the available web applications each with the media types it can
handle.  It replaces the <spanx style="verb">appName</spanx> and <spanx style="verb">mediaTypes</spanx> properties.</t>
  <t>Introduced a CONTACT_REMOVED notification.</t>
  <t>Added reference to the OpenAPI protocol specification.</t>
</list></t>

</section>
<section anchor="version-07"><name>Version 07</name>
<t><list style="symbols">
  <t>Required the <spanx style="verb">keyid</spanx> signature parameter and that it matches the
<spanx style="verb">kid</spanx> of the verification key in the signer's JWK Set.</t>
  <t>The HTTP Message Signature algorithm is now derived from the JWK
identified by <spanx style="verb">keyid</spanx>, per Section 3.3.7 of [RFC9421], instead of
being restricted to the "HTTP Signature Algorithms" registry; the
<spanx style="verb">alg</spanx> signature parameter is optional and checked for consistency.</t>
  <t>Replaced the unregistered <spanx style="verb">/.well-known/jwks.json</spanx> endpoint with a
<spanx style="verb">jwksUri</spanx> field in the Discovery response, from which the location
of the JWK Set for HTTP Message Signatures is discovered.</t>
  <t>The <spanx style="verb">Date</spanx> header is no longer covered by signatures: freshness is
anchored on the <spanx style="verb">created</spanx> signature parameter (see Section 7.2.4
of [RFC9421]).</t>
  <t>Clarified that <spanx style="verb">created</spanx> bounds the lifetime of a captured
signature but does not by itself detect replay within that window
(see Section 7.2.2 of [RFC9421]).</t>
  <t><spanx style="verb">jwksUri</spanx> and <spanx style="verb">{tokenEndPoint}</spanx> transport: HTTPS remains mandatory,
with the same HTTP fallback allowance for testing setups that the
Discovery Process has; dropped the HTTPS-only schema pattern from
spec.yaml accordingly.</t>
  <t>Appendix B now defers the missing-<spanx style="verb">jwksUri</spanx> case to <xref target="decision-to-discard">Decision to
Discard</xref> instead of stating a stronger
requirement in an informative section.</t>
  <t>Updated the signature examples: replaced the legacy <spanx style="verb">Digest</spanx> header
with <spanx style="verb">Content-Digest</spanx> [RFC9530] and applied [RFC8792] line
wrapping.</t>
  <t>Added informative aids: same-string note for <spanx style="verb">must-exchange-token</spanx>,
Appendix D criteria label fix, <xref target="signing-direction-index">Signing Direction
Index</xref>, <xref target="appendix-e-navigation-index">Appendix E: Navigation
Index</xref>, and companion diagrams under
<spanx style="verb">diagrams/</spanx> in the OCM-API repository.</t>
  <t>Rehaul of the Notification (formerly "Share Acceptance
Notification") endpoint and payload, and adaptation of the IANA
registries.  The core notifications have now been fully spelled
out, clarifying their scope.</t>
  <t>Introduced an <spanx style="verb">encryption</spanx> optional object in the Share Creation
Notification payload, and defined a corresponding Encryption Schemes
OCM IANA Registry.</t>
</list></t>

</section>
<section anchor="version-06"><name>Version 06</name>
<t><list style="symbols">
  <t>Introduced IANA Registries for resource types, protocols, share
types, and share payloads, and populated them with all relevant
values defined in this document.</t>
  <t>Moved the <spanx style="verb">federation</spanx> share type definition along with the
corresponding share payload description to the [OCM-MLS] Draft.</t>
  <t>Improved the http-sig related text, and promoted it from an
appendix to a normative section. In addition, made the use of
http-sig a MUST for implementations that offer it as capability.</t>
  <t>Sorted the Terms and removed duplicates.</t>
  <t>Addressed the IANA early review: added the Status field to the
Well-Known URI registration, added section references to the
JSContact registrations, moved the creation of the JSContact enum
values subregistry to a dedicated subsection, and reformatted the
registration templates so each field renders on its own line.</t>
</list></t>

</section>
<section anchor="version-05"><name>Version 05</name>
<t><list style="symbols">
  <t>Introduced a <spanx style="verb">/request-share</spanx> endpoint to request a user of an
OCM server to share a resource.</t>
  <t>Refactored the <spanx style="verb">webapp</spanx> protocol to align it to the new security
standard, by means of POST requests and the Code Flow.</t>
  <t>Introduced new <spanx style="verb">&lt;protocol&gt;-receive</spanx> protocols in the Discovery
endpoint, to signal the ability to receive an OCM share carrying
that protocol.</t>
  <t>Introduced new Internet-Draft specifications to cover optional
parts of the protocol related to webapp integrations and federated
groups.</t>
  <t>Renamed some requirements and criteria to improve consistency.</t>
  <t>On a Share Creation Notification, made the <spanx style="verb">sharedSecret</spanx>
a required parameter for all protocol payloads that specify it.</t>
  <t>Fixed all example URIs to use <spanx style="verb">example.org</spanx> across the spec.</t>
  <t>Improved the JWKS-related text and fixed obsoleted references.</t>
  <t>Removed the already deprecated <spanx style="verb">/ocm-provider</spanx> endpoint and the
draft-cavage public key advertisement in the OCM Discovery endpoint
as all known implementations have migrated to the recommended
alternatives.</t>
</list></t>

</section>
<section anchor="version-04"><name>Version 04</name>
<t><list style="symbols">
  <t>Clarified that the diagrams in Appendix D are illustrative and
not normative.</t>
  <t>Minor formatting fixes.</t>
</list></t>

</section>
<section anchor="version-03"><name>Version 03</name>
<t><list style="symbols">
  <t>Fixed formatting of artworks, code blocks and bullet lists.</t>
</list></t>

</section>
<section anchor="version-02"><name>Version 02</name>
<t><list style="symbols">
  <t>Added the <em>Changes</em> section.</t>
</list></t>

</section>
<section anchor="version-01"><name>Version 01</name>
<t><list style="symbols">
  <t>Introduced functions, roles, and object models to the specification.</t>
  <t>Added support for SSH as a share access method.</t>
  <t>Introduced <spanx style="verb">accessType</spanx> property in shares and removed the datatx
"protocol" in favor of a cleaner access model.</t>
  <t>Improved resource access description with token exchange, and
specified request payload format for the <spanx style="verb">/token</spanx> endpoint.</t>
  <t>Added RFC 9421 HTTP Message Signatures support via <spanx style="verb">http-sig</spanx>
capability and RFC 7515 (JWS) compliant JWKS and prescribed use of
JWS for the Directory Service.</t>
  <t>Updated and homogenized capabilities across the specification.</t>
  <t>Added JSContact extension to IANA Considerations.</t>
  <t>Changed example domain to use cloud.example.org per RFC 2606.</t>
</list></t>

</section>
</section>
<section anchor="acknowledgements"><name>Acknowledgements</name>

<t>Our deepest thanks and appreciation go to the people who started the
work on what would become this specification in 2015.  In particular we
want to thank (in alphabetical order) Guido Aben, Russell Albert,
Holger Angenent, David Antoš, Hrachya Astsatryan, Kurt Bauer,
Charles du Jeu, Andreas Eckey, David Gillard, Andranik Hayrapetyan Wahi,
Dimitri van Hees, Christoph Herzog, David Jericho, Frank Karlitschek,
Christian Kracher, Ralph Krimmel, Massimo Lamanna, Simon Leinen,
Jari Miettinen, Jakub Moscicki, Frederik Orellana, Vlad Roman,
Christian Schmitz, Woojin Seok, Rogier Spoor, Christian Sprajc,
Peter Szegedi, Ron Trompert, Benedikt Wegmann and Jonathan Xu.</t>

<t>We would also like to thank Ishank Arora, Gianmaria Del Monte,
Jörn Friedrich Dreyer, Richard Freitag, Hugo González Labrador,
Matthias Kraus, Maxence Lange, Lovisa Lugnegård, Thibault Meunier,
Sandro Mesterheide, Antoon Prins, Justin Richer and Björn Schießle for
their direct contributions to the specification.</t>

<t>Over the years many more people have been involved in the development
of OCM.  We would like to thank all of them for their contributions,
including Jean-Thomas Acquaviva, Samuel Alfageme Sainz,
Karsten Asshauer, Miroslav Bauer, Felix Böhm, Maciej Brzeźniak,
Diogo Castro, Gavin Charles Kennedy, Jarosław Czub, Milan Danecek,
Michael D'Silva, Lukasz Dutka, Pedro Ferreira, Renato Furter,
Klaas Freitag, Raman Ganguly, Eva Gergely, Hilary Goodson, Daniel Halbe,
Dave Heyns, Jan Holesovsky, Jan Hornicek, Carina Kemp, Fergus Kerins,
Andreas Klotz, Matthias Knoll, Christian Kracher, Mario Lassnig,
Claudius Laumanns, Anthony Leroy, Patrick Maier, Vladislav Makarenko,
Anna Manou, Rita Meneses, Zheng Meyer-Zhao, Crystal Michelle Chua,
Yoann Moulin, Daniel Müller, Frederik Müller, Rasmus Munk,
Michał Orzechowski, Jacek Pawel Kitowski, Enrique Pérez Arnaud, Iosif
Peterfi, Alessandro Petraro, Rene Ranger, Angelo Romasanta, David
Rousse, Carla Sauvanaud, Klaus Scheibenberger, Marcin Sieprawski,
Tilo Steiger, C.D. Tiwari, Alejandro Unger and Tom Wezepoel.</t>

<t>Work on this document has been partially funded over the years by
multiple projects and funding agencies:</t>

<t><list style="symbols">
  <t>The <eref target="https://cs3mesh4eosc.eu/">CS3MESH4EOSC</eref> project "Interactive and agile/responsive
sharing mesh of storage, data and applications for EOSC", whose key
result was <eref target="https://cs3mesh4eosc.eu/science-mesh">Science Mesh</eref>, received funding from the
European Union's Horizon 2020 research and innovation programme under
Grant Agreement no. <eref target="https://cordis.europa.eu/project/id/863353">863353</eref>.</t>
  <t><eref target="https://www.nlnet.nl/">NLnet</eref> through the <eref target="https://www.nlnet.nl/core">NGI0 Core Fund</eref>, with
financial support from the European Commission's
<eref target="https://ngi.eu/">Next Generation Internet</eref> programme under grant agreement
No. <eref target="https://cordis.europa.eu/project/id/101092990">101092990</eref>.</t>
  <t>The <eref target="https://www.eosc-data-commons.eu/">EOSC Data Commons</eref> project "Services for inter- and
cross-disciplinary data discovery, access, sharing and reuse in the
EOSC Federation", received funding from the European Union under Grant
Agreement no. <eref target="https://cordis.europa.eu/project/id/101188179">101188179</eref>.</t>
  <t><eref target="https://www.sovereign.tech/">Sovereign Tech Agency</eref> through the <eref target="https://www.sovereign.tech/programs/fund">Tech Fund</eref>, with
a specific <eref target="https://www.sovereign.tech/tech/open-cloud-mesh">project</eref>.</t>
</list></t>

</section>


  </middle>

  <back>








  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+S9+5LbRpYn/H8+BYKOGKk8JKXSzVK53Z9LN1tu69IqyV6P
ViGCJFiERQJsAFSp3NMd+xr7evske+6ZCYCskuXp/fb7HDHTqiogkZeT535+
ZzQauSZvVtlRcuX5JiuSB6tyO0+eZvXyipuXsyJdw5/mVbpoRnnWLEblbD0q
4cHRDB8creHB0fW7bpY22WlZnR8ldTN3Lt9UR0lTbevmxvXr967fcGmVpUfJ
8WazyuHRvCzqJC3mycssXY1e5evMvc/Oz8pqfpQ8KZqsKrJm9BA/6lzdwIPv
0lVZwETOsxp+AWOt4cFHrx47l26bZVkduSQZJXlRHyXfjZMfy+RFldVNDr9N
El7Cd/m2zjabrPXHsjpNi/w3mtJR8uDRy2f062yd5quj5FReGq/KDb3z7Qzm
Np4t6aFtlR8ly6bZ1EfXrskfrumTzs/o6fj+OJlnyQ9lcRrM6Gk+W+bZKvpL
PJ0XZTHPquSk3FazLJzXml/9dkMP1PT3MbzbnVb0xKxcR9NK7qenyyl8MJxV
upzn8R8uOyl887On9AyIIC/ibXqfhb+Op3Py+tmjV+E03qdF+W29BQoa11nP
OZXzbFyvyxU+AENdW+P4zo1GoySdAm2lMyC61lVIrj5/8PQgyYFokzqrPsD6
FxksguaQbKqyKWflKmmWaYMPAdHMk6Z0Rdnki3N452U2y/IPeXGavEir5pwf
bJbZebJMP2TJNIOvnVYpUP48SWezrK7h9aQu4V68zGSnkuRJA4/XSZ2v81Va
5U2e1clZ3iwTvgOyJcliVZ7BU9sZ/KF2z4/hj0P4V3KWrVb0v/hKXc7ydAW7
zpfN1mAvJsezBqbcnL/YTh1eVdresXPHyaysMlxjMkvh/5WLBDYHl322hGWk
+JcquZqNT8fD5BiuOzxSJCfndZOtk+MD+Hy9hFuM61sCV4AXKlmivpQmi3yV
HcjaYBOXMGA46v1yCmM6GfM+P1luYUthD+tFVlW41fCaHzpv6my1ANqBX/1t
m9MDOAyc0qo8hX3ADddJwip/XsIUYAhYVj3LCtjuEpeYr1ZbpBHYmmyo655n
dX5a0JHD7m02ZdUkqZtWZYoXBaZ0SrtEew3UhcxvCD/NVts5TmMKE4dFJis4
14ZHwfU7XUw97tLjEk5kBccfjglbsjpPthscANe+KeGveCgVLgQpKSZCXE6x
KKs1fBOmB4/kVUB9OERAfEAO23Rl5KgP4v5spzXsaVY08Pl1WqSnMOD0POFz
M8IaGkn+nE0fHv805ju3zuewEue+QMZflfMtLaa74rMUpwtEn67gM7OywMXw
zOHwblw/vE0CBS8IXad5tlmV59nc1bDTGT5wB1aBJ2aP5OvNKltndOtgvnUG
9xruxGaVNrgt4SE5lAz3y4/D5Fn2sSHRB8cPU3zA/yzP9F84iZMsxROEFb6C
TTwtYVB/S2BrYU8+5POMmMlsWwEl1bN0lU5XGb+/WGUfc/jJwflUKdAbbAo8
lsCs5A3YArw9eJj4AuwvvF4iXcJv4Lop3ZOUdcQ1cMVn9NV5ucE9HjLVZfAB
ov8lHiqQLDBE/EpTVrIAuu/wZhqvYp2+x3uF/Aj2kSaHl5T+Nmf6qfLTZePg
FhWnsPmv8DYhD0Xh9YE3nbeC1tHio8qM4fmz9NzRuoEd0XqR4cG5iSoBZ90A
b6qTRVWu6bs2D/yBGTZ+FnfHwfPTbJkiM1j4h5HChdPAcuAGAzOWGySP2exw
9Us8G+CO/P11NoMLmddrnvkqa2qZAtBpAVuZlCgyQC2AM0b2B3S6hZvi4CBZ
GVrmG1aIkK0CL0Pmyq/SzYaV2Mv4hwbWAqtozuBQHV9cOPENPg7iBI9IFj3G
i/UqA2LmowQtK0E1q04GT1+fvBoM+X+TZ8/p3y8f/fX1k5ePHuK/T74//vFH
+4eTJ06+f/76x4f+X/7NB8+fPn307CG/DL9Nol+5wdPjXwZM3oPnL149ef7s
+McB0x2y0HK2xZuYoESA1U4zZm2gS5FMrB0w2VmVT+EHeOf+gxfJ4a3kzcvH
D24cHt57S/+6e/jVrbckhPgzxA7pR0eiNgVFLq3wdWAhILs2cHzIlvByLOEC
J8gpkfVnQFCLvCCuCWS9AnmKBEo8Z9PAGyJB1xncoGJUAK8ggQBnAOw6K/Da
gVyhw83m9h6TJ8ljmu+dr27BzEm0ruqM+PSRc18m7949gG/y0b97B6rRMegG
5XZDVxuoFiYGV22Nl/KlXfMzopl1tp7CqQM1geKDI9cgtfGe1LSxvCy6d7i0
k6ygm3dCtEIXNBwSDgxGgZMAkp7nC1oaEHcZ6u+kvvg/mnRozjcZEB8u5mFe
z5D8kb3Jp2RVokmxMlTlWa0CFM6NJRNfL9L7kKiPXzxJdLjzeHS/jn2Dl1Ng
FMWlB39sOl54DsoFXzAXR0aDH6GtCK44DLveosxkO4j51mmVkToE1gLNZFOC
goSTQ+4ZCHNkRzCAnwCeBp7FIp3lK+Q7fIwpTLkiXn1OywdtS6b+14fPaNKP
tygv/wrzyBc5vPSwXOOHn4FubRI5mQxIpI2zjynyctSLBxMe6AmyuQzEP9Jw
iqL0O1gkiCAaXf7tOa88zroG7n8Jy+j7A+4gH9hQzlx1NnnyVfke1UnTW2Uc
Oqr5vELlQzizvIDkjKNlQI3ECGHdKV5eOI9GBodBoqeDaYh0lStBqukDMDRp
85+hIm+G6yXWtGvvXqKiVDdMTkBwM2RFOzcPxoMvyfREmu2a/gW7COOo/r9/
F/Xj0T4iN2nt5O/ZRximvZO/ex9rMCNrJsLvX716QfIPfxOP6ZKe3Y8GtTO+
DFnLYvkTe2hpiNPZrmivRLWa6Xdgu9PCT48OKJoRqLs16NA0kefbZlQuRlNk
Hmv+vVqXXY2AuDXpBMkGNPyctT/Tf2Qi8pXHcJxDfhPUatIjW5NKroLOCCPC
gwc0UGcjrtQhIUWL0LOkVaBc2ZDNUZkNYp8bompZNMydgKWBpaYcec+4wWbb
J4TlL8vVXL6QColPy/I9DEo7J8KvQ+6wo2fLHPihapN93AXFKF5+0lBg9Gwe
zY4faq1Z78LvXHGHuD5rvcokL1itbfMF621Q8DI3K1osRwgGBVFE8zIFWbHw
jF9LVUzgucm3kxFa1EMcoEhAoSrhw7AaspbTOrtza1utkqt8B1+//HHEVhOY
XOgyGtXpAia72ixTuA6m9AD5o9Z1686tu2+H8F2Ss8ltdh7AOBtYHqlYYIU3
rXXSkkQHAI42HzXl6HSLO13TDvBO91wwGPc0K1CG7ziJcBNwEau8eI9rLXJg
VSDA+llN38ULfkEzNRqr1ScDfJkVmEHaDHCjQz7L2l8oF4Q3BD4vtDCQe6sD
Qb9Qoc8GFFDkQKwfioxoLQ4+yaYnWtlgY427HwVbAMwwlDdwsE9QXIGFOS8z
+jXrWPVsCVa7EZifBVik5zprGAHGw0+DAg5HBuwReOCRI4dgkqAXWy/LN+EQ
g28HtJLkTTI4GtAs3+JLA//MgGxYXEoKZzQkL9gILnmdkxHw+tXj0V2hC3ba
5Xi96wy4AZGBCRX6jhDFCq1w/LgQUXi8fpBNWdfoGECyoL1Yo5BB6/tbujHE
5FN8WVcHYnwM02DXHO4KufGMUbAtS4e2InalfEAfWOXvkfomBVg7xbgAIywv
vw3UxG87iuMEaWmAa9ONevIChmnItwJ3Od2AZKSNwIsH863/tkUlYQpn9D5D
84pe+XALiUCnCTZ+ibcSbvMsX8NAqMAPkaLRfXgKagkYIHPyGCPNhMYiDIP3
/ua9u3fe2vnT1n8DnxnpzK7RN/WD13DUEQ7n5GZEhIs+r1m5BoUDrZ5Zii4F
k8t8S1A3p0fhN1tyRKNeNFcDg4Wr2RtoTKA/7SC8iHJzyECfZvYuGVLsP05O
geIKXg2ZvDJJIhX49oc8pcd+BtVv9JcCjVyylO8c3n4Lxw2G6OTaGPXC0Xv8
4zW4FhN/KVF5kv1QJ4FeL1wcvB5wntB6Iv4jK0KCyj6kqy1zhU1VbjLWTVAo
gKBZl6RyqOkIx79oQmeJmN7k8hCPcEdBxJ9DzVJYtWpMduO8CzRSqknJDm1h
JCy0pRJUnNKhiB69l7EOCy+Sn8jPZKcdugy0b7Uek8W2YJOP3m85aWWQDcZL
QB6K/VmJZgFGP16xOHLA4jr03sIP8N7pko1+1Mi/1iACPjoQtdh7hq8lL//2
YgADwUGTv2L0+ulxj9bSFULtDW7rKrgNHKtjTRDIYK+pFaigQ3otVcuONgG4
If1AgRay8cnnr3OIpR4pIefEAHJQKdYX2Hn2vRo5ChAd2WurHPZgyNaQDzJE
H4QtVS/6kgNQnYOQ0SScwf5w1k7uHd59e6BMWDRHGqMOyJ0vjQ0rRGJfEffy
Lj+PDBG8S7pqns0oTDFPmzSJvRFeWzSvP9kaOKgQ3/6AxpHEdHDcBairrDHg
JNGURiMYf5ZbPiRXMH0+AcJEEZs1M562LiU01o552+mFRTrLopnb1T+xvZQQ
XNmzN2QQfcjMiMaRCt0BsuCA8yK3QLKJZ9S9rp17qmE6FhM8nA5Wt6+knOXz
s4I0jqLtOGxdR7ysfRcyXt/u64hGRB1zjasDOjJ+dICrGTwqmiqDswEz+zH+
7eS8mHHEY8mGwtVHj09ODuydqlxlcnGFKOsgwgSa3VUg0ewjqDVkwGg0Al2c
A7ggA3m3Sd/L3UbxX8fnYUyNTAN0+7boga7PKRNM3SEIIQc0JuCbUSD1JFhF
IsHn1insnmA6xYCkHjkvr8nW6AeOGITtNw3P07AjaM1gx9eRTYA4hc/t5aWs
A25QAlc57lzAXIVY8HWlYfRMgsG+RRJoVKWHI1LXZYpex1pUcjEMUGXjlVHk
h5dqK/waTxz9mOmqLtlZzg8AAy0rsp/wciEDwqNMkNRAhy/k23CDcDbBVG2l
Rtdow5mXRbZDbroNi6tBTidOvDYHyIvIl5SikxSXtNiukhb7YXZWka+dY0cw
n1pF+Z7DiHQDNCblPlYsiY1IyW7gT9ahwhKInFqmzbkGXZHEf6e1YlBN9sRi
oHyJ5uGM0TWsti5GqUbwyJyUTjZqhrsEjPHWsurdWTRastWmpYnxK1vKCcFU
H/RUkqwJpKbecBI2AQsJp/0iq9Z5jXeP7V+N143MaiWhnVJ4RlUm0//a8ynZ
DFuXc9FU6ZO6vRYXD77/kvIKKJ5cqwLcmgAmBlW5Rev9F2ACl/nGfKfIr/nP
7D8J/ZDTTDSdlBYZ6Q1Jzt/cdJ0TO12xJxJ1fl2bhkvcNojjGn9Pk67iEwvP
VxgZyeaRxhzO3zJqQCzXqC3jkeE7Z2DdLM9Z7undi5atoqAMHKhB2GcY5O9g
oMbiZiS0qzzWf8AmlWjnNBNmxe6etJAMGjK52BAFYw7VN1mZOF+HvBI/ynYz
JxuYAsNNvhbphYRQJEV2Fk5WLDIbXkZhhSuLvGxMzPHHzVOy2YJBNcMYMCjW
P/z8F9ithoTJV7cPvwKtkwxY5mfkUhdHdHKSnxYpSU92RXBgkJi4zkH5LtjH
66xJSYfU4BIrUkhW7Ip/mKeYcvP65Y+42kpTZtBRk27SKYa3cg0e/nz8y2O4
kadK8D9jlHR0DP/3S7kdPUY2ucEpUmaWN65rDoXRitgeEmXpvO2WijyTSvVj
59wXXySPxTKru9ko7FSs8ZMgncAyVSvOvDWkARcZ3oUUZoTGf1o4SzlJVau0
XJDVSg5wjUMUGOkDVRgkJnq12L2AIqgpHYtc8Scl8ZC1uBk0IuvnhUv6IjI9
nZPLZrYo+2twpzRJDX0bqN0ou4Kbl7xDdaR+R3vn2homO/qSriVIGRbx59Sz
AaP0RYlZs7Qrk4rjSyzH5F2k3rwLFtiJidpKO3/pWTLpo1kdRYlFm3NhSLgT
B6YZJC9xc3ZTDG6gUQ1tpEjmnr1xsvNHtPWdnSatUC93d8Pp77Ir8auYxNdy
ePA2RDNglwXZBS/DdCLdIAcaOvN5lKtx5tiarwH9pSbLxFJyRG1niVa/w0RA
9GIlPs2vjsbCvAb7PhJRe+rIjvQW+S+Rq4g8mcRRyOBTV3wifn2g4TCO5iI3
UzgfFCQmY/x5J8iP0DVJilYp6q3z6V0B/6K0PgvetwMFwuLpcWJoOA7QfJAT
iF74JhQt0VyGkkFQc6STt419ya5Gr2hIuUIUbYpBsuh4yHYRhvlvxGrwQd7Y
6iBVNj6xeugdNv7A+IqpZ8YpfXAuT68bxtNeRGBCPOJZDEmHZVeyg1hg7Hfq
77xflu/xgrt3D5gm6nd20wKCYu3JkxNsLHDu480G1/sxeUi+7HL6K6aAoaJH
yWNi1FBaE5xqnEJ0usWZoRD22Ym8LK8hi4Yfpo5p3Bf+gmYLJnxR6td3RPEr
ojHOAFvli2x2PltlIvrafIqVWfhO1ci+wHwpZ7bGJZJUdzDxyD9LJDns9dny
+XnRLK6tik8nVC9pepwTbMFy0BvK1QexrWOLfZ2+57TBllHmdnh2dONa3ANW
t0ktX5hXj1aIRW33GdXe0xrfGkyTJi82Wq3DftczUqIkiPcZRDCHa0AFu1Zy
lmMyB5BV91KIqs1GVNOT+IsyvccBYQlgLUsongT/EidPwVnWY1GNA+rOQnfM
kZyzpiW6YN24ubCzfVspWcO8B8QSKHtiiVnUfL3OkP1wWl5NapNdB1Rf+beU
7IaBbTBtk+QNEjls0VuLabpUYkQb9RbgIGdLlKg+0ZNvB+4tawJ0pR6FRC7c
wbn72aKssj4Cw92W9V5MSa5NJqQBkp7k0z16yIUDwk7Z19Ugr6OP+OBxtBj8
pbAHnA7n450H8Ni6xMg4HQ1l8yI3PcEESJBEwH5QRd2gRMhoONe6ki1/eUxK
USbLVUutdKvsQ7YyeXewK22ptRGsO/NMMTBbD13MqS41SrLEZNGCRI5ERaNL
IOtihY91ygR9o+fCxIh316BIpKz5N5L5nPd/jZgeXca8is7RlJjWlskVpxTU
MkoRSovaTtXFb6kooZoGTlsA45VvXcuDLruifh2zqs/5C/T3c05IpTBMY4MB
sX//6umPPj4LXGnGjNphbgNrMmD7iWnP9iMzIpsULwyH4B1+wYbrj/g+S7Lj
Ipgt21Zlcb4ut/XqPPmQZ2fMus3/INZLSw1mXyQpr8W5r4XRKA4mseoCM9WC
fEjar9bxakmct0lE0t5537Tup3Weel4dRl1uV3M0fWh3UIvTQCAom600cNK6
KVPCseXJWiO8DOo6JplidUaQnhrtbKCJOnfCcYjV+dD8G0wUfXuY9O+h++Q9
TLp76CwNj+L8HOv2cWIt+pHSnrCSAO+daYKOdp0y4mZbDLCEVS2JEiVfUVss
bz2JOFLGVLGemq8NrcIEkynwk5gYGXA5lEpYFkNJCKS+uTArVd28/cU2dM0+
SbkxPgHsA2P8URQIjzk6X1L9U/bWgGX8FM9tncFeztl50Bt55yPeFjUlLEta
uzeWkHrhAKwEoU3JGHvIzKG38SIrTPyhHIQxcdBgwlKwldW9rBOlh6dv0cfz
Bmwnksd5lJ0xFKXIXwPQnIFmKk4Gs1Tt4Eo5tNc1m1K0Ubw7XnGlRHlgrvA9
LIvSwAlmmxd+SmzN2MikRashJztZE7/EwUBb3qzScyLkioV4W8/02wqMdZ9e
QfYXbMG2oO1tcR6MqbAhNxdHAcpzrEIIDNRuppoa0pRaRqlq3eQ/dPVr0nYn
fTaI3cVZr71f3qI7piPswFBcw8e9/kRaVhNmy8mgUZ5rMHycqdhZrc+9ZmWp
P1s5nrE5zov0Q35KW3RhknPCUY+1BRF35tyrNEGtq68iIF/0bnjwKbMq8ejM
OyGVACqeOhuYnBE7NG+vcc28Ef1mR+a/7gLlAPQ9deb5bODiy4FGZ0IgeStV
FI9rg7lFkkG2a8dYdIiQoO0ttlI7uOnNkh/vOMng22rGBkn0YBxEqbOSSxS/
x/lDdGtA2nbypTgSW0tKKkdkL54Mh337Vy8pPZ1Shc7UHF/73SM85PxgrIjN
MLrJkYQKw9ww5XO4Vh9bucNKM/G9cl1qZiOWfdXGGVvu7OGOIXR65kLmkMWL
5/CjiFcqppLLN7nGEYiRxrsmnP4Wp+x2dkfMqgSPCwbjY5ykHsXg2q+gjk00
yjFBcxCmPnoFWs9E6xJ4ossMq4FhEPQ66S+n5fw8ysFPfjh5/sxXw0URcHMl
YYRUCd+Xp4n2DBbbal5zUoeW8x0lEzywDfoH1Is3wdogHzXaUXuiHHDcHq/B
GzORqHt0i5LwV116ozHZpw9zQkWJZXL3BdUMSDOj71ERMGdI0zgYAG7NC/XO
Jw9bE9NFRWatpFDmFy6VMmZxxGeRp+5aGCBIV19TGCFMrqUxd3DHMVXCWHwo
R0Wh8Wo+HUxaG/sLGWBnfpilitP7Pg7WUy7srtoeVLM5rWx7iqkxpClwfipp
Hn33AnYvqi/Q+/DqxxPiDsWuqCG5Y9IPsDVc4tzLslz7RktNPXIRmDLnObVS
e5M34Red/+Lbq18g3sNIEkApN5r/coBKf8Q10WMUaoRk6LMeyNW8KaWjfmQX
FN5dzD4EG6wdePMFsZTwC6JxW6yoRgC+ToZt7XdB3J172LsMl3I5JDAN1N7C
ekHWH1uSrCt7RBMWi2IvNx2j8VfMOtEJn4AvuniS5eRh8al0YuZh/gOG0mkT
9TIOI5+DjRWYqJxnAq+WFACEM3qEtl7OXpf2Ji3JSLSnyV7nzO9mJyuzHBSc
iXGJhl2J1boOk9/zmP9EE3ZU+N4Aw8pxu45XdTmk0LMGXG1sM97ZbiVPJhgr
6WzpXeNoo34o87mblZU69AnRgLgUh8Hdk746pMuqdKkPJ3ntbZF/zOZks+LH
LEUhL3z+VFMOEwkoAUOBx2CVblFl2ajJPqLfZrNVbAm0H4PpiL1F3ibyvmrZ
P3mCCb7BSSw771tZ7s8iDVFW8OeaYEsk+CVnWovLrxLTYlNuqL6AhtY1xm/6
OBQqu20mV3vHBkEcbBnkpKfUVu3JvHZghMLfBL2DZDJzc0n9CXEKmHVZkOgB
HrEeYanVxD6GaCeqHIEmhYOjF03lCyoomolOh8qH3413A+0t8tNtJWgToV/W
76lcS38ORYYpN+93byWLfWejt3ARQi9RlN8TfUerWZx8jg5oW6tUYg0JTD6m
Bqt9wUOmGhHkkrZd492arWT3mWr7qk8g+eeCFIS41pQ0zFa+4F59/HfrkDJ+
S4mU3/7rtEivXfVpBxfrVjtVq+LzVSuexmcoVrv0quWFepUWVX6aVhVopZFe
5Y6TG9ev++PFfNWt9yDvM/dAP3Y+XXUMI926zEjsByH/54d0lc8pnCdSDzhb
jpoBDnXz4qH6NBmp6VN3l4+bkzDmF/kD9y7+AJoA6QpP49ySF8cWf9tw0VFL
KerZKS6MZlfYLp2IZzLcL3371DQXwTr0qWl9+ZWYH3VOF95rsup0V4MR9usP
VYaB2IIok93vmFC728d7gmn6kmJivJKyApF2iiv7NLxh5xlSqlwfW2mpd3mc
lEpM/ljVFo4oBLcJuPvjMhByNYcsh/BHDDQGHly9pLQRfPflllM00UlIGpUs
pWQMSygsgvfjcvwtKzhlOiMkF/74GoEYOmhw45AJXcqbvM/hKxk37M+7wMHs
IgezpMIwiNsnuJRlZwJXMt7H9vYSYdhusR7MYdo0qDAmUpRSo8b5ahBTzDVf
h3z35CnkLF1ODVD1daiqpSjSijPFCZ9ivGhRM6efcrWW5Niaxgm6LmX38nct
HZPDwz6c9ytai+ZIZ1Gl8RErOAkzG4jaM049DD+hrM2xs17uIZfndtZigd6K
mZ+yRZH2TkG9guvAurIohxgfD8xYPSmFsENHC0bh5BZgIMTbJeSlLE4tNgEb
QQIWF0HhSfpVSEzOiElqcZBi1uk8swHMRyW3k0p7KWJXa1oO5tDSZdlDnikN
XW+JDp+VZAnA6JKjRUkz9fl6nWEqPlojNF3EaLIj0+oIF8RLZU5dWdAKHxhn
pxQZzt90QnHdyK+oMO24jtb7eGi99pXPPqDBpxdNA1R0t30eTkhxSoaI8RcQ
REKpp+eOUtA1ohrVkqxjRZr1MvfKhDjFiBnWgmJlWEdYMyxfkD9bZeo7mGMx
oPgPHScLT5SipfgYz7piisNs+9OCauZ4tJqU7i+/lOmovkp/O/rySymfbqLI
jg7/v/7H/9TElzbgBDlp9AWqk9+DOnFZzAmuoN2NOtHBnEiSR1xIT4XqYvir
rxUdF+nt2+m9O3ey0eHt2eHo1mx6b5TevDcf3cpuzW7funnv3jRdTCyfIAl2
ll7vFuuzJJ+V6ynth6ZgoIZ9qY/11P8PrYKHrr9t3Ui3lGpSqOhl8sur14e/
vHp/49n6dfP01U+/Pj25fv2XG09u//jzo9+e//zX5tl3r6//8tvr609/e3/7
l/Xj9V+/e1ZPb/70/sf1T7d++fnwbPrd6y2Wot78oZiMcc/IDwkUX4utk4dk
EjA7NLTZ02jTm2c4PQweJ8lVJm7V2mRbYD10o+DWoj9IT8/ndB4IZAlIVxpG
tDcCd1AiGyJXoNC6FKexXWzWLD7nESu47rAxksbLPOYbQOkwIeELvdCS8QNh
rEiFXOpzjIf+6UyKDBA3QGu7SCxTnM/0w0YhuVJTSLEIAVgpqa8h7U4Mb7dN
H9fO0vPF/0NDfYNlJJeh6MBDIkqOxX0kYqiRf2HyIvqi03eSxCceKf6pVVw0
wzwiFAsSxlj5PcYnUQdrOa886w62W0sI6Pp2a18mTpwVPgJoKAJwjLDUrltZ
pXIjs5LV8B1rEN/QaDtyGgkiJZZWnNKMYGKub05AltVp1tRWMSB4m8fzDylM
5hSLGriyxQNkWlryTJMfEemhbR4ryKMC6Q4dw7pYSfCi3Iawmx7q0z4N2/I4
r8SXh9XivPuddMlkCrrS+wtABcKUdMp3zBlAkYQOXuwexWlHoiDfd0fLw7zR
bNb056nQNwOggCCRhlNDyPxzadMgCkol3mOwGzGTKGtnaVreWHegIZbfM+Al
x9YXtG9qZmF9u7n4u7DUCk/gdidaoEuvyFaRGY9aBZMUK5hr9AljEIRTMHs/
hkrWEl3LxFLZCQ+b3EkratVpM2RCXox8kT3r21PYuBFMd7TA2sADcUiG62jF
p8m1GN6MDMU5MV1edUGubhJlrm8FyDNV555mBch80fZzMQ2Cj7toE5Gcg3IN
Aj+As0O20v4IqnSzZVmSd9GFKUWq0IrunHK295pAXwhB4YNkZmPlAUEPOXYB
4OAKcowhH5B7BeVGMSfpktmM8Uv9lW6dqHqN0WjpSXK0Wk4EYUXdbirBEDXe
+LBB6VCDtQVcIVdNnO0wyW1F7qrW460k5gtfWIfJwoSKO4yMTcfGZm7xelUH
IixE8o/XwRLPKEfbr87h6ii6YjGKeOGpqOj0Nu5hSDgirtxp/qGTAneiVeNY
dE6xj23DwLAcv8yjjE3z7S9RL2qEPWyo6IbzMNNqmoPxW/k8zhFCC1klKQUt
8wpoBVV5YPWE+T3sO2wmhbzhwA85nynyo2BNuzLTu/UMQkyqcJRtxq98GCFK
xNIm8AEuFZQ0GOTPVvOOsNIZKA7nDm2l0/RCiquVLNjtbnBTjByNHqZthUes
RQgGPI0XC98lxwGWvOgZksEGNv0VbKVB751fwQRK0GYERJrcrrW/lD31ekiF
/DUL7YEl19lR8nnHpBDkk/2s0PlLjXRJQAzzyFFBAd0JJAoix2ZFzkjmGkti
aeUjndyZoeZEtHUnp7omnPItW/yLVVnOLas30J3oSrQ8Bm0gCzIuUDSiZzGt
aA+4qPJ0i7cPubCDowU9eI1MUOigNguX3JFtwN1Yml4VZ/iB2+1FRg8G+lLg
AuZ8s1mCcLQX7xmI0mhQQXA7T2jsYWI/69fakKmRa8Pcr3U7TN8zORT5lHps
mF0tiEZ20aRkvXzIOXfegAc9bKHkBHY94MYUvuimtEnacYjof7wb1yulGN9s
WwcwijopzYvjYG2IP+BLiYi0Y5VPc8x6E6Y5yTgeCw0KjbrGMbHAkUHOB49q
UPp8cPj9C8Ovp9+XlBIw5+x1zkT/MmYwUcyMBm4X9ez4c3Cz4fcKp36UdJEo
ev6M+B49vw7wMzgiWqD2Q5mmeW3BtrZML4PSf6AaTZDkyGhbZfa8SwTxnofM
YsUIIj2GmRZ89dGpTF6lYh56jA2iT4veU6zThJdT0eIIc4DzKkMshN7vE3tB
hogrjyIrSZjadDUnVDEw/GlEwvYnA1nxFUR8YayeWR1LGjSRfz17X7+u8glH
W3nTe6orWIEHdRepMAGCOCcPOrnOzJ8+W2Zo95TUDoAIgzNHMNmjwHvrHwUG
3l5treKmv04GrWPxbJAkpWHYqc/ar3EY2DOPeRBCWFgaC0kjRG4zwCS/nmth
QEWWNBQ4MQWqdVInrGBXwHSQeslf3quJYD4Kd1UI7rSTQCGxh4riK4usIQ06
jyv/d2IHsjJUa8hR07HhXbCAgQ8LPvtPL54FrRx0lU9euFCJHEsCXTczGGdf
zmZb6lvAtao+HWafrOjdC8apkkO+0sXOv0KeZ9epCtT3MWgkIHslVxBf6QFu
uDJ2j6liR7K/OTA3zyhR2FcCc47BMEL94JCG6FHOzuED0G+Oz2Ke9BtLnXl0
BMxMPwECCj7x9uoXqfx5lI38BEY0gQOpeuIjA5EkqQFNgHwq58n7190iUiPF
n8+5LFqtR9G1Xxnqn8mcaKdVl5/15eI62osYjKQ/PQ/Z8SE2SePmSzkHK9Ko
5oe0TXEbMfMATk7mxuRPi7/Niz/D98hMbdibTek3qdQrt7yVsGP0zRtH5A/r
2Q8NgDO6WQ8Jkz3qiIV+9+iV18lL7yTkaXWhSPnbN4/YtUlmLsKqC8wt5yrE
GTJiUPGfMA3GxWkygjnLJhM7D3PshHBaUgUJfu62fPYWfbYoQd1aYOsr9sxF
TkjkznCP0fWAr9NUJGUOw2b48wnpM2I81lmzlUYvVYZ8h8tnb4xukn0Y1Kih
3u/aeMkE9klCJPZQyYRv8xlR8k+8aoH5JVge0/r0Jmot4GO6jyyGesZQdUYs
pZ57L6Rg+uZOLSrp8HDWqyz3hoPnoC5PS+AzaXGQjNCzb0E01T4FwEUfTxvy
lecelDUaNd3kP4nmcJVdwgeSJ65Eq4pFPEZiykjg5E4mg8Px7fH1waQ18/kL
ysFrfQHBrIXBmNjSXOCeeccf2u1Lh1tCE/DKnAW6gwkcAycCfjMHBW1apSwR
fBoTBXv6P/z0nJAhTpoSfWStpWqPKUxUA0Uorar0nL9mWZegDlRRSxj9XDv2
DtRi4dWWzIpQbryLJwn/PgwrIKWq0hqP4ZJSStjN1uaLxinCGKT1SwHpNAvQ
OloFY56Mw8w42sNonz2WVbRu32kFA4Yo8lawyLQaUraY5Y0gzGkPl8E50u2z
IACZFAFaJg0TfRFODz810auP7kdyHvoZkl+CS88ScYKR974OmjAFzg650AMk
X7OA6OwH8nmBJ6NipjdPjp8dIzwCRVZ4JSCb87RIR7PotweEeS1nFK2BYg0d
zGHOzTmSQIgWDDx7/srvJUyVvWBogaPrJh5WjniDhYzETXlILqwgay4kacqm
1SOmb+B9Dg9apLlkKXDrIyEtj0YP+v4AnSCDCYXckzUQ13q7BrthBTausnk4
oMmA4IrhOSprP28fz64zYV2QD8QOg0FFf+eBGB94wzN/O1EkV2kVeZV3Unmc
3xP/iDd+6UqzqRxiItfKhGjjesifPelE/kzSrddpn63tol6KyVk2nacfJkNK
Txc8CIpyK+ZfwoZQCGzlp537I2kFNpPkn//8p0uC//4e/ZQkA/704CgZXGOY
m2vwI7Lqa4Nh/7MjyR2Cd/6eDLZVji+n07pcbZtskPyj7zVQc/HxXX+Lh5TY
HvzwZjBdpcV7bNKWLzB2O3jbM36Trt7TAmCk+loNhkc2h3/n1wbRk/+INuTv
R3SG3wwwoXnwD2eXZWIbO9HLF3jrMp//daVmdk9l6Km02dWXj7hFIMLHnxPr
nQdKq4G2UIDIHz/fPN4SIIZJXS8nBxhYRBB6KisOWSpn6kUYBPi+Fo+cUVPQ
YBb1dsG1FCR+JrrnE56FfTs4YZxDfEAyK/sxnJ0kE/fPsMcgxccfm4DCy8pf
b2sjTbkZMb5KG3ucyyLTRgU1/hfGpoMghshZxfAPkBlalVEyjBgKbItTlUez
5JUAecE2ShWsOOVEy6mFGelKdJtC3nOs+8Uyood/yAx0J30cVpZfawj2iUl+
nNdki94ZPW0ZhDvtMSvWLASxByf+zhL3ngy4qAdu4USvGGXfrlaqWKBeKJH8
SAHUoBvns2fhKgg/vbNMgZMK8gTYN0FTD/YQKK9/74YSekEr7lyu6ZARVvG/
vm21j2kmNWwnGOe6ndFH//iDC77UOTjhdxN5nwV52L3sjB0Z4Y5jSEWySSSd
R7L5k+hr6lFGkUgIIpSkhyLqSJ4eJRPisVonYV8gZ85GAjp48mTG2mU01jqt
yrNa/eNgu3v1MSVsWFBE5xglRIfOVLqgLLarFaX12CiR94WVwG1FNWr8/thP
lyVB73yxnG8eTRjr8vBx+5DY1Fqj+PrJcGfYSgAh8X1lrrTgcz6LygBYeWI1
QkLtYl1BcxhW0at1MsF45RHSih49+1RsSSHZ1jQ+VQLMNhaKJcfwNQmfyyDY
NpUhhePOs8E899P351wuT/QnJ9+37hZWDATYuyYFvSpm8FMvIx3Yapr0hvir
iPmXQ983Wlkd5iFglSL6BASQsk25SCFsNyiUcKLFbDQtBA0LwIX8vKvArMP/
QpcgDTPb1g1i/ZqCFtRk+ZlzrqZe2kAcm5w2hphYzUCwbYHlI2Ps0LU10hNo
2iS95K1P07VD6z1aeI/9EbciCp/2Xgr10eR1q2r8uO5KDRRgIUTNjpwppz3g
sOvRChbC0MQdmGOG46FkFQK15YIomycJotCu0LLqEeUDolJqsO18ScDokFQ8
3gzGntZ4d9gLV7wrgcMJ7H0x1CcDqagYrRfpgPhcBDKi0rdVxspFPalrtwcC
NfXp42NNaObSW8ao4j1kB3teSaPpsc4hXuylphFVJ3ChCGWpUtU6eVYL3w9i
ZKcjqZqB5vazRm9aaCoCrNrpgtBQV6laso8fiVtroiNRequ+3AtaiBu4LAvy
fk/LLXJZhblLrZCc6Ipm+lEhHnmvqGIJdKVP2yXHvb7u3bpx+HY3GgEGzrwB
0IoGOi4stCIpqbfSoEogbJBFc3kv3zhDUkdVb0fYrx300+VK3mrPaq1XC6fr
mKHrDQE0ZuPgPAaY9tWZMSIdJckYsLiuWyoXua5DGgf6hJQgaB+OsDmt0rlC
reOc6UZyq3pgY2haa56DVgEcaHIuUrJuQxHynMsdPVDNfEXsr2i3llWaEpBS
CnwJDXI7ANrz+AhGmJ18uS9rki9n27pE8m13wTyH62wzuctyJJcY+vn+Ei02
UszunviaX9OSkXeaIbvJqh73TVD+HzhEJR+doIgx90aK5XBLJyyaajOaBMg/
EHAV9tsDvrVLuNkD6jniLHxrHNG/YBFv6HDuxrYNboaxK3ymE0KXUC3+iyeO
21DVlxZrOtHtui3T1qCrjOADI+NhXRmmEkxuncYHVVp1h+ilEIwiaGqTS3xy
E7zkGVhtmVJV9ithFIzDr1xGKJ1Z5D+qlt7L/iPUPi+yFhziV5mAWouacCeB
eJiXkojNcn7SM9WJL42IBDFW7aEr2Yi4m4ejO0LXSfaE0q9j0Sgygk1GrBPQ
Exe1CSsajSwoo6M9w0DxQR2Cae/NA9wNxFUBnRB3ZrQgwK9EM53GxNAt9M1R
PSlB6d8JLq7cbLJUK0bs6o+/HIfb8+btRNqihDJZyHOasxIgWFye21TJRO8l
DqDF0/j79uB5HXTcRXm859bC+un7I8X7HoU8/EDpVFNEiDgJBjAsLAXCpqR/
FMKpdH1h7evJC5cEiAE4lCVd0FiKifi7h6PDYMFBA/qCI6IQatRBKad6YPMI
WzLRXfSg7rLdAtqzn8kz0gqP0kRctqfdSmBGo1JCzjfKITnLpowRQxYfLpGF
vqKExyV+xAqA4wBTtNIfUBIHyj04nkQSjsKQD8s1SA38Q+UbE+738stdCnQi
f42Ul/tEPaA3XA+wIepvH2RZU1RzaWkXr/9bqyxF+i48WbC7mTk4ffkaJYuM
N8uN+L9nOWb0rLN6eY23ZECE7tU/NZaLljZgoodBRtW9MlJ43Mm+T7lEDkCq
pX7Lb78vy79sb+YfymV1L/23eJO/6WvFG1KFqJ5tUiAq0HQ1Aw0xbdbrDOo7
i3PnYiWFoDr3pswJr8Ev0yVBUcyJEqSUhXkJmnyF+YeqLUsPh6B7nMdeQotl
GInu3Fpoc3lyiOr5dSDqFRMpBAWUOP0OYnWBz4Q1+9BmCSi2lVga06voLVZh
12kI3IUZ60s6IZPYVLUdaSexnrI/qeAa0sqgRT+RJdhDRc0ya9mdiZQPkKOr
7ZEIbNLLWKRNq0+bPI6Ij7Xcv0DlT5MJ5+WeZCBcmglLf1I3QMcdrbBQH5gn
PFHxnIm29jKlPgu+dc4u2XvSl959GZ5Sq3eYsQgTU2wRa037EIXaILFbQdAb
sFuMvpifegN5gE5JF0GIsAwyFGfRR2qDnZUkRuV77JXwuD0dh8iG0r+5FFdg
/KSsHJUmr6KOneX03Q/9+OTPwGp23SDnXgTMZ7ehzh0gguIFTL3glhFHLu22
mGv5AyZ6lbsnLGm+5O0OGWGU9GvMM/ADuMBRKVvdcgZIhYl7Y1wAFCTqVL/J
R5Y3eWB5WZy2dcxIUjxH506CaOEuDwgyvewUVAmuVvHdoV3/wmW6l5/Xq8gR
h107sdIO6+I3q/JcsOrmYCx6bMRixoRDORAUaHUVFvbJX0HNQIMSAzSUK3Yc
HV8AgbdrzSZrGqyRO+MifysAweJu7gHEqQKXoo2WZ/PL5IRxNYLc7QKsbHiJ
YCCRrvNim4UFYB7FXjZiKHacH0bsIcEgbMmcvuMaSg8/FBBnYKDXdI3gWviJ
/r7d4/srOSn+3mmwjADxDajId4ii2EfgKcvIERJMgjLJTdPcFsK3omao/dvR
FcJ9G/J16+34QFHj69jbEzX2YFG0drYTO5Oru7tpR+XrsXftKlF0k4W2e8OA
G/ezWapJ6292YqViTCGENca/jWRmI8mXPzDj4o28xZ21XMsQi7xnB61uM7vh
UN0l4VCF5S8yWbpAo5LychFiLPO5E+EUUXULCMEWtUja1YcsyJCL4wL2mdET
RLHEylxgWzgccZbBt9wMYZCE/434EPlP9BSHmEeYrBM8RWFYnQvGw67WMzhS
zLTjVtBwP1vJNuF/qH8O2b5CBPDBTMAA5zl6ZQf6FZLht29ef5vwH1T7wkTd
8LVVVpw2S3tNEMBgy37LtFON3WJvzXFSpLpepEOwOPhA1uVzUEwewyktC2nc
AHQHS2Nb2T9P6Rw/hUI5PLqDr51/lHwRoMWVZwmiClE59AanNQ9mCBR5Xguj
YAwxrHS368bpgZjICZSPd7XKCM9LotPsyOLAOc1MsFjcV+Mb4xu4gaYYSe24
Lrad6/G3bbrSdk2T9/4BOQMfJEViw8ixiE8iVIwdqZZAEcM3fyHtAfb2eHWK
9LFcY6wQdQqqZk/ttxgrpEObPIRdmwgYJDtcVthnBH4LdxH3Qu0nCTrYHh45
EjxrMEfBNpKmCpgAj6H3s4rAGppoe5I74zvjQ9uew8Pr2HVcKjApIkFwpIG3
cVGlp5TkqnzHH7M95YzawhKiD1qMJXR6pfaN4AifiDZMJ4bndqt1brI/8a2Z
JHbDycNVm8/QINjVRNT5DZ2AOXAcMUlPUSGlHn6emnOqJAaBQIlRIDwDOkGO
l7plivkFeoC+lIjCw4Pv8a/+0L3G9pDvNCdyDZxFmCmsPHr45LtHJ69Gxz9+
9/br/niuxojQAhrduH0H7YhjW7DwS00JEZQDsSGYe6ZV1SKc4MAmTXr6zYAS
z2NKuTG+2blGr4tVzmi1zl9kYOrZKiiuRhOe6/Xgs3hhtOtzl5SDUZC8xGHH
tNtk4Zlw/Q5OduJ5m4ILK6aZH406w4sDojFENbwtp8izR0IPVCtxHAubMBid
Ur03ScRwdNpRDJ0EmydMprUtuiTMWiV6CrwUtHiiP4ZewQPzgJfjNkf3hEcs
Au+9Yl7p2pVDYZF0laerrx2lCl+eJbFo7nneOcrnxsF9YeQuRhhtIx0bslUq
Q5vAxyahcDLTSvYPx+CHguun3Z7R1EsN7K13b7oZHnw7qQLm52waYHHifB6B
nXLOTQP9YoMsEJkegn357sWOoINRNTgfeUXYz4GuzN07t+BCTx7Nb9y+fXgP
7hb+9u71mzfeDp09cIBn+fLRg+dPnz569vDRw4sOvSI/hzGe8KwTkBdLQmpP
EZl6tkoDiSEc+EjOqg5h+FVDMJKiktMeNtc6OxWQeGJxWj9LUha2PRqJtIAV
hNUOs5a7Wzu/tXlhXOnm+Ob4q4gvaeHmWXre1VoJAkjSOUGaIdkEiA6e8p1g
fkY0Q9zb00sfgbirXrC2tA70XGq/XWmrqX3J1CvrsKafvRmYB+inMwx92Bhs
b0agphTNdo2cCE2wKnMBqePTPzw/eXREQ5W2krTx5faSAGPirib8d0EKJQbl
z9xQw/z9jkiGgtfpKb5fEvgIZT5KggA1iBViwhyDWbIA0ShzmCvNuDY5GXwU
G3U4OO6RXIkffj4J5jdBQ1wCV8YOnh4/iLZQkizd5PsTlJpDqyzRjLYjy/0I
P1+UCv1EU2bfBVWnYE2kJm6E0WfbFdhLihFtwNC04CQ6tZ00mavJe6l6DW1A
zwVBognctMsWG0hXmO3quiIAdnUYwwinUxC3Yc4xpwz5L3EFca7aTq3WuXfC
GyskxhIfHr0zNqS6WC6zG2HYnn9Duf61+9SbJurSyZPvSFdywrOKUtNqCFLY
viPw6y1xwr4UuVfDZJIpd+Z0L3yaU//pFWPew5hfutCFEPMucjed5XXmIl0q
5ljkWrGZIsb+1vAPMPu4yZst2TIMyEJNTn7WDFyco395SfcdIVvQEKDKX7n4
pmcOA+bdR2xqCCloJakAO+08536KxYZsQ2AxsJt9nTdcq8O0scbsEuxcENjn
iTBdwpzrdQgooKq3OeD4VLR4LYLPZ8d0JHfGRiBCcJgxVWIDRkJ1Seo1ZTFE
0mOkge/6PTDnplyBSYbRR80Z23IvXJgRp/DbBVFCuYLXSe1qTdIGddN6AjwU
g0ZMP9Z4VLn0EJKeqfk4tMsorCR4quiEFtcBdzNR7wH6ylCbXGXyhxQN8ppa
Ubjg5XVe89+VGhreLslzNsWZSqe5VW4/HaQBjeWLQH4E+qF1bQbKRRVGTohs
bzLHxTPbPmeDgUYOFKsc+qy5D9josZg3VQKEeuUnG+vcP4Wyz2kct4NxW60B
SkGbTZRpjfqRv8ItrQ7uDiyvu7+qA1ssM1CYpJLSGyMu2DPkdkGw16vemlnD
LX4UiWvS8qdpMEPavgNXSSuD2Q8MPTJ36nF72uJkJiOK9REdnuVGXNjpDVQ8
P/RoBIsaSri9Qbmrvi+l1zDxR+057hSrIwGx+S1jLh+YvnntncFiN3Iq4ty1
gfmjCI1Cy2ZiKBq8mTaDcBhRAaFPygS1VOKJ+poKyxIJCsV6XNgH4wipRj3M
4SI4qZ8yO6VkDTSZj+cjkiPL0PtWHxAOS8sEQN3IkFQY397s65jkIjuVkaB8
o4qd2baRsiQOZWoxU62dwQxu0vNVmc4NybVuuMZFQurMTYAVjIGCrMMlo35x
Qry3Qmyss4ys/1xCZNSVEVO5lejhKp7m1je+MnyOwE/9UNvKJgRMIkYHFQvN
RKFOAoATOKydCctk+RD2rNHAJovOf2/wo484gvgG9x1Vd4DJXUlM5DS9pkoX
cCyqVwQdzRC2YpWK0tCn+WNBJ9lV5F1/925PRtO7d8nVCbVwvMZ5aZMDKUny
1Zia8Q1fqr+mv3VSAuTTNefcfV4OGjrr3zzEbpc5QyxiDBQYGrw2l9+OmpKi
oPDbA1Ys3uxMftnbiwN3h5HZNFJj+/H3KPfiH7Yv7bVLYE52plV8Fe9L8oa+
RTkVGk2ir2gECRbzRqfDgd3gCf7FgQIIvNlBuxeutxPbCmig3bJTF91uwBut
Oc6Eby85SP3ywTNNv+wc3acshEksAO3ZQdhRnE2X1JfYctlzxN2PanW6wbzP
PCPey5Fnh5+4tNb0FdAaPnPpC/xft0D3xb4cS4eNDqRZdaoAyz1HErZm62lF
G3WiFdYW5Zq1t+CKIeP8v7TtLMUmYt8BBfajrqD6707qkfVrQoHdVFvrkBMV
cfTuNOkdFCB1+zduB7h6C25QQXEDUbor2Zx1Zs2D9l0WWhOMsN93J4RLlodr
1VftXvPeXHhnyVufmAlvdjACqGBaYaJ5hYiMOzsXdMsRO6Lkrc/Zx+m2Fxwa
LR+Hlo9PqN+7e0GHMnahfcJOotYaNKCv+Va7dBcSpPjv2FwtziMa1aQIBF90
HFCThP7wLMauvV/huluJPfvoz3n6618fIqISaPx+cvlQrrZw/TE/dtwLPBlk
bxj74/J39nwFWCoIGdxGOzIknGEErGL6d/9GuHgjOk0SLMEM5II21qQGPoJO
yl5TYAGTEJtKMhcM2Ee8c4ox0rkeepc61VNtHHvjONHn6gmX+Thvryj6LlBC
Zd4LrpoK3RfRpIf8nPPz1oF9giS91V5Xq/SrnrgY0so3GKW/4/R9oXRQH03x
O3SJu/CsvWOCHdW6qC4S0Qs2pcIA9u8AIkIgyR2JbALiV19wEbDEwinx+lZ3
DMTF7aoELCYi6jYurat3XlgMNnNHCw3e1vV2ba3vrK5OUT7bck7vah1U7Rhi
TXdt7E2+JJ+UBkst1uimkl8mwBYiDKKarc4NDdKrXXui4zjZeqrdGE2LwBHl
Y+LQIpALSgMX3tjFbcVt1vRrsu6liowKzExqGadrb54SZbjX5O7p0gqfLs4Q
rW0D+LRQJgULMJldkAyrlNUWcuHzc84auWk5kYa7CWmPoNF/YxDpniJRdpiy
zhn2nauDTsVh4JcLIDJyL0dOaIzTxW0h4UqOnrx4G4M8eiA/vhkIA28p/VIH
pw2wxctBNSuwWIInYyeEYg2epahvIIAmM36xaEQm4KXTFHJ1v1l/O+rxgqBB
suXavYLBv7W0WQQNEgInK3OaLnUHjTLrB7cP57Ob1+fz2a2vbs5v3UzvXD88
zO5l02l6Z5Z+9dX1bsOqQbgZEaQfDPws6PZqC7qKzIPOnRz5B/EMlI2Pm4/N
ICigEFWZkwfCrVY4h/Dvn/ZJbbFNrl4EmEH99yTqPU3vX4UN/+X46Y9cdrpO
mwMDpcS3COwRDaglFb5EG6Nn/WQezz0FXVxc5E0ZO50Z7c2vQf11SjXI6nEd
EWEwAD0VJPsXUYXIKtXUuLclCjFrGK1lpFzMxBX3/nUgydNtWgGRShecU8xF
t4glRzKjHf1qdv3urRs37ozm99LDEVDQndF0AT/Ostn12b2bN2bZ9cPwaLGx
Abv1evcn6Iws+/3AXuDOFbnEYFp7hmnc1GiREAU1vhOj1kndLPlyfeYW0i0n
EMEYp6tyih0maW81axO5q1bjW5t2P1GVZVa1AOOg/xgWgH1J4owDCucDpWGp
IashW6lzAOGDNPTo5NW7k++PXz6atCr1x1bSRUWshKBN/Jze7umT5DjvpyOe
cIgtQyKjYqJdynG4cm3gg7XaXUmyESlgeeYSO4yPpiuZpArNFAHKM51lvtfe
Ewo7Ap9MiyYM6oPpoCfX4RhZWs2WIwToHR3euDnop62T/De6wyAqgAXgRpSw
40EZEKPqzRpda2TIt9amwEBc5auNN3nzreSZxlGv7ySk8kkrduW0Sx3OCP4k
gOyTePaTALhHz1mGp9opSQFQ8T7NfBL3obdV8dcz0gWLXKvL4sl5rcImJMW+
PVOSMZG+rQ/jsUK5IJOIgqseLIiC6OQEwVAUb5VTfJSAiOUwFtsVMGFDfqMb
WoX9lCWjQgrJKKFlvIfYaQMqqTRjDmzqLZOESyKiiAhUPqZNa/uon0/V45ua
NtRtAmG5JdYjkQbeWL+eJBw4r62yaxzKGDieCLh4jx6C7drg8bqla8T36s7N
23enXx3evX5rvkjvptPrd+7NFtdvZ/PD6fVsfiO9QBeQ4uxLzUdQtUM1SG5E
/9Ru3/hqOr89vT2/c/dedmN280aa3fvq1uzOjRv3Fouv7t7un5rxBNqph9zF
+VlLZZFfR43qeWdbSkU0oYc50H6VR1/hDfiEz+zait2f/aFcFsnDMht0NFI0
acPvCeNgZ49PuWdoWuS3gps77ENSyRgIH3lMAPU/MdV3Eh0s6dbMs4Orx83Q
gPCwcKz2eRKsF/f7dwScj1VmeIbbIEkMsuv0x1bgTQDELDKYZGmYYkd91NxO
eLJeKGAFKPsU+/vrUMgP2ZR4+uPJ2+DTrHQOFpm+Ngi8P+Isai1fyqdrYN+1
56tBD3SV8f0+KQqbUwpi6PzocS35aGHglVQ+t8NV1PY50UrZ6yQhZOT1cfJn
j4vGkpia2ZJn0vYRsdtEz+T3BygPIg4afiS8PDH431V2frApEaCReyTy8Xh8
YDI0fJ8IX1/cUfIVekYwnxIWz29MJOeY8zcYzTlujFdjGtF6hYJETAXJGnBJ
p8tfoI699PcggDCPT6kPuDzEyf4dzqmAVWYfN7l0ZokUNExA8X+iKhalQEqQ
YIsGW31Ts7iaRfbrVw/4We7z9brIPybZppwt+UxETVGsInM3LY2x8BU0FZWm
kDFaKQu1uk9pZmxavZ8cT5D9Mk2SyrI5OWRWbs7Z4EK9FTFQrbcE9nVHHcZa
HBAjKJIMswhImeBeFFirIUAO+Lk5ARbwXml3sXCTffK9omyG9jMFscTZSZpQ
8HzU0idkAbSjXvXbtad+J8RykrFJWXxM9bb2G3tW3DZwo7BkLEq+z2vxDnpk
GDCu+PTZvOLwEgKR84rCIBDjRHVufWB7IhiN2tId65MKECmJcnXOFpBXUYJh
uXIxGrLoMWWDXeY3ePiaTW35a7SHHs8W85BGm9PNYNxziWmcHRc5qMM4oY/2
QnF+Kuh9sPi/81qe0+b/I0R19U0i4EQV+xsnRm4H+q7WfLaAU6Qkt2fjcLcY
0/WxECftzOnmdGCD5VbcSoMqwvcCRs+qDRxR04UMrXHCIUpm9HS5kFJU4rUB
mMG+w+uZ5hqBUC+YJhgRy0iZbm+BT3Ds+bpTOFZ16ZB3lUsS715/6/OmxzfH
La+VwMJ7ftFhE1I3MhNg1bobGlKFpK/DAWU2ERyUtRzw4Oh06sjp0K1JgXlG
HB/bG+LlL70PnsDUz9gTrQF/RSlE+Pqd47fBi7n6Ks1JRLJe2cHRNQzHdD73
V4xTlVuS1fZyv4j12LjONwXxlRzcmUkPcoT6CGdE8D/1I4it4KMx9b740mdp
uIy1xs20TKP3+Ie1BgWJk1fsS2yWWMfCCOIlKbJIP+chtz4yuYTduk4yvkIS
8+P8WBF5ofmk3x1KMtJm20S/NwZCfjUehhshGPDi2H/4xn/thy3tPBhMtIbw
2shkbu6ezIRMAIleypdd8snf3vXlQ0lCoU8bPiWPA+f1bo6aDdqK83d9GEB4
4MCIgFrTUykE4wLTwD9YZGcoua1Vl2FfGhQe5caEnmsPagVvYiNxSknGBsHi
NeUrCH/6taysL5WWrQLBmadJqI98VFFutG0g9fpSZ7cn24CFBIlN0eloC1kK
Y2ZNcFq0VQv9yRqTDSNhE1xmTcGRDf24ybSubprZLqFTT3LFS6GCvk3tYIkI
d8MymmG3BQx1CIs+6AKsbCY7wq7feICtaRY3WivJj4+WjEc4lVRhgieP4tIk
VD4cjq+7LrI7WRm+t4VVWgkCj2+8IQjDPRT6c1qhRnGkDbLtE2hb10ttxpye
Ma+CQWAuh//ukgjnUIvEqe2WbRVlSuh9pIRvXkb4ZthGyt4ch/1v9cbi1tjQ
7LI0nWDk1XomxP6eS7Xh/lPnpoV20kVtYJohqZCb3Zdoivw0baVjMAGxpdRD
kC4BnOibK/zOFYJp7fRzGKHpjn+XaqiV4geoW7TXRDDLh8ZYUB4/TSzIuzL0
IUSJlJYPCuw/QanefPyUb7K6HFlckZHFW1GUoUHq760ZRDQMZarnXAVDDXUI
auu8mKFyNkJpWUuLANTEuMWCH3WunRMIM0xL+rC0EGiW8g4o3sPo6h76UtYm
XgTycnCDBJob263bDSWhkPPY1OpwlbE/AabHMyGTVQB36CL2droVd7ufC85T
m8Tz/uL9rOajDTkDtQchpUZks60E82PbthcN3jTUbQDISF841jYKAX9uddgx
CMUnHgGB+8wwtozvFoIaILngXr9+8pC2hkONpO+wwKTWO5xNMvfNieFedNpx
elg/C9aKph5NVWw8GgRLCHxajDTHCaNMKWVVoMzh7kKYgSjkpYh9gfvItxjC
T1FhIM4AN0JhA4mWSjDQGUqHEpiYhrDIkJRg9DvVyaokluq7l4SxpYzQyjPt
0CEtZZne8sq2m3N4ifOkBPfTtqCDrJj2KUtGZdAvY8dGWl0y018EWoghQEqW
QGIFsfdeAEtgQavytGaY/sSnPTJGMLdxOfcTNla88U3Ae1kxjYa0Fz7Y4sC0
6GwnK00RSojbwOAPI66C4nV7upgD0ZF4Jf8SepqMMxJOjY3B2YlDqZgfSjE5
gQZWaNvYTX8Z2a8j8doGcxmx02z3W8E+RXm2ezcqetLYNu8Rn4vEBVUe9ZDA
jr3szRONcrgCgcGDGz6m+SvaOJlsSEphGyOJahI7XaO+iPiVul2g4ntSjGUn
8jiakffmfAW503zxL8hs66T8BiFiFkAahrXCqU4o9aKMZRnHgOnH0fajOFwv
0ta+o5W5XbMIghU/fXw8ChoHqatn16b4U7NUme7G+H4mEcx4TKZ1O2FAMWd+
M4vJZ+6WXMbLUotMXusMAYRDSjeBM+ZiLsMApqUo0WILx32aIKXldTTBywhD
0XZHpCiRXvIhz850Fa20mTbf57iTOrvTtnclasUb0iWNEKkGJHNVTlwsz0T3
EGEbuFz7AypN+AVs2C0NdJK2SONl9Qoy8t9wgXlKBuQ8C/gKSTV5SnaB+tRf
IOBMDevKOGm11q+5f1+e9Wp3NJ5mj+iq48ZquNvWx007J3hADqZKbKe1gztK
C7Yd+nN5iUZs7TZsyQxTq62Vi5bh7uzOps7Vbo+2S/ZmCzqz7VzGhf3Zfnd3
Nt+erKc3WzeJVo+GE3ZToYvQUtFZz3NuAdub7d/ujmlw4OdRN8OAAP9QnSWE
fGHqUnWtQ2DIf0x98Gle4c2CNeFTrOOsy7lXPjp6kNT/i9Yjw6EwDsbboQIR
WWXYzQxjOay+7Hrz05QekVFUesykQFwzo4WeabK01hMQ7nWarDOUn3m9FrN3
JC09W8f2L1ehOkMxl1V3ke/IkvQrAoI/0M0DSwMQ3Fw7O2gMVtxEQ7kDLYBs
shbNN+eHlBwwnwX2OMzDyKVvQ2o9KcnQts9zbpl8mYep+Q3sBSsxZ3L8xF9s
5Y+y4AmmzPoVvRj8mnlzDBu6Zxc/2UKKW0gHPh6lbTKCTqkpUngLZfrsddls
hhHTFrrBpKBQKbZMutSHnS7Udb1/2Tq70McK5Djox+MjKLp1ocovRBOndrMW
TgSKQlqjfixo8on+/Z69kik3vIyCALz8d6Ir+yioKRvH9MDbq19Y/IVfOVDI
0wh2Ku6sTrFqtrdl1lLBEdUQXmhhEsfw153DJbXXTduBr526WZB9GPgEe5RB
y22uRaElzIIUpM5su0ork4b0fr9exjVVrG5x1xVSH9hhEvjWs6m6C/z855mq
VuYIYt+uj4lZJkh0Z60qSHubiE+J/K5Bp0/WPdTPehSQvlo6NL5P+CDS9OjU
KegEzFZFKkiWFvNS0VSyQK/kiZv+xNsiokNLTFU4KD+O/Pr8yhXr+L5ogX/t
1vViWtPSujjuwZlVWC8g14oiGtLTHqO6/ICWw6k87y8BwR6ryXK7TovRogLt
Zb6KMx71yKNDH4ZenbzgDEHy9i7SGSFMwbQoybDiTQn1LMsjjiZFkL0XuMjp
GdpUeOjpk6ePdFj8zUEQd2qbP9SqkcBr4j5lKoSSWCOS+yQXAa+5/zJtbq64
cLhDGIyVUZ7SY5SbpjFb73EVtiw2Gs2TpNYSHY4oA14/kWFQqyi3xBkVgwNE
E7mpKeEUlG8BKG6tE0lWu5FrlcjCsIqpLdtpgbQkEe48yPIn24163mnfZMG2
xbr8J0BM32vRce6L4mu56vVuWvFNocPcOFNwpNdxDh+gndCPk3/l7s27b51x
TnZ6W24JH0PoXhC7pcM/xTO0qbid+8ZKy46YUk3l6fBmTzjeT4+Xw9NDS+r6
mliKwgszqMS5pOmSckPFmysBG7zbaOoBI+zMg9MQmNdUqgbErS14YiRihy2f
19Dbmey1ngSWgsTEQjUINUHNYObt/+c//ynnwv8NkPUNjpI30W+T5O+tn+FJ
ZCbw5OD7bH6aPSxngy48/MBffhxzgLbotXVavUdzAXvm0i+WzXo1eNt6+R/t
0fbMABP002lZpRdPofN3XrLBU3yAW1KmdV6PkbIVV2KM8+wZ/HIv1xs0k+pl
ljWDzhCddbvuX/WQ/n5ElPnNAEE0Bv/oqCd6mTvqKHfgC9uNk3M6YH7Edemf
wm49I4itAtbHlyXynk2Vr7lTFYqIQvBdU4zUm40QN8iuTfOpsxWjEuDEwTyu
qOQJPULCM9q5jqIJ0TBzyeBfZ01KIatIuE65KLWCbdcGOhlcT9LExLfBMS/6
jUCuj+PSqELq7WKlMEhCROYJVyyQXBx2Fj6h2yehKtwnRaQQFUdVPM8Pd3kf
MXXq/9tBaOPBvYHobhBaZCa6CmBzFvVlY89lkLcbfI3eNrHP0hV9UjT+bLM3
tipezv/q2CpOgLwl0sYx1NMowl0vUbuA2doWBdedTwqVOWSZ36Kjd7z427w4
Qo38mm7DNXSZTiQ6Tu/aKxO9ebEjse2FC4Egw0Z2eptITAaHLRuq0De8NKQi
H3KQWH+YBoNIvuyGpepFPKVu+uBRf8xEADw31F2PWZK0PtrTrnJ6TkF8MmgJ
Y4YOjr9JY8D3DMpDAbwCI4/7p/zWsvKDCB3WtytUmYCa7JmOPhlUJKaKncR/
IcC6vLCfLfi1d1SOlf1e1Cb5ksA2uePkxvVD/2vQP5ttzWXvl50K5uM7j7XI
YXbGU0hr08/kA4QMFabvCjaUuwAbKkCGsj47Ii8ZKioO9BwhOxOyDcrLJh7V
zkh6HpSZxa6EcBDuCoforH1j+NTmq/VBEHuz9tceFLTZVkUYLgzAYehnrSYO
ZDnWO5B0GcNx3bp+fcdxUePaAE1VICY5HxYz5nKBx8RB9p453wzBx0CyDUOL
mCiQcsMmcuQQE+VBb148qLbD1LtGnIJD7E5aBcNQt3fOT0AcPNMIEVMkZ8xZ
RbZHuaChh0morIiwjWUM/dLhX4MBMZ6Kk9q9vqgyjJfZgC0Lui7oE9ui1Wmq
B+6R2UlvGa5AP9IHYlSXRajt+HsBWt8cD4j5C77Wj1uHsxSi2IGa5ZLLNS4U
GdYFUoIByile87BJxOO/PnzWKpMk4rCkWQ81xlkB0nWqT5RdZna4tpwamHcn
GILxWrfEy+7ahc8hDfH94+Kv3wPbiW26itIunEFWi5fQdlcIub258Jm920ub
O7Rwzo6OkX1bR6tncOgkBNFOLgWi7aIOf4ZX/Xn71EMh5Czh9t7ZfOcjxJO0
dXfnOS7Mlcf0IDrVgvwUoRxjpw2XKFQo8m9fhQXa17VABbE3Y+0q6kBoxk3P
B6/UpmtOy/K97kKHkxBAAanp5M9uBEcdcVwkzRcp6CozFFRmQ+EEUk0rMbrB
Eiu7/pKB2RHEcwUaaAYqGPrKIv4oXFZki9caVufshu14VnRGO+YjOll8BjHA
5pMgg2OHJiNHK5y253Bd0CT4XBpvGgxN+/ObFDbnA7ZKw8SHuWY9OJ4BGtUo
qRH5+COtwnsHCaHEj7xOOHmXkMp5O7BbBHYKIwRYVKjBoIiEgpRBrkHgKCQ5
A/ChQxoztymO1Tdt8q5vtOxA+mUaPjitQCJ7+I35PJCkIM5LrH0ktDzfowr5
DtOE1UamK9dFNyRlcUkpIgRi5r6IjqcWaGtL1bc00dxXkvE3eBGkIrCRl04R
UiZNBFaM8ddL2LyqqAMYKJgsA0ahmoMdTn3GhdEsZYvq7T/xGgTdeGlqf0Dt
FKLep+RyYaQC2o74uHbgujrhzkcRsGuMf/v/b3zXfqixcIeiEnVQ2oMEXKoh
UfFYdWq7e4rOInbBbkrnq89+X213CwfkYYndiNsFjOgEkHCYFqqUoXDnd6+E
Hc6HYUESvf8mGRwN+MW3E0yzb9KPVhTDzXwD2UO4yMddESK0atGTsOSZrHRp
rWA6kW8Hat1oIt1DS2Osrh/Yn0uCenHSnTQ2GCS3Mdch3qRqe0s5dgyhgbc/
qvDuxS+QrVbnW2wPcLVM0RIXzFdE2DPQQFyv34UYaX0ldK2x/OmbvH0CuUvr
Ez2IafKNoIYaZdGpb8nkOmjZmhTX2l1OApHGEhi3eyVlQ311bUErurCdVTTb
XgSz7nw78GWChkVt6eS+kLs1Bv0yxNU0mdBv3j189ODHJ88ePWzjgVErOmZb
4lOy7grBbKM3gtpsu4Uo1/VC+rY/8K12OD4eylejBPYmCY2Iw2jtVwTMHNi+
LVARQaeNoFoR1xQTaSQWvMo+pOQ+9zs7Ao1+A5QRiRUG/0TXcOsbWJrnz3Di
ffm+kW8EkOXaJ8TZUKjh2Bt+vmNn4HPRRnCwmbAmPLsKM5q2FSUuc5+A4FD4
RYlOWpXkeVzMhmvoQNy4XQyfW4O99IHlx1rGXbSnPERAWK36lkq71lzUYDOK
itU4orixeyKh2kzaiUidJ/6OuhLu3CwMTFAPyBK0VxW7eeVnJSQmPUXazQVw
Z15jxQMqv0Cd0eRkJZQQhipu7LtfZS0YRtSsOH4Q+/l9n5pKLiVOOIAsCf2i
4vp1vQo8NaJZ56u0QrBmXxDkZ2iT4Qm2ZmIzjCfOJR/zROIaH2h6HHfgSbqw
3rYdepitspTKfrYb9n2gBoXRBTw4X4zECMhckdRztenW+BZa7YvPakBHNMaC
SQYOsIxkfyRixB6ShbMcw6bz2eBdheLqCAzFq5+0tbBJS/E6cqNkwFz6+MGD
Ry9ePXqoqFqkxLPkw4/4tvMcCuUoo39dmXz0OqcaBc5Tsu6F2IKXXz+j/22/
3IdMHOWEoh6b1p4kuDmTfkRS4NFsxbuH+cz2xQffHz/77tG7F49ePn1ycgKS
5nKfVms8SC/2u8F+XiHVsXu8rVBKaK11cBKTPqCXlktdfemBJFQlLkZpMa7F
qUsYOSfngj4t047C0wlVkUWaL4PG9kGf7EU2gZFprKAwAv3/+9FkRdfoYtao
isTh1h05LP0qKMUv1IgUDoWj9HMpmuKlS+F2pZRLmqanR2aWWgRyzgh26m7q
tuGWkscdFDlpg6fiLMg15u2jOD4YJ7PII1GrXHpKy7TDgAdP5TPAyUB6TeLL
LOk0O1fXaV3nEMoPaAURlHgi2L0vRLLEATlxmeoHWij6RoHaOysVdFRzLadd
7FDc1BbaqeXCarxYjHMpc+ioyHWsWdbaqRmzkKI/yKvim9lwTNVDSNFwaJNo
ESxj4rMTxT/FqLaB5tWSRGkDhDulYqW03bGEEt8sHbTpneUwxB9kVeGcYJS7
EIRUOwQ/ttWxsKdsp2sKude4vQYBn8GdLd+Hod7A03M1g0WK5w1la0nafMVl
n8qR6IwPrOsde+28T7SNISexY65UIJJ66VO0mXHQ+Q1Ua375iGh40FUu+3Lu
On1SCKL4/Q5eJl47Lc0PvGCS++Lr3Pjci1JMj7yatx2H414sRcS895GrvPY2
P7nLAoYlo256nOzUy9S7GVHqcmM8omXNidEjSK36xHMkRl/rixyRPqCpJzI1
g5bSjiRYbiXBwtK15nrE9GhxblTmNJvi3Bz+bGRIPo98SEoZMEFCkiOmWXOW
SUQ43A41F7VcUB08uuQFS/sIVbnP+W+xZuqu4+iGpxfQ2iXUUderjtoZ9Smj
Q+MzDAI5bFuu/bppcind1PVOwOfBX04ncv9KnShwPvwBWpGn5P/r9KI97SJk
hj3QyMFdMX2kMxkPWVNlUn9CHSM+Ux1TpJ+knZwXTGqP/iQn1k4G/pfrT6/6
GIb48iStmix8McUVflucWHSylU8E0ko5tprhW2LogtgVLtmf7OXQbTinjqar
cx04kMlDUvjZmdXH5ykJSc4hqNLnzvQaeZl0GN4kjhXugON3gXOBzmIQubYG
k4tldOq0Z4S6CEJ/vQjrVNMn/d8CaV3MXQfxP/DmRWIci7IlomVZbPJhVRB2
tlrQUKP1W1B9NeL1Tk360CnY1WwZAF8aNktpJ7deLvc5dOK+ce2mDSHfpC8a
BS5Fafbc22qujY+HnHaXU3pnWw35EDHFwEe9v9lCHOzpCwy8ikIPSiJRR3FM
5IhMMz/3sYcZH3ZroTykIQzRgiWOT56DDCChCU+bfcgTD7xNJU5U4OQrB/dF
1en4LFoUOXt3hOwuEnpHMcv+LDG8UxBHwshv8icK5CB9tk8kRx9ptyXY25Tg
DOuQpx6wVOgxhsL3pHmlNh4q+dcXidqej/ekgWMst15yobaKCelD0QnhdOfw
uQ2VWuv4DNndkd6yo3iilxbhf4AQ/yPEeFd6kB96WZbsQ7cq9igEq/wCpR86
OMj2SjbUFierxcqhtvV1gL7LCoGAE1O098b1QxWg6GvQMs4UUd1ApBQsmVDO
Ic8JRLfmN9A1mLht1LSN7wZVqdf+6yTQAyRIt2/z6otacFMQx8U2VNi6IQhZ
WPhOr13sxXHbQhxv2uCQ50WTJr+cwmR0PEwYASHVuakdPdDyrwRdLut+k9t6
pHAxkO/aI/dSs4wYQKMHZ4Djp75CuXBB3xkXHQiY9nomTT/l2TFRLn7qJm2X
fUtrCsrS+/eWNKD4gUBUFpeRjmNOJCo6Uuqy8U7YvQzuUziNK7FoQzdUfLi5
9T1EG4TbIhaq/aDCMkXLn10O87F70iR7SqQo6CDuKKI09iahvyGvvUQe7+EH
FIKVeBuHwC2tR2YnSZ/KAry7IWPEUoxW2D3hW9t2hshFdcom9I7v15zF2RTV
miFvcT4SiIqSJmcR27l1/RaljH0R6NYIZwg8uDdwWWWUB2NYzNKSgnc2XQ0l
kwtBO8if1jUIrhCgymod9V6R18W3Mnjw/Nmr4wdoaDx9/hOHmPrsLJ4QTLsq
2T/LQSWnLnucWOQbOitDrZAK6Tk1o5VmsIKb64yOcF/nVXoWpPPF9ELgx5Jf
wFYYWRRl5VJyhYo7mL53RWcGXyYWR9tFkK8ZpkI0mK9oX+Th2Z0L/H4bhXv1
4/RX7RQVpi/5brB4FCAzBE6m7fmmPX998uilbTjd18F3L5+/fnHRIQhiFG+9
qHEo+iMGYxFczQCUTjuUQUD+aK1fwOK6XtKK7jWTIV9q2kD+JqGiOwG/p/R0
Tm6Ij1fTQ6zJA95IrMYIw9Ft55zFYLVMsOU8EzBVvap88LosMlC4FFHinj5H
ks0GMhbUcPi0UHDPZekEc3PfCkm3NQjCuqAwELP3SAeVg1JqVRfWJhNKpsBs
RDQ9HxZesKBU2DDsq98jrxtwA8POFl4R2vcSIsY7xI1rgf9zcBjf5ZpXJyA6
Ml2aXId8WyHy1GYTd0D6vy0MHHd+/QRDyyU9JkoZYJ2PDXwf0QTFvs27zU5a
k2l5A/b1ZBMIHo3LitglSVLKI0g+LbuSo3qvO58i38iiT4Ic4TS4Urw7laGU
ZEuagsQMa0taT9u3xRy6jJpMd0IpjxtmxtyC5xRfFhqGq1AJVVfvGVI780IL
1aEyxfs6iecYlptLdnxweI4g6BkDOjhG5TL7z5Geine368+RXsPhV+MyY9lK
f5s5P72FeAT21w5s3Z1iHxUtD3yRntdD10kdpDzr8uL6BWW3ZlaawunLNcRm
oBjQXOqT0F9Llx7dYocdqBRuA94ghLg54GUFVGZkm6QVRrx1WjjU+MHmYSSG
xgWNs/JY0G+svAhsNez4km7ykQHzHfiM/1QA/6Tm5YiSucgA/xPPYUQNf9Jm
+edJInX9kRys31x/O/aGlBrkZLFrZoX6bZF2K0qElaS9sbvBlqlvBa5l1x7V
vunsYV6gJ8ADfvm3/67/wurUf0zCJgSR6qNCOWh4QJxPShnE0p41sfcP1ZU6
A8bc5LN67HvqaA4gl4qn7NWvWg3OtbNBAI/lkdR5cdSDUTdtK43qY0kCEnhT
Bzeb/4I7eVOdxa2PjiMkFONDsofZ/AjeBFJ9smAYam1s3wcF13cWXGnBLhfJ
jO4DTAtrK2Lt/3/9j/8pED8tmLYhIwkE+MedpUWoMDwI462x5V0vQSUcrei+
hCjcQ19Sw+7UtAkh22SMfnTv5OpJxrN5Y+BxcMew1f0IW90fyFawyu978u1H
f6ZEDonVS2SWx1Ea8aCadnB4d5EcksMQbbgDwczjBOWbknnSgWKOz5bSO7Dm
NmjnxPtiR5LWLO2GUhEqEH0ouxgvoIyJV3aGKFhiiI2PosOL+QrJ+MYOYlTk
5l0ygLhrUW8rnW2nv6QUZpmPIK7Dpn15+viY9AyYFCxdBwoAoqNmBZgEztUU
mAmckfutnejvbo377yWBB8YV7Zg2G91NHCtHlwjdMO3Biygdu++iVD29fP7i
8ZNnD+0ipqdYTEpLko7bO9sVDNk8PZOOkGYVYYJFwYWONIyX/pM/5fM/T/r6
FeycIY7QmWRTHnHRcX107ZpKICy5+XNHHF2jT9I8giNpQ030tWGIp4TVhY5u
WjI5ljJ60gKOhCdMpGZLWhT6ooEue3F2SayOGDtF4iVFJtsiDS2fd5EI62Nt
LE7H7vY4bJyT98tNlTXR7ksAWijLWaqhvu675AhBHsXDy9+7HDe3nkkCodn3
2b2EyYAkwakHn/jz0bf7qWAS5qnxsnID911ncJwwL0wQR36f3E/rfEYwK8Pe
khvu6+SSxOzAsLUTFn2IyoyLVNQiZvGpYnAazEN0ReZS1qguwZ6dp4pi2UtO
4yn0nNr7GUIYGD6VQFOM3Z1xRzPZqZUQvnufVsKbECombaWkdY0CbHBFU+aT
NfMOLCQECKPaydYcmBmynyr15taKPSah/UD+W5GuZLy0R/II5JqkxL+gO67w
BkHYmxdx5dJA1izPqVwvmAli9SDWYt/WYIvcxuJVuOM4jJQGo7uq2NYG+BRA
SprqoBthuau0GAFM7xHcRGDvBE8d3UjvmnIz6eiyOAibuXJ44gxDN3UX5zFQ
vDsMC/c9UjNFcO0V4TjKPil+sQCnI71Ihl8ovoVGd0vwvp1AryOnGvYxcNyP
mIHnHro+ysRgzY0lsl4WgemlTB+QHR6Leg8Sct4ECMifAYA8z1CeVZ7xxJDG
XjUO7zm1IAnRkoWl915yi0vxUJzUrYy2hZBMo8QgyVSAFWfR9r7FHZTn7+RM
38G/yQ//DichWS4XPifY0tY/orAWEtJpBc6TFbOiqUrK0trV9DqOMP6cTY9h
4wj4QPB6W6fPewy8AEnGoxuVghLEkV6ePEIVeS91361CcBN4rkEYk6CfGSsp
uO+YIMYH8rW0IOpSeQtr2hwhHuI6bKrUWqqAVszLEAfI1lFlPIMA0VXqhPlc
A0To5nyjqfezZZ590EufkjpfjurtFD1sYm58/+rpj0wfgp7CHDRIrxfmKm1g
COYNX4w4oiASaJ8GorKhcdihZ7GYOBD3xArzslsw1yFitQmrTt65AHhEyAnW
OAQtQB7UOrz74m/qEOIYZqC/+9WPnEzIt+gM+KJEn1ugRTKgHpolXcNAMEZt
7a4uq7jj/7/WlAbAN24+NhN2Axo7EogKFa+sFtXeXiSPG8pLjIFxamrH1pck
cSJPDsajYNxxQSUV0pBYUl9SLDn8msf3/MFTuc2+cQIe5Yq9H8bfnqOemdwY
X3dfpqFd8Q59BV9ymgzHX8l8rr3nm1AzqoyyO8DyC9FDJf1c+hAiSF8QzdRz
42qIeH312D0rA2BreZ0CmMzxEtJpPpQrcvNbPygKBb+iK65YeeicVd5RRFxg
n22u6CUdUA6D6ev4hTqCizqjslbm64vRjWo1poqNOgydZkJFt8a3xjdQafTN
ruJ0x6hMnAzxZPJxdHZ2NsKDGW2rFXaWnWfzCTGVIc4HIXkK5/v4yDczwxv+
E5MRvic4tnhPBn/GFN1HR8mV/34lodjtWQVXltKkYBkwweTuV/duOEcCtb0P
uIfXDseH7nu4YthYtJXR5UIEkqMQe/la73rs+Yf5KcKkIM2Pbty+883R3cP3
D4rV89uvf7m2/o+7r083H+//XPzt8O53v9z8efnbD8XDX5+/+nDy4dfp8uyb
Ixvmx6w4bZZHyd3rzsCmRk+KzRaHzk8Pv7k6+Jats0Ey+JaZMkwnh58EmHY0
p5kMkv8O7Nh+uaJxBwdfS3rHN4df3bx+9/D2jevXv8YHCQvrm4G1vgm25Av4
2+Hg63R1+s0gm9+4ffvw3uDrJoWfgDMN/DRlgkfTpzfqn26kt8qndzc/z279
9W517z+md6d//Sq98eH7w/cv7318df38h5vbR7fOnt9e/XRn+h84gcPZixvV
s5t/e3ireXl7+QC2hJOM39HJd/nAvzFY1DuYdd+k/w2f+QYHXp+/Y8FLr7k/
XfNU9WfNVmMiVuIVb6wYVcUOWDVnGDCWbKwzmnjzte6/12H3Ngl1o7xh/CmE
KGPTd85ILNJkiz8C854EOGVS20eJGtEuWdtFjblJ0kN//YRwhD2xnbGiX2gC
ogIJ0ZcN78AFwI+KMCAN7IlxGNzApHumk4C3D50gAXrMSlZwBChAGauCoD6J
0qITbm+Sz00/IC4iHo6NZR20BPbOhMLryfO/cGiDpdOIPIo5TpYAhwRXqBUb
lh0nFgT0jLDciEo+CBVzxCO/u7g5v7m4cWe0OMzujG5Nb301upfdzEb30sWd
2fX5rXR+d0pRzgG9QlcC37tP4pr/IhrtuxxHvHn9uvsHf68FAU4E37IM8poj
6JRpLioAkA6RMNi4tA9FydIPT7huqu2MHDsfcq4x96n9fbo7q7mGtMlJgd36
8sixKtqZqRLe8ApSslxPlxCp8QLl+eHxT9rsZeJ3R00TLLZF05dvDk8Rbl1G
NZk53R4gglrS6ETPDnaMzxb1VLI0uTgwXWdJSza3BZAHYN0QI4Z/L1htz1zr
XJYE10dW1lCym1Fvl2rA1sOSGVs4skaDlhw2sXVaFFoA+qiq4Brq7an7ro94
xfruiSbeIoSsMchbQHO+OIdDJcHdiFC6Cq/jJRlNhXizMQm9LEDW+FekdZnO
O5nhINlB3y8w85QSBfzAHPebtIbA+gL9FbPuydDZb4gT4SPbwmPE6nNc2r0t
DJb1nZdVE95hj636ipJq6OJZRlvKWQoU0OZgey2OibKIKpt80yswuzAZBx2U
/G/Dku27eoTGaD47xAz/kJdhZq4Lv9I6XrZ6ySvFfBPjcxK2LRCuh77vwu93
PCf7v65rdK3IWORQRS1Z5AqjpZymM22gO+Y0AYVUbAuzfcFYTCdO2l6Wbry3
Y1jq6J/QunWoR9VdpiZGcAqM8YDYyBUMSov2f/paA6d0dyWGVyzOtL4oaLga
SyxqzSEA3PJpXGkTxmiH5sDfORuOIQTgoBa1w0/qtDhe378XmCK0byM+penu
vmCv9zUkSWI8MQz8xsfNN9t0vijQy1TN2Uck80ait2mj6AXvpR8M080oOPo7
dyEAdE0ue/Ic85cbGM2TRtG5BrdXKkE6dh08tVrB1CqK/7JPCrNq4KMjqqXY
NnDumeYBnfD9sTQiY0dHGEZiy/XYWqJ3+wsEi+yP8l985lwoZF+7b1/r1eoD
IGhEPeunMxIfOzovHi8aLmsgYx1Hv3+F8zz6j1S7NQ9hH2IYtH09nvczP5jG
fc268mkkPInYPQ+UeYwhoHjLlO1QQzAps1xmSae7X3+mCLO75wayqlOg48HL
g3fnEufvNA/kDz5/Y5u+peuOrJ+6pOaOKN1Tf8WtimEXCfyMO3efs768H9Mz
Tk02EHyxIN2kk2nSezzMyAXPoIe77E5JCbhVTAjMln8MGASXBVt6z4j2ecUZ
ntHh/Q5+NO6eB7/Ye93oHO4nVBLCcygXybIEY5ITw4jDIAry1vJFfeqlYPhm
VN+Q3BchdtxHBF1pwVmy3PjM4xBHfJQI9L5/BEe/SCYsNJ9XUMhQFhzX52sw
u2EtSVWuMlO6oq3Wi9DHkHazGNq/vOlXC9mXzJvnZyyd/zC4toNZKpkfG5nT
cyJRW9gOZxiz9yc+lE3rnsG+RRxzzRlIx50X7z4pIZpAsEucS0JQL+ODzQgv
DQ0TK65IEI3l3yv6Sy8VYkqQNJyrG6yXpApKdrLzoOSHSBsywoGjBC9zWKAH
CNiRmZU8AsUaqWPDqRnY4gbDVTj3csYtugWTaYCP/zf4b2Aueoe/krI+w3XV
uJuBL3NJitSycI5eNma3+M/ZajX6C8ECYJhOfUKWfNtWHsRm13yqLhTTIB6x
HjgPiex9B3icSG58tXEf7t45vP32AJQNnEa9XSzyj0fuCLZg7dwDPm6LUVb4
lyePXj127kTSQwTIVVZ8tT7AR3S/kqvRfhzAa9SsA5/BqtO0wGxF91JS0wMU
Y3zi2bVj2qofTh5ImQm37FKcqY5+RZ0E921Ra6TLbtG927dv0hZR6Q3mB8sO
Sfo/Ru6km9trdJHiX4Es1wh5f5IjYuJPwDxlVYfj67DXBVBz+Ftaq2z3g57t
fql9GvF+PaQajo3u07FVZrTBvjG8kVqPKNyt2BVRU0/DUTKQhwbJ1RPK0B+a
vnlwRO/hSAI/gOmjUvYgdqSgqg4wRPSthlMGkjNk4RWuuuF0day15ndhYBOM
tWT105SkZgimdL8sEb9zaCUuMKefxXYXNiE5Prl1YGDu1cXDV+hJ9E5QW7Yj
5Fa1tBsasF4RbEPwye8JmNR/gptJ1NgTD8vvpVcopvgGdPYIeETyE9Wge6gH
zjGOqtjl+2A4ZKsdn4/LeuhJS/vh5cpJ45niNPQWDpM3b69+8WstVSEjwqYd
6WQOxq1L9sInvv8RN80P98nX7YVmuOqVy7NmgbGNI3/30HVnz1HICp7j7Xvj
n3obPPSA8RfxuQfU7uf/7OUFgUvVYsFdzbT+25cB4f6/z87Zj5dW07zBfkYu
zKSt1fM7kO6J2C70rKzeDw7MlSNoCAxA4rdHW3NzEwALWeAbu5jv+AIi8+UT
uyktuBx/CKnheK5z2f5IWpPQmXMdIvoXkIrslPjtcU3Y/jhm8x2mRKcEZ7Xr
nDLYsxGTBSbAxGe167BO/INwfVDDIigUw+oLBuJqtX2bOXBXdTdpLw/I7UkJ
h4Q2TCqXndUQ1sMh+ZvjrzDhH7sEO22BLDRhnW849itY3Yz6kCbRUeHVg6Ma
uqJMotNiFRtPReE/O8dGOTD0JadfEr89cON//yb6r/Xjvv/+HV//z2DD6Uej
jGsBWSQ9//3nH/L1nBsmyZBW6BiQFuXuIenJo2QL8df/cxT91/px33/8uhiG
e78+1TJ1tgb4jT/m65LUwqzHfx2uGEakFRlNwsiUFxPs/Od8HUkHWeRz7BH+
ADMzMOq+xNxVjSgrn0y+w3JJuX0e0zPs4idhMruJUmCZN5hsOPDfcPSNq3CU
B8GXQHq0grkyEN6zWEgEDe+oly0D5I+pbTpuHHbowyz6xuoPguEY7o0zhxkC
i2GtZNKKZcGTh38MYsvjpeipAzLq7h7euKPZCHBNKFMBvvzoI/J29dJbb5S0
8S0nOHUK+Flgr2huKVEddm+m3pKoRlqEpo4mw2IWWw01zkzz+ZYzaCgJ1LAe
6GPCZPESWdSjbePsO2CSf923B63twz4KLYrqnDZvsGZL2vtA65jcR4NEjTJU
lQiDrIOwunPgq0/TvZhAF0ACIfLFm9bzEebEgRT1yxyoxbn/NlGTnGzPLGHh
DFIVRuu4GPaNdG1KLlkQ20Xcmziz2lPKLkviLdxybYmUmfv3pBuIi5CTvjaf
ZNDWBVe9D24JN8+mT4aBUhY//IKuHSjMvXcqsStFb4qsSx5cJOv2i5vOw07k
W0DC8PMeKRcIw50S73fNgdBeg88YfEj8B/7jq8jVI6JDcnKDEfg31wL0uv0j
xA/iCB69jYhoZETUO8Jn7oOIIGZKLwyP6hP5kb3YYUUseNylWNEju7vGh1Jf
d231j3jjme1SLCBq0TjY+JmI7yO66ZS18qk3PSktXczGt+E/l99RByJbG+ee
D16WK2BqKP3QgT6QtPIBR67QvvMxN+28GzbXDlzJ5BqHyfsmoh4RRZyMAUvn
DIeks0pKhYPZaMXTQDyHFJ/cEk4WFgzQNJ1M0549GHaXpX8b9iyF2qL1JiJ0
FkM+dSwi9UhqAfqrY6ua4V9jVmxAGfwjKhw4YNESB3ysLzjXtxYq4dOUBODA
3DXS/9cx3uBC72BxZucaKy2ZtV2KqV48Pp91wCYp4rOb3cW0Ab/w/9r1PNYN
fcr4QWXexePXwJEiNn/B+PC8DU6/2Dv+J+1nxIqZ8n6Xchi8+lmaYS87Zthp
ujS7WLChVv2BypZnwcH4A+dVzs/D8IyPTp1OtQ/kk69bkM1ofwYB+wBdjWwd
F1kHtUDM8Vhh17rgTbN3PO9ApXLgoX/DD0WYwcPEXiP/GOws7uro6Y8nb/9F
HGgHT/AEeAkus2OM0Mzuv4lsIe5+4oKv9Nw25fO/78Lp25915xRzqWPpOb5Q
w+4VZ3NohxqWExIUXl6aSeg9jiuc7R4OY3qMLMKznEupMPqjmGs0E0PFa+ps
tTgKrLBkmlMyCKiyKXoWFlt0nq3ht6nWZUeSeRiRexpjzQZiXpqC2JFLe2HO
n8PEAwEA5q3sTvyzTFRNRwhXguYgQkRqsx3hARheJ7hWBZbyEd/oMFAfoYg3
5qMw2hxQBspuJLWcN1tb99LDkpKujTf0CHBRBJq3LQwE+evWmea1BOu4VAI2
x8nmYG1ZXhRUiXFWABt5RDqjZpAzXUamG5KkJ0elRk+JsEer7bqotSsARrTO
WyIjBlzq83AMXQ/do6d5h/URtogkOhwSuXR9RDSr0EPErirhWfPY4eM+gcBa
N0PU85BiAlxyBOajuybcOOo6LBD+EtLBihlU0z1qfaCtGwi69LCUah+TEcHX
JbRE9e4gI8i9R968Zsh9gPRbDxCPs87TAm/ffDuTBXLSEhK2ZzXSKgJzvbhh
OjOd2DvPm0NfskV1v+FJYuy+L88yQtPLtQKVSmZBzT/HshUy1qW90zCwGOnu
kQSfZs6zH3a+wNmnecsq4FSVWboCrQOIU/rchSLXUdvzLcWWpWAD7zLMf/Xw
+CckyB+eHr/gDaQ/gLqImX2foh2EZxSSSFlQ6QblrjVSICnXaRQcsa2estHY
IRxaPmBbeQ77dcIdthCWWP2X63Jul0EHu8LI2aELlxUVr6d0aasdu0Ouk563
9JQnC/j4OkMmb9AhvFHnFO4ybP34WGrbXnLZYlWlssspg/qR0/mcUrjmJS5Q
w4JYKIWXzUpy/w/5yfodNZf0lkUqlnfbhIbMp/rMPmk+bc9ZpK6xjfe/i/u2
5TayK8v3/IoMOqJN2gAoXiRRrLHHFC8SJVJSkVKpXAwOmQCSYBaBTDoTIAV1
+aV/ZKIf5mF+oB8m5q3C/zV77b3PLZHgReXuYYRdApB57mefffZlrZbexVo8
S/PsZ7VyAqXuMeXU7HDf3J5aOd/Wnn/KOAcK6iwn8mOV1CZWZU9Rjayt7je4
DSIv5mDe7bAOS+z7Ddi1HQV4y5XiyvK7y4EjYMHdDherNA29BtWM28BQNSwc
w9puqrVZcUESUtAE1gaE9Mdj5wsJgBS+X4FwOy5m+Q6mbxO2vuAg6xcsX5xS
RDeQhgfjUzkQ/Zo3hpq74GzLC+ozEZY17weqU7VDLn2GKei8gew9iepE77HP
F20zYYQkaH/szhbxIzrEYDqWEVJZXWbXGgITMPvYAW0cRZkYcxNwWNk4EH6T
em/yViIzQ0lNQ/Xg7AwS94Jg7M5M4H+dKfAeATNPks/IBSv7eJ/Etb+HmQ2/
sS0hMXVYqZ5/YVsaZXi4NptKafk+ljtLMdy2v60tM2S4jyylxp32jW0JdnLw
+PaMs2p+KT4QdX1hGBzw+0sJ4NW/uZQaUPc3lfJPWLvBSb2b98qpuDGPe5fp
6PEn9WwJ/39O6tS2o1NxO/5ZLv7/CqH4IDsl9+pxFsuHlMv4RYPrB1kx3bMP
t2c+yLKJuLlJmUkAbJANASyJSwYaPCz66VC0orF8M8I3Bpmcl8E+gyAwrIb3
hKEVgE7BkThrT5+unsppn1QA0KucOWU2SXHGtQcQjXFGe1YCHQUuCJvB5qBw
MJ/AZaZ82QRmH6yXEoeRlVHSH2W5LqkbhX+8SHowSwBeKhZjGl93p7T3Rkx8
nTEsL0JtW5GDgKjEjOXzmY6LEmgoYtMprZXHUF0YVbTqRNu2bRyQIiiwgSPD
4zLJ8osycfgSNOvFZIzpEqWGj+BCYSQDAwL8xjkSdpLelUTby7izSOHBYjNB
haHQhA7TZoQ7T3Jr07oETMLQopoWXY7Lb8XdYdG7akmizJRxH9Jy3BJbrJgI
yuSCmoMJODiOmM1SzIpwvrbmoMhUJkNA1CS6umr8WOSvqYYO2ywkUbliWpOI
drZDUBsQ7oqaT3UtmXRhHoWshEmjZcfGMIBGQurAbsBRMlSYLSHOSa8FG80a
mKRzFQ8KUDGGJuPTW0owKrl2tT0AwMqBDwjsrY3zpqmEbR5KLq9By10mmify
k5HMiKQuY6wr0+40HjDQlqA3jKeRApnBkVVaVcGuMC60tmkEf6cT7dfM2Fj2
6RdFE8dNyMPSlFxBnXpjwmxFKbJ7SIgqPUaA1OP4rRh7ggsxg5oB+0k2YKTL
I/aHk+QV0+TBGJgHzAj2mgEj/FTZ9MCuxPYej0eCZiSiJctLfu4qZVgNi/6X
ObY8mbbITKQLlwRIaB40VqZJoQxtNKuJGaz8eWaTXEmjBBOlTXec8HWsb22n
2BTJRepdMCOEw1BFfRc/RZ+QEdbyEM5E5qquaMOkLUUE4uMjA5Kpy5K2A1bT
JHei6noiJts8lVXQhVjO+1jLAZehTHllDiCFiUWgC+0omngwU2Np5i6wUmhQ
ON/yYiL3SAUYrV36ijJyKxmNwUsub5FW6WXC20LEQ8uAxkt+TWkEeYQkpF5m
SSbt8lNQ5sEkYXLK1AR/asK0sCBbsvmI2y1trnjkMgYPr+8fBbHPsRRpkDlM
Fldt2uoe4RqgeApe/BaKnTMK9W5dZV/BsQS0A3oCL+iH6G+TYpzooQViCslm
nOrvAi3Bsb0iPOFjwiJXYCnML2sBpZxvFVqJPauuSMTNCvNXbPD02I0/eyQd
4pyl3VeUYxo8kJGlZvUbqZ+wERgHo9kOvIF4rypCocIY1twJMBPHF6luT+P1
crQrwym72FCQEGRF6kcNAYV9jA4rS7CgTcqJH3QeMDUrPJcZJL85Ub05PGhn
tJbObOgmM01XmVVEilKo37xhiLj16rvCWYeEiFYQcI/V7pVYkyks7COwT/NS
YDXA6wNWQa7HreRZeORycWGVLpOYZ7isxPkq3ktEwxckTo9lrZshmN+wJDIC
xDkLjKKQxD1459z5MJ6agsxL4yKyPlU4kSuefjYWTeAzURBLOFDYSWIEvz1f
GX6bJXfkYLrNTpV7G6ORZoMoEry3o93t94eHu+92wBYlSOaa8esO/AV9ZyG2
qHiArIqCYHN/NE3MnX6aFhM9UJVjoavubqXE62Lj5ACHYVmBxzWdhRQ3SUNg
L5iJGYgrd3QlRgUT7j8BNmCVXg8qB3zB6vucI5BucehkWzvddjVoZpcPfmDA
fiu5TmgGuPOIGhWML1qBzYnXYVgGYMt5JlVoiPsUGebIi69ikwPugVjYQPua
A95TZbAUPOAeAahXdle2JPrAsAoFq2BninDlYc5uDYfxeQ3q7NwB3hrQM8Zr
U3gu9lgJGDR0mwB0kafADT3DGzh8WBe8+UEOs1ZUjzPA/d0ghWA5cYHaeoy/
1AvFWhiWAcI4uRaEh8TCdfsNF7C2pIKic5EZbDw5/tGTYTEYQM2/Rv5UJcBu
7I8V5dpAyzGV5cwwTHLWDqDZyPVDz6JP7sZl76+BTaAycL/B1YCkvxit56pz
3i4FRlv0Oe3GbznBklr85vNbqm4sTz1/uvL8VPaiQJzGexJ2ITlpa09ONQnN
6je94IIttxe4x2sOXz7vA3lmVJoLRQoOlqpRskzpUmjdizwuBuy22OQQG+m2
3ah8ncwFHJiFImlE40t8jPS0ovOVk+4Mx7FjS4DewMLMjDHdkWVUUDyL3eg8
xII9V/uQ7trKaa30nwEPFbeGlShgBUnIsW0tYzXJkLPHFzZ3Tr0ylwTeh7QL
r3mBAK4ws2vCgIEuVksacENjp+ial1nZ51u7CdfIqOSbgjH74zIbXDKmPt21
py0WC9KQyuB+c4AH65JyZpYWz4YvwjpAOKcj8AHTfTGbjBx1b1lMkyGubFaa
4XRoGdFuqFs9Xu6IE6CYG73FoMumKX2tEeDR1KDKKFdGu6P3h7Thsb9lNFqY
Q0lv5LB5mljpScEmCdJBlFDKQTF0hGRPbWBiL3onP96kwQ8nMEJufdg/jRdO
6vZIqwmFG5XaqC/p2XC6GBks8F61VpSDzoCGbdLtZMUyogToyeV+0as6l+PR
8L93aVB6l3/qkwAaFtf/AibXP+lT/wIl5k9SxtICdeIExtb2zv6r3eOP7a2D
V6eMDUIn98nrhBq4NRxA37gciTLBciPY717Lbm9vO1mSJ0hpXRb4Dz49l/l8
lCXbvqRS28lw0Phl5wva77XreP9VrVHBCeA178HtmDmn53wtbfmd/Yz2aV3S
QJJzqysrL07jl2XSz2ENOe5QC0lcCvS7BUin2aRnWXHeVz9qdOTRlB1gnqgD
pv24iwICEtYakyKM2V1Gg5bLix6qXVpoRYdJSdeUlRcvnmt71l5sPKP2wBJZ
Vu2DlI6Vj52WzBTf7I464rZLKrb7teKDTrRw8inPGNLfXn33neduke7IS5vx
q5SKzHrx8ZS20JfoEY1Fm6ix8Zskp8viFKC5T6W168/WN07jNySuL6oKe4/H
DzLqJalsK89a/N+1VYX1oX8/W493qL5oFyDb1KHHDBpqQzvek2LeTcuI2vFM
h239xQo1ZGdSVSnALzAq8WHHrLZdMRAWCnmPI3HHiZpIKa5UwdY0afp4T9Ns
s6juZUzmmwnpsdQoM5eCivyaNDlq0E4nXmQSIxkfh5IaEGzFe/BrQHJ5u+HO
2lGJNyhU/8qqqX9jjQZlj44Ikq7vaBW9HWIYaJre0IfXpKkAnf4jhumQZG/C
foEQAKdSg4rvwTBcA9V9a8g2kdoRrp+VNW0i6SBPsYByXDUOqVXYiUMcwGji
cXKVjSZlIq1fOGHQWcyeg+pefPP5eOkRawgVoi2HCbfjqWvH86AdXmUQB1TN
26X7pqRWz/Pmejbm1eMJaqpu67HVbTRUt/FkbbW2P2lrZJPqJkkwrPvcgt0+
3zba2xO6seFsyMbJMGoQ0fHibn/n+HEtQxNqk2/2Bzu6SMsZj9E0jMZBmnWp
WS9Fxr1DsKRZoa8mGexkudyJo8+luRI3IWFZLAUV3I9qMLWKGyy72Wvt8/VT
r4ULJ1ujbjaYsLZ3EX+6JrWGeU1uqviguNUP0oAY8j7CQvqMc+WB+wY1epNq
GwJgK1wtMQCXyaglks6HyZp/GlQRjoPqMVsG9XnNeCGteLGy8uQ0OJda9Tap
LbZ3eZViP6s0jo4NXewj2oDaPBG7akQc33ToYOldjQCktEWNOILZoOQK2cxw
XZT5tOWdBnppinwDgGnIuABj78xMoBoMwV7aLXUVr66bJuCmBL/uMJNRoDP9
tgDH3g7vrnm61v19poLnV/p07TQ+HpNKnadXUu9BcXFBOnThBItCnACMh++C
R2nA4UOr1oCg4Ex+XNueri2ZJbG6vqCt2ni2Hkg3amCKBJ733KA9cCC0j02w
fk0zjVgQvpdk02Nz9aIZ9MIEFt+8P96VuKXtl++Pak9H9ae38fRjVhm1H6vM
naWrRpLSGf8EC63kvmG4X14m5SC5wbJ7y1IVkZIquT7z/G93aEHGWHbTbpn1
ow8Ms8DniWvlozbBBm8Cf0Gsijlh31xr6jcX47HmjViUQ5Jdu9LGt4Uwt7/k
JobiNTbiFbLrY/plHCFGQ80AUShrH6NIUkuwol9uf4ifr2I3D1mbZG0A15v9
DxBscK/oeVCQugE7Tit+1TFK5OCym+SZ7ujadYwxrwaKvWHChR/Qwn6ZXIzb
+IpJmTJXSttc8FjF+wxHbMZK0ADYKS0bNtDeQRGmI4j5fmRP9iwKHSOgVJFe
If3LptjQRIDhXwfJFGRUOjGP7+doWLUt+l2bAzOqB/cTR9HzF7S0Pidj1iSx
DbYmdMbcJsM+1hnJrqQs06EI5s+TVvx9R+6leR/uxOgAxHUHvOqoMjWyQC6F
takW+tiDnBrnHeSrTwQ4c4tJwLIv8dZmfAgmv/ZFAks/K+Lq6sXqiZjB9C6M
eB9g+Fy9wMrlmI0jF3CrXlDBkhprZjpn2Fhg4sO9rYD3GnGucFNENdrLOn4q
bF3NRDQBeL9hToPxlElpQut43XOEmsWC3VLu4nETrwebUBltV/JJLHHKLAMI
+3hx3g41tUM4lKnbFiTRQoAwgKDHWuyxvKnlju5s1mQ83+nVMtlkTVyZQCW2
ZqpEOUFiXQk1fxOsvCYeQSZswEbj0lqM2cEi8FviOGNMVHYAwjhnXawN9J2G
ao3WRkS1S8qNCSnAo7Wl0dKhA+JRE0cYDHyeT0odjna4ZipmP6k3JXCFFgzU
H4kjbzK6r92yBpoaqwnHtj0j3d6mUUNEQaQ3GX5mioDQYhwJgQb32njAjb/I
y1ayJLnXpZLIwLEhy4hqHUemxrSJA866xZVBr9ljC0eN+BclVMny0gZmPzFO
Gwa8Khtlw0RpK5GI2cuwVCDJnaiu5MsRfdnJiqXYO3psYtnJPjtGTxd/Jx5S
ht1e8sWPMiyk9DN0W7EfW0n3chOWfy8MxN3tdhW7X70NiXmFaWKsTiFKBusv
7C5WPwIHInlxKeIMdDgXvD/ZNkd7P8Bjv9aiKiZjFPwpCU4zUZnqUbOpnZxO
5XktZD1+OjqIZhmMz3++vao+gazUxnGiGuddspEGkk/xeL8g6Idey0aPGP1K
FqItl3EYLfmj0D36JGbLdPouo5XnPnsUBmBhMz5h1NN/jSRGcuFqPAVNzvu3
HxZa5rteeYPvdpW0zX6fDAeN319lfXw/2xChgLPPfcFTW1/T4/GHrf737Ztu
9qz75ocvve9/fvlhb3X/+cXOT33639mPP629Wd/6Wi3wi3+n/z+dR0tFC8dq
87HSJcaLx9ySpSh6xaAlyV1oT8bbeBdxIFMC8qgqcm6NDrCJSe4ORkA0fj4B
4PKnr+vPexc7K6/f9w8/7v+t9/nn/sZ6dnjw/frghzf97ec/7W1tX6z8kP3t
UwMB4NPVlUjmm5v6mUQzRn2UlFn6l6Z2Cg0Y439hDmlHdKbJaChfezk19OPz
3pON9dXVZ+3+i2SlvQLSsS7ox2jInvRerK320icy2wvFbZ4y/VLKztMs/8vs
4pAn5fsHPcqF0jZDIOU7be/WsIv841191y/zQU9aEIxNBafgr4McIPoF+XV2
QCRJeFO3kB25EbQ9XesGYmjT7TNwLc6ML//i8yHgkcuLbHJ5W5Rfb/NJ+WKj
v3b7c3Z7WboXnIeL9/MCklcZtRaMHgundtP8nTZNA22h8xR22YZUafLyhKMS
A85yawT57ayaln5yU6hIAxLKzdgIs6YV6m28qM5W+c37ps5wKTtn4S/On8OE
hBjhfx515sbTJ8+ePA2pM+dJzbnEmbUphfgTZYGnU7QVX39RcR0vWpvtEuZW
UsTT0HnccgwsSb8fX9LKEi2GJKanqNHdg9Os6bBjRO1o8RwcnueCGLvEYdQm
Cvc7idfxnekkjK44KIKfzwca74izns5hZiGy3fU4K811AegKXuy4LTriAUi6
dAr/9vX6nyie/7MJWv8pq2yGnnX3Ovmy/uPe3266Zbnz9ftPW8m74R8nu9tJ
tfu2u1UOvm5sDXevfqyub/764+rF8dX3e8NtbkDy4/7op/yvnzZebGyvjp/s
90fdvcufjza6V++eXP402B78icapvqjpOvMNipPVaXNrrwrDtCyFlIu9NEPC
usQPHHcm2oRTYxePVCotiQR1pQehHUFVHNxo1ctvjA+T24PFiY1c++vM3LR9
NGYOrOk53ZY53UKCo5yGs9KBu5LpA03oCgfFKGGsEgKQjivr5dym9/Ko0rli
Imq7RX8KuqW9dNyrR1cFeipecjzlpsK2VPjn5c4tHAsItcwh5s81VFdAcPjd
UNuea6yYezFAId7dAOGndHl2xUKaiN3aAOzKXAvmAXUKQOVxPJPQ3BLYdy/Z
4sRSNwqBy468TBPc1x9AVqZFLoH4yI2ed0lxs0D3D4Xdo8VqWwzanoOiZ5Ld
JnkG/lUnYMHsOzXh9I2CVBko+PeaMDpXmd9C18t0kIguAJk8I/SpiEW2R4jw
X4qeutV1znLnXK8qcyrhyb7IFL2E3kCRtLN6l7b5VygkwM1xDlWzzqJnHdy8
jRJTO2/4ULBDatavRbfn5VGMqCDetsNMg/QbGp1UwY522lH0vKOSo1a3xz5r
vZzUb5ssIH2k33iVSjcLpdbCLVipCcwJ7g7w2uLj7BYUYWPxPO+HTPY3iB+R
iBI0Zvqh8FxRtGfBqzUHkp8Sv08wCLKrOHUsGVYciHeRlSObO5n11cfp5Xu3
wrGW5J0fPFnrx8f8hujbrSp292tr0bMwXBWUCbCdcaakeIQZC6YS6yVbEsC0
xDcTtvxJ8HsiUPyTfOym2QSiG+MCTc8gM8MVmUT/wLKyvTkbKY70D47Eg35K
AzcbSs64yQhgZV5EDdG2EeXGIB/xfQX6oTOxyNK5SHoQlUa+7LuweUvl7eUw
RWKybjGufZIX+XSEvBQJlH21+xEQD3oMvfl87JIxbXyGBrFHZtFglK889u5R
0k896PDi4oLVNoN5ZCaLkQaSvuBxFWrkMUtUzD10/v2B07f3j3Z3NuNzF0h/
HrepmZchVwxH+hk82CFnHHCEaRTb4ZK+W2702ckK6tNAeqmM/ZGC60jFGiYR
zteRXW2rBefIRTBL1t7qIcgzd4tCm20yLY5X86Qccq20LLtVMUQ0Js4WBWCY
eqIwzO/aF2SvTf6lbaE2JI950yRl2uMdNGZ6SV3kgZMgaTrcSnZrLMmjeLJW
IouHRS0vUbajkuMvPhiSjiV9B24GBykBXuG+kBLFjOCrDxl7v3uSD4LrhIZO
xeo5axxL896AOQBWylZMWxOIfuBoK5MBlm99gPvO1jB3LXE9Zj25YY7USOqb
6nRROyODB2S5GS9AKfTMvW7dGfODrjRr7XP2PrZEDNnMoJPGWLwy4XWLi77Q
Dw0pnkl2ZUGf+nvrW+qhc3dzfX197WGVrT6wMqpr5cVqZ+XZRmels7K58WTj
ycMqWLMV8H9hSPm7NfqwvMOEWCvoMV0HF+QBe6rgh06nszDPXOlLd1o3GmHA
yeAV27uti6Ioza7HemcCPwi9qSRkA+Gs8F4WmnfVY2EzPjP0Gy+L4uoMQvhM
ozHwgX4XsS6/GIZE+cS20rMWxzvQx080aWf1mwgpg8kA5hHJ5LYR2XS8DxMo
QpFkSOfCUpjYfIYSpHWwXF1m1xUf80k8QHSA8EG63msmg98NHqAzhSqUBgs1
48WF5vZyY6szFnT6YpdejBF4Y5KlIMEtmY5x+iCd0SRVIN1CGCxYzRUcwWXk
PKaIpzXIaAbulhTPCfMTs5pHE9KdOrcmT6Dpg8poNl9U4lBQ1J0ZFnS4n0PF
tUqHLqsAX5w5Nml2PJ6hzbQCOAze+HdCu7dCN/ljGqvjEbcx5rZjlJ6hV5dS
HhlyLUhF9o+qOo4OmludnBi8yStD/6OsWp7jCtE4JBwlxsCx4wUrw+Qwak5d
0iuLCjeQCw4+GfMkWhebWdk08eqpEs4ZVQOC7o4vS06DdJpNxAmByEz3+Guk
JzYDg/Ed6R7GUCjwu7qUcJpBEpfUs6+ikzheYlrtrndmFMXAxjAh7EG0hQwQ
QA2dS3dmddaRA+GPM4w3f4x+icNeAV/jl7j+h+/aMeumm/EnwdD4xS+kbZtF
B8UpADPsmw21uh/NP2ZqDH40bInej7HpZeUee9Lp/GFOGTfx7N9Nc9Nmvvyj
DIgJQTMN5i91hO/qakN5Fp/GcfNBoTw74xE+O9v0IE906fGg314WmIQqDmgQ
IZf4bTMFKGDL6IOm2UYvVPmkey4og5t05G8etIokZbBCxNBaBTDALCw7DQ/b
mfualoV93OyypjfcglaIBQ4VsNNtRlxkuhYUbdlu2qMLW81tGsZ98eVCkFWs
WznypJAwk9tZVyucHbvgUORjoq8SI1LraYN8MJnvGAfccWpiwnWCxiBieTkp
q9TlEiECgsdPUGVDwla9YIplwqDlMnaGhUTLLji6JzFMWmiDlREzcutOmVHf
DnOea0tNO8nYYPfgO+AYDGuyha9Ite+sTdH7jlHddtxzTfXqj//DSQYPP7g7
je58uUkgNj03dw/bHmMbfiQNgBbaiBkmOc1ON6mbBn6JhwQvmGGVMTLbc9Gb
6GS4xK9gxPBGjZdUlVK5J+A5GTFuDGwHLt/Ggs9IjWJMoKPGu1DgfTMLpgTD
H+u9S2qG99IcMWK7pidrMCeBNAn2lokb5QOWlQ7dTKpueBseLepmsogFuldi
YoKwnsipD1lu0jzHnqmiEpwMNzAW8SjQJBBpGmgRNlDnno1j2n/fxlGmXKwg
s/hVtMhX+p2Y182pLN8JW/iDNol3yhoR6++RxjOS+xFukuY67tgkXu9m9onC
K8gzbOhaJNFlXpHV7w3FvPcN1hk/L8N099FaGTBsXW14j4cSr31i43grJjW4
D+P7YOIp4v7QmfmVyBF7W+S/+3dJbl5HxqlfapLPaNuI0BRkzvqbdCkoehm/
qsn4CeftYpdxdxODfcC+PIma0n0um8xS3c9uswC86feVc4lkAgAj0YaDiV4e
YF5Wh07tVJyhHDEHJG/JyKvS5CY/BLmMSYlUOwYOtXcNHnFmMbsJMsbmALSP
QedKXJ9r9+GIz311V9uezJ69Hva2IDDh5s12KEWy8i+cVafOtKsXYQ5pM945
eAY5w7/I2wqkgzA3uUMLN1qkMacSPDgWmHfbFUcDbPAuZkddUj4i5Y38zlqW
usWXGoMrYLhkIDySakc5ybM/Dtyazl/Wog1Jy7PMFP0oREFnINrM5OtL7K2W
2rFogvZvVtjUxJpR0vH3IVAjfJnnnlp0K3qp8amH1kiC+zoz1LZzayQdiENX
+4F0aHpKkCzufkrk3RbLx50sGRaDpqeu68PQWFYAoDH3qU6nE9f/vmW8Gl+1
9WgI+z1vuJqa/jWv8sYbZ8N3YV2N18h5bzU0ouk66N2H5fw+8ukx9TL9S7zt
SVl86bf22+uqK95SVzv2sgTiel2sdVhKKdMWfks1pbYoIDNvWbaYf/27V5fx
r8/OgrxVW2y/+Iu+ipveau439zaALgvfmi1JPrp2t+VgeOBbs+2+76375qv5
rbv/HvRWg43iAW89qOibh/f1vsrl3qmHCK+7e5vyTbW0xQDBjroHdRiv0L1q
OvvGna/YjJBwB9z7SkAN/rBXajvznleaxPsdrzxokN27yipp5XrTHUMvGTUi
jeadLQKpRhtovgy4AfnLOoGh96VjKTRfBlSK3pe1J+tbvbmd829DVmXATcNo
D3q3QCqHjBipC6q8yRXIOxHw3nvLT2Qw+ex7emWSncNmBv23mOJZc9BQtfnh
7WKoEL0FZdA1ZJhyjBgnkLFD4sICrJn4gR7UQH1VtAp+Fx6JT0cMOmM1UgvZ
O2N32Csz+hGpN2UiFwBr3gjIpAPLpxu1kFRIrkT2LJLIf2ZRZIVcRqDh2qOw
mQIExKPlpX6dmVP7LGJHS2KvKpLLpflhQYIX8vzmmAqatl/z+YB9ElY1V4+Z
STC72zr/gLptyQ/88236fIGv7nycH5RRdmrgHH1r9q9ZrvBPAZ3IvM5Jr2Q5
mNbMPtdu//mX2TvoPB2k4W+uSCP1NyttE+8e5Hm63B1vMCwWT4Fdx87L88BC
bgK17s435nbTJYbc8bZHrLAol+kl6bIfKUsqwSPr9oVHHFrUXNWhwjvzJfJi
gi/HyTgwZd+5czzzG/Md+7NhB3muLTFgm3ikndotr+Dw8Fbd2BjV7rI3GxQz
NicJaKRFQg5cWr7/ujAJr8Z2gYeM1Oe1xJJcRsIuL66KoeCUVW/REEDRQW9Y
oJaCw2O/72x3vu3bknPz7k7CGGY9V9zCCo4VnZ8gRHvRT+5tNV1Ym9SwpZkD
jE2ZU0GYt4fWIgIDW8qE1bK8a604Hfc6SzXrZsMoS3SfWEM1yFKOO37TrOuw
akPWsSjg65xxH1RoVv7cmQ1OGnlnrE6RbUZDHutO0TdkJhaNlRcwlrkgtvRT
MDz2OYjUHNXxMZvqZSVv6TsoWyfUlmKXmExbhnxhvLMjhbpXIFVuBFiet4Aq
TR+kFbwCbpPMnvtqmO5OZ7o6z/0h1SBHSh2EMOqKNXaR8bmXOuFzFgzce1Bl
n//kjNzwEtEVw7MyVl0upNlxIqtEXCJsDUc8SyW0hn3TFknzlygc4/oW12eO
YNntIDSBw4vY1QUJaTHCG8x5c2R0KCq9s0D/PlWBNWvWivSYMutuyXllNpyz
dzxZ9EZmZ9zz5CTr17/+TT26u5w5ZrOG5+4MzQie48iE2neORSQ14eO1v+bI
jIZmulberYxyk2suXBuvoet3th/fVo8Le1FzhBqnSiMT5Ot76zFqh31j3hh7
f3e3zb3TWE5WVZNGy+o9Q18zoO4HRrh7uhkOHCSPZ8O57935aozxnEMa/L4K
HeePcpS7vcpXzslw6J9s4kvP5ugTtTA250ubcxiw6OINM8/xvViplOdHZb7C
KBobCWOfqu228HEjuit7XWQOEhP5F9s7KbdYNTg+NewZ2nxyIMKQiRz01t9N
OYxcdEHDIBC6vkz0P16XBEWoAd7hkpnzzIbER/XLq+9JnIl63Pqwj0py9aEO
vTMx4qwGF0wjFNJfYp/HxaiHGm5u4mdvU8FLBhI00kzFQYg4o1tONHDOtvuC
AB6guGOTQC9wLHCNUXjBPUYiYzQIYHp9zzWkIVLGXUfs8N9kyczPd5js6jfm
R5rCTI95mx3tY11xoD3UGhsPOeeGcW/QXO1FN2rNm7p2S5F4gJqqfPRALT2I
197djN8lN9lA5nafdPcv9+CaSBApG8fQOedfrQx7BFyv3htxkvWr7xgrB6w4
yM9mqB/mn54MeYWyHmy9wJLwcXZGS+dkxkd8uvg7RN0n11nbcjYs4aJzYvAC
fyfvy/VgOzBNchiYj31y3gucWeffsVvZ1BrF99QrVVhrZkPx1kfAqXZZ3i0m
TEmhYAfxABLyO6rIr/chtX5Iy3al9wX/fsgOqfjcBg7+oRMaJqSLGK9vZ+mr
NcABeoN7vqEJmuda6ejKnS/+9qqP6aBsq1GafpUqzxvuteec0vjQ2bRhAXpp
kJODXrtjNKU9kuIlK/bxSXu8eg3iy44JGpPdiOGQX9o2nKyd4RcZiiDbQhow
m4xB5csDVJrZ1+2++hDb8pMU56MimnQIM6GqUgBRHQdvUWWcFiaJjOfm6eVz
BuLnSbCMDNojDcJXKDh5RO5kSHtFP1Rc0ql+AyqoSCHqTfX7ux/3Yh/Gzhzf
ozQRMugU5nwJPb3J0tvIBLomEmlDMzocSsyfXLI5EnJQKDYIoBKGSTWG0BwK
jb0cymPTXoQ0MJYYkw7Uh+VVNn496XqjYzPwuRdPNmiQ940UxH02Pqf5qM41
ac6AMYn96NxtLJtCOhQqk0gSnV0GIb3ho/GQ8pmQVmFz6tjAqj6HDL3D/Uf4
uWQImcmvZ/LMqSTJ+sKonfPL7NQ4D/SKsCszjKv+tmXNkCN9y/rJaDD/m1kB
auP3HMmHhvlTcqklJdulJ7uEcEnQEZg2TsCW7mE/cwa2Hqp1JgszC5zgCQ1O
obvQByyI5v3tJUMzkt3tbE40lUN121Od1UltP1OlWAjmtc5a5zma5zGTOL4W
KkP0WoBjlpmh3UMNC3OZAhxN7HdmDJCh3ThuYAYxNljGkLtMe1dKtMOMI9SS
HKRtmAteNn1N2pc6OCbtPEBBQJp/B/li547tUnAcoxk0BDP+s9gLLRlLl4hk
VLQoNpOpc+V4Gxr4XjI/DNDM6jnipG0Ov4ARIrsAmAmO2MwJ7U1qS1pd5pAt
Ga6vYJ+QfCvdxGpcax5joKjZ+X7eWe2sSx/sjPOVa5vzzjKlBfGKZC2i0mxa
IdNhgzCC3FATwB08tICJx7MuYDTp8AK267SnW3/q7o0JpibvF7dUxkwzV2cb
6aaPpcUM8RET/MD9uakJ1MIeCMQcUkshJHH+WVFVwaLFU2c5izgGgo2cfgKu
sBTFBr/HP90NFxKy17+L+ySzrnWNcgvafHXihN8EOj1yDw2uh8WycqBRQ17q
DhpQd/cFJzlBuGZMIdh2A8E45oCaCsEz7sbO8CmZYI8WLzhtWV6FURzAjwoL
rq9l2xDFP8Sf9HAKcRs0QbXaNMJeHlA6rnPD0yM7wMzIDI2Pw+/mqFbloHTI
tshjx8sKQOQEf/1GsMkz7WtxPLuNWhwWiNNqnJrGuYwkNb60GvSnKL5Xg2p5
ylJwE/LetfpS2s7t7/Z9g0ub5BlH4WsCqcGu8LSi+RqUCNLLZGJZeAMov0Xm
mS1pxS6Ixr5ljf5RHDy6sOSkK7M2WeAJvnKQaAjQLMACwMuKD4YsNcCevaJM
a+FpyrB8KwzLF0Alx04BVS3k1mTcMjmy6tfJSkH9rGsJOWB/DZD3uTtnNM5Z
xyi8mdR6GXaLo3VZ/2BOKBwUbH+ZZUqPJOiduQ8M7XpNvXgWttZ/NFOY7zCA
o+WCN1r2tqC/MB+W3I+kwfrddXE9GZr9OdJjcDi0JLFRbNjXTd8M57HBmcCg
HrL2ygeND/kgFdbimKl4oEYbERvFtbEKWumzxRq9wgF0K5T1H8BHVtom2Kgx
zmvDl+kXBaAF3XXBmrLChrDqaY0L7COasSF0YC8DbaNgEjFaBmsYbACD6moq
TAyFYVln95ODwaRR4/LtAsDRgWMJyEGxH9NyVKlzSW4F/Ymo0mrT1Mzqvt02
pF5jQ8odY9Ok5l6KM3BSqSKjKLZx7BNNHO2bHWcQl/hlc0Wy+nHlXre0BMGb
IPG1M2Auy1YPsq+k+WTkllQ16RpFUMae6uaO9r3geRMVLwJbR8lJCnXJpzTe
kqRUyG1DOl2yA5gJ9wwzNc6E2k57Wr89nC8rWozYFDw9kVEAlPJWsieZM1K3
c2UgnHUVJ3aHilgVfGqzVWYuVhiDIcAGM3v3ZCwcA9wf4yiG9Qwkr1O+ZrJn
mcFTLaWjwW2xJJA1sYciz/+bqfTPJmTPtaOaUXqpZjMCLe4dQ4HLrU9Rv3hg
JPbP0InyEBisLL4kJmOXQzrbqBA0vs5KyAyDTIuuYppKhGG/kWI30XuIBjV6
oMyKwGMyYKkQgc2XCYLToy+UuSHWHE5Wc9BTuZkInPoN5P09SLie9Dj3QUkB
1pJYSnJPM+cwRBLH9bu3ChQZIujQqH0v+yK42RaYElQxhhn23MMeOTf5/qyU
QcmsC1HgTbd9AapIYqihAMJNOvbvzzp8TgQkQziUprSjr2lZcCkMBtM2wSTn
oXYge1roDXrJDS5JDrDN2TGNumkcSk7JNqVhJCseBL7szQhiVh5G2aBMvKsq
NbEYjSArsCCSIeN/4AyoapJiffYeJOlPqmpR0zzVkAMWailLEUfZuVOGj88M
+Osq4ARk6MtM1Wt2hr0HIXxK5g8nAcxAnF26hl7Jgu2SZkS3T1hp6oWtWk2Y
gS7UQHbmpRb5T6+Ee/VikvdU5ns5ZX5ymDku6uYTU6mGoAqAxvFrASmpbIhK
BRMagDprQuJcfoT1xxp/ptY0Gh6axgM3/hL5oMJ4+iK5EewXUtMQqZuWtlY0
PtgLZRgnE+gjosJw4Li5IrR0ih2ymjktjEKjuOjGk3a+rKZhs37dIMH8h4vt
XNOBGUXkqwdojB4YoxJvxAACi5lszeN5sKDy8FsaoDuj1QBLzLRyBnbLv9gx
gTfpVYMUEB39Wt5jKGca1oKnHBiaP+ZpnGUFYyMED3PfSjiF1VQZ1wPVig+y
ZCFnV58x1yC8TT0IBrorDES2R9H7SUnzml5jmmhL57p9wESQIluUPSOFtQan
BSrmxNhxYtS2CHsQasYtmyyKyRA+3l7B5AszNMDUYmZ5Y1eseKcnYBq4pXLU
dMwNQYI7iaPrS7pagtiEriYlYNdj0P0U8VYXtC1HYE0keSfw263odTGEoWgr
h48XB/YO3RT79Hlc/OPfW/HrktSjaRJvkVRISPNiAqQJLaOXySQtWxGNcAmw
nf4kfpNOWvReH5wS8W6PiXWlsFck1lgNwa903byKXydTumWnYyov/pxcZq1o
JxtldFUhZS+PX6cQE9uXJcmi4voS2Ptfi4Ep7Q2ILS+LFtgTqdNvqQGkrdFF
6QrNwTu0XOO3aDh8iEcYEfqYkcgegsSqqrJRER8koyTPkxZtkRGN8UFKil7e
it6QtCYJm0JgYrjeJFeTLt1Yql7Wu8pQJ3QB6sF7Ou6GCQr4YUgb9agAJZlX
P93cqENfW2CH+jkDn1IB5q5iAJ/o8XUBElvv6esy+bnXij7wOX78NaVVC4Ix
atlHunlAdLXilzRD/exqTDr5AI0XkmdSbjD78Y8TWrGfU11NDO04zK5Stzr2
K/7PVlmADPAVVQsQ+iTeSYfUQdJ5qPe//keZc55AH2NMV6Z0ymNIH2gC0fts
nNBMvJ7QEn9V5F9//fdh+pUGs1smfepSdEhHzWVGC4DGfwJesOQLW8wPRN4d
FKCsiA8mgzwd/Pq/sCY+XmZdRos7TCd5hjV1TP0qC8gwGgy6j/fTFq9HpqPM
cJC8QQZvruRvQq/0MzedRj1Lf/2fQzbIRHKZVzwOxBgxB6jRDxukTPReiC3S
eEq3JDbzTSW+Qfcx6wNsSMjym2J449woSt7L4AiW+dpORzgT0DdEDR0ZoZmV
YQNbkcDe4dh+Q6dO+yMJTRrWrd7fJrQLbrBwk9EkxUa+SCCc6HOWf21FtB+g
YtKOpfnGHqXlTFJ1mNzono330iFsgb/+xyWY+5Jelv4cvyy/pv/4P3mWXGEr
FjS72wnsd7RQqLo8Nvv8bZrTIgRjZ0KF/uPfktt4++uki0poN9AOzUmtpzIO
sWKodTu/P86GaO3B5CqpvsY7k/EVffqQYob3UrrKZ1iN0KVpePZIsmAFvB0m
1Fe72o6wV6kh+WAypKp3b5L4VVoOUnx4DdKVKa3Fos+cl9QCusuRgCH5Rl3B
fL1Op7xoIFmggRQ31dXUfC7zDA2m7tLSSqh/o2uMUDmYoLO83CIj1N4OC+xo
t8bzYjj0t7EVOodUGmRMVeXZgMTCMKGppBIPEoRPoTW0oC8LWl0HaVlQYz4k
8Idc0YvYAixTMp6zw+SKtJX8qkAzqIGHSV5MsCPH9G8SCBVE5U+XKTOF0WZt
/3SZ0Kxtl1M6b2hjY4uQYkeNnCSt6K8F5MYhrcnMjdXhr/+Xnig94Wa/OUqq
ETX7cJKbOf3Hv5Ho+5qSAL6tIBDfJDR81PxbKuhtNtZvd/OS40A+/Pq/S5IP
W6QgT2iv7xdVdiFC7oKe2gJTuGx2+q5MsNxoJaRULezGLT6VhgULV3punOgR
EB0VOMV40oZ0hUomdGpwBbRwqLmwmpF6knexSGQ2ehDBGV0vEm5g9DGjco/H
acYPbHd2OvHH7JZmjVv1szTqE/tQIF4+FiPazF/T6wIanxCmFTXTFuPNsmzg
M5qpnS5gTTU4dlasdKcO7ZU0R4GU4hvTRKxatKFz2pbVZhS12a55sn28drh7
/Hp99/3x9ulJr1oDhdCpeTte2NcwYQN1kAyyYbqs3ifEHEPpRdF4T8z0dAxA
JHPgmTWIm/szxBLqWgBMH4K3gAZNxUFQA3TH0BsxU93picdrdNpyMdemP8aP
GO1OoIcnTFpa5L+vsAGzr0XOjG1QnxnST2MY8uJGrabgpUvo/Fbj9CvkjsVb
gzKVK15edOKTjWdra0/XaGzg+ajaZog6NIIn7w7ydHx6kg/xnyDm7eTdq/0n
pDmSiN+jwvWZNuzIp8J1H12QXKDZoM1kLyLGLWq7s00XQomK+X0VnbzDDfiV
4I5INISYKqj0QXZa746kwtGMaXeid+jOypOVJy9WX7x4YntE92HuDa8HzA3z
eHLVIGY8SUlJ6fe8NaHat0wmx5G3BVkESjb7bmgFZgwgzovARpO09P4idmHD
zFmmSo7OE4n69xwK6h2THoeTrp3mOYxqc0idXtnYWHn+wnZaO8WzeMzOTFi8
PpL8ofmHIYXW3jipzSn/LNNJP7bRIDOZiT3y4xMdKHlIRjeyW8tRoOg362hK
J50sR8Fqn/+cPoWomctI1557GqT3/B39/3LkL7s5z+C3iBeQe4A+SYtqi95r
FP9AD9EUJHhWO72c9Zdlx0T++nrYi3ZtRmbRhW3Gl20sqXZPFmfQyJlX7qlK
VkTE8xzWU5kF0RnTjC9HdiLvfIz/jxZk3uYLoM6PXSh3vqtbt1rGoySc221G
9o7+Hy1hOtyVLAIA

-->

</rfc>

