<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-morrison-identity-streams-00" category="info" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.32.0 -->
  <front>
    <title abbrev="Identity Streams">Identity Streams: Per-Trait Source Attribution for Inferred and Stated Identity Claims</title>
    <seriesInfo name="Internet-Draft" value="draft-morrison-identity-streams-00"/>
    <author fullname="Blake Morrison">
      <organization>Alter Meridian Pty Ltd</organization>
      <address>
        <email>blake@truealter.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <abstract>
      

<t>When one system tells another about a trait it has inferred about a
person, the receiver today learns the trait and a confidence, and
nothing about what the inference was drawn from.  Because the
receiver cannot tell a trait the person stated in answer to a
question from one read off the person's activity on a linked
platform, it cannot apply the lawful basis, consent and context limits that
belong to each.  This document defines a source tag carried with
every inferred trait on the wire.  The tag names, for each stream
that contributed to the trait, a registered stream class, the
provenance class of the observation, where the inference was
computed, the lawful basis and purposes the stream was consented
for, and the contexts the trait may be used in.  It reuses the
provenance-class vocabulary of the Morning Brief specification,
establishes a registry of stream classes, and states the rules a
receiver follows, including refusing a trait whose sources it cannot
check.  The same tag carries facts the person states about
themselves, such as when they are available or the terms on which
they offer something, and those facts keep the limits of the stream
they were given on.  It defines a wire field only.  How traits
are inferred, stored or scored is out of scope.</t>
    </abstract>
  </front>
  <middle>
    

<section anchor="introduction">
      <name>Introduction</name>
      <t>An identity-inference system derives statements about a person
(a disposition, a competency, a style of working) from what the
person does, without asking the person to declare them.  Such
statements increasingly pass between systems.  An identity service
answers an organisation's query with them and a credential issuer
hands them to a verifier, while an agent may pass to another what it
has learnt about the person it acts with.</t>
      <t>The obligations attached to an inferred statement depend on where
it came from.  Data-protection law ties lawful basis and purpose to
the collection of the data an output is derived from <xref target="GDPR"/>.  Consent given
for inference from one stream does not cover inference from
another.  Some inferences are prohibited in some contexts whatever
consent exists.  The EU AI Act prohibits inferring the emotions of a
natural person in the workplace and in education institutions,
except for medical or safety reasons <xref target="EU-AI-ACT"/>.  A trait derived
on the person's own device from passively observed activity differs
from one the person supplied in a structured exchange, even when
both carry the same name and value.</t>
      <t>A receiver handed a bare trait knows none of this.  It can
honour the obligations only by trusting that the sender already did,
and it cannot carry them forward if it passes the trait on.  The
Compute-Location Gate specification <xref target="COMPUTE-GATE"/> already requires
an inference service to keep the provenance class on every derived
statement inside its own architecture, and says a statement that has
lost its provenance class is not consent-checkable.  This document
extends that requirement across the boundary between systems.</t>
      <section anchor="what-this-document-specifies">
        <name>What This Document Specifies</name>
        <ul spacing="normal">
          <li>
            <t>A source tag, <tt>sources</tt>, carried with each inferred trait
(<xref target="tag"/>).</t>
          </li>
          <li>
            <t>The fields of each source entry, and the CDDL <xref target="RFC8610"/> that
defines them, with CBOR <xref target="RFC8949"/> and JSON <xref target="RFC8259"/>
serialisations.</t>
          </li>
          <li>
            <t>A registry of stream classes with general initial entries
(<xref target="classes"/>), and registries for lawful bases, purposes and use
contexts.</t>
          </li>
          <li>
            <t>The rules an issuer follows when it emits a tagged trait
(<xref target="issuer"/>) and the rules a receiver follows when it accepts one
(<xref target="receiver"/>).</t>
          </li>
          <li>
            <t>A stream class for facts the subject states, and the rules that
keep a stated fact distinct from an inference (<xref target="stated"/>).</t>
          </li>
        </ul>
      </section>
      <section anchor="out-of-scope">
        <name>Out of Scope</name>
        <t>This document does not specify how traits are inferred, the trait
vocabulary, which facts a subject may state, how sources are weighted or combined, the container a
trait travels in, or any settlement of value owed to the subject.
The tag is designed to sit inside an existing signed container, such
as a COSE_Sign1 structure <xref target="RFC9052"/>, a signal in a Morning Brief
<xref target="MORNING-BRIEF"/>, or a verifiable credential, and it inherits that
container's integrity protection.</t>
      </section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      

<dl>
        <dt>Subject</dt>
        <dd>
          <t>The natural person a trait is about.</t>
        </dd>
        <dt>Trait</dt>
        <dd>
          <t>A statement about a subject, such as a value on a named dimension
together with a confidence.  A trait is either derived by inference
or, where every source is of class <tt>subject-statement</tt>, stated by
the subject and carried as stated (<xref target="stated"/>).</t>
        </dd>
        <dt>Stream</dt>
        <dd>
          <t>A distinct channel of observation about a subject, under one grant
of consent or other lawful basis.  Two linked accounts on the same
platform are two streams.  A stream has exactly one stream class.</t>
        </dd>
        <dt>Stream class</dt>
        <dd>
          <t>The kind of channel a stream is, drawn from the registry in
<xref target="iana-classes"/>.  A stream class names a kind of channel and
identifies no party: <tt>peer-attestation</tt> says that a peer attested
without saying which.</t>
        </dd>
        <dt>Provenance class</dt>
        <dd>
          <t>How the observation was made, as defined by the Morning Brief
specification <xref target="MORNING-BRIEF"/> and drawn from its "Morning Brief
Provenance Classes" registry.</t>
        </dd>
        <dt>Issuer</dt>
        <dd>
          <t>The system that emits a tagged trait.</t>
        </dd>
        <dt>Receiver</dt>
        <dd>
          <t>The system that accepts a tagged trait, whether to use it or to
pass it on.</t>
        </dd>
        <dt>Use context</dt>
        <dd>
          <t>The setting in which a receiver intends to use a trait, such as a
hiring decision or an educational assessment, drawn from the
registry in <xref target="iana-contexts"/>.</t>
        </dd>
      </dl>
    </section>
    <section anchor="tag">
      <name>The Source Tag</name>
      <section anchor="placement">
        <name>Placement</name>
        <t>Every trait an issuer emits under this specification carries a
<tt>sources</tt> member: a non-empty array of source entries, one for each
stream that contributed to the trait.  A trait derived from three
streams carries three entries.  An issuer <bcp14>MUST NOT</bcp14> merge entries for
different streams into one entry, and <bcp14>MUST NOT</bcp14> omit a contributing
stream because its contribution was small.</t>
        <t>The <tt>sources</tt> member <bcp14>MUST</bcp14> be inside the integrity protection of the
container that carries the trait.  A tag that can be stripped or
altered without breaking the container's signature provides none of
the properties in this document.</t>
      </section>
      <section anchor="schema">
        <name>Schema</name>
        <sourcecode type="cddl"><![CDATA[
tagged-trait = {
  trait          : tstr,          ; trait name, issuer vocabulary
  value          : any,           ; trait value, issuer vocabulary
  ? confidence   : float16 / float32,
  sources        : [+ source],
  ? issued       : tdate,
}

source = {
  stream-class   : tstr,          ; registered, see Section 4
  stream         : tstr,          ; opaque stream reference
  provenance     : provenance-value,
  computed       : "device" / "service",
  basis          : tstr,          ; registered lawful basis
  purposes       : [+ tstr],      ; registered purposes
  contexts       : [+ tstr],      ; registered use contexts
  ? window       : [tdate, tdate],; first and last observation
  ? share        : float16 / float32, ; 0.0 to 1.0
  ? consent-ref  : tstr,          ; URI to check consent status
  ? return-ref   : tstr,          ; URI naming where value owed
                                  ; to the subject is settled
}

provenance-value = "active" / "passive-aggregate"
]]></sourcecode>
        <t>The JSON serialisation uses the same member names.  Times are RFC
3339 date-time strings in both serialisations.</t>
      </section>
      <section anchor="field-semantics">
        <name>Field Semantics</name>
        <dl>
          <dt><tt>stream-class</tt></dt>
          <dd>
            <t>The stream's class.  It <bcp14>MUST</bcp14> be a value in the "Identity Stream
Classes" registry (<xref target="iana-classes"/>).</t>
          </dd>
          <dt><tt>stream</tt></dt>
          <dd>
            <t>An opaque reference to the stream, chosen by the issuer.  It <bcp14>MUST</bcp14>
be stable for a given subject, stream and receiver because a
receiver has to match a later revocation to the traits it affected.
It <bcp14>MUST NOT</bcp14> be the same value for the same stream across different
receivers (<xref target="privacy-linking"/>), and <bcp14>MUST NOT</bcp14> encode an account
name, platform user identifier or any other identifier of the
subject.  A random value such as a version 4 UUID <xref target="RFC9562"/> kept
per subject, stream and receiver meets these requirements.</t>
          </dd>
          <dt><tt>provenance</tt></dt>
          <dd>
            <t>The provenance class of the observations the stream contributed.
The value is drawn from the Morning Brief provenance-class registry
<xref target="MORNING-BRIEF"/>.  That registry deliberately omits any token for
passive observation of a single individual.  Rule 7 of <xref target="issuer"/>
says when an entry may carry <tt>active</tt>, and <xref target="device"/> says how a
derivation made on the subject's device is tagged.</t>
          </dd>
          <dt><tt>computed</tt></dt>
          <dd>
            <t>Where the inference from this stream was computed: <tt>device</tt> for a
device under the subject's control, <tt>service</tt> for infrastructure
operated by the issuer or on its behalf.</t>
          </dd>
          <dt><tt>basis</tt></dt>
          <dd>
            <t>The lawful basis under which the stream was collected and the
inference made, from the "Identity Stream Lawful Bases" registry
(<xref target="iana-bases"/>).</t>
          </dd>
          <dt><tt>purposes</tt></dt>
          <dd>
            <t>The purposes the stream's consent or other basis covers, from the
"Identity Stream Purposes" registry (<xref target="iana-purposes"/>).  These are
the purposes as recorded when the basis was established.  An
issuer <bcp14>MUST NOT</bcp14> list a purpose the subject did not agree to at
that time, and <bcp14>MUST NOT</bcp14> widen the list later by reinterpreting an
earlier grant.</t>
          </dd>
          <dt><tt>contexts</tt></dt>
          <dd>
            <t>The use contexts the trait may be used in, as far as this stream
is concerned, from the "Identity Stream Use Contexts" registry
(<xref target="iana-contexts"/>).</t>
          </dd>
          <dt><tt>window</tt></dt>
          <dd>
            <t>The times of the first and last observation drawn from the stream
for this trait.</t>
          </dd>
          <dt><tt>share</tt></dt>
          <dd>
            <t>The issuer's statement of how much of the trait this stream
contributed, between 0.0 and 1.0.  The shares of one trait need
not sum to 1.0, because issuers combine sources in different ways.
The value is informative.</t>
          </dd>
          <dt><tt>consent-ref</tt></dt>
          <dd>
            <t>A URI at which a receiver holding the right credentials can learn
whether the stream's consent is still in force.  It <bcp14>MUST NOT</bcp14>
identify the subject to a party that does not already know the
subject.</t>
          </dd>
          <dt><tt>return-ref</tt></dt>
          <dd>
            <t>A URI naming where value the receiver owes the subject for this
stream is settled, for deployments where reading a trait carries a
payment to the subject.  How settlement works is out of scope.</t>
          </dd>
        </dl>
      </section>
      <section anchor="example">
        <name>Example</name>
        <t>A trait drawn from two streams, shown in the JSON serialisation.
All values are examples.</t>
        <sourcecode type="json"><![CDATA[
{
  "trait": "collaborative_problem_solving",
  "value": "high",
  "confidence": 0.62,
  "sources": [
    {
      "stream-class": "direct-response",
      "stream": "6f1c2e0a-8b7d-4d2e-9a51-3c0f7e2b9d14",
      "provenance": "active",
      "computed": "service",
      "basis": "consent",
      "purposes": ["trait-inference", "disclosure-on-query"],
      "contexts": ["general", "workforce"],
      "window": ["2026-08-02T09:15:00Z", "2026-09-30T18:40:00Z"],
      "share": 0.7
    },
    {
      "stream-class": "linked-account",
      "stream": "c2a94d71-0f3e-4b8a-bf62-91d5e7a0c3f8",
      "provenance": "active",
      "computed": "service",
      "basis": "consent",
      "purposes": ["trait-inference"],
      "contexts": ["general"],
      "consent-ref": "https://identity.example/consent/c2a94d71",
      "share": 0.3
    }
  ]
}
]]></sourcecode>
        <t>Because the second stream's consent does not cover disclosure on
query and its contexts do not include workforce, a receiver in a
hiring setting cannot use this trait at all (<xref target="receiver"/>, rules 5
and 6).</t>
      </section>
    </section>
    <section anchor="classes">
      <name>Stream Classes</name>
      <t>A stream class describes the channel, at a level of generality that
holds across implementations.  The initial classes are:</t>
      <dl>
        <dt><tt>direct-response</tt></dt>
        <dd>
          <t>The subject's own answers in an exchange whose purpose, as the
subject understood it, was to contribute to inference about them.</t>
        </dd>
        <dt><tt>relayed-response</tt></dt>
        <dd>
          <t>The subject's own answers, submitted through a software agent
acting at the subject's direction rather than typed by the
subject.  The choice is the subject's, but signals that depend on
the subject's own pace and phrasing are absent, and receivers
<bcp14>SHOULD</bcp14> weigh it below <tt>direct-response</tt>.</t>
        </dd>
        <dt><tt>authored-work</tt></dt>
        <dd>
          <t>Work the subject has attached and attested as their own, such as
writing, code or a portfolio item.  Inference is drawn from the
work itself.</t>
        </dd>
        <dt><tt>peer-attestation</tt></dt>
        <dd>
          <t>A statement about the subject made by another identified person.
The class does not identify the peer.</t>
        </dd>
        <dt><tt>linked-account</tt></dt>
        <dd>
          <t>Data from an account the subject holds on a third-party platform
and has linked to the issuer.  The platform's authorisation of
access is not, by itself, a lawful basis for inference
(<xref target="issuer"/>, rule 4).</t>
        </dd>
        <dt><tt>third-party-metadata</tt></dt>
        <dd>
          <t>Facts about the subject's presence on a third-party service, such
as counts, timestamps or structure, without content.</t>
        </dd>
        <dt><tt>public-record</tt></dt>
        <dd>
          <t>The subject's work or activity in a publicly available corpus.
Being public does not make it consented for inference.</t>
        </dd>
        <dt><tt>service-interaction</tt></dt>
        <dd>
          <t>How the subject uses the issuer's own service, observed by the
issuer in the course of providing it.</t>
        </dd>
        <dt><tt>device-activity</tt></dt>
        <dd>
          <t>Activity observed on a device under the subject's control,
inferred from on that device (<xref target="device"/>).</t>
        </dd>
        <dt><tt>subject-statement</tt></dt>
        <dd>
          <t>A fact the subject stated about themselves to be passed on as they
stated it, such as when they are available, where they will work,
or the terms on which they offer something.  It differs from <tt>direct-response</tt>, whose answers feed
an inference (<xref target="stated"/>).</t>
        </dd>
      </dl>
      <t>New classes are added by the procedure in <xref target="iana-classes"/>.  A
class <bcp14>MUST</bcp14> describe a kind of channel and <bcp14>MUST NOT</bcp14> be defined by one
platform, product or implementation.</t>
    </section>
    <section anchor="issuer">
      <name>Issuer Rules</name>
      <ol spacing="normal" type="1"><li>
          <t>An issuer <bcp14>MUST</bcp14> attach a source tag to every trait it emits under
this specification, and <bcp14>MUST NOT</bcp14> emit a trait whose sources it
cannot enumerate.  A trait whose provenance has been lost inside
the issuer is not emitted.</t>
        </li>
        <li>
          <t>An issuer <bcp14>MUST</bcp14> record the stream, stream class, provenance class
and compute location of each observation when the observation is
taken, and <bcp14>MUST NOT</bcp14> reconstruct them afterwards from the trait.</t>
        </li>
        <li>
          <t>An issuer <bcp14>MUST NOT</bcp14> emit a source entry whose <tt>provenance</tt> is any
value outside the Morning Brief provenance-class registry, and
<bcp14>MUST NOT</bcp14> emit a trait about a named subject with a source entry
whose <tt>provenance</tt> is <tt>passive-aggregate</tt>.  An aggregate describes
a cohort, and a statement about one person drawn only from it is
not an aggregate.</t>
        </li>
        <li>
          <t>For <tt>linked-account</tt> and <tt>third-party-metadata</tt> streams, the
issuer <bcp14>MUST</bcp14> hold a basis for inference that is separate from, and
separately revocable from, the platform's authorisation of
access.  The <tt>purposes</tt> list reflects that separate basis.</t>
        </li>
        <li>
          <t>An issuer <bcp14>MUST NOT</bcp14> list a use context in <tt>contexts</tt> that the
stream's basis and purposes do not support, and <bcp14>MUST NOT</bcp14> list
<tt>workforce</tt> or <tt>education</tt> for any trait that is an inference of
emotion, in jurisdictions where such inference is prohibited in
those settings.  A categorical prohibition applies whatever the
tag says.</t>
        </li>
        <li>
          <t>When consent for a stream is withdrawn, the issuer <bcp14>MUST</bcp14> stop
emitting traits that list that stream, and <bcp14>SHOULD</bcp14> make the
withdrawal visible at <tt>consent-ref</tt> where one was given.</t>
        </li>
        <li>
          <t>A source entry of any stream class carries <tt>provenance</tt> set to
<tt>active</tt> only where the subject initiated the act that released
that stream's evidence for inference, for example by linking the
account.  Section 3.1 of <xref target="COMPUTE-GATE"/> defines the active class
this way.  Where the subject initiated no such act, an issuer <bcp14>MUST
NOT</bcp14> emit a source entry for that stream in a trait about a named
subject.  <xref target="stated"/> applies the same test to a stated fact, where
the subject's act is the stating.</t>
        </li>
      </ol>
      <section anchor="device">
        <name>Derivations Made on the Subject's Device</name>
        <t>The Compute-Location Gate specification <xref target="COMPUTE-GATE"/> requires an
inference from passive observation of a single individual to be
computed on the subject's device.  The derived statement is retained
on that device and is never transmitted to a server as a passive
observation.  Section 4 of <xref target="COMPUTE-GATE"/> gives the one route by
which such a derivation becomes visible to a server.  The subject
contributes it by a fresh active-class act, and the contribution
enters as active-class signal and is gated afresh.</t>
        <t>A trait contributed this way is tagged with <tt>computed</tt> set to <tt>device</tt>,
<tt>provenance</tt> set to <tt>active</tt> (the contribution is the subject's act), and
the stream class of the underlying observation, normally
<tt>device-activity</tt>.  The underlying observations never appear on the
wire.  An issuer <bcp14>MUST NOT</bcp14> emit a <tt>device</tt> source entry for a
derivation the subject did not contribute by such an act, and <bcp14>MUST NOT</bcp14> emit a
<tt>service</tt> source entry for any inference drawn from passive
observation of a single individual.</t>
      </section>
      <section anchor="stated">
        <name>Facts the Subject States</name>
        <t>A trait whose every source entry has the stream class
<tt>subject-statement</tt> is a stated fact.  Its value is what the subject
said, and the issuer relays it without vouching for it.</t>
        <ol spacing="normal" type="1"><li>
            <t>An issuer <bcp14>MUST NOT</bcp14> emit, under <tt>subject-statement</tt>, a value the
subject did not state, and <bcp14>MUST NOT</bcp14> carry under it a value the
issuer inferred.  Changing the representation without changing the
meaning, such as converting a time zone or a currency format, is
permitted.</t>
          </li>
          <li>
            <t>A source entry of this class carries <tt>provenance</tt> set to <tt>active</tt>,
since stating is the subject's act, and <tt>computed</tt> names where the
statement was recorded.  An issuer <bcp14>SHOULD</bcp14> omit <tt>confidence</tt> from a
stated fact.</t>
          </li>
          <li>
            <t>The second time in <tt>window</tt> is when the subject last stated or
confirmed the fact.  Stated facts such as availability go stale,
and an issuer <bcp14>SHOULD</bcp14> include <tt>window</tt> on them.  When the subject
withdraws or replaces a stated fact, the issuer <bcp14>MUST</bcp14> stop emitting
the old value, as for withdrawn consent (<xref target="issuer"/>, rule 6).</t>
          </li>
          <li>
            <t>A trait drawn from a <tt>subject-statement</tt> source together with
sources of any other class is an inference, and its value is not
the subject's statement.</t>
          </li>
        </ol>
        <t>A stated fact is unverified, and a claim that a third party has
checked, such as a licence or an insurance policy, is not carried as
a <tt>subject-statement</tt> source.</t>
      </section>
    </section>
    <section anchor="receiver">
      <name>Receiver Rules</name>
      <t>A receiver processes each trait as follows, and stops at the first
rule that fails.</t>
      <ol spacing="normal" type="1"><li>
          <t>If the trait carries no <tt>sources</tt> member, or an empty one, the
receiver <bcp14>MUST NOT</bcp14> use the trait and <bcp14>MUST NOT</bcp14> pass it on.</t>
        </li>
        <li>
          <t>If the <tt>sources</tt> member is outside the integrity protection of
the container, the receiver <bcp14>MUST</bcp14> treat the trait as untagged.</t>
        </li>
        <li>
          <t>If any source entry carries a <tt>provenance</tt> value outside the
Morning Brief provenance-class registry, the receiver <bcp14>MUST</bcp14> reject
the whole trait as malformed.  If the trait is about a named
subject and any entry carries <tt>passive-aggregate</tt>, the receiver
<bcp14>MUST</bcp14> reject it.</t>
        </li>
        <li>
          <t>If any source entry carries a <tt>stream-class</tt>, <tt>basis</tt>, purpose or
context the receiver does not recognise, the receiver <bcp14>MUST</bcp14> treat
that entry as permitting no purpose and no context.</t>
        </li>
        <li>
          <t>The receiver <bcp14>MUST NOT</bcp14> use the trait for a purpose unless every
source entry lists that purpose.  A trait inherits the narrowest
purposes of its sources.</t>
        </li>
        <li>
          <t>The receiver <bcp14>MUST NOT</bcp14> use the trait in a use context unless every
source entry lists that context.  A receiver whose intended use
context is <tt>workforce</tt> or <tt>education</tt> <bcp14>MUST</bcp14> also refuse any
trait it knows to be an inference of emotion, whatever the tag
lists.</t>
        </li>
        <li>
          <t>Before an action with material effect on the subject, such as a
hiring or admissions decision, the receiver <bcp14>SHOULD</bcp14> check
<tt>consent-ref</tt> for every entry that carries one, and <bcp14>MUST NOT</bcp14> act
on a trait whose consent the check reports withdrawn.</t>
        </li>
        <li>
          <t>A receiver that passes a trait on <bcp14>MUST</bcp14> pass the <tt>sources</tt> member
unchanged, and <bcp14>MUST NOT</bcp14> add contexts or purposes to it.  A receiver
that derives a new trait from received traits <bcp14>MUST</bcp14> carry forward
every source entry of every input trait.</t>
        </li>
        <li>
          <t>A receiver <bcp14>MUST NOT</bcp14> present a trait as stated by the subject unless
every source entry has the stream class <tt>subject-statement</tt>, and
<bcp14>MUST NOT</bcp14> present a stated fact as verified.</t>
        </li>
      </ol>
      <t>Rules 5 and 6 take the intersection of the sources rather than the
union because a trait is an inseparable product of its inputs.  A
receiver cannot use the part of a trait that came from a stream the
subject agreed to share and leave behind the part that came from one
they did not.</t>
    </section>
    <section anchor="relationship-to-other-specifications">
      <name>Relationship to Other Specifications</name>
      <t>The provenance-class vocabulary is the Morning Brief's
<xref target="MORNING-BRIEF"/>.  This document adds no provenance class and
inherits that registry's rule that no token permitting single-subject
passive inference may be registered.  A Morning Brief signal that
carries an inferred trait <bcp14>SHOULD</bcp14> carry the trait's <tt>sources</tt> member
in its body, and its own <tt>provenance_class</tt> <bcp14>SHOULD</bcp14> be the most
restrictive of the entries.</t>
      <t>The Compute-Location Gate <xref target="COMPUTE-GATE"/> decides, inside one
inference service, where an inference may compute and whether it may
proceed, keyed to the pair of provenance class and signal stream.
This document carries the outcome of that decision with the trait
once it leaves the service.  The <tt>stream</tt> and <tt>stream-class</tt> fields
correspond to that specification's <tt>signal_stream</tt>, with the stream
reference made opaque and receiver-specific for the reasons in
<xref target="privacy-linking"/>.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="misdeclared-sources">
        <name>Misdeclared Sources</name>
        <t>The tag is the issuer's statement.  A receiver can check that the
tag is well formed and signed, but cannot check that it is true.  An issuer that
tags a passively observed stream as <tt>direct-response</tt>, or lists
contexts its consent never covered, has produced a conformant tag
that misstates the facts, and nothing on the wire detects it.  An
inference tagged <tt>subject-statement</tt> is the same case, and it presents
the issuer's conclusion as the subject's own words.
Receivers <bcp14>SHOULD</bcp14> accept tagged traits only from issuers whose
practices they have a basis to rely on, and <bcp14>SHOULD</bcp14> prefer issuers
whose inference pipelines are subject to audit.</t>
      </section>
      <section anchor="stripping-and-downgrade">
        <name>Stripping and Downgrade</name>
        <t>A party between issuer and receiver could remove source entries, so
that a trait appears to come only from its most permissive stream,
or add contexts.  Placing <tt>sources</tt> inside the container's signature
(<xref target="tag"/>) defeats this for any receiver that verifies the signature.
An attacker gains nothing by moving the tag outside the signature,
as rule 2 of <xref target="receiver"/> treats an unprotected tag as absent.</t>
      </section>
      <section anchor="laundering-through-derivation">
        <name>Laundering Through Derivation</name>
        <t>A receiver could derive a new trait from a received one and emit it
without the original sources, and the restrictions would then fall
away at the second hop.  Rule 8 of <xref target="receiver"/> forbids this.  It is a rule
on conduct; a receiver that breaks it has broken this specification,
and the second receiver cannot tell.</t>
      </section>
      <section anchor="stale-consent">
        <name>Stale Consent</name>
        <t>Consent can be withdrawn after a trait is emitted.  A tagged trait
held by a receiver remains signed and well formed after its basis has
gone.  <tt>consent-ref</tt> and rule 7 of <xref target="receiver"/> let a receiver check
before acting, and receivers <bcp14>SHOULD NOT</bcp14> retain tagged traits longer
than their purpose needs.</t>
      </section>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>The considerations of <xref target="RFC6973"/> apply throughout.  The tag itself
discloses information about the subject, and the rules below limit
it.</t>
      <section anchor="privacy-linking">
        <name>The Tag Discloses the Subject's Channels</name>
        <t>A list of the streams that contributed to a trait says which kinds of
channel the subject has.  It can show that they linked a platform
account, that peers attested about them, or that they use the issuer's
service in a particular way.  Stream classes are deliberately coarse so that the
tag names a kind of channel and identifies no platform or person.
Issuers <bcp14>MUST NOT</bcp14> encode a platform name, peer identity or account
identifier in any field.</t>
        <t>An opaque <tt>stream</tt> reference that was the same across receivers
would let receivers who compare notes link the same subject across
their separate dealings.  The requirement in <xref target="tag"/> that the
reference differ per receiver prevents this.</t>
      </section>
      <section anchor="minimisation">
        <name>Minimisation</name>
        <t>An issuer <bcp14>SHOULD</bcp14> emit only the traits a query needs, and the tag for
each lists only the streams that contributed to that trait.  The
<tt>window</tt>, <tt>share</tt>, <tt>consent-ref</tt> and <tt>return-ref</tt> fields are
optional, and an issuer <bcp14>SHOULD</bcp14> omit any a receiver does not need.
<tt>window</tt> in particular can reveal when the subject was active, and
<bcp14>SHOULD</bcp14> be coarsened to the day or omitted.</t>
      </section>
      <section anchor="stated-facts-that-locate-the-subject">
        <name>Stated Facts That Locate the Subject</name>
        <t>A stated fact can say where the subject will be and when.  An issuer
<bcp14>SHOULD</bcp14> carry such a fact at the coarsest precision the receiver's
purpose needs, such as an area for a place or a half-day for a
time, and <bcp14>MUST NOT</bcp14> carry an exact address as a
<tt>subject-statement</tt> source.  An exact place needed to deliver
something belongs in the agreement between the parties.</t>
      </section>
      <section anchor="purpose-and-context-limitation">
        <name>Purpose and Context Limitation</name>
        <t>The <tt>purposes</tt> and <tt>contexts</tt> lists carry purpose limitation across
the boundary between systems.  Their value depends on issuers
recording them honestly when the basis was established and never
widening them afterwards (the <tt>purposes</tt> field, Section 3.3).</t>
      </section>
      <section anchor="categorical-prohibitions">
        <name>Categorical Prohibitions</name>
        <t>Some inferences are prohibited in some settings regardless of
consent, the clearest being emotion inference in the workplace and
in education <xref target="EU-AI-ACT"/>.  The tag lets a receiver see which
contexts the sources permit; it cannot make a prohibited inference
permitted, and both issuer and receiver rules require refusal where
a categorical prohibition applies.</t>
      </section>
      <section anchor="device-local-derivations">
        <name>Device-Local Derivations</name>
        <t>The rule in <xref target="device"/> keeps raw passive observations of an
individual off the wire.  Only the derived trait the subject chose
to contribute crosses it, tagged so the receiver knows it was
computed on the subject's device from that subject's own activity.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests IANA to create four registries under a new
"Identity Streams" registry group.  Each entry carries a value, a
short description and a reference.  The registration policy for each
is Specification Required <xref target="RFC8126"/>.  The designated expert <bcp14>SHOULD</bcp14>
refuse a value that duplicates an existing one, and <bcp14>MUST</bcp14> refuse one
whose meaning depends on a single platform, product or implementer.</t>
      <section anchor="iana-classes">
        <name>Identity Stream Classes</name>
        <t>Initial entries, each with this document (<xref target="classes"/>) as the
reference: <tt>direct-response</tt>, <tt>relayed-response</tt>, <tt>authored-work</tt>,
<tt>peer-attestation</tt>, <tt>linked-account</tt>, <tt>third-party-metadata</tt>,
<tt>public-record</tt>, <tt>service-interaction</tt>, <tt>device-activity</tt>,
<tt>subject-statement</tt>.</t>
        <t>The expert <bcp14>MUST</bcp14> refuse a class that names a party rather than a kind
of channel.</t>
      </section>
      <section anchor="iana-bases">
        <name>Identity Stream Lawful Bases</name>
        <t>Initial entries: <tt>consent</tt> (the subject agreed to the stated
purposes), <tt>explicit-consent</tt> (consent meeting the stricter standard
some regimes require for special categories of data), <tt>contract</tt>
(necessary to perform an agreement with the subject),
<tt>legal-obligation</tt>, <tt>legitimate-interests</tt>.  Each has this document
as the reference.</t>
      </section>
      <section anchor="iana-purposes">
        <name>Identity Stream Purposes</name>
        <t>Initial entries:</t>
        <ul spacing="normal">
          <li>
            <t><tt>trait-inference</tt>: deriving traits from the stream.</t>
          </li>
          <li>
            <t><tt>subject-reflection</tt>: showing the subject what was inferred about
them.</t>
          </li>
          <li>
            <t><tt>trait-history</tt>: keeping the history of a trait over time.</t>
          </li>
          <li>
            <t><tt>disclosure-on-query</tt>: disclosing the trait to a third party that
queries for it.</t>
          </li>
          <li>
            <t><tt>verification</tt>: confirming a statement about the subject to a
party that asks.</t>
          </li>
        </ul>
        <t>Each has this document as the reference.</t>
      </section>
      <section anchor="iana-contexts">
        <name>Identity Stream Use Contexts</name>
        <t>Initial entries:</t>
        <ul spacing="normal">
          <li>
            <t><tt>general</tt>: no setting with specific legal restrictions.</t>
          </li>
          <li>
            <t><tt>workforce</tt>: recruitment, employment and work allocation.</t>
          </li>
          <li>
            <t><tt>education</tt>: admissions, assessment and teaching.</t>
          </li>
          <li>
            <t><tt>credit</tt>: lending and creditworthiness.</t>
          </li>
          <li>
            <t><tt>health</tt>: health and care.</t>
          </li>
          <li>
            <t><tt>civic</tt>: access to public services or civic standing.</t>
          </li>
        </ul>
        <t>Each has this document as the reference.  The expert <bcp14>SHOULD</bcp14> admit a
context where its setting carries legal restrictions distinct from
those already registered.</t>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8610" target="https://www.rfc-editor.org/info/rfc8610" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8610.xml">
          <front>
            <title>Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="C. Vigano" initials="C." surname="Vigano"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2019"/>
            <abstract>
              <t>This document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8610"/>
          <seriesInfo name="DOI" value="10.17487/RFC8610"/>
        </reference>
        <reference anchor="RFC8949" target="https://www.rfc-editor.org/info/rfc8949" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8949.xml">
          <front>
            <title>Concise Binary Object Representation (CBOR)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
              <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="94"/>
          <seriesInfo name="RFC" value="8949"/>
          <seriesInfo name="DOI" value="10.17487/RFC8949"/>
        </reference>
        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="MORNING-BRIEF" target="https://datatracker.ietf.org/doc/draft-morrison-morning-brief/">
          <front>
            <title>The Morning Brief: A Federated, Identity-Attested Situational-Awareness Payload</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-morning-brief-03"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC6973" target="https://www.rfc-editor.org/info/rfc6973" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6973.xml">
          <front>
            <title>Privacy Considerations for Internet Protocols</title>
            <author fullname="A. Cooper" initials="A." surname="Cooper"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <author fullname="B. Aboba" initials="B." surname="Aboba"/>
            <author fullname="J. Peterson" initials="J." surname="Peterson"/>
            <author fullname="J. Morris" initials="J." surname="Morris"/>
            <author fullname="M. Hansen" initials="M." surname="Hansen"/>
            <author fullname="R. Smith" initials="R." surname="Smith"/>
            <date month="July" year="2013"/>
            <abstract>
              <t>This document offers guidance for developing privacy considerations for inclusion in protocol specifications. It aims to make designers, implementers, and users of Internet protocols aware of privacy-related design choices. It suggests that whether any individual RFC warrants a specific privacy considerations section will depend on the document's content.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6973"/>
          <seriesInfo name="DOI" value="10.17487/RFC6973"/>
        </reference>
        <reference anchor="RFC9052" target="https://www.rfc-editor.org/info/rfc9052" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9052.xml">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t>This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
        <reference anchor="RFC9562" target="https://www.rfc-editor.org/info/rfc9562" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9562.xml">
          <front>
            <title>Universally Unique IDentifiers (UUIDs)</title>
            <author fullname="K. Davis" initials="K." surname="Davis"/>
            <author fullname="B. Peabody" initials="B." surname="Peabody"/>
            <author fullname="P. Leach" initials="P." surname="Leach"/>
            <date month="May" year="2024"/>
            <abstract>
              <t>This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing System (NCS), later
in the Open Software Foundation's (OSF's) Distributed Computing
Environment (DCE), and then in Microsoft Windows platforms.</t>
              <t>This specification is derived from the OSF DCE specification with the
kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have
been incorporated into this document. This document obsoletes RFC
4122.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9562"/>
          <seriesInfo name="DOI" value="10.17487/RFC9562"/>
        </reference>
        <reference anchor="COMPUTE-GATE" target="https://datatracker.ietf.org/doc/draft-morrison-compute-location-gate/">
          <front>
            <title>The Compute-Location Gate: Provenance-Class Routing of Identity Inference with Wire-Layer Refusal of Unconsented Provenance Classes</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-compute-location-gate-05"/>
        </reference>
        <reference anchor="GDPR" target="https://eur-lex.europa.eu/eli/reg/2016/679/oj">
          <front>
            <title>Regulation (EU) 2016/679 (General Data Protection Regulation)</title>
            <author>
              <organization>European Parliament and Council of the European Union</organization>
            </author>
            <date year="2016"/>
          </front>
        </reference>
        <reference anchor="EU-AI-ACT" target="https://eur-lex.europa.eu/eli/reg/2024/1689/oj">
          <front>
            <title>Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act)</title>
            <author>
              <organization>European Parliament and Council of the European Union</organization>
            </author>
            <date year="2024"/>
          </front>
        </reference>
      </references>
    

<section anchor="document-history">
      <name>Document History</name>
      <ul spacing="normal">
        <li>
          <t>draft-morrison-identity-streams-00 (November 2026): first version.
Defines the per-trait source tag, the stream-class, lawful-basis,
purpose and use-context registries, and issuer and receiver rules,
and carries facts the subject states under a <tt>subject-statement</tt>
stream class.  A source entry about a named subject is <tt>active</tt>
only where the subject initiated the release of its evidence, and a
derivation made on the subject's device reaches a service only when
the subject contributes it.</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81963Lb2HLufzwFjubHeBJSlmRZtjVJ9pEvM1spj+1Yck3l
7JoaLRKLJLZBgBsApWFc3s9ynuU8Wfrr7nUDKNsnf5JdSY1MAuvSq1f311dO
p9OsL/vKnucHl4Wt6e9dftW31qy78/ydbafXrSn7/KrZtnObX/R9W862fdnU
+aJp88t6YdvWFrmpC3rN9PSnH+ZFZcp1d5CZ2ay1t3smOMiKZl6bNU1etGbR
T9dN25ZdU09LfXLayZPTo6NsTqMvm3Z3npf1osnKTXue9+2260+Ojp4dnWTd
drYuu46W1u82NOTlq+ufssxs+1XTnmd5PqX/z/PFtqpkyueV+WjzX3RK/rJp
l6Yu/8Ngf+f5RdXbNv/FtmVRmjp/Rwt/3Rf8oF2bsjrPZxjif9MirMGzh/Nm
nWV1065phFuLSd//9OLk+PiZ/vn0+Mmp//PkzP15dnzk/nx26p89ecx//vL2
/ZvLNz9Pn7+/fPXTOc/uDux6xeuvy3qZP29Lu6A15z/ZwrY4iIk/iSkdm+1w
Nldlv+XdmWp6cWdaW9uuy9+ZXdWY4oAHDwT7Krn+PwjWm3Zp+/N81feb7vzh
w8IQs7Rm/pGoVtp+cUgjPSRueDhghLVsbzrD9h7yUB2NbzvwgFvkZU3z1raf
vsTLI2ZKxpgePeK3aAG0qZOjk7Msw1jpmZ09e/JI/3x29PjE/fn4jP988faX
dx+uX01/vrh+NT6RF816s+3t9HUzZ7rkP/NU79rm1tamntspXQyi+vuG7hGd
XLMIV4bvk6Vn8ruyX+W/li2NY3ZE1fd2se1Mhac/1POm7ugNOtAwas6j2u5/
4inOlSSVkmS6JJL8F09z71jTo8fDU83zn1++e58ez3u73FZyKA9effiBHjw+
e3j25Fn+4Ge6CS2R9yXtCETt7ZwfC2/8sI+wtN/z/NW2bTYWpDJtVRKZ657l
4YtmW89LPrKe+MI/9qEulfRDetptO63sH4cWjxr6z0NblQ9bu3zoVvqw+Wuy
0WNs9NWH6cXl9OLF9dd2e3L68Pjs6bO8MjtwXtHc1fnKtOumLjtipnZb2S6n
x03bl4tyXhJBSjqNqiqXzJQPLsIXl/EXF/P+v5s+urchgU5Os2w6neZm1oFT
+yz7dWVr2qTNux3JxHWObXS0oIYW0dJzdC1zQ5oFao/+b2U6KBxVc/JttrEt
8eKE193auSXJ0eZ9U5hdXlnT1h1/I2NgqyanK7uAVpvbCT7JMB3OQEa8W5me
XymDAKB5ifXphBZtsz7M8+d2bradxWOZn3NuahqJ9+AXjXFkgXknKrmkI627
O14jrf5vW9IGrMJpZCYFKdmCzmERvfs90YTuwC3EElgir8r6oy2yDbEUxOUE
xNHpzWZT7fjdytyRsMlnpiu7Sa5yiklAf/f2j56GWZc96GP6bGarhmhAi7Jm
vqI9Xq9K2nUz3zKTFHZRkoKiuTuBH71Z0pQkCGhPEJCZJRrswvHI/mm1WMod
CU8eUt6D/KMlAbVgslyQRYZ18NoY12CMJpwdHRWRZlkSn2B4eSWfQ9Dy2Web
IH75U8fLzYzk2i3fvQkdLr09Pt1MJVkxGVGOCbbZtpuGBDp/q1ODKbzwz2gv
zEz8hNI35rw1sePM5tuOWYBocdnTdrY6ZrT4qSz+lkTqjEQGkVT3kaCLvNvY
Oa6/7CsjJjKzquxWfERCJ3k1JhSIjjUyK8rqRM6YwMWLpqqaO3qwrOfVtsCM
LfQdXxDdzN2KiKGM0AXey+YrO/+o59zRGUdM0uULYuFudCE6uXV09nbd2eoW
S+y2xBNE3TtIB/piR0LQ5uaWcB5tkk60FcLads0i8m5VzlcZP0j3hvbQNWvL
V9odCZYr83+0diNnLLyvxPUcSGPcgUWWRAyIJjmpwP3g5HxR2oruaF3t6Os/
N3dCli7DMt0FoG30DTiVVtvN+S9iJggYHMqcxOuhSMN1WRSVzbLvIMbbptiy
tsuyizr30DswqwpKwpW0wE5oiAvaeWkp1M0emLwoO+LaUjgfYm+9sT2NssO/
un4HUi7yu6b9SKT6QSSQk34qVkkA4ERwwXn0Do/Gh0hXtLDEXHKrIBuv6PSy
aF3ER0Rb8A/JpQ14e2b7O0vUlb109E60V6CQ23JuM5GSuH8KijrmdZKFJDOJ
txmVYU4n1YnEGAKKsuvokWxFX3TyCGRtTuxNV8a2EAMlbZ5GNksIN1xOXhke
U+XDhCj7DDqH9UivFI42D40CpsJS6DSvWdqQHuaF0sr7nqSbyDGay4tGTxwi
3cbWhfAwHXDGV4nujaoZIKDpJiAgkkuEKOjY7xNQNFMmAqiq9B1lcMBDJuW2
J0EHVhQWKuTYP30CQvv8mSZ9oYqCbwDkWiQqvZJSqQLuyKF15g1kR/pgpqQE
T9CFDN92fJ9pX6tyVqpOxJUNchPEhz7JnNayf5BA61S0vPqQX1wC5/gxHCxw
zGnXjRwB7d5ktem3AJTu1FQnEd+TAp1bJiB9aOnqCUQra9LJPZvWHcnWP+Z2
07O2WtuCRG7Fd9osLHErWBsTffrkkR9T8UJFpVI5U0Xo9TngXmHB6EJUsB89
SFdE9BUAjlP5RQmp1mWe+rEQ3ZK+LxVX4FhIfGzBZLRq4v8lQRwLSQZZms3o
PFgeC0BgEQ1dzBS4NdUWMukioChcICyEGK11iuxjTdqBzry2wlplJyKSVEC2
amrSCap1wz2AoMxnO/EQyBEpxKKzLQD0KoAebLSYZHwaHs741a5xAGQm05cL
fL9hfRZpWJbVxB7ZXqMvVZh0XLHh+PmzX0Jr/7YlEU+yvI7YWWUSLrJXIGO8
UeeCgdyZh3tODEXyLWeFcwdMP1+VuNR0UqqRzY6xlX+DSUSyJ6uarucXR/OV
7urxFZmy8oV+HGI3YmCS+oXgPLdBQf7ztumEhiTa6gJoYyicSTF9l/+KN3nQ
lw4QXgk9iVLZlLg9oMJJfqPI4GaSIETBeilAJPvgwadP9Nbnzz8c0kC43qxd
+eoKOJSRac52FyDWi5cvX9MpqsuGDpBBbO41NThG9Fb+4vnb9/ros9NnOGsa
41+v3r7RD08e04eZmL+mUjXTHfK27kdSMvZSbdWyLlnzYJWgCW9Ln6Stybp1
MAZDJEGCEIeK9RATTxIupCGcOHSEUaxWq35zUE1wEt0Ay4jG4BCWKYHlBVqI
p5+OlQ9xnx/MzCH1wNVWxnBP6kldJPTgDQWE121nfyX2Vog3GcyqR8U3yTi7
CC8DsZCAoD9Y1CVXkFYgT/L8YMq3gqWugKWgfBNzxSkmufa7fOVRWp6iNC9A
sgC5JwIpdUPGbwc4gRcx4fEcAMaAd7ZcrnqBewS0ZsSEOjhO0dA/ScxlahS2
hiQ9dNYEj5saoKfvK7mUtCUWxSQpggmkKzjMnAnFCrwrl7U805VeyBDVWFtC
0OoDfgmCrTODTb14e/Xq9yt64DioDbkRcLN9/swgkb5m7qa/E/sj+/QpcYbi
cWxFMRbD9ADIhAF4iYQHvMnpl/V9x76NZQttF/AOjjm/JpRf1k3VLHeCsD4C
ojctSYiDXz5cXR9M5L/5m7f89/tX//bh8v2rl/j76s8Xr1/7PzJ94urPbz+8
fhn+Cm+STvjl1ZuX8jJ9micfZQe/XPz7gezl4O2768u3by5eHwiciHmPdWUD
aw+bajetBV+QKKcDm5NpK8r6+Yt3/+//Hp8Sxf+XOqZJMsk/4Jqmf+Amymys
QOWfsFAysvEJkfKxVBXJ2E3ZmwrXjAyCFTuS6NIQ9f7hL6DMb+f5P83mm+PT
f9EPsOHkQ0ez5EOm2fiT0ctCxD0f7ZnGUzP5fEDpdL0X/57829E9+vCf/lQR
E+XT46d/+pcsy67kqmTnLDMH2M87k9ReAmrny3/OAs1pX2dL6bULJqlxdxND
AToVJLPolU7cZH2ztGI9QDnEnqYIEtLctuSnHASf7YKgy+Cpc44KwROqAUvW
iSJub3RlU7/mm4mTpLMdVhJJYXb5qCI2nXtsIFAlDsR08FIYCLK27BWMvChj
6mwZxQESLltTQ7ZjoQrdSSyIRRUbLcAod436saBrCH6wsvHAlAZx7i25UfS4
RqCYlqp9YJ7ZP0hOAzkHw4Sp5Hcl/1SOIAu24PXp5ox7B16y4OVTf6Kq/xKn
S3rU1Gbq1Xq8DjkWdmzRiKM5ajjtxcQFZiLVRAC27Xfn+c3G2nZqOCrE5L0R
MMhgDdY8FIfGjGgMZ4l34jZmPUX7fDcAh7RX9kuk/i/2Wa1NYVlUCFRi7hv5
lwCHBoB5IO+ZqyJyQaofDMfYExLxNKVVX4qdLufiXMDY9z4kQ8+/Vwiy5w0H
V9J3+B4x85FAhsO2ZH4kKzkXg1/shiz70Hnr0w1OGhlbKdW/FGMlyHUG1DKo
cZN5KUHDr0q2RgsiYsd2eMua2dmYJJKYHh3u7pDv6PWI8zzfKRwkxmPFSIvU
UPA1AYJP3wFFMzB6B6uWkX/2igWIc3474CjklVvLuis9a+exM5lH8mT5rme2
PYfUa+qpXW96eOVaI8g4QPQScA8X0Tl3M70gX3Tujg1mR4vWWh2h8+viT91s
6j2SjTntRsttl/4RrCUTIxoCyQ1Hp9jwUiPTwg/QrEGxsGA6S7eTmTr/QcPw
vd6ubk0qWX1BQ+rJ6IwLGKmJG3qMe9RnE/CREs9vP6GaWbqva4wNA4PgAYBo
xpFwtb4gNGa0fu/Ai9EX4zwGgLAyaW3ews/U1CX9yZ6nIdoRKH5FxufaZNnf
//73fF4UVSaXcCpH+s/5J2gk/tv/7zzvaamT8MGP+gRk6MQdaMDkNIKo3mgE
Qs7RAH4Efm7/EH+KVDIPsaga0x+f5Q/lr0cnE4g+BfZ+or/8o37224QH4aGL
sBNEuCYZ3T69CbJj4Rd16O/dcQhokPAgnr5SBjj1b3+JXs3G/G3rVV5rA4KI
fAXybhRfEOqweSkxDz/BgTikDogYB+rxOMCD4mb80kqiwEys5bESZ9ZGpMTr
v032vOsejmzfb3pvG6R3x+dzR/qX1J9/Vw5Izum3yY/5omw7wUV0Nn2sIvn1
bgXE4V8f8whNf3R4BBF2fHjk2Iq9MHQKeyn04f0lHmcnjYdG0PhbWTEZCdu2
ltfve59uhuh8QMNgI2b5V//348COBJYUk7MA1w65g/j3gL2Pwgvqm5zSnSai
EwkPcNFFxrEfJfGc5FsfKINrUUUfIyOgvnKtFjMZOtmjR4+ecXh42tPnLLvq
JQsZdlUOPTIQNT9x7OWKxA1hqXmXkY6KrtmN0978GUk2AYLsoXTS12F49QMP
U6GQVDLEKuxDSbAfILPOjDlJBelt9NfQk5wfmtDRE2vXDm2JcAoLwzXDs2w5
L9iUlhBUMEHkmosjSYGIU0WGEYP32jIyWZueUQuBaPqwtbfOHRorXkZAhjTj
nATBYRboBB04s+EYhWQLDb3xR25B4kT0+jVaSge6bUifm/luCqxPp+u9YX4a
IlYjfgu1A2gEUQLeAKA9tgE+t85rInZF/PlC4ZPzl0BDkklSEJaQHUSGHK2P
ZW3+4cPlS/V8PD47IWj7kaAkZBdCiV8i/9pacXh1NvarglNvwp1yPPkNAeok
wByBJZwMhlDG7YZ2ShobHgWTHRuzDTPA8ewtZr+wsnphq3LGaWswqQSIE637
5qPlREOFzkSAxLRApCXnKB9uVlESitiaikZ/v6VPnuD74IfECcHIYWcjYDEQ
GLvXxN9/I9LnRjjl0ydRTHQy/BZ8b4Z9vWAtnh1Gjbce5ci+71yAhegleATn
4rQeTuXXPdkASlMIyDjOLy+RuSZj3sgd5UXwHA5Mx9PzATYVHOKiTeUtmqs1
3uUGY3kjWYKpbGDDuWaUObMrUy2welarjqGSKKAsQEyVUZYCRwM1NVQuSNiw
2IOelYbiMH8tszw3iURUvzJkIjuwVSI6De55fpw48X03dg3IFjiI2E1iM2i0
mnc64B7Z7ObCUvi6QDAygft4JQb3Yd60iGy5DANdAIgVMikKNi1Aq4FxQd+y
ae5irpFeLcqC3c5mCRMFcd+e50e8q1zbgeS7g+jSbAQaUiT1DEEo7znktAss
wiJhi75mD4swsgAeR+oYBN2beMKG/8K0+E/E5LxJvD1Hul/xJXaApfxCp9nL
DsFMZY4QKOYW2bP6V8F3Pwobyje/SlFAuNDqErhhrOaGl5P6PsqLwFyQF2vI
fZ3XpWbF24+E7cTHwIDxsDwCeS6rBbPxBjgOKwaLZQzG0YbtWkHhJJiJvKbO
RQVC2kwddCZx3q4bCfkoF1YP3EFMhhyMCU0/dk+smqpwVl6LsETkiu/YTuSE
BniTnHdk3+1k8pQVu/9pIezDjOBBcGjtkivAqRbs3BK+96EYF2JFBHmgpml3
AQCHze0BvH2c5UfoN403OfYI5lMAupJvVthN1ewkM0XGxaLi5Kbg/YCi20k0
No3CSNJPFLNBLkG3J7+H8OqrP8x6g/we7+CIWDv4NCfquVdQOobVh9kFHQUT
QfCzlYEBNmB2/xVJP7A6D3iaAzLnIPfNrGmZg34nVEDYcv1711S3tF+27A54
PDy7Ij6Rj4KBTJ8fHZ6xRXygXEsf/YXtjU9qdRzE6BsDFQSC5mDSbgM+4jGj
B/HI2eJ4fmKPzPTp7EkxPS1O7PSZeXw8fTQ/WjyxJ7NnxfFpeC+gGbyrZon/
1mlmfBfbrPwlS3WhBLN0NKhTI7QfIVjIsULwpyi7edV0pJ+nTT3lhKOD36JJ
Vf7hbQ0B4y2wAd+U6FmRf/wkcqGnR0+nRyfXR8/Ojx+fHx39H7wmnz+bPjq6
Pn56fnrEn4cRWObwWTzhjz5PvnwC4lSfKpjedwDzE/PstHhyPD1aPLLT09lT
UuKLs5Pps+PisX1ijuaPFk//Ow/gK5ROvnYikZlYc5NdLtmh3pGH+txDt/GD
PcSVWgRA09/IJmYDN0rzpctIgxRjKTlIgQqMQxoik0w1CX52QTsXDb8hGZaS
icRsM0mdzCSC1IvsnNGaFCNrcloQOgBxwCRGP9FY+2POpznjkLlT4Wre5p++
c+YspFMSyHChShGvGsaY8EykPG4lJqTnUaqkz6B3OmcPliA8hKMa76LbXJ6E
S6Ig4p+T8B8IDW/FeyjNWTOaEFiKyaD5TZqMqvw0EWAT6RYBxl3fNDiECWM8
OGK8vse/Ahr2OX5rUUqV2dFd+qaFwf8/I3uJndurttkuV5wuvejvOH91KcYx
LhDUTT80VpgGAD8ksEUp0zZRP+UMg8SuveZzaZx9Ew9F2AMRIo7dayDJJxqm
oUHdwMZlwW1WrZFMXyx41nFsIjZ5oVk1ussZD3AfIHP8Lh+dIegnFQhEQLA4
W1z030Rjw1nh8yQ5kdPVR8lBltDytQ+tALO0Zc+pvew1YE/Jpmn7RVOVdJA9
56CG2p2RrYwRsAi6kFZsqlEAbm8wOF40W5uznc8V9R6IQuPMDsrpZXIiIsFL
mBbTp+Iak3Phi8uA0c9TovFFk3A2SYhiKnDLuUvAZERJzlyVAKviF+90YtNM
n0ZxAR+T8981C+bSufU5ZhOOUDPBJuxRiuzOJEE0zTYSGZSfsh0QLXS6tr1B
Qio2+5Pk2Axp/D0S3siCwxmONqp6RrNZ8pxtXASQJ2Jg9CT1O07SdFZ2SGFm
ISwW1GZLht58Ktbg+Gozm4C/XB4mp8HIS9Uuyken1zdbhu/PLS6PPBKOfY06
r9Jn6iG4FRONrRjZ0ZTtPjN3bOhiuF6WOVPaGzq4vp4cPnXUyws1XRVVEpHa
jvM2JczD8U0mhXgxpm6rfAV8xYkblc/hG/wdzr3QujAeO2ZYCvG7D4JDR9yo
o1wGvoGcETbKJisiES0FA5pswwmhsshO0mRyX3PTf7WoICoNQWo5qVMc/4Sz
McRoTKoN5LlBtYHWCki2rux8JBUnqq+cMluI8filVLc39i7Wl7kpiuArooOc
22LLKW17ExQykUFstTmtvj9DIXH8RskByAAMlUYbKVEAWVIVzwhDIvrs8wO+
UEmQZceHwyitCP20ngjFR1HA2qc0MrMBno2D1UNfsoRt95epYARFULbertnp
FkWeFUgELy0E6Ax+AMnB5aCtrML76DQH14raJxKcjDYq4iUJBaTFS0O/MKaQ
Ki1G1rmrrvQZsUlGh/NgxR+yAUwU/WiH9MFiapGKklRtFsTYSKvugrfF+VYe
jfYSkThOy1XSxT5vzrCqcQddpGrb+6D3N7qrJ5o3c8/xujQkScNyQkIzr+Ll
YYj9K7wZhbZuJJ/A/zsgYT4WOhTSlAqKzAgkwCnkCmcYdXDmnubH6LGwKySa
gQh9epj/RPdpCAV4kv2KM7gNRM4npwR4wEn7I/0sYph9IjQgtoe1eTq7T6ud
xos4GMVP9F9FDAoZFF0ET7D4NslCgw9a4aifXpLBsuzxXlZTR2vk2YSUC57P
3BUS8OKdZbanbE8NLhRL+NNLZsEAN94Ou4F0u/G5Oursr3fecyhETIS20EAL
T1A9l/91SwQqyrkEdkS9sBYqY3SalMGIdGGpJRaf5LppuwUuPXHPcyIe136E
chlHCsjSjj2K2dlhzkW2zlyV0GJwjuG6MKtOYrHGtCGbaSN7KsX61Ighb5+P
Rs5ShRq3nRDTgAGPrsVNQEu/LbsSHEUvJc5MpQ0uD6wzjnvS0p8chroCETOI
MSFZOrZUnbsuudpEPUny8pEkn0Pbpg57MUjFZLO5IA6OhlXWdBJbj3ZJ3GVv
NXskuVhazCruBihNjXY6KuiVRimUGnmPDo8lJjYoRIkKGAR5RlqB1d+dQdXh
r1/YSd0o2pkzq8eHilHuE+LiPPV7Fbi7R9TyZfN2aMAqnh19hBgmlfiDoyR/
RVpOkQb4aCQvQRSlAceJB/WlD/MRjInifFf+zZeCKz99p7BSUhP+S3VArv4H
QZdBUPDbo56CSH1R8X2BSRWVLuMtKheCDuTkLC0cC9iZfUkEOuS6twQjnceB
yQyg3kp8W5ebRcuN2O90L/MtuaiU4QQq0RvAj9kuE8grPBVHXWeEJhDPcRc7
WoOLl2gydnC3cMYBbGciqu1WyuOq+ZVjQxW1y63LYDe1HLxLXtACBaXKUuwD
HvgweNyTrEO9QiEoLIghxIVVePhI7yTbI1qCXHkwXOrIHYMVS85DFkf34xQA
BrgVZ/Qm5ercv6aqdmMDTem7/0XHH1onIOyXaRH+/ZDOx7ZHYsFk0anvi3dG
7jQ6W+GUOhznYKYsBMTHU9VRMnzsu9nDz/clHUiikK9GUkEhTZFglqjEChwi
6DDJtpcVrUyaksGSeI/BynAglnJsC3Yhlue7Srgb0ZmyCLyuJ8L+Rr4hzl1x
2xAtcbysboDKx6aUI6xLxN9bHGBCAC0S4P4AtawpOSzJxZAxmUGSEbxrQSx9
VA7DIesDj1b8N73aKc79Ej2DUdbW1OzNc/Y5cdItck0lIoessP/gTFTAlvm2
BVswo6xNP1FEvUGJUGR/jUADX/qvwoWQdcIEKrnwUxTR3jst1IoEh2T/e4wh
oNTJ9Lso7yC5hYqZOOH4JgTfbtQD6EdRvmKz7DoEJJhEQMUaaBdms+k15fi6
jsIZPJIG264V9yjHXoV5upApJS6Skv38SwQsTcX5o2IDDffhghp+PSIx1oJZ
kmXF8JDddcQzSF3vhoBhHzL1sNQBCRg9mvlrxOzx2Naj37FzkiMjp4f5nuis
2XeRvLsirvThM1I3g2JUcQz7Qt3YVHDVcJF0QPOMER7ykx5KeCaUSXK6j3Yz
KJwtOkeLt1zLRtho1Cg8qog575SzjH3+W0Xylw2XVlbXbVv2QWwa+mY38eXF
vnAo+xJB2Pvj6jO8/8fHo5KycvZZsTuL3RkKMbvQekR6lDSbzkVJOFMk4wPj
DS6IJTuRhZdxToe73YSAh8n3E1eBwaULJFK86ezX5QWfi/mFpkH+q6Rq5MRP
P0r1l1yAr6X5u0OPCjSTBAeeFqqnj9eD0/cJbY94DWwWxVLPZzGkkm7ki2H3
yre6Y8Zra627yPiO1GgVrZKgCwQ1y7vkmFz13R6LQoXKbrCNPY6adDneTSQr
ElV5+lXaJLnDk1zz63w1dhCW7HxI9u/d+5DqS3TtuvfwvBUp8xNpVGWB6igF
09mw97px04lb5Ho05JhDxah3o2zrCqEbRjNBMuncsNvVhNfn48rEUJ6Lysm2
RYINr957UpoFSy5ld3EwfMsS2ZiMHTnfukpHDM7kdZMIXpMyLOvK5YOPqPuS
L0e8z1XXSF8j69yU3ucsHS4kqDBw8QT/TuxygSGBEXjV4rh4bmlyzWn2+Acp
2ZzSk1vOuB7YhWn9mCsgw9EW2kyz8+VkA1ZT3ctSnr0eiXuFXROMbYW6STUR
S8JExBm50FG1rJDbKVHJCEAdA+nrpu0jJxJt/ulhfFDCaBq7CD3BeC7puLNH
eGL2bS3h/WK4uMK3L2PIEBJMEfxNuMTfOtcsiaSNvXNXBhpenyycZ4tnEdSr
zUbY/zU2C8AJ2u4M3XScw/xZsvegMwQIB2+Kr8GdpalzcifumXOfKXIP1B94
zcP8MYig4RyEQGmlZIswsc84dOD1VtulrYQc0knSFEiTbGv1CZioKNKDH3H5
wkvgI0giSpiE7OcctdJzIgQ4Rmy9yAHrGyUFfyZW4fUIMnClNwJX83CaqTW3
FtnUpZpdPPBgNIS7OLqnppEiG+ne2K3KDcZ8y1u/in1JnXidvtTJTa2IRN9+
3417KYy67xHXS83wsIQAR500VfDamgBkwEv0quTvR3pHzOapw+LOuxUnhnPm
cKiz4ts1aEMn/hdp5+DUatTqSs7LiSffeYg//r4b3/xSE96bYhdgMmLcEYr5
XbS1G1WrVNYNEKJFCZF4TZVbXZnol3yCe5ywcxRBTlylJnhi1A3IhYwTHcE1
DBq4w/pdhq1kYmcMfSHUPtpdyMvYmLJ1Ufnh8ToSC4sfDvqcxDWhBKjgjpON
s9jT0mPXKU37nDQceejlNqhMkR252I3WNYl9m0Akbc6TkR0rIW3dg+lTxyqf
LS/8dx1sEpahSdehUkqqN6R+Ks42mroxfeGRa7dV1tmeyiJJcrPzLSNtNDIr
uQGz3M7vvst/KTvtVldo7bTeWm2pkqRWBPsrwR7Inxb156NP+vYdOn8K4vUn
x+nk29DOKrwoshENqxN3AF8lGjBy4cZNwVwZUrcvtQBNhYBBMq8hNe2Qxb/4
BDlNEauCPhFRbF1TVHhVoOAJzvASATtCq0h2C0wUpErH1Ki9J7FbzwE+0cKx
91z9rPe4zXy0YG46bxs7ndVlyZGgQqHaMlOboUcGUoL7whz6PgGdkxHSHSBp
DdDFsVlN0WecQ3cUmG0uu4bevbU+mtoDNXKriSTgtWFeduNkDp46AmzKja2k
gWSbJspvi9KVUHPdtpR7FPlL2s2ypWsBw1nMeFeUoHySFKLNm22Ff67pcEfV
+F2TOa+AwA/2CmsWJORFFKPuWI6KmhB9oOG9jHFowF50xmgzgPUGIR7Vte+t
Ls98ry+Eucgw0iIU5/dNYaOiEz1nN8YhGmNy8shHVMPQHJ1nR4JTRAHngcSt
jG1wP8QEDZBYOZ5IFCSkzYq9xjpsW6upDo6hoYDLOSNSzuu1YccoJrvWZM8Q
qErcHXI4AkLHGNQEFAo/J46VneQkqJ3PlIV7Wy5L1gNC7KinltN5HGXmuXo4
2hamqjKDUIdvtscOw1WzcVV5T0fbp5OYlYUci6QzsWMbxEIkCgMQdPsxzlPm
s+LOAp3r0TxrGWzsydbJ3Kp1MfuaJ7v7YCrrmlFmmetKqV0OgmuPE1hitOly
cbQ5QuiEtkLhMEee/Kwtfjyg7lyfLFbYsRDnsRmQ8O2HJ21Jp3Q4tLD4MkZ1
jhFFK9vHM4qJNlPzcN77JrXtUGZJug4u0UBuoU8zQSWHu0tvBHElEpdJ5+9E
NY504LVczegzWbD22dcgLkAaszQ6JIW2zZIBmmmKu40KlHxToMScTbu+SZow
t93NnNDDyGhe8tIPmQZ2X0h2GlyJQ2WPK8ZJCEkH38hpEPUZcdyhNacIZiL/
DXvPXAJcbIfROfumllyX41X9zrcsCtm2GtufqLFrOU7ps5h9suIkd/F1HsfZ
Nk63Za7HpGSZou37HFaDxvvjRkaqR5JC3XljWk52S1HJFxoSDdsRuVprGNWa
xHypenFUqh2e1kJt67Og4VxtfSV3VJvNafs7AZCH3N5YEZ+Hm1HpPPZwZyJw
oFUFIQ9dJB1uV7g5pHcZfIM6JE2s5D+HQbxtyINlcnl8LlJhTaUpN+LRCo0y
ObeSNVcgb1itZHxyuXjk40bbVVVwhwo+a2L+zimIYeCEpT7rYg/VcXJSQsI3
O9woHC1Ksdl/Ls4y/+aXLoIsXnvH0CZ9eSZqlLmQcrJHssW1ea47Jwprm410
MprsjwRJC506EbjeaYoNHWYhaFXHLI9rB/qRuhuFsu58CoA4OoIVKFegDmYV
fgIAJcY+OChqBbSQ4DAXvrMpaGPBMwy3sBQw+7KHOFF45i29OkbyWWL1avKE
eF7Uh8br7RjrqqUWO/VIJCRyPXIPooOsNc7tyz2M+U9UiU+xa4nZ76k4lsVw
+QyvpChaeGGNNHu6N7jD25JXZDqsSAgNKQRnm8+CzuWXBDqXdM6OGL5FDsE6
z4uY5WhYFfm/tbY4fw1FoXflOk0o1LCrSwIU/pedOYpV/u3ost/f5JYvA8kC
CY9IsQwneztEL5FbRZZrwlAE5nttysj72VtALrYSN7LmUm//fpR1y/kj0eb4
fk2iNLFH2u70RZQE+C4kAZJS/8bu2i6lEB4dmprd71CAct21WSkqg8GTM65k
UHd3nLG4p3l2ljTPHnbCduihsn3ScBb9jqRzf1K17ryL4qn6MWoFzVmFJt2Z
qzvxKQDC79w9Zp+hJFBERbsEAETIkDgzX8uzdOlonIkDsVHFuWnCpowCWV34
nhXocwtv6d2+DDINGGdR8pj77Q/N13nrBLvLEwu/LOLEELeWydKqNuZ6zraa
OPzYNWnUQAIdZZ/8Asa9XTQ0PRyenrT6TVOSJP//4s3FHtAZu6xAfIsby89i
0TC5kE+5beMWyZJ3wvZSNv65stD+YUlIFRbNK+jCYYDPJQRkHdK2NZl7I4fK
UXOvxb3W52GFlSUUHlrZ0TYSl2/+Xhip0E7SxydnnuWlOy8rEfsHuqepWsxc
1Mln08BVtyUGm8vPYUTte9PYjL4IX6Q4GDR3JpZXPhvqywUbXHlGvDxs7hAq
Q5NCkiy7TPtbTyRyrx69+HSTtteuGNMT+Xyf12pcZUmfpZWDkz1VepNRvvzk
nmT5ybDUK3RkSQquJvkozW6yTyuqL1mPNT4bo35bcbor9hb3TRwtETyeBTy+
/zTizivuSKTZyuhAzj1s04zEcRik17xa/G6QapsfaMe0C6JM2U/D+85hiPZG
zpkiPgaI7d5Ahxas8Pm6rCOJiqvCFj9qfFWaStQYJ/GDoEv+8aeb7EFtkQYC
fUzLI1pKr9c6QgzBZSzb+YHOoyLtVU3D7wswI9AyCO2gkRgfKOTLjZMJK9fr
xDfEV8Mi3P295HetZhzpfX+ZMfXRA/9mUMV+cy4SO8qcH/QzQRt1z15aIIEN
nbPN6SnvsKazidJfwJKCXhlLVkBb7Zt2R8NA87hh9NM4jMYF6wCJ/PKelgfY
gnzqfWqie5pBipF2dMdLrrs9THwaVZx4Gns/d2lnkt33pRJb/nGsPO4jYrqP
0MD7jzT/tiONm9d4Ief61dxzrFrlTotHXr0W4jNj+ugEs2TiiOO9hxyEcyjd
dlv20u3Vrl0TErEcUGhqKlfnxe+GhIXzKP4/iZrGijEIOcyZ8vQOuryUPb1Q
kTpwnmT5kKYAOEd9Dp5c4UcyV/Sk/JFrh2hhhDnx7BzTSgkw7qYUtKrM5Lg7
PyTCQBL1v/VcRDsmKpE3iLRgl8AhhhbnmfjGB6LRx5ROfzMgk+qZ8GsePnYp
P7Y0M/OPwCn+Zyz+LNcCJ/313z3NH7yhO8P5XejZ8cO5tjDSVnKoAH4ZlW/Q
FrUDavzrGOH+T7UAUOqpp/JDbVmepAORVnEcGoEjDZPcB3AnWgE+/umt9IcZ
PMbaV4KbJ5kG0us6zkfYX36H3BtNo0Xt7LcU3WitjcsHcAU26lXIvr3PW4vL
INmj6kvzjfPTtgcRTuZ4Vfafwpzs8Ht3AAA=

-->

</rfc>
