<?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 4.0.9) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-curtis-myterms-02" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="MCNP">MyTerms Contract Negotiation Protocol (MCNP): Human and machine-readable agreements</title>

    <author fullname="Benjamin Curtis">
      <organization>MyTerms</organization>
      <address>
        <email>ietf@nowsci.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="18"/>

    <area>AREA</area>
    <workgroup>WG Working Group</workgroup>
    <keyword>ethics</keyword> <keyword>automation</keyword> <keyword>machine translation</keyword> <keyword>contractual agreements</keyword>

    <abstract>


<?line 58?>

<t>This document covers the technical requirements of Verifiable Contractual Agreements (VCAs) between individuals and the entities that engage on a network as defined in IEEE7012. It describes how individuals, acting as first parties, can proffer their privacy requirements as contractual terms and arrive at agreements recorded and kept by both sides. This includes the hosting format for contracts, negotiation of contracts, signing of contracts, and auditing of contracts.</t>



    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>
        The latest revision of this draft can be found at <eref target="https://codeberg.org/myterms/ietf/src/branch/main/draft-curtis-myterms-02.xml"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-curtis-myterms/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        WG Working Group mailing list (<eref target="mailto:WG@example.com"/>),
        which is archived at <eref target="https://example.com/WG"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://codeberg.org/myterms/ietf"/>.</t>
    </note>


  </front>

  <middle>


<?line 62?>

<section anchor="introduction"><name>Introduction</name>

<section anchor="purposes-of-myterms"><name>Purposes of MyTerms</name>

<t>The purpose of the <xref target="IEEE7012"/> standard, otherwise known as MyTerms, is to provide individuals with means to proffer their own terms respecting personal privacy in ways that can be read, acknowledged and agreed to by machines operated by others in the networked world. In a more formal sense, the purpose of the standard is to enable individuals to operate as first parties in agreements with others, mostly organizations, operating as second parties.</t>

<t>In this methodology, agreements shall be chosen from a registry of standard-form agreements in a roster kept by an independent and neutral non-business entity. Computing devices and software performing as agents for both first and second parties shall engage using the protocol defined in this document. The first party shall point to a preferred agreement, or a set of agreements, from which the second party shall accept one. Party-to-party negotiations over agreements in any of these contracts or other agreements are outside the scope of this standard. If both parties agree, the chosen contract or agreement shall be signed electronically by both parties' agents, and a matching record shall be kept in a way that can be retrieved, audited, or disputed, by either side if necessary, at some later time.</t>

</section>
<section anchor="definitions"><name>Definitions</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 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>

<t>A "PERSON AGENT" is defined as any system, such as a web browser, mobile application, AI/MCP agent, or any other tooling, that negotiates MyTerms agreements on behalf of a consuming party, otherwise known as the first party in <xref target="IEEE7012"/>. An "ENTITY AGENT" is defined as any system, such as a web server, operating system, AI/MCP agent, or any other tooling, that negotiates MyTerms agreements on behalf of a providing party, otherwise known as the second party in <xref target="IEEE7012"/>.</t>

</section>
</section>
<section anchor="hosting-agreements"><name>Hosting agreements</name>

<section anchor="agreement-types"><name>Agreement types</name>

<t>There are three types of agreements in MyTerms:</t>

<t><list style="symbols">
  <t><strong>Relationship agreements:</strong> Agreements that pertain to the overall relationship between the PERSON and the ENTITY, such as for service delivery or data portability.</t>
  <t><strong>Personal Data Contribution agreements:</strong> Agreements that pertain to one-time data use or exchange.</t>
  <t><strong>Legal agreements:</strong> Agreements that contain the legal language enforcing the Relationship and Personal Data Contribution agreements.</t>
</list></t>

<t>Depending on the interaction type between the PERSON AGENT and ENTITY AGENT, a specific type, or set of a type, of agreements MAY be signed.</t>

</section>
<section anchor="agreement-levels-and-codes"><name>Agreement levels and codes</name>

<t>Every agreement MUST have an associated code that represents the agreement. Each relationship agreement's code MUST represent the level of restriction on the agreement.</t>

<t>Restriction levels SHOULD move linearly from most restrictive on data use to least restrictive on data use, meaning the fewer characters in the code represent more restrictions on data use. An example of this would be:</t>

<texttable>
      <ttcol align='left'>Code</ttcol>
      <ttcol align='left'>Level</ttcol>
      <ttcol align='left'>Meaning</ttcol>
      <c>SD-BASE</c>
      <c>1</c>
      <c>Allows service delivery</c>
      <c>SD-BASE-A</c>
      <c>2</c>
      <c>Allows service delivery and analytics</c>
      <c>SD-BASE-AT</c>
      <c>3</c>
      <c>Allows service delivery, analytics, and tracking</c>
      <c>SD-BASE-ATP</c>
      <c>4</c>
      <c>Allows service delivery, analytics, tracking, and profiling</c>
      <c>SD-BASE-ATP3</c>
      <c>5</c>
      <c>Allows service delivery, analytics, tracking, profiling, and 3rd-party sharing</c>
</texttable>

<t>This structure simplifies the machine negotiation when multiple agreements are in play.</t>

</section>
<section anchor="ensuring-tamper-proof-agreements"><name>Ensuring tamper-proof agreements</name>

<t>To ensure hosted agreements are tamper-proof they are built as Verifiable Contractual Agreements (VCAs), meaning that when a party signs an agreement, there is proof that the content of the agreement has not been altered since the signature took place. Agreements MUST be hosted in Markdown (MD) format with a hash of the content in the URL.</t>

<t>Agreements MUST also be hosted in a web-browser friendly format, for instance using Markdown to HTML conversion tools. Web-browser friendly versions MUST contain links to the raw Markdown versions and MUST contain links to the machine-readable versions.</t>

<t>URL formats for web-browser friendly HTML agreements SHOULD be in the format of:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/<first letter of type>/<code>
]]></artwork></figure>

<t>URL formats for Markdown agreements SHOULD be in the format of:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/<first letter of type>/<code>/<hash>.md
]]></artwork></figure>

<t>URL formats for machine-readable agreements SHOULD be in the format of:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/<first letter of type>/<code>/<hash>.json
]]></artwork></figure>

<t>Web-browser friendly HTML agreements MUST be generated directly from their markdown counterparts, and MUST include links to:</t>

<t><list style="symbols">
  <t>The hashed markdown version</t>
  <t>The HTML legal agreement, if it is not the legal agreement</t>
  <t>The hashed markdown legal agreement, if it is not the legal agreement</t>
  <t>Any vocabulary definitions used in the agreement, such as the <xref target="DPV"/></t>
  <t>The machine-readable JSON version</t>
</list></t>

</section>
<section anchor="machine-readable-agreements"><name>Machine readable agreements</name>

<t>Machine readable agreements MUST be JSON. The format of the JSON MUST be:</t>

<figure><artwork><![CDATA[
{
  "version": <machine-readable agreement version>,
  "references": [
    "<link to hashed agreements>"
  ],
  "agreementId": "<UUID representing this agreement>",
  "created": <epoch time>,
  "ids": [
    "<optional DID id>"
  ],
  "permitted": [
    "<purpose>"
  ],
  "prohibited": [
    "<prohibition>"
  ],
  "validRoles": [
    "<role>"
  ]
}
]]></artwork></figure>

<t>Machine readable agreements MUST support signing via DIDs as per the <xref target="DID"/> W3C recommendation. DID ids within the <spanx style="verb">ids</spanx> array of the agreement MAY include the ENTITY AGENT's DID id, and if it is included they MUST sign the agreement before it is considered valid.</t>

<t>Multiple human-readable (hashed markdown) agreements MAY be grouped into the <spanx style="verb">references</spanx> block, and SHOULD include a vocabulary set such as the <xref target="DPV"/>, the primary agreement, and an overlapping legal agreement.</t>

<t>The <spanx style="verb">permitted</spanx> array MUST contain a representation of any expressly allowed actions within the agreement content. The <spanx style="verb">prohibited</spanx> array MUST contain a representation of any expressly prohibited actions within the agreement content. The <spanx style="verb">validRoles</spanx> array MUST contain a list of roles or parties as defined within the agreement content, such as that of entity, user, and/or third-party.</t>

<t>Machine readable agreements MAY be signed by multiple PERSON AGENTs, however agreement UUIDs MUST be unique per unique JSON record.</t>

</section>
<section anchor="retrieving-available-agreements"><name>Retrieving available agreements</name>

<t>When a PERSON AGENT or ENTITY AGENT wishes to retrieve a list of codes and their corresponding agreements from the agreement hosting entity, a publicly-accessible API endpoint SHOULD be provided for accessing this information.</t>

<t>The URL format for the API endpoint to set preferences MAY be:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/api/v1/myterms/agreements
]]></artwork></figure>

<t>Retrieving agreements MUST be completed via a GET, and the response MUST be in the format of:</t>

<figure><artwork><![CDATA[
{
  "version": 1,
  "created": "2026-06-25T11:54:23+0000",
  "agreements": [
    {
      "type": "<type>",
      "format": "<hidden|ranked|multiple>",
      "title": "<Title of section UIs>",
      "clientDescription": "<Description for PERSON AGENT UI>",
      "serverDescription": "<Description for ENTITY AGENT UI>",
      "agreements": [
        {
          "title": "<Title of agreement>",
          "code": "<Agreement code>",
          "url": "<URL to hashed human-readable markdown>",
          "jsonUrl": "<URL to hashed machine-readable JSON>",
          "rank": "<integer rank, only for ranked format>"
        }
      ]
    }
  ]
}
]]></artwork></figure>

<t>When an agreement is rotated out for a new version, the hashed markdown and machine-readable JSON versions of that agreement MUST continue to remain available for previous lookups, and the agreement MUST be removed from the endpoint results. The version key MUST be incremented by 1, and the created key MUST be set to the date of deployment of the updated or new agreements.</t>

<t>This agreement availability format SHOULD be used to generate user interfaces that allow for selection of agreements dynamically. All of and only the following agreement types MUST be supported:</t>

<t><list style="symbols">
  <t>Hidden: A group of agreements that exist or may be linked to from other agreements as a schedule, but do not need to be displayed in the user interface.</t>
  <t>Ranked: A group of agreements with ranked keys that MUST give the ability to select only one of many
  <list style="symbols">
      <t>The lower the ranking, the more restrictive the agreement MUST be for ENTITY AGENTS</t>
      <t>The higher the ranking, the less restrictive the agreement MUST be for ENTITY AGENTS</t>
      <t>When a ranking is selected by an ENTITY, they are indicating they require that rank at a minimum, but will optionally accept higher ranks</t>
      <t>When a ranking is selected by an PERSON, they are indicating they require that rank at a maximum, but will optionally accept lower ranks</t>
      <t>Multiple agreements MAY have the same ranking, and if so, MUST be equivalent in restrictiveness</t>
    </list></t>
  <t>Multiple: A group of agreements that can individually be required, optional, or not used by an ENTITY AGENT</t>
</list></t>

<t>The below example demonstrates a configuration that COULD be used to generate a user interface with 2 radio buttons and 1 checkbox:</t>

<figure><artwork><![CDATA[
{
  "version": 1,
  "created": "2026-06-25T11:54:23+0000",
  "agreements": [
    {
      "type": "relationship",
      "format": "ranked",
      "title": "Relationship",
      "agreements": [
        {
          "title": "SD-BASE",
          "clientDescription": "Only allow the bare minimum.",
          "serverDescription": "Only request the bare minimum.",
          "rank": 1,
          "code": "sd-base",
          "url": "https://domain.ext/r/sd-base",
          "jsonUrl": "https://domain.ext/r/sd-base/371...216.json"
        },
        {
          "title": "SD-BASE-AT",
          "clientDescription": "Also allow analytics and tracking",
          "serverDescription": "Also request analytics and tracking",
          "rank": 2,
          "code": "sd-base-at",
          "url": "https://domain.ext/r/sd-base-at",
          "jsonUrl": "https://domain.ext/r/sd-base-at/00d...41a.json"
        },
      ]
    },
    {
      "type": "pdc",
      "format": "multiple",
      "title": "Personal Data Contribution",
      "agreements": [
        {
          "title": "PDC-AI",
          "clientDescription": "Allow AI training on your content",
          "serverDescription": "Request AI training on user content",
          "code": "pdc-ai",
          "url": "https://domain.ext/p/pdc-ai",
          "jsonUrl": "https://domain.ext/p/pdc-ai/2a0...177.json"
        }
      ]
    }
  ]
}
]]></artwork></figure>

</section>
<section anchor="configuring-agreement-preferences"><name>Configuring agreement preferences</name>

<t>A user with a role of PERSON AGENT MUST be able to select a set of individual agreements they would agree to during the negotiation. When a PERSON AGENT wishes to set the code that represents the preferences that have been selected by the user, an API endpoint SHOULD be provided for saving this information.</t>

<t>The URL format for the API endpoint to set preferences MAY be:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/api/v1/myterms/prefs
]]></artwork></figure>

<t>Setting or updating agreement preferences SHOULD be completed via a JSON POST, and the POST body SHOULD be in the format of:</t>

<figure><artwork><![CDATA[
{
  "agreements": [
    "<agreement code>"
  ]
}
]]></artwork></figure>

<t>Multiple agreement codes can be included, and the system should associate those selections to the appropriate agreements. Additional information MAY be included in the JSON content.</t>

<t>Authentication MUST be used for this endpoint, and SHOULD follow standard best-practices for web authentication.</t>

</section>
<section anchor="retrieving-agreement-preferences"><name>Retrieving agreement preferences</name>

<t>When a PERSON AGENT wishes to retrieve the codes that represents the preferences that have been selected from the agreement hosting entity, an API endpoint MUST be provided for accessing this information.</t>

<t>The URL format for the API endpoint to set preferences MAY be:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/api/v1/myterms/prefs
]]></artwork></figure>

<t>Retrieving agreement preferences MUST be completed via a GET. The response MUST be in the format of:</t>

<figure><artwork><![CDATA[
{
  "agreements": [
    "<agreement code>"
  ]
}
]]></artwork></figure>

<t>Authentication MUST be used for this endpoint, and SHOULD follow standard best-practices for web authentication.</t>

</section>
</section>
<section anchor="agreement-negotiation-mechanisms"><name>Agreement negotiation mechanisms</name>

<section anchor="client-preference-delivery"><name>Client preference delivery</name>

<section anchor="on-demand-proposal-of-agreements"><name>On-demand proposal of agreements</name>

<t>In this method, the PERSON AGENT to ENTITY AGENT negotiation occurs via the exchange of data over HTTP/S, where the ENTITY AGENT delivers an endpoint location to the PERSON AGENT, and the user must take an action before terms are delivered. This eliminates any sources of pervasive monitoring as clients can ignore the request from an ENTITY AGENT. This method SHOULD be used for interactions such as signing Terms of Use, or agreeing to actions in a website or application.</t>

<t>First, the ENTITY AGENT hosts a URL containing a JSON of the details of what agreements they support. The JSON format MUST be:</t>

<figure><artwork><![CDATA[
{
  "endpoint": "https://<domain>.<tld>/api/v1/myterms/put",
  "agreements": [
    {
      "type": "<type>",
      "required": true,
      "url": "<URL to hashed machine-readable JSON>"
    }
  ]
}

]]></artwork></figure>

<t>The below example demonstrates a configuration that COULD be used to demonstrate the supported agreements from the above UI example where an ENTITY selected the lowest ranked agreement:</t>

<figure><artwork><![CDATA[
{
  "endpoint": "https://<domain>.<tld>/api/v1/myterms/put",
  "agreements": [
    {
      "type": "relationship",
      "required": true,
      "url": "https://domain.ext/r/sd-base/371...216.json"
    },
    {
      "type": "relationship",
      "required": false,
      "url": "https://domain.ext/r/sd-base-at/00d...41a.json"
    },
    {
      "type": "pdc",
      "required": true,
      "url": "https://domain.ext/p/pdc-ai/2a0...177.json"
    }
  ]
}
]]></artwork></figure>

<t>Any required agreements in the array MUST be accepted by the PERSON AGENT before they can proceed. The JSON record MAY contain additional data and information by use by the providing system. The endpoint variable MUST represent the location that signed agreements can be submitted to the ENTITY AGENT from the PERSON AGENT.</t>

<t>Next, the PERSON AGENT MUST validate that the URLs of all agreements from the ENTITY AGENT are from the same hosted subdomain as the subdomain of the configured PERSON AGENT. If they do not match, the negotiation MUST be rejected and the user MUST be informed of the discrepancy.</t>

<t>Lastly, the PERSON AGENT retrieves the machine-readable JSON agreements to begin the negotiation with the ENTITY AGENT.</t>

</section>
<section anchor="continuous-proposal-of-agreement"><name>Continuous proposal of agreement</name>

<t>In this method, the PERSON AGENT to ENTITY AGENT negotiation occurs also over HTTP/S via the exchange of HTTP headers, but this time on every request. This method SHOULD be leveraged for interactions that do not have the capabilities or process abilities to support on-demand agreement delivery, such as for up-front cookie preference negotiation in browsers.</t>

<t>First, when a PERSON AGENT makes a request to a particular web page or service endpoint that is MyTerms enabled, the ENTITY AGENT will return a response HTTP header of a MyTerms request endpoint that MUST reference a JSON file of the same format as On-demand proposal of agreements:</t>

<figure><artwork><![CDATA[
X-MyTerms-Agreements: <entity agreement endpoint url>
]]></artwork></figure>

<t>When encountering a MyTerms response header request, a PERSON AGENT MUST alert the user to the request for them to allow or deny, unless the user has previously approved that PERSON AGENT to accept all MyTerms requests from that domain. A system MUST NOT allow users to accept all MyTerms requests for all domains. This alert MUST contain full host name contained within the header, including domain, top level domain, and subdomain if one exists.</t>

<t>From here, the PERSON AGENT SHOULD follow the same pattern as if it had retrieved the JSON in the On-demand proposal of agreements flow.</t>

</section>
</section>
<section anchor="mitigating-pervasive-monitoring"><name>Mitigating Pervasive Monitoring</name>

<t>As per <xref target="RFC7258"/>, to mitigate Pervasive Monitoring (PM) and thus decrease the ability of entities to leverage MyTerms user preferences for fingerprinting, PERSON AGENTS MUST NOT deliver information beyond the signed agreements unless tied to another flow outside of this standard that properly notifies that user of a data exchange. An acceptable example would be including an OIDC login with the signing of a Terms of Use, where the OIDC flow provides an indication of what data is being exchanged.</t>

</section>
<section anchor="agreement-negotiation-algorithm"><name>Agreement negotiation algorithm</name>

<t>Once the PERSON AGENT receives the acceptable agreement selections from the ENTITY AGENT, it is the PERSON AGENT's job to handle the negotiation. At this point the PERSON AGENT should compare it's acceptable agreements with those of the ENTITY AGENT, and confirm that the user has allowed the agreements required by the ENTITY AGENT.</t>

<t>If the PERSON AGENT provides terms that are less restrictive than the ENTITY AGENT requires, the PERSON AGENT MAY sign a less restrictive agreement.</t>

<t>The following chart demonstrates how these negotiations MUST occur. In these examples the same codes from above are used.</t>

<texttable>
      <ttcol align='left'>PERSON provides</ttcol>
      <ttcol align='left'>AGENT requires</ttcol>
      <ttcol align='left'>AGENT supports</ttcol>
      <ttcol align='left'>Result</ttcol>
      <c>SD-BASE</c>
      <c>SD-BASE</c>
      <c>&#160;</c>
      <c>Proceed to signing and delivery of SD-BASE</c>
      <c>SD-BASE</c>
      <c>SD-BASE</c>
      <c>SD-BASE-A</c>
      <c>Proceed to signing and delivery of SD-BASE</c>
      <c>SD-BASE-A</c>
      <c>SD-BASE</c>
      <c>SD-BASE-A</c>
      <c>Proceed to signing and delivery of SD-BASE</c>
      <c>SD-BASE,SD-BASE-A</c>
      <c>SD-BASE</c>
      <c>SD-BASE-A</c>
      <c>Proceed to signing and delivery of SD-BASE-A</c>
      <c>SD-BASE</c>
      <c>SD-BASE-A</c>
      <c>&#160;</c>
      <c>Use must be notified they must sign SD-BASE-A to continue</c>
</texttable>

<section anchor="requiring-multiple-agreements"><name>Requiring multiple agreements</name>

<t>If an entity requires multiple agreements to be signed, the PERSON AGENT follows the same pattern as above, and SHOULD alert the user that certain agreements must be signed before proceeding. In any displays offering up the ability to select these agreements, the PERSON AGENT MUST NOT pre-check any options unless the user has already set these options in their default preferences.</t>

</section>
</section>
</section>
<section anchor="signing-agreements"><name>Signing agreements</name>

<section anchor="levels-of-attestation"><name>Levels of attestation</name>

<t>When PERSON AGENTs sign agreements, there are 3 levels of attestation, one of which MUST be attested to for the agreement to be valid. The 3 levels are:</t>

<texttable>
      <ttcol align='left'>Level</ttcol>
      <ttcol align='left'>Title</ttcol>
      <c>1</c>
      <c>Server trusted remote attestation</c>
      <c>2</c>
      <c>Cryptographic attestation</c>
      <c>3</c>
      <c>Auditable cryptographic attestation</c>
</texttable>

<t>As the level increases, the security and verifiability of the attestation increases.</t>

<section anchor="level-1-server-trusted-remote-attestation"><name>Level 1: Server trusted remote attestation</name>

<t>In this level, ENTITY AGENTs MUST give PERSON AGENTs a checkbox that when checked, represents the signing of an agreement. ENTITY AGENTs MUST default the checkbox to unchecked.</t>

<t>Under this level of attestation, PERSON AGENTs are trusting that ENTITY AGENTs will act honestly and transparently around storing and abiding by their preferences, with no third-party auditing.</t>

</section>
<section anchor="level-2-cryptographic-attestation"><name>Level 2: Cryptographic attestation</name>

<t>In this level, ENTITY AGENTs MUST give PERSON AGENTs a method of cryptographically signing an agreement. Agreements MUST be signed utilizing a private key that represents the PERSON AGENT. This private key SHOULD be fully controlled by the end user, and not available to the ENTITY AGENT in any way. This private key MAY be owned by the ENTITY AGENT or an agent, if that ENTITY AGENT or agent was given a capability delegation from the user, and that delegation MUST be cryptographically signed and provided via a DID.</t>

<t>Signing an agreement MUST occur using an EdDSA JWT and a private key associated with any public key in the verification method of the signing DID. For example, if the signing DID document is represented by the following FedID enabled DID:</t>

<figure><artwork><![CDATA[
{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://didspec.myterms.info/v2/ctx.jsonld"
  ],
  "capabilityDelegation": [
    {
      "id": "did:myterms:fedid.myterms.info:GDj...",
      "type": "myterms",
      "archiveServers": [ "https://archive.myterms.info" ]
    }
  ],
  "created": "2025-10-30T16:00:14Z",
  "deactivated": false,
  "id": "did:myterms:fedid.myterms.info:iuK...",
  "recoveryHash": "d0a634b07cea22a9e3865eb5598e0486636bb772976bf93d",
  "service": [
    {
      "id": "did:myterms:fedid.myterms.info:5c7...",
      "serviceEndpoint": "https://fedid.myterms.info",
      "type": "login"
    }
  ],
  "shortName": "person@fedid.myterms.info",
  "updated": "2025-10-30T16:00:14Z",
  "verificationMethod": [
    {
      "controller": "did:myterms:fedid.myterms.info:iuK...",
      "created": "2025-10-30T16:00:14Z",
      "deactivated": null,
      "id": "#55b72a71d2431bd5eb10b347f1b272da",
      "key": "9ud_btCMlYQRHkTyyKMNtC48avmC60fCZhWNIbOsNi0",
      "type": "device"
    }
  ],
  "version": "2.0"
}
]]></artwork></figure>

<t>Then the private key associated with the public key <spanx style="verb">9ud_btCMlYQRHkTyyKMNtC48avmC60fCZhWNIbOsNi0</spanx> should be utilized. As this DID document also contains a capability delegation that MUST be of type <spanx style="verb">myterms</spanx>, any keys in the verification method array of that DID document may sign on behalf of the user.</t>

<t>The agreement MUST be signed via JWS following <xref target="RFC7515"/> after following <xref target="RFC8785"/> for canonicalization to deterministically sort by recursively ordering the keys alphanumerically and sorting any arrays alphanumerically. The resulting JSON data MUST be submitted via POST to the entity endpoint for submitting signed agreements. The format for the posted data MUST match the provided example, where the public key provided is the public key paired with the private key that was used to sign from the verification method array.</t>

<figure><artwork><![CDATA[
{
  "agreement": {
    "agreement": {
      "version": 1,
      "references": [
        "https://<url>/a/74d...33d"
      ],
      "agreementId": "1df77ef2-e3c6-4f2b-859d-379cb9874d78",
      "created": 1760621627589,
      "ids": [
        "did:myterms:fedid.myterms.info:YTc..."
      ],
      "permitted": [
        "service-analytics",
        "service-delivery"
      ],
      "prohibited": [
        "profiling",
        "third-party-analytics",
        "third-party-sharing",
        "tracking"
      ],
      "validRoles": [
        "entity",
        "third-party",
        "user"
      ]
    },
    "signature": {
      "version": 1,
      "id": "did:myterms:fedid.myterms.info:iuK...",
      "signedOn": 1761841201,
      "type": "JWS/JCS",
      "jws": "eyJ...ICg"
    }
  },
  "publicKey": "9ud_btCMlYQRHkTyyKMNtC48avmC60fCZhWNIbOsNi0"
}
]]></artwork></figure>

<t>Under this level of attestation, PERSON AGENTs are trusting that ENTITY AGENTs will act honestly and transparently around storing and abiding by their preferences, with no third-party auditing, but gain the security of a referenced cryptographic signature.</t>

</section>
<section anchor="level-3-auditable-cryptographic-attestation"><name>Level 3: Auditable cryptographic attestation</name>

<t>In this level, the same signing method MUST be used for agreements, however an additional zero-knowledge audit record MUST be provided. This allows a third-party to validate that the agreement was appropriately signed without having any knowledge of what the agreement contains.</t>

<t>After the agreement is signed, an audit record MUST be generated from the top-level agreement object, which consists of the original agreement and it's signature. This object MUST be deterministically sorted, and a SHA256 digest MUST be created. The format of the audit record MUST include:</t>

<t><list style="symbols">
  <t>A context of keys used in the audit record</t>
  <t>A reference to the agreement ID that was signed</t>
  <t>A zero-knowledge representation of the signed agreement</t>
  <t>When the audit record was created</t>
</list></t>

<t>Under this level of attestation, PERSON AGENTs are trusting that ENTITY AGENTs will act honestly and transparently around storing and abiding by their preferences, with the security of a referenced cryptographic signature and a third-party that can audit that signature was performed without modification to the agreement.</t>

</section>
</section>
<section anchor="retrieving-signed-agreements"><name>Retrieving signed agreements</name>

<t>For services that store signed agreements on behalf of PERSON AGENTs and ENTITY AGENTs, an API endpoint SHOULD be provided for retrieving signed agreements. The URL format for the API endpoint to retrieve signed agreements MAY be:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/api/v1/myterms/agreements/signed
]]></artwork></figure>

<t>The formatted response MUST contain the level of attestation used (server trusted or cryptographic with a DID), and the contents of the machine-readable agreement. Retrieving signed agreements MUST be completed via a GET, and the response MUST be in the format of:</t>

<figure><artwork><![CDATA[
{
  "signed_agreements": [
    {
      "agreement": {
        "version": <machine-readable agreement version>,
        "references": [
          "<link to hashed agreements>"
        ],
        "agreementId": "<UUID representing this agreement>",
        "created": <epoch time>,
        "ids": [
          "<optional DID id>"
        ],
        "permitted": [
          "<purpose>"
        ],
        "prohibited": [
          "<prohibition>"
        ],
        "validRoles": [
          "<role>"
        ]
      },
      "signature_type": "cryptographic",
      "signatures": [
        {
          "version": 1,
          "id": "did:myterms:fedid.myterms.info:iuK...",
          "signedOn": 1761841201,
          "type": "JWS/JCS",
          "jws": "eyJ...ICg"
        }
      ]
    },
    {
      "agreement": {
        "version": <machine-readable agreement version>,
        "references": [
          "<link to hashed agreements>"
        ],
        "agreementId": "<UUID representing this agreement>",
        "created": <epoch time>,
        "ids": [
          "<optional DID id>"
        ],
        "permitted": [
          "<purpose>"
        ],
        "prohibited": [
          "<prohibition>"
        ],
        "validRoles": [
          "<role>"
        ]
      },
      "signature_type": "server-trusted"
    }    
  ]
}
]]></artwork></figure>

<t>Server trusted signed agreements will not contain a <spanx style="verb">signature</spanx> key, as these agreements were signed using standard server trusted check boxes.</t>

</section>
</section>
<section anchor="discovery-and-standard-response"><name>Discovery and standard response</name>

<section anchor="capability-discovery"><name>Capability discovery</name>

<t>Per <xref target="RFC8615"/>, all endpoints SHOULD be discoverable via a "/.well-known/" entry. The URL format for this MUST be:</t>

<figure><artwork><![CDATA[
https://<domain>.<tld>/.well-known/myterms-configuration
]]></artwork></figure>

<t>The response MUST be JSON in the format of:</t>

<figure><artwork><![CDATA[
{
  "methods": [
    "continuous",
    "on-demand"
  ],
  "get_agreement_endpoint": "https://.../agreements",
  "get_agreement_prefs_endpoint": "https://.../prefs",
  "get_agreement_signed_endpoint": "https://.../signed",
  "post_agreement_prefs_endpoint": "https://.../prefs",
}
]]></artwork></figure>

<t>Endpoint and method definitions are OPTIONAL based on what the system supports.</t>

</section>
<section anchor="standard-responses-to-api-requests"><name>Standard responses to API requests</name>

<t>The following standard responses SHOULD be used on all API requests.</t>

<texttable>
      <ttcol align='left'>HTTP Response Code</ttcol>
      <ttcol align='left'>Description</ttcol>
      <c>200</c>
      <c>Success when retrieving or setting any data</c>
      <c>401</c>
      <c>The user is not authenticated (invalid or missing token)</c>
      <c>403</c>
      <c>The user is authenticated but not allowed to perform the action</c>
      <c>404</c>
      <c>The requested user or agreements record doesn't exist</c>
      <c>500</c>
      <c>Unknown general internal server error</c>
      <c>502</c>
      <c>Bad gateway</c>
      <c>503</c>
      <c>Service unavailable</c>
      <c>504</c>
      <c>Gateway timeout</c>
</texttable>

</section>
</section>
<section anchor="IANA"><name>IANA Considerations</name>

<t>This memo includes no request to IANA.</t>

</section>
<section anchor="Security"><name>Security Considerations</name>

<t>This document should not affect the security of the Internet.</t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC8615">
  <front>
    <title>Well-Known Uniform Resource Identifiers (URIs)</title>
    <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
    <date month="May" year="2019"/>
    <abstract>
      <t>This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes.</t>
      <t>In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space. It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8615"/>
  <seriesInfo name="DOI" value="10.17487/RFC8615"/>
</reference>

<reference anchor="DPV" target="https://w3c.github.io/dpv/2.3/dpv/">
  <front>
    <title>Data Privacy Vocabulary</title>
    <author >
      <organization>W3C</organization>
    </author>
    <date year="2026"/>
  </front>
</reference>
<reference anchor="DID" target="https://www.w3.org/TR/did-1.0/">
  <front>
    <title>Decentralized Identifiers (DIDs) v1.0 - Core architecture, data model, and representations</title>
    <author >
      <organization>W3C</organization>
    </author>
    <date year="2022"/>
  </front>
</reference>


<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>
<reference anchor="RFC7515">
  <front>
    <title>JSON Web Signature (JWS)</title>
    <author fullname="M. Jones" initials="M." surname="Jones"/>
    <author fullname="J. Bradley" initials="J." surname="Bradley"/>
    <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
    <date month="May" year="2015"/>
    <abstract>
      <t>JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7515"/>
  <seriesInfo name="DOI" value="10.17487/RFC7515"/>
</reference>
<reference anchor="RFC8785">
  <front>
    <title>JSON Canonicalization Scheme (JCS)</title>
    <author fullname="A. Rundgren" initials="A." surname="Rundgren"/>
    <author fullname="B. Jordan" initials="B." surname="Jordan"/>
    <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
    <date month="June" year="2020"/>
    <abstract>
      <t>Cryptographic operations like hashing and signing need the data to be expressed in an invariant format so that the operations are reliably repeatable. One way to address this is to create a canonical representation of the data. Canonicalization also permits data to be exchanged in its original form on the "wire" while cryptographic operations performed on the canonicalized counterpart of the data in the producer and consumer endpoints generate consistent results.</t>
      <t>This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8785"/>
  <seriesInfo name="DOI" value="10.17487/RFC8785"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">

<reference anchor="IEEE7012" target="https://ieeexplore.ieee.org/servlet/opac?punumber=11170391">
  <front>
    <title>IEEE 7012 - Machine Readable Personal Privacy Terms</title>
    <author >
      <organization>IEEE</organization>
    </author>
    <date year="2025"/>
  </front>
</reference>


<reference anchor="RFC7258">
  <front>
    <title>Pervasive Monitoring Is an Attack</title>
    <author fullname="S. Farrell" initials="S." surname="Farrell"/>
    <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
    <date month="May" year="2014"/>
    <abstract>
      <t>Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="188"/>
  <seriesInfo name="RFC" value="7258"/>
  <seriesInfo name="DOI" value="10.17487/RFC7258"/>
</reference>



    </references>

</references>


<?line 665?>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+09WXfbVnrv/BUo/ZA45SJSm63jumEkJVbGsjWSHDfTMycG
gUsSEQhwsEhmLM9v77fdBQu1uMlMe1o/WCRw12/f7mW/3+8UURGrA697ur5U
2TL3DtOkyPyg8N6oeVpEfhGliXeWpUUapLH39enhm7OnB96rcuknnp+E3tIP
FlGi+pnyQ38aK8+fZ0otVVLk3Y4/nWbqGkeHbt1O4BcwaLY+8KJklnY6YRok
/hJmDzN/VvSDMiuivL9cF7iS/ta4k5fTZZTnsIRivYJ2J8eX33eScjlV2UEn
hNEOOkGa5CrJy/zAK7JSdWC27Y4PqznwJufHk85Nml3Ns7RcHXjvf/Dew7co
mXs/4JPOlVrD6/Cg4/U9VSyiIMdPflmkS9o3fpP9weB+ksfmcSBgKv3Y2XHn
WiUlLMrzzJTwmddendqDgaMYG3yrPvrLVawGQbqEx34WLA68RVGs8oPh0Hk3
pLFgBSovbIMgDRVAYz5Is/lQIDeMVDEb5lkwnMKig8UQpkqGG2A8+LiMYdxM
rdIHjNrpAHQWaYYgg16eNyvjmHH4nUp+9ZdR4h3SFPQWuvtJ9BtB7cATEqM3
irePY36bpDd5ENH+O0maIeyvCYjn3x8+2xvt4sejs58OqKPQ65Ff+ECW0bUf
rL2f0sCflrGfrbmJn82VA6Ob7WAwj4pFOR1E6TBcXQ/Hg236S83NjuBfH5cM
WNk+pK9EYt54a7yHSzg5qi5BBQqJII5+U6F3EsKXaBapLPe+hqb5U+96NNiC
EQ/TTBFao0IBwWSqh+P63hKAHPeIiQD6mQIyLghSefsubm4GN9uEkcvzYRiF
fRj+4TsYdzrIdA50T46Pj/e3RuPKpvChh09hoFMh/XPN2mewuTQBiteAt/is
rzZSSn1cxbD1AX6kZecqu45VMUxXfvDvq5L5+N9Go9H+1vbz0aad4IqqW9ll
0tgf7z476AwGg06n3we2nebEkZ3O5SLKPZAtJfIkcOo14qRYAA+rYJFEAWwg
U38ro4yZ1ktn3k8qA9zRJg8dzp4Yzva+/ulwAjidquJGqQQEWBhdRyE0ygmD
ODwSQBEpnMsv4NvcnysPpKfvJdAL2N/zYV1qBjANYQCDgIF3UsDzPMiiKfRe
pDfu8EAhQYGCAzrPoiwvvJWf4TQ9LwAZvMrS2UxluIAog2+MmMr+oKMrroib
adF+Bs2BNgtHhEHXAGQirBBbXKlV4U3X3jQtFl4ewSIHHoE3SoK4DBXDdZHm
tEImL/xjJoRVJo4iAVA7b/JonmC/6lNaWRlGRf2VIHoZhWGsOp0n3gm8SMMy
IKHcefLEOyuzVZorQqmWNkAOylvxC3yOC/70ScP+82cvL2BGPwt7HmxSZTcR
tLsCmZQg4GSUngd7LlKENqBFVdB/A6LFWypQD9LCwQeOwvAG/l4pRuRKs5HG
FtDCjb8WukGkTpWH+hRRjyuJVTgXhBCiQpwIsCK6CbYLQwJ3hPiQNoEIop0K
5cEr+BOHQGpIj0sUSYSt2EPtCSKpaEJJA0b2rhLiD3fr8FSmblAnLsChKgIS
L60H0+dFvK5oB3jKIwml50CFsF0ZDDB/gvuBhSxBUadhGqfzdc+dIF/4cYyA
C4AagUFnWbqEnWZqHoFcWOOe9H76uHO3Ly7Vy2BRgDdN8T7xuFqpBAU7wT5R
JYp7L0mT/rTMEfI5M/16AGJjuSpp9aG6jgLFHJans+IGrBHEOc4quwPBgPMi
oxBnMeSoQ2XfsisRJTjlnBGl7TFHmhSu1EMuVQ5C1jLSKo1gM4A2H8ZQQKeZ
Ci0kAAcZvMlVgeCyAOoxNG/AQlowZdhV6pH9IEDIpYkaeGf4vF+kfW7gCAAg
VZDGddgnayE5oD3D7bgWIhi3NYIyLQuURLyQAKiGO8PuNYKBymcMWA1HGoKJ
XOhDz0Nb1hNYKkLRBKBRMfBslpLSAIrVklCG/UoQKTIL+LFAhpyLDLWjEVER
lQGf19i8yCJ1rZDXUebhB1hRGOVATfgFplQRgYE2Hc0AnEBdORg7PZTcebpU
ZBWCyImWakBy8AjJImJbguQfWLooAMIcTPF3F5fdHv/13rylz+fHf353cn58
hJ8vXk1evzYfdIuLV2/fvT6yn2zPw7enp8dvjrgzPPVqj04nP3cZQN23Z5cn
b99MXncb9EqIRaGG8gX2AsSJ4oz0JetFovHvDs+80Q6I738B/T8ejZ6D+OYv
z0b7O/DlZqESnixNAF/8FaAH/LxaKT8jJABOAn8VFaxckclQTAOIEXoTr3t2
fH7x9o03+eH4zWUXhZ/mMuRcoNV8DZJiCeqrBHbAZ96NmnrTDMxYlaF0m0bo
B61WMZANIqHnTU6Gp7B2IhfmskQkNew6jYFmekwWmleUUT0u+adIM0BUM+JP
pOG8JJlCjNaqwIqaHAAAuNpv4E0SrwsbPbn8+bE7RnsON2wFt273x2yXle/9
261Ip/p+0W54JfaK47gh1xhrjzw25hwy3VHWwCt+XBWNOL6s/KDT+cb75ptz
xV5ivohWTsODb75xzUnaPcCt8JEVUlo3ikYkzswdQRuc2EAIU9ubjDWLFVQn
iBPQPoDAGEw71HsZexurFOYCwkRlRes0xjy5UmT1RtOSrLQHrxqkfR+lDk9R
oumQeepjsPCTueJpXqt5xUVuGxFlsS8GS0ztYxigRJ2n0GcJtN6rwhbA8KBN
AM6PSJGTQcnTkJTxyXIktLbBmdiBpnH5o4caEkw58BcC6koErnWmflKhERCB
VqcMarQWg/QXJwLdbiC7Y0KcVUokqRc+WupI43kaRGTsYXMGoPEfmQFM14F3
DCZilaDMy69yHoGGNyMIEmBNuAl4BhBlMAnk7OCdzrnzWvYh6mEJxOwBo4PM
BTlM5gNafXbAa3KNDN0AMcXK39ygRxa2poOZugFRAmSGKHSsXdqP3QqZuc4W
cndEknwSXzEWxE1axmBFg3/cuT2EwW5f465uT3nu287txVH/u8nF8e3odhLH
IPAbDGfb9Ce3402t2GAAwl0XUZC7fS5vtzd16tkerOPQgLmqrAv6n93uPGgA
3ZmHQrclihtjbd/uPnIwMxCPuw3mtjETMxqf/XNASknREGALQAFGTph4dcDN
dRtRj3vLMi6iVSXCSLIZcL+K/TXz1TFoxIzIBBCrsj4sp8KLMDt6MjlOjG6r
a/7ycJWObDrA02kZxQUK2YdGClyCBQ6lHfjaYgZBkBMzW8u7IF0DgNET+4WQ
NEiqpNA+mZUKC1hMkoKvglLLj4ENYC/gIQRiGcMcPsEXNO4VQihAkneEErL9
1EAB9ZifXYWoR78+PXqqnXly3HycbaHXoJckTPfu/DXaTbWRwbhKq8OT0dAX
MwlEQgQSGWUDzdMj7RUlaMIH2tUxCwLp8Ory9DXOjMEcEtpgR+QD733bkNJG
VqK1CxDlVa51bebf2OFNe6TYzX0aoW7dD7YPQJCdsB5u3SrtwSE3kZVk9LJc
Y5inM5A/f//73zs6mvYiTDGG+3LwoojDl8MXbNDFqkCzH7ECSgceo/h7SR0b
6zF7/aOnH75AUnk5WIbtC7kjX/DHLuhXMBR4Sa00U8eNZg8wYSW2Ekbg1hVa
m3F8Z6nBGqQl+S3A3yKcaQAJkxk6IhsRHTJckwptfyEleUuLiauWUw99v6hA
EYFsb20l02LD0F8yzgTs9WsTVWd3gP1JVJ2hxo8zqDZCObx2dPbT58+yngbG
f0TjSm8YhbYONLfQRKdzx0uDJBxRQh6aYmghNJM0EhL61PG8rkzePfBebKZH
vcSXPexC0RIFsimHXv9JAenuC0QrSgcBuV3Zyy60+Ct1NA9PQujZffHu3cmR
tVFYQUSO2/OyS90CWBBQHS5RrVKMu4CdzUuJQncN6QrxgiYwjBuFzsygxpZR
wYPo1hLic1tl6SKaRrVm8hC3b5te+3EUnqdxBQYZfOc2nc/MX/diLC9X6I6Y
+O915OPqKVK94tgp0tDJEXj077cPKZyyhP4hWQMD2SkHFYUSP8D3DxjQ9tdN
VYn2t+ZE6zixOQ9WMA/HXGt4Q9qHbALwsmG5tZGnaoY2JndBdzwKSQ8TpEAt
nGqbZYEJU0tkX9eY9GmLu0ApROI10T8fLA1+8KZxGlzxmkVs6h36LueiX9LC
mhLvzaKl77oaEshKyBWN/dUKsVOTDgOPQ0ofDHlpuFc0p19LapFLBFJFfcSn
OYhRH+1K5BqxzR1sWgCLrcHM/cHS6hfOaQd4zLSW7jdMG0c5yRzkBQpcmrij
DaXcNY8rPll6cVi5h9I2I6wMU+SLSJvTg3vYzPU4KVWgCdH1bUFTLQAFlYis
h/LJStYyif5WUvhafySZygFONrnPOYRJAZVrP4obEvw9274Vrxp243IhQAf4
gSwtHRF1wEp+sQ57RJhcyjCdkrJH72xba2bXTJZYjwYo2ODlNI6CeN3HkHWe
R7jcydkJtAg5PG7NEEn3hGS5SHMtsE02FSQSc4Q1dag9rqMyLmwO2XFl2Vjw
dLd146+i4fXIpOEdyJK0dcHf1IwgOAHrSO8oZH3vh+PLngkgMRBzZVpvMLtq
OnNUU1BdTJD3t/b6493L0ehgd+dgvP2vW/CvW1WAVmt8ov/hHRpqpBXJYqP2
9JxXQG8WURiq5DbzkysV3mo6dtpS5pqaXuInyvQojkm8O8mdhkEMtl5xRAFl
UprUyflOaKuQ6bsTpz/HO+/rXyHrSv8WQLjA2LSZmmVgmiJXUMuJI05CVWtV
ZjGbHUCc1lKpqSOthmp90WR+19q/1aar9UaMUVeMtc1BgOCDHgfmEVCMUSE2
siD432f59NeO/mYsC5YkjhODajdLC7LP05L5DtPtN9p4Y0VXN4lbC5dcszT3
tA9eC8OhwI6SUrGkWpL4N0IPZwfuvo7SMvdicLvLVW65rTYSJX8wTBZasWVE
BXAmEHrO+ke7vFfaECFODTi9z+J9ZKcRvqy0RrEjRgRWUeDmQrWK0/XSCS2U
q5DhmBEAK/HTy4qJqrdM0WQtLazUJA8BptOuEykxjrjO/EDXR5D6l5h1LPxa
DZuG68RfcuZt4E3imNW5pHZYTuEYFcknMXqzcbY0VQiSrO+9IlFy4E3YtqpN
x1UbH0nnoGe3xgHQwufdEJKaCUlMhuQBUFcZq543BRoMU3KsEp2nV5TNi/21
9ZuqABnA0s6JGTYtjYIwwi+AV1krbXKOgVIiL0EHaRkEKMMpTQjdwO5YHNUn
gkK7K5MwSHIl2RhVC5fqYRtUWxdyF2bcRTRftA0cY6L8SwcW60EGRIbn7THh
gzDQaRATq8MKhcAX10qZYhgJlcM4VPHiLcGlXZZLRtpNhPQlrhQap5zOlh1h
p/xhq2H18QWr8T/euxrGGy+GVnPaEhJFk4KSBRQF9JcOLsTBydOegTkuBsxb
Cec5OMLiho6d4U6mCXy3ICpes2yjbWI6W/ZBeRLkDJIPLu4Y3WxETRWKBR2X
D0FCJljXhRlCSnjOonmZsXVPcx9ulDp+jc2Yi8YAjjBKEcyFDvmNPGDg4Gqa
fvyHGTxuSqbN7GFmbzFyzls7Psq0kPh+zZpoM47eJtpPI2qaIj0L2wyq3Vtt
I+qOhABkdd8AYi2MWk2cPOxP/Vy1WjbaamajeaA+FsNs2NrBMWfu6jTc3h8N
BoPxaI9iho5h0nsYYPuTywfAdoIBcoatSaRUsjoPADCNoQH8kFEEyuO7oNwH
CnwsoBt9Hghr6Dfc2goB3DsjfxO4xRDstXPSKgzaGEg7Ci0stDlp/IUMdXZ0
2J+cPAjniO7JCWInSiQdvU7LTAcCHoDzc0F3bRSSda2jaPQCoPp+9FDUroZt
7e9Gq+4zHPtbgNLR/n4dpZtN+ydPEBMk3asGneMuY3UO7VOSUhhuQX1Ucdm0
ZiOL3BpDpqzNKqqqHqMKKcz+0lPsGUomcVFJRg68tniGjV+Qra1z0W3Zedf/
p/ekrSmN59oS2k5Etf2g+ETuX//TgxPYXeISF6rgCt6MPYuNWHX2U49WkEt2
9vbCiVngN2+ahuv7s0WfNijj7gu/5jFXotcNm0riT1KxpwPDdklc9YRlZEQ+
ukAD3mExrfFuTB7RXwHeVhm1cbwsbxKGkcTyHfzpWJ4JSMtuCTY6TgmcUcJD
8E0D6aTjd7lQB5GFxnYlbsxelK32nYJ06a+oOAaxI9lMKs23EzRDf+0Mezev
mFifZpj8iznmIaG/Gh9pGP1PjPI5jHQfkO+K9XEA4VFxvkczzD+B8pzyKbdM
ZKmw8izKl1zPd0gq2AGVqV3B10+8t0kf/AupflmluR97tVqRatF5r1kcBsiu
xPsqZx2CoMxywgXFdqQsjoIvaHhQJfSry8uz4UUP60OyZnJKL5iKRQyFxamA
WuSJuyIrlUhRLku0vP0rLh3jIIvkrOQYSGagokI52wFfwUZnlwuLP8E+Cbju
cQUGiZ+jBw9uWVSkmdSzs7HDIjKaJ6lsRVumXItf9fZkLoZsPXjEtSCmQi83
6RGdMeRSUVjRu5zr7whrxLWpyezompM8Kqgw0anIBSL6HmsGek2Qo9RAXxP5
XDI8tEsWuBIrCxU8j2kFN5UooVgSEndi9qOOwmstyWiNV9eoukc4lMWXh9a1
Y97lA5PmeXugeEOgt2K/sRj4XZx3pwurVh2/a8/yTLHK8N2JmZG5yFKa0Q6F
RL3yQofRzHj/QFS0O/33IOTRruomR+ne2Wd+nD9q+k3e24Nctcdv+073ouJM
YPmKHr9WrE10Y3O46ChQcM0a3RUBr4UlMrUctwsUS8pKKpR0vEkIW0OOJD3F
3RyLDibCmleZz5a1syHJYxtpf+1nXG7YVqdrNAFyk2R7nf2KyUrHqIuCWawh
8Aw7uRsHAfkGYN6i8mgZlBFnJpU6RRAbXBofx628WpkStY55QzFKKROElTLC
TS2/eWCLD0mKQOPKevHID2FJwu90FqdXd96c1MuvLBkq6tLaR4gszIWIuI/A
BVcrPwkw8f7ax+NrLaDR5mylkLWWYHI1BSYH5uagnlPuiu5tHWgDNloOOQGF
GaZWq+X3MVqoetMxUFqtGHzlLWB3dKgP49Y0Lx0IgKEUFTqLDbBJ3WPVeObP
23Q+kZZg0wS0A3/FiY5ICi2QH/Pcsw/R/pb6otQYeNZ+teXL7rGJctUHeiTz
Nr2KXI+jAh3AlRQO5taCuGlxcZZgcuVUjyLBz1SKf6MA63LIrF3R8WB7ZMN6
ELjxyJ6I4YOXYYutQnkCoLoy4+IXMfMdxPChBD2SXk51KhEsesNi6cyi2J4E
RRYVCwYgdp/hLCr1P/oyb98WB2M5G7ljDkrMakD0v3QSvbAarqpk+8tuQrYp
O5RN9eo4kDJklRWWwXX1rzZM2YFbEn7IF8HjMirBwpuEslamJ5Zb69xuvGYf
/posC4BJnb0kX4OysAZ6IxGJtkm1eRMdQdBH8mQtOG9+73Bo2MILHkwfz+Zt
V6qU8KYGErMe3tegH1cLkxiiPYk10GFWGhZIL13JqRD9hE6rGukczSjTSOlT
4g3cJVpjLfKn6v0Z+lr5WL5Lkp+r8BZ+aM9H2piHrPU+IvRmMDqHKU5BMsw5
AnVmPJhT48GAvcB1h58+ybUCVCCXekvup1p7eV+fnT4V9VFimRfmh/JqLlYX
colc0sLOYJEoy3XlEZszGBxPQEZUHdqrwO7C0ogIsqphodapDko1jAFN0RHb
AX7CyewZkb2cqa2fpGVCRQArPMcDXfRBDb/g1ZN8ISvHnPvCgzVMsqT2jHEu
Z2sc6gLz5O3J0SHYMagGjdpz7gXwa66e9ZOpIy1e4je5nNnWgQjtm9HiYE9T
8g/1KhvnsFw578dzwHGxWHY6b/WBipqmD1SkFb2zV+cksQ37tdpAPSkarQ/9
Ve79mk7ZA0vCWDXDzxPRs1qC15YmYUgMBlH6Gc95ta0w1/B2TvzXzrnRkTQw
t7KltfOMMNTlm5WYW27NbrFuayYMW2nVFRv8cUiCq0Oy1rIBP2kqQZkxb7NV
wSinql2/OZh7ju2yUkyC58qKqve6YEGVq+phdmJGMpnoYgVuIfSeW8nGkU2O
gpDLirtDlxemvtUrNlC4re3LPBCzBh+cU32Qd9u57df/NZ5sfuCcZ9N/b8/Y
wSEzStgQ6cCeJ515um2ztz359iXDQLffZ6De7zMgNG5sEZ7dgiDiwBrIMpGI
UiZOT4ngTHOcRxeN3bIJf06IxYlbjrQRi1C0j6wkQwRtp9+4uoglfQv1M0U7
dOhoWKLDSjC2bilRYYcc9XXm1BvXpcXsH4tbDHviG0bA/5aiJxTdMzbhylVF
OdrcHPONe99Eu9eJag+0ZZ+qNfhM+UoOpbRYa36MntdaJ+RQyq1MYLCgQuJQ
zXzkI0cFU3j5QhNG9YD4az7iimqpwGu4+DYwNlYrddUidKobkqPk2/qkbHWY
nq7U4ls2THCCWkgFmqQbnGI3IgA+bEBRAzM4zIRnWPn4KpWSoqy4RZYf3V5Q
XhnDLjQ0liEWyl0MtBrfHmbrVZHOM38FK6q93b6d4G0VpFGCze3QsOICMLQc
qWYRTCTBb65AbpInAER4Lccqjd1EG7Vj2c7iB9POvNGBd+9mrEdMy+hVtEfu
VNFVUeiboiDPnuCkR8hstQyVa7E4iB+0zaWJjtxZM0UKNCyj43HCJFSZs+gG
sdTWijYRAsCcN63OS34iXnayACKju3ekRCTJ0UhI6EkGzhaY9Dqqj17zlONS
rMqjiqnaY/MhQYfKnEow9zZVkDQ+8DbS0hcjRyIJeDrAHZvKz6xcd1HRcvZV
hFhZANn9xl4m3clU8I0pbbnIatCJnC23i41soL+15mtmQA5bgwi8XXuqg4Ib
toC4LTwnF+Tc+OuW6SQ3nN4k7RYX372hL+KIZk3i4OQJCpMbkJkIarSWTJgF
z/7hASAub9eGrF0/O7K2iclFtiJF4m0m4cp5yqOTI6CXixakOQaWHAnG2H54
dDHxfnx/KbfuuPBwbkfgGhGAHJ/3oNfiOrKwCXTSUBOSy8i4Ju97us2CrDkB
XqWBvb0Gq9A1mVhEWIvyexVCc4nj8EWCNunwLSXxPxY23dpy5V+S45V/w+uR
BNBtfDwK8TaKgSQkBugODq/Hw6D4SNHxOLTn9yxWjwzGmtmKiEocYdwDGfNg
Bpo9rMxw8MPRr4PBwCmukhC/NHIKqfDiw2vFUppyI3bt8q4yctctDmqpu9zt
j7b621uXo72Dra2D0c5fOP0SKgwbXktDk8l42Gai8k96M10M56Md+MrPF9R1
y9/b3plu7QfKH4/952r72d6umu7uPn+mtnae7e1t702n+/vj5/t709nzbS7Z
7EpM7wuBuxvsV4Arox23ZKeavZs4Ie+6W4MquIlZ8QasQkrMUEXctxsG68rJ
gLsx4DLVKfFUc/dGGmaPwwp3fgAdUMMqLSQgh3tV8D/Z3Z3uj/39UTje2R5N
Q8DnaGu6vbM/G03H++PQt2OB1MAez8vwl2lxeBr//OfzV1eX6/WfTt8UhzvP
/Ovl4d7W7PAvi/dvTqZv8zfRVhP+fCFcHQG2vLg7Hmx1derqciGX0Nwl1ui9
FWsfHrG8DzpAgFlX0nuYzSI7LcqrUo2SABInzDcqBRtCnip99t77IJj80CMR
TGcW7hC+zrldGKyyCDyHQdZ05TIorYTEd2+eJRBtgwrmx/cXjijm68L2d0e7
nz97/gwvDKi/fLb/DF/SNZZ+wpe/yTWFnKPGrUVJlBdatWGyYYrOGiZPQKLR
5YahMuWDtH8/Xi38BHaVSTe+IDDjyrhkzVBotjM1POgBQlMKglJQy55y0fk9
3C9VyIklIV6kibBTnSC3poRjPUhYOUSv/Y0V5+bslJRbc3KXeFGeVpM2QOcQ
qGkmAS/3lU/RIkvWdfsLzRJdHkCEYKyQjZQ0aCtnAkZjOdTyqFntLynqxpn/
iu59gQmLoT/c38Ec+PZ2qCtd/9qsI+bT/6Nwtr+vZuO+2g72+juz8bT/bPd5
2N/efx5Mnz+DgfaftUm80f7e1t54tDfe33323JFmtYXdI1F/vgxQojYW2bwo
wFU7fVNY7tQCm5c6btIyavNiAf2cbwhyh3OciPb53AZylVDltS53byyj5dIC
es6ssWEK9zHKGTOsW9/QNXfs3EdIj7VCzOgqfJsw+kfPdkbjrVFDuYB0G/54
eGG7/XqDG+2q9Y8w2snh3Oqdz3zfA/Henx6v17SG+t/um3Kqeq4vnDNhCMo2
mEHCWlzD4Lri2m4feA8IhDScXBOR096ESK9G7aQbQjJH9SsFJr+pLO2bS4J5
k6YmpVbgapKDFBb0K9AB6dos6rB6FaWwU7ds/TmENJ68XXD1OWl7sxqdgqmO
pU0KrFomBVx9HeUmpIlbbduQvZTHKIMiXfWZHO1I6RSLPHoSUqPrOfIi1/YD
0BLYxe4xAC7UwYSJxTaDjEcy87ebALom3PcuXk3Gu3teGM0xy2x9YhLnbRfV
NHcp5d50bnXiiYuIzcmWqFzC4/SlxjaVrwvOzQbBsjJKlYFMPWpE1LxFoy2j
2JHTkI314+Cy1/9F0uJLZIGgu8JH+kAkg8QUZnH7G77hRqqLNO8s09AaMnWc
NSrtG0Zbp/O9LSOR/Bluvi0JXLGia6CvXXSZP/jkSXbH4pjaH1A0b84CNBf9
37olYyh0bopUeR0cK3br4qu3kDZJlZnu67wab0YnoUIccjYJnJinzqF8Pqdh
ZM/mW6cGd6L6D7jXg+f45a761TaD2fuSW7Sk4wa72rv3Rq2abde0rx94u5Z0
3nzHlrHbmitsu2+rua52k9qr3cDV0q/daPZa7uRqdt5g6nruLV3SSz59rlib
JKN+0ZZlhay7zYZ3nIxssYEFno+3g82kG21harHJHqaX7TYxAaDNsP9/wv8/
Tfgs4fsi4cV/wv/cEvNa2rEpqclSwfSOvSbsg5nrA5pxPSlyzqtVOcoqbs55
mGKsmurhNPg0/ShZ66Mo59g1R5Z0L60N+EyUE8PTzTudM138hj+3hMVv/KsT
rJzdA5q6D19/SpqnOxzcqDgm8zEZdjHklK03aP3IKLC7lbk7ov6pqsrxEavN
G7rOrRFsVXjsazmn2wJTUq2TK6Zw2OZO5qqwOvKXtoMiIFocs6Pb0osO9W3s
S2/buomG3tSPX3NHDNU9ekKhaJ1e4NuR2CF1L/5E01z/goOHxz/wJh7r3+lT
sFKkxGbrRZ0IqWgFTT9dwFovvmqQbV4/HJbyTzi4g2AdFRU9n2tqoMu7nZPz
pvphvLV1e1HSIU9O6TvGK9/jbuKxGPCEHjtbo9tLXVgit6Y6RxLRJowSkkB0
b1Akp0fTK5U8pe7ble7VrhiKoAF1NV2q/QMpLZTF72zt3F7aymUVSvVl5TIi
8b/CVOXJV3KXEfTdhS2/S/gnEthzjrnSPqGf/yGZorIszajt+PY7P/Sw7PXG
X9OTbSoYwRL1MjG5anqzc/sDtyMFAq7MLf0s0+TNBM8p0GWYUin36Qk+/Sw3
SS3VMrU/IZXYOyxg+9gO8IlVONoba4yl33yu/9iX5DYIorOZ1BZV3Dr8fkKb
V+ha0S9KTf3gqtP5L3KMtZ4OcQAA

-->

</rfc>

