<?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.3.13) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

<!ENTITY I-D.agentic-ai-usecases-requirements SYSTEM "https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.agentic-ai-usecases-requirements.xml">
]>


<rfc ipr="trust200902" docName="draft-curtis-agentproto-cross-owner-usecases-00" category="info" submissionType="IETF">
  <front>
    <title abbrev="Cross-Owner Agent Requirements">Cross-Owner Agent Use Cases and Requirements: Spending, Delegation Depth, Ownership, Disclosure and Retention</title>

    <author initials="J." surname="Curtis" fullname="James Curtis">
      <organization>Independent</organization>
      <address>
        <postal>
          <city>Rocklin</city>
          <region>CA</region>
          <country>United States</country>
        </postal>
        <email>james@curtis.rocks</email>
      </address>
    </author>

    <date year="2026" month="November" day="19"/>

    <area>Applications and Real-Time</area>
    <workgroup>Agent Communication Protocols</workgroup>
    <keyword>agent communication</keyword> <keyword>use cases</keyword> <keyword>requirements</keyword> <keyword>delegation</keyword> <keyword>privacy</keyword>

    <abstract>


<?line 34?>

<t>This document describes use cases where an AI agent acting for one Owner asks an agent acting for a different Owner to provide/receive information, process or store data or otherwise work on an agent's behalf. This communication can be unidirectional or bidirectional. It lists the requirements that those cases place on an agent dialog protocol, mainly in five areas: a spending limit that stays with the work as it is passed on, a limit on how many times the work may be passed on, a way to check which Owner an agent acts for, the sender's control over which information about its Owner is disclosed, and how long that information may be kept. It does not propose a protocol. It is offered as input to the working group's use cases and requirements document.</t>



    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-curtis-agentproto-cross-owner-usecases/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Agent Communication Protocols Working Group mailing list (<eref target="mailto:agentproto@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/agentproto/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/agentproto/"/>.
      </t>
    </note>


  </front>

  <middle>


<?line 38?>

<section anchor="introduction"><name>Introduction</name>

<t>People are starting to use agents to act on their behalf in ways that have real world impact on their lives, relationships, finances, and careers. Businesses are deploying them in production workloads to deal with intra and inter company processes.</t>

<t>Three big things can go wrong when two agents meet. Without shared rules the Owner has no framework to agree upon how much may be spent on any given task. This spending can be either a computational token cost or real world money moving between the requesting agent and the receiving agent. There are also no limits on whether a request can be passed to other agents down the chain, so an agent can sit in the middle and forward to a third agent that the sender was not aware of. Finally, nothing lets the requesting agent share only what it needs to complete the task as approved. Agents tend to default to sharing whatever they know, which is not usually the intent.</t>

<t>This document lists use cases and requirements only. It does not define a protocol, a message format, or a security mechanism, and it does not assume any particular right answer to solve the problems.</t>

<t>The working group's use cases document <xref target="I-D.agentic-ai-usecases-requirements"/> covers delegation between agents and approval checkpoints for sensitive actions. This document adds the case where the two agents have different Owners, money is being spent, and information about an Owner is involved.</t>

</section>
<section anchor="terms"><name>Terms</name>

<t><list style="symbols">
  <t>Owner: the person or organisation an agent acts for.</t>
  <t>Cross-Owner dialog: a dialog between agents that have different Owners.</t>
  <t>Requesting agent: the agent that asks another agent to do work.</t>
  <t>Receiving agent: the agent that is asked to do the work.</t>
  <t>Allowance: the most the requesting Owner is willing to have spent on a task, as an amount of money or a computational token cost.</t>
  <t>Hop: one hand-over of work from one agent to another.</t>
  <t>Context item: a piece of information an agent holds about its Owner.</t>
  <t>Retention: how long a receiving agent may keep a context item it was given.</t>
</list></t>

</section>
<section anchor="use-cases"><name>Use Cases</name>

<section anchor="a-personal-agent-buys-from-a-business-agent"><name>A personal agent buys from a business agent</name>

<t>James asks his agent to find flights and a hotel room to Austin, TX from Ontario in Canada. His agent contacts a travel company's agent and asks for a quote. James's agent knows a good deal about James, which airport he usually prefers, where he likes to sit, his frequent flyer status on certain airlines, his passport number, and that the trip is for a technology conference. The quote needs the first two, and he might get a better price if it is able to share the third. It has no need for the last two, and James would be upset to learn that they had been sent and an agent now has that information about him. He is willing to pay a few cents for the quote itself, but no more. If he goes to book, the company may need his passport number for that booking, but the company's agent has no reason to hold it after the booking is over.</t>

<t>This case needs allowances XO-1 and XO-2 because the travel company should know the ceiling before it starts. It needs disclosure control (XO-7 to XO-9), because what James's agent knows is more than the task requires. It needs a statement about keeping (XO-10), because what is shared for one booking does not need to be retained by the travel company's agent afterward. What is retained by the travel agency and airline systems themselves is out of scope since we are focusing on agent-to-agent communication.</t>

</section>
<section anchor="a-business-agent-passes-part-of-the-work-to-a-suppliers-agent"><name>A business agent passes part of the work to a supplier's agent</name>

<t>In order to produce a quote, the travel company asks a fare wholesaler's agent for a price. James did not choose the wholesaler and does not know it exists. However, part of what he has agreed to spend is now being spent there. The wholesaler could in turn ask someone else. Then the wholesaler's answer is lost on the way back. The travel company cannot tell whether the wholesaler did the work and charged for it, or just didn't receive the request.</t>

<t>This case needs the allowance to cover the whole chain (XO-3), a limit on the length of the chain (XO-5), an honest account of what was spent when something fails (XO-4), and a way to ask again without paying twice (XO-12).</t>

</section>
<section anchor="several-agents-of-one-owner"><name>Several agents of one Owner</name>

<t>James also has an agent in his car and one that runs his home automation as well as an agent that deals with his finances, another agent that is handling his legal work, and yet another agent that manages his calendar. They all share his calendar and location with each other freely. None of them should share those things with the travel company on the same terms. What can and cannot be shared depends on who owns the agent on the other end. An outside agent claiming to be one of James's would be handed everything which is not acceptable.</t>

<t>This case needs a claim of ownership to be something that can be checked (XO-6), because everything else depends on knowing whose agent is asking. It needs the sending agent to decide what goes to which peer (XO-7), and it shows why an agent cannot raise its own standing by what it says about itself (XO-9).</t>

</section>
</section>
<section anchor="requirements"><name>Requirements</name>

<t>Each requirement below is something an agent dialog protocol has to allow. None of them says how it should be done. They are numbered XO-1 to XO-12 so they can be pointed to in discussion.</t>

<section anchor="spending"><name>Spending</name>

<t>XO-1: A request needs to be able to carry an allowance (i.e. the most that may be spent in total) including anything the receiving agent pays to others to do. The allowance needs to say what it is measured in, for example an amount of money or a computational token cost. Without an allowance the requesting Owner has no say in the cost until after the money is spent.</t>

<t>XO-2: A receiving agent needs to be able to refuse a request before doing any work when the cost would exceed the allowance. The requester needs to be able to tell that apart from work that was started and failed. A decline costs nothing. A failure (partial or in full) might not.</t>

<t>XO-3: When an agent passes work on to another agent, the allowance given to the next agent comes out of the original allowance. The next agent is told only its own allowance, not what the first agent was given or has already used. The total across the whole chain cannot exceed what
the Owner allowed.</t>

<t>XO-4: Every final answer says how much was spent. When work failed part-way,
it needs to say what was spent anyway and what is still unknown.</t>

</section>
<section anchor="delegation-depth"><name>Delegation depth</name>

<t>XO-5: A request needs to carry a limit on how many more times it may be handed on,
and each hand-over reduces the total allowed handover count. At zero the agent may do the work itself and may not pass it further down the chain.</t>

</section>
<section anchor="ownership"><name>Ownership</name>

<t>XO-6: A claim that an agent is acting on behalf of an Owner needs to be something the other agent can check. It cannot be something accepted on the agent's word alone. Any agent may decline to say who its Owner is. It needs to be unable to name an Owner falsely. In the third use case, James's agents share freely with each other, so an agent that could falsely claim to be his would receive everything they hold. An agent who is forced to identify their Owner could inadvertently leak information about their Owner.</t>

</section>
<section anchor="disclosure"><name>Disclosure</name>

<t>XO-7: The sending agent decides which context items go to which peer. A dialog needs to work without any context item being passed on. If the protocol required context to travel with the dialog, the Owner's choice would be overridden at the first hop.</t>

<t>XO-8: A context item that is sent needs to be able to carry a label saying how far it may travel. An agent that relays the item needs to keep a label at least as strict as the one it received. It can increase strictness, but never decrease. A context item with no label is treated as not to be shared. This is the safe default.</t>

<t>XO-9: An agent cannot raise its own standing with another agent by what it
says about itself. How much one Owner trusts another's agent is decided by
that Owner.</t>

</section>
<section anchor="retention"><name>Retention</name>

<t>XO-10: A message need to be able to identify context items and how long the receiving agent may keep it. That can be a period of time, or only until the task is done. If no length is defined, the receiving agent does not keep the item after the task. A receiving agent that cannot work within those terms needs a way to turn the item down. In the first use case the passport number is given for one booking, and there is no reason to hold it after that.</t>

</section>
<section anchor="peer-supplied-text"><name>Peer-supplied text</name>

<t>XO-11: A dialog needs to be able to distinguish what a peer is asking for from material the
peer is merely passing along, so that the receiver can treat the second as
information only, not as a request.</t>

</section>
<section anchor="repeated-requests"><name>Repeated requests</name>

<t>XO-12: A request needs an identifier that stays the same when the request is sent again, so that the receiver can recognise a repeat and avoid doing the work twice.</t>

</section>
</section>
<section anchor="relationship-to-the-working-groups-scope"><name>Relationship to the Working Group's Scope</name>

<t>The working group's charter limits dialog context to identifiers and lifecycle state. It leaves out content such as memory and prompts. Nothing in this document asks the protocol to carry memory or to understand it. XO-7 only asks that a dialog still works when no context is passed. XO-8 asks for room to attach a label to whatever an application decides to send. XO-10 asks for room to say how long an item may be kept. That takes effect when the dialog ends, and the charter names termination and revocation as lifecycle the protocol manages.</t>

<t>The allowance and the hop limit are two small values. They go with the dialog and they change at each hand-over. This document counts them as lifecycle state.</t>

<t>The charter rules out the behavioural security of agents. XO-11 is the requirement closest to that line. It asks that a dialog can tell a request apart from material that is passed along. It does not say what an agent should do with either. If the working group decides XO-11 is out of scope, it can be removed and the rest still stands.</t>

<t>The charter says agents need verifiable identities separate from their users'. XO-6 is about one link only: that an agent acts for the Owner it names. It is not about proving who that Owner is in the real world. It asks for no new mechanism and depends on the identity work the group is already doing.</t>

</section>
<section anchor="relationship-to-other-documents"><name>Relationship to Other Documents</name>

<t>The table sets this document beside the working group's use cases document <xref target="I-D.agentic-ai-usecases-requirements"/>.</t>

<texttable>
      <ttcol align='left'>Topic</ttcol>
      <ttcol align='left'>In the use cases document</ttcol>
      <ttcol align='left'>Added by this document</ttcol>
      <c>Who owns the agents</c>
      <c>Agents run by different providers</c>
      <c>One person's agent dealing with a company's agent</c>
      <c>Spending</c>
      <c>Checkpoints that approve sensitive actions</c>
      <c>One allowance for the whole chain (XO-1 to XO-4)</c>
      <c>Delegation chains</c>
      <c>Scope narrows at each hop and loops are rejected</c>
      <c>A limit on how long a chain can get (XO-5)</c>
      <c>Ownership</c>
      <c>Agent identity and authorization across boundaries</c>
      <c>A way to check a claim to act for an Owner (XO-6)</c>
      <c>Disclosure</c>
      <c>Dialog context is passed along the chain</c>
      <c>The sender decides, and labels travel with items (XO-7 to XO-9)</c>
      <c>Retention</c>
      <c>Not covered</c>
      <c>How long a shared item may be kept (XO-10)</c>
      <c>Repeated requests</c>
      <c>Advice to check the outcome before sending again</c>
      <c>An identifier that stays the same (XO-12)</c>
</texttable>

</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t>Nothing in this document stops a dishonest agent. An allowance and a hop limit only hold if the agents in the chain respect them, so they are no replacement for controls on the payment itself. Once a context item has been sent, its label and its retention statement are terms the receiving agent was told. They are not locks. A retention statement does not prove an item was deleted. A checked ownership claim shows the Owner approved that agent. It says nothing about who the Owner is in the real world. What the requirements do is set out what an honest chain of agents will do, and make it clear when an agent has gone outside the terms it was given. This document assumes the dialog is already authenticated and protected by whatever the working group adopts. It asks for nothing new there.</t>

</section>
<section anchor="privacy-considerations"><name>Privacy Considerations</name>

<t>The disclosure and retention requirements are here to keep an Owner's information from travelling further, or staying longer, than the task needs. They also create one new leak. An allowance or a hop limit that agents along the path can read says something about the requester, for example how much James is willing to spend. A protocol meeting these requirements needs to think about which agents have to see those values. Checking ownership has a privacy cost too. An agent should not have to reveal its Owner to every agent it talks to. It may stay silent about its Owner. It may not name one falsely.</t>

</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>This document has no IANA actions.</t>

</section>


  </middle>

  <back>




    <references title='Informative References' anchor="sec-informative-references">

&I-D.agentic-ai-usecases-requirements;


    </references>




  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA6VbTZfjtrHd81fwOIvxnCNpxpPEiXuVfmPnebLw+NiT42zR
JCTBTREMQbasZPLfc28VAIJqeZJ33sJjSQSB+q5bVejtdltNbursXf3Z29GH
sH1/7u1Y3x9sP9V/DbZ+a4INtenb+gf799mN9oQn4a7+cbB96/rDpv7advZg
Jud7fBym46aWPcLRDXjoQtP5MI827jHhdSz9rDIPD6N9unluedJnVeub3pxA
YTua/bRt5nFyYWu4chj95LeNbOC5wXYOtiHF29evq8ZM9uDHy13t+r2vwvxw
ciHg8OkyYLt333z4c+WG8a6exjlMb16//ur1m8qM1oCo+2HoXCNcJe5Nt/3g
Tvaz6uzHx8Po54HrhOC3/nSa+7i+/p5UNb4D7Y/2gtXtXVXX21pIrptyrfwO
mmshWr6NBfPyQ5vlK1+H0T2Z5lI92X623Pi/JKWule3PfgL5UFz9v3yPv5+M
6+7qRaB/cnba7/x4wDMzNse7+jhNQ7h79Yor+Yt7sru06BV/ePUw+nOwr5ZN
XlWVmaejH0HiFgqAyfxlV78V5WHfWlX6F/wbil+xHxTTt5bWha34W+MmqPAH
3zx2jiKAhA7g7a5+ey+P/dxPVPJfezfZtv5xgtplM6uM/cwz/qRmsxuxTagq
GsR4goyeRITvtl/vhHTXbI1bjKjUxV1VbbdQ4kOYRtNMVfXh6EIN45z5GFoK
zegewE1WZ30+WrH7+v5dVD5epOhxeO17q45Sm/BIG3u+xNSt2++xB37WpZOH
/v2Ta+2r0TYW5NeZFd9v+LCxIUCOdZg8Dm/NZPjNT6Dl7EAarReH5wNfhPrB
Hk2339XC0co+wUiPxzV+aCGIhr+Zjhs+lD/s6ndT3bkwhRrnrEwYP5gJ//gs
laEzjS0pAJem84d6iMa6oUX23QWs1XuySJ+E/Zg6xKCDs05u0q3DZC4QtZuO
crawZ0KNx2BmMCHAJigaE1/CwUd/xhH9pZ4czS+/djIXMrt66YzfIPXmaJtH
KNQ1x6S1QmGB6trIRoGGO76gHGGWHrJ6wmJ9sVAV7MjPIBGv6na0JY2Vtt1I
xCGVnQezwmb5bqTzEdFWJN96cNH7iRIcKGiTZSnPsbcXO2pFMv2Ak8FT4psC
lSDyojRekrBSZDL1nTrCybVtZ6vqN/BXMNrOYgtV9b31Qyc6o2pGMWYcxo1F
XoHfIDMqAhS4MZoftX2mKoXdo3miHcHWQGHX1u40rN7pYBdhgxWdxmgkG3zd
u970DR+Q+gY0IA/t6v+Zg+vhFuSKPmGHzl+ErqM98dwh0y8C6bxphcxWCKBp
OfBoZFd8grrgJQMtKDqcDTsGBJwHx+C+2D2I8xx8fR6pRQQDEH/2SQona6G9
n7A5DSEcDdUzzl00SLWKo6Fi6/2IGCYmStkdeMw8JEOeYVnRIugfk7rWpT5A
RDgR0SV6dvae6NTWMSjAWMjMPJno3JN/xHuNDxP9vNDBCSHrgn+fuMeDnc7W
9tnfbRBNR5eAnPQBY1T+nXRIROR/XfBkTZwykGYIKNIT90t0Rn8E614XHKI9
nvX45ohwsamxX/ZJvhkYAnSF2qqQBS86m1F2M9QTPuorMU4lD4Ytqk+ZM8n1
CI9/hnV13WXDn48ShWwR8FYCEHWCKQSxs3jvVPfWqlFR2njTyptUD53SDIzr
tt0pBMJC27dqgnszd+Kv3NSJJSHDMapgg0v92PvzJgUYJXkOMwmVA2iu4rPr
dKXB+hPeTtrXwQWUwIuK2MLwiPgZwHKtwWlTS9ZC+pxHZG08hW56F07qkK7Y
DToFJWKoA6NEMwNZ1KM7HGk+4azJLvjuSQWFQx86e1I/+1Tcyiz+85//TVr/
17+gEAgzFDgrG3e0NNKuCoIvSCYYvOs16tNcYGmSpiSChOhtmQ7TtmolPDxi
AlH9Egsk2l3legQxdTjHBE1exbujJJ9lEhh8TiSuf6Lc2h2j8wc7noB4tvr4
ToWJ7fEmccF4oILiTtcpbYfXSniuifpOgImk7CtBLaH7mhnu9MOVlygthfdF
IFR4uXiAF23rDqt48mwD8I49NFa0S4Ljq/dd589MDvrSieHtynWz/M6u62La
EmaWsCr+uhGHxbcToSdCQ1SU/1QsJQ3feuB04j44RbsVYICXJa7vR3+SR5nt
KAdRAaCE/YVRxJ4o/MFZIqj92gyS8o6+g8Fd4QuVXiy+7hZsYa5jtKSSR2sH
4WU5l87LkChZRQwrV4f48pv6PhoVmNZ9HmbkcmHL4LMmYH1UVQr7Rd10lcwz
AgwidMcgEL0OlE62q0ePfbDgfqaqNvWHv+nW73tADOcZ59+a3rRmV3+bNyT5
YslQ2wg9dilrvwhFnhIqFG3/fcZhOy1K8hrGV25x8L5VQKCilVUp8Bo3Dn6E
7G0OvsNo9+LF6vF40rlHKxkA8WIjjO/F+nDIvrtYQnYzzZILGztOSGrct6Pk
dDkToRzTz6cHO25ino15axrdQOtVXiaE3t7DRy+Ug/hiYyUBK5spH+H73o10
hrOPuJP5kmH4YCfqzk4EPCg7YXNuH4G1QTBOOSmGM+ZSyRgRtPAAIYZPO1Me
ofo/+xmogtXFEKzov7Nm7DNHF+zE5/CgkLWVrBxakYOegWPVztGdYAr2ypsH
2Lap9/YMAaf4PWWJwFlst9/AWrk9nHqEwN7tKZCDV809eP+oOD8BQLqLcHpD
QXF/EMj3pFnCvYvXs5VFmbHQIcb14sWUtdlPmunTHoLmn+jRmtIlq6gyTYpx
of7b++0XIjB8eAMZNoYZUs2kdAUoULRAK1fCrOsU3+1ZP7pJUXwQzeox7dLT
SUXO5zjmDyQb///q5SYfKODnlj+BcMqX0ukXIBQTc3mYEa+wmklFtQxOpJBn
fvH6+jDiXMXSqchOcsvQQ9RFZTL6083w9eFyQzhLnKASCBsB2OMhv/Im1zcX
NVX13TpcAugXVzvBwFC3iApnyRyh8QOWOCitPisy3gM4BBLso61vJ7+90Tva
xbi7Dq6KloOAKh6Qi1sBvGFmX0vq0xiK3xEGtLm1gDLIpki4uWUvmqPrPSk9
w0htMN2yXww+EixiIIW5tCL25uh9tMHlRZFU1oxYIUzO/kJ4Cgf2ZwLdTeZG
VHy04i5SB4kipbBR8HsusRLPGmPQK45sxOJZGsyINrS74E+WpmK7oMv7KzLJ
n4JSnNJJaRSXsPAyzaMeciUrVCHkCgmsy9XNFfsUztK2YNEK4z1E63UKqH9G
0uPC/sVUp65PAV1uBAKBRSkYaM3xVJ6tJZN40G9frlojEqttf0DJG41nWfp7
LmXR2bM4M02T4I9oheBApS6VLkWqVdLeuC7IBr97uYlZPXZVpPg5cP9zrIMR
oSVWn5ltxMPfvFRD/5GWkNAFGxpLBy0DCtaUR1M007CzikYNjW9IPB7nXqHH
0bMImSefsgfyBdVVbiJvMPPHNpNk7qLTsMKrMTwQ4Ukc5WLWFVJEPyr/FybW
56+dgGAONkSKoYXWjGJXFyozptryoWzW+diqE9qsARrRnQEuLGu478i1KvOU
wn1K2+qQ0qzIHbQrI45GESBhWDJqiRgDWWJrl0WMnN0HjbvavI0lPWr2cx8K
nB63UxKxDgVvz2AYXJuWNJ2BOWrGfrB1JD9lkYwaKGIcR7O4qKWtimDYpx0m
4pRbmVIPEStKw4p43GK4U2LzwWrVh9Nokl8WOac4ncGjZJ7BTKnyqfcVCxT8
WmS41HNYILiU/Q0FIp6VwIeyN1gITvLty1xVQ6tntpsvqw4IpTAa9nylw3Lu
mUr1nIelLxHYc8vVAgCQbP6VeN1qElNV39C4iuIZUugYsEMhtF9r6ipY8xqW
ro2SJBw19EcDhchbLEnmD2NVSGVbhTYKNb54w66PQMXUK2JhrlkBvk+kMsvI
J8aQ2AGrKr58h+SZWk25O4M9ErZF1BhVojmUfu52oKkoIM207r0xq/jJdC/x
qelmVWp/SQb1rCXGgBdya0ubjl6TyXJqJg6CynojggJanCkSlkRMGPYXc5Lm
6/+1OM19yBW3N+vjiFRJSuyuSasQh7muQKu5dyFy2YnE36jE1wK4JXmUTtIv
zuqJaLT1UZ6aL88pUQsFGhjsL42gglKAKs+4F+i7daQkae1CCNiQ8lKBU85u
BMLsobNIRVKTbh09VWAeaQipNcgHXEKM/Ln0t3RqwonG3ME6tMLCapXMb+8Q
VG1RxEcUl4Y1Sz9An2+uUnzs9WrLo2fNngGjzVhT4u7oDk6K9LVwinccRdO1
2r1MkSMvl+6nGuFSO+qLuT1ATiUNd6hn2gubc20ESPQNhGb2lJ7BkRiyogZ5
RLV0woUAaWkRSNzV3zDwShruEjTLYURa4hmP7FS02mYRtQmc3AKDbKqyMZu9
a4EyMDVCFWo8Vxew8w7mzvAew0oxAW85ARcaf38zvMSYcmMWpeWQDKRcDiox
x/l+U5EGye5L8wiuPzdxXhAlq1KSNbJEMBqscar/YUdf5GEeULTIUuznKVLS
erVB0rKfR7G8dcNdWc+jfuH5S/KsmVVdqS/yns41pbsq8x6/X5qWpUeWCdiW
LX+J8ZKIJXsWwGPJPpL0RWILrwIa2OfvJKPcs4pZZBDdN+vfr4ZyZZ72OglN
EYMT7IWDPeChwK13/dIOyW3pzboIjjVqhGjXyG09ylAUIrEtnpEkLPQQ2Gjk
S6VBAUm0iQJnFpQVvZQcSuujiXmSg3a3v8TJmrKTaiTTYje2DXFsZ83jjVZL
8Vp0h9wfEKP4w524/hriKL4JEdOUjcbAkdkK7UiUVTSRNaHxPyety7pXqTVg
nuNKFycOERSMRBDT5tcYOhX3ZhysR26WaRyHukfPwiRjUPrY6NqWobsMiEc/
aKT6o3hESVuqEMKvJb8cIgzgFY1SygiECdTcKTQorYVWtaqxnQ5QrR6Vd4/9
XN0RC6FJRm0GM1Tq8kl8rZeGTzSkNnkZoQwbUzYuZ7MhdslkDAVdyuPdNasi
Ss745FzmFaybdAothbFfyoY4NXERD5u9TaMvFeRXdwuzn8a2cuq6vFrgbvUM
7kqXQVPGciVDbgTlWUTubnCsI4bLtk8lMi/sPvfXFV6+purTfKzoOSU9Z79b
W//V6P85YswNeicD1aVGMWzBO99KrkcikeaBZHEFZ7nNJtOpXpubVI/W+8Ic
R3zt5ua5S5eGh2cjWyCfjpqfI7xURwlwSH4r2FHKT9aUuSyLjQHpzOQjmHhy
YFUHS4FV3fqq7eoSDrlqAaaGOfvx7j/0W82kSv0eAWgb22Z4F3pS7Ur1cB2V
Cu2i9GC+m104qu0ZrdxyBSjECcpENIXejCioSotOIJJTBLAmkqQ5bLTaMVOh
H8ZqtlDpWbGUhD3RxaoyVNMMNnHwuuDqZLeDumX8NSiHb54DGMYCtVoXhRSv
3+QOQYbk6cUU6aTN8wkG8MUfehdRPwnSVtGTd23E/Usrk92hWJ8u9z8S/F3d
b4Pr/sgW6+2pMZttVHe8hBDVWeSEhVt1zM7tbXNpOqtdab33ZM1TBNnyJsf/
jCaGSgSqU/iI1HMa2NP8Ll4eEAdYzYnZWV1lqZwM4j5eurQzrydItJMIIJ13
8fK4gdhaZEXBKtkOqpreL+EmXY+SPf64DMLSsM1MEzFJyhuSk+PNA6KT5YZk
zuYEUdLTkfj3fEcirGX02Kt3r24zSTybDAdldg9ZT4tFRZbYXsmOnDXYSwOQ
sQSYJc5DadBPqTsGbSzKW0k5tt3ixYKlpkpHIJdHuC49szPYOLEf92S62YbY
oeA1nzVwSO9fSGOPFADG1vj9+qKAYHWdE6zJVVtT+hLDelMo4i+B1E/Oz2yQ
5tsXBNiCNlUfX6TkWnZw5MJZiNfBiAxcr1Z9w5gkzkhzNHt3USsXUcyUd+8k
cq1vkuRCK4Pc2PVpoxT1ZlKGbSu3zcaWeSpHKRvG8JgPwSKv1BS3kcIUPULc
J1yJVKGB4nPJ19ARfF8iugaCyVmGMzANZpVtRb9IR2N4IXL+UsejQlTPoW//
KO55d1USpTsWC76UW0K043RpT8K17CSXPrWXWC+wQ+96RN7SNa1Fe9xc5rDn
5SKOzluWJqXkWOXtktodNgraLRW8BOCbEfe9wKyvow0Hlai0XSEosebSxB+s
9HmfKfX/d4MHhH2sP/jBNfXHBBNubPexvm/bNLErqfpYfdxut/k/bPbTs8Z1
4Ov6YZx77rFccYlXckeued+n6zUZNXJ0sADTZ8NFnpcak9jgbXG/KPaj5GrY
84tG8bQlYiVrup7xpHbp717KYUW7QtZwI0mSsL5xlNsOKVQh9OmMwQ96d3K0
PyMoQ4iQxrqJEa+T5FaOXB/QsZGcmjsFSZCL3Umil8vi7h8xWmuHCLbPOQe9
juet7uKapQzmzVAZPKZiXLv0yuwyrOaXVYK/ClLFuOtjLlm1vmHA0aQjuTCs
ikXF7esRuJydCwLs9x0noIz6IrtvF4HFqcl1Kkzj7bjRFUITW35ycbgn8pAC
bp7Y8Uvt0qXkVp7u/yN8ixM3HFpx4hYTyVsYG+1bHb+qfhXChEnshOA3TQn1
3ud9f5VYTZFWBbwo/t6XDueKbhOD90A4wOy4yV1/GQwQxsul8lOaQMdrCTnC
DeYiz1LF917IWBerbFjmuyYbKStjvSxASyb+UZvFjYQxFTC3Kqaz0VZqOcWA
GXT8GwQtlJ7vWN7lfrIZJHErXlCctOmcxlHL8EqdQQdBRdc0XiuNkUSV8S4O
fdI1Vk0xmlrsJzPLTwt0X10MV5Q/1bqPZrloAKq9DEXkNg7e2MRO46N0HBpe
/FGkt1xjYzdZpkRxOCglpsh6dRXt+ral3CsNJRAr8hijjGQTkxr5hIEa0WKT
wOZJ+Qp1mNYP8RZMkVxVgMywUlVKhvxe/0Dnmdd8EIpWfw61GMBKoDLnlWui
qXXT5w5UWdQpAJFIJAkmNmo3+ucf2jhilLHytwnlRRsp5/JsGd7USGdGEAu5
YavvymtlgLQ47WJQoYieg0E81HLOtGplRXM2tQuXUcx6bJV79zrOX9/dkkse
tP0FuFs7xbowXJlkrsh58mO2cLmqV1y5lXolzcETnpcELK3q7FwyzEh/eaXT
psn7ov0W8Sv9Nm2M2oOeszST8Zu0ZlMviXVOR5DtxaoY+6m0Orhuuey0XOBM
a+QGE2M1dZW6zvJnGPff3d8wutI54uxOVqbbyvrXHLzDUv0buF5E3A44AAA=

-->

</rfc>

