<?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.38 (Ruby 3.4.10) -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-xu-efficient-agent-discovery-profile-01" category="info" submissionType="independent" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="Agent Discovery Profile">Metadata and Query Profile for Efficient Agent Discovery</title>
    <author initials="J." surname="Xu" fullname="Jinliang Xu">
      <organization>CAICT</organization>
      <address>
        <postal>
          <street>No. 52, Huayuan North Road</street>
          <city>Beijing</city>
          <region>Haidian District</region>
          <code>100191</code>
          <country>China</country>
        </postal>
        <email>xujinliang@caict.ac.cn</email>
      </address>
    </author>
    <author initials="B." surname="Li" fullname="Bingqi Li">
      <organization>CAICT</organization>
      <address>
        <postal>
          <street>No. 52, Huayuan North Road</street>
          <city>Beijing</city>
          <region>Haidian District</region>
          <code>100191</code>
          <country>China</country>
        </postal>
        <email>libingqi@caict.ac.cn</email>
      </address>
    </author>
    <author initials="R." surname="Zhu" fullname="Runkai Zhu">
      <organization>CAICT</organization>
      <address>
        <postal>
          <street>No. 52, Huayuan North Road</street>
          <city>Beijing</city>
          <region>Haidian District</region>
          <code>100191</code>
          <country>China</country>
        </postal>
        <email>zhurunkai@caict.ac.cn</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>General</area>
    <workgroup>Independent Submission</workgroup>
    <abstract>
      <?line 49?>

<t>This document defines a metadata and query profile for efficient discovery of
autonomous software agents.  The profile describes how agents publish
capability metadata using explicit tags, natural-language descriptions,
example tasks, protocol bindings, and operational constraints.  It also
defines JSON metadata, discovery request, and discovery response objects that
enable discovery services to combine structured filtering, semantic retrieval,
and fine-grained matching while preserving an interoperable protocol surface.</t>
      <t>The profile does not mandate a specific machine-learning model, embedding
model, database, or ranking algorithm.  Instead, it standardizes the metadata
and result evidence needed by clients and discovery services so that different
implementations can interoperate while optimizing their own latency,
scalability, and ranking quality.</t>
    </abstract>
  </front>
  <middle>
    <?line 65?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Agent ecosystems require a way to find suitable agents from large and dynamic
candidate sets.  Exact lookup by identifier is not sufficient: users and
agents often express intent in natural language, while available agents expose
capabilities using heterogeneous names, descriptions, tags, examples,
protocols, and endpoint metadata.</t>
      <t>Discovery implementations trade retrieval cost against expressiveness.
Tag filtering, semantic description matching, and example-level matching
provide complementary signals without requiring a shared ranking engine.</t>
      <t>This document defines an efficient agent discovery profile that separates
agent metadata into complementary signals:</t>
      <t><list style="symbols">
          <t>explicit capability tags for fast structured filtering;</t>
          <t>natural-language descriptions for broad semantic matching;</t>
          <t>example tasks for fine-grained intent matching;</t>
          <t>protocol and endpoint bindings for reachability; and</t>
          <t>operational constraints for safe candidate selection.</t>
        </list></t>
      <t>The profile standardizes published metadata and query results, not their
internal indices or ranking implementation.</t>
      <section anchor="problem-statement">
        <name>Problem Statement</name>
        <t>Agent discovery has two competing requirements.  It must be expressive enough
to match natural-language task intent against heterogeneous agents, and it must
be concrete enough that independent implementations can exchange metadata and
queries without sharing the same ranking engine.</t>
        <t>Existing mechanisms can publish web resources, service descriptors, or tool
manifests, but they do not by themselves define the discovery-specific
combination of capability tags, broad descriptions, example tasks, freshness,
matching evidence, and ranked responses used by this profile.  Without a
common profile, discovery services either expose platform-specific metadata or
return opaque rankings that clients cannot validate, debug, or compare.</t>
        <t>This document therefore standardizes the metadata and query surface, not the
internal retrieval implementation.</t>
      </section>
      <section anchor="applicability">
        <name>Applicability</name>
        <t>This profile is applicable to registries, directories, marketplaces, gateways,
or local discovery services that need to return candidate agents for a task
intent.  It is not intended to replace exact identifier resolution, endpoint
security, or post-discovery invocation protocols.</t>
      </section>
      <section anchor="goals">
        <name>Goals</name>
        <t>This profile has the following goals:</t>
        <t><list style="symbols">
            <t>define an agent metadata object suitable for high-performance discovery;</t>
            <t>support both structured filtering and natural-language intent search;</t>
            <t>preserve fine-grained capability signals for multi-purpose agents;</t>
            <t>define discovery request and response fields that are independent of any
particular ranking algorithm;</t>
            <t>allow discovery results to include matching evidence and confidence signals;</t>
            <t>support incremental metadata updates; and</t>
            <t>provide security and privacy guidance for discovery services.</t>
          </list></t>
      </section>
      <section anchor="non-goals">
        <name>Non-Goals</name>
        <t>This profile does not define:</t>
        <t><list style="symbols">
            <t>a new transport protocol;</t>
            <t>a new URI scheme;</t>
            <t>a mandatory registry topology;</t>
            <t>a mandatory ranking formula;</t>
            <t>a mandatory embedding model, language model, or vector database;</t>
            <t>a reputation system; or</t>
            <t>an invocation protocol for executing tasks after discovery.</t>
          </list></t>
      </section>
      <section anchor="requirements-language">
        <name>Requirements Language</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>
      </section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <dl>
        <dt>Agent:</dt>
        <dd>
          <t>An autonomous or semi-autonomous software system that exposes one or more
capabilities and can be selected for invocation.</t>
        </dd>
        <dt>Agent Metadata:</dt>
        <dd>
          <t>A structured object that describes an agent's identity, capabilities,
examples, protocol bindings, and operational constraints.</t>
        </dd>
        <dt>Capability Tag:</dt>
        <dd>
          <t>A short normalized label that identifies a capability, domain, industry,
task type, or other discovery-relevant property.</t>
        </dd>
        <dt>Context Description:</dt>
        <dd>
          <t>A natural-language description of an agent's purpose, scope, and supported
tasks.</t>
        </dd>
        <dt>Discovery Request:</dt>
        <dd>
          <t>A request sent by a client or agent to a discovery service to obtain
candidate agents.</t>
        </dd>
        <dt>Discovery Response:</dt>
        <dd>
          <t>A response containing ranked candidate agents and matching evidence.</t>
        </dd>
        <dt>Example Task:</dt>
        <dd>
          <t>A short natural-language example of a user request, agent-to-agent request,
or task pattern that the agent is intended to handle.</t>
        </dd>
        <dt>Matching Evidence:</dt>
        <dd>
          <t>Data returned by a discovery service to explain why a candidate was
selected, such as matched tags, matched examples, score components, or
policy filters.</t>
        </dd>
      </dl>
    </section>
    <section anchor="profile-overview">
      <name>Profile Overview</name>
      <t>The profile has two interoperable surfaces:</t>
      <t><list style="symbols">
          <t>the Agent Metadata object, published by agents or registries; and</t>
          <t>the Discovery Request and Discovery Response objects, exchanged between
clients and discovery services.</t>
        </list></t>
      <t>The field names and examples in this profile use JSON <xref target="RFC8259"/>.
Other serializations MAY be used by a transport or registry binding only when
the binding defines an unambiguous mapping for field names, value types,
arrays, objects, and unknown-field behavior.</t>
      <t>The base profile defines the objects and processing semantics below, not an
HTTP endpoint or publication transport.  A binding supplies transport framing,
profile identification, authentication, and applicable limits.  Peers select
it by configuration or negotiation; unsupported required bindings fail
explicitly.  Extensions add fields or constraints with defined semantics;
local policy can restrict disclosure or use, but cannot relax hard filters.
JSON examples are illustrative objects, not cryptographic test vectors.</t>
      <t>The following figure shows a typical implementation.  It is illustrative, not
normative.</t>
      <figure>
        <artwork type="ascii-art">
             metadata publication
   Agent ----------------------------&gt; Discovery Service
       \                                 |
        \                                | builds indices
         \                               v
          \                       +-------------+
           \                      | tag index   |
            \                     | context idx |
             \                    | example idx |
              \                   +-------------+
               \
                \ discovery request
                 v
   Client ---------------------------&gt; Discovery Service
   Client &lt;--------------------------- ranked candidates
                    response with matching evidence
</artwork>
      </figure>
      <t>The discovery service MAY build separate internal indices from the same
metadata.  For example, it might build an inverted index for tags, an
embedding index for descriptions, and an example-level index for task
examples.  These internal structures are not part of the wire profile.</t>
      <section anchor="conformance-levels">
        <name>Conformance Levels</name>
        <t>This profile defines three conformance levels for incremental adoption.</t>
        <texttable>
          <ttcol align="left">Level</ttcol>
          <ttcol align="left">Name</ttcol>
          <ttcol align="left">Requirements</ttcol>
          <c>D0</c>
          <c>Metadata</c>
          <c>Publish Agent Metadata with <spanx style="verb">id</spanx>, <spanx style="verb">name</spanx>, <spanx style="verb">description</spanx>, and at least one <spanx style="verb">bindings</spanx> entry.</c>
          <c>D1</c>
          <c>Structured Discovery</c>
          <c>Support Discovery Requests with tag and protocol filters and return ranked candidates.</c>
          <c>D2</c>
          <c>Evidence-Based Discovery</c>
          <c>Support D1 and return matching evidence and freshness data when requested; include score components when computed and disclosable.</c>
        </texttable>
        <t>Implementations SHOULD state the highest level they support.  A D2 discovery
service MUST accept D0 metadata and support D1 queries; it need not operate a
publisher.  Clients MAY use lower levels when local policy permits, but MUST
NOT assume that a D0 publisher supports query processing.  These levels are
functional contracts, not security or ranking-quality certifications.</t>
        <t>For a D2 service, <spanx style="verb">include_evidence=true</spanx> MUST produce at least one applicable
matching-evidence item and source freshness information for each returned
candidate.  If access policy prevents disclosure, the service MUST omit that
candidate with a coverage warning or return an error, rather than claim that
the requested D2 evidence was supplied.</t>
      </section>
    </section>
    <section anchor="agent-metadata">
      <name>Agent Metadata</name>
      <t>An Agent Metadata object describes an agent for discovery.  It MUST be a
single JSON object unless another serialization is explicitly selected by a
binding profile that preserves the data model defined in this document.</t>
      <section anchor="top-level-fields">
        <name>Top-Level Fields</name>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>id</c>
          <c>string</c>
          <c>MUST</c>
          <c>Stable identifier of the agent</c>
          <c>name</c>
          <c>string</c>
          <c>MUST</c>
          <c>Human-readable name</c>
          <c>description</c>
          <c>string</c>
          <c>MUST</c>
          <c>Natural-language context description</c>
          <c>tags</c>
          <c>array of string</c>
          <c>SHOULD</c>
          <c>Normalized capability tags</c>
          <c>examples</c>
          <c>array of object</c>
          <c>SHOULD</c>
          <c>Example tasks or request patterns</c>
          <c>bindings</c>
          <c>array of object</c>
          <c>MUST</c>
          <c>Protocol and endpoint bindings</c>
          <c>auth</c>
          <c>object</c>
          <c>SHOULD</c>
          <c>Authentication requirements</c>
          <c>constraints</c>
          <c>object</c>
          <c>MAY</c>
          <c>Region, policy, cost, rate, or data constraints</c>
          <c>status</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Operational status</c>
          <c>expires_at</c>
          <c>string</c>
          <c>MAY</c>
          <c>Expiry time; later results must be identified as stale</c>
          <c>version</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Metadata version or capability version</c>
          <c>updated_at</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Timestamp for freshness checks</c>
          <c>signature</c>
          <c>object</c>
          <c>MAY</c>
          <c>Signature or credential binding metadata</c>
        </texttable>
        <t>Field names are case-sensitive.  Implementations SHOULD ignore unknown fields
for forward compatibility, but MUST preserve unknown fields when acting as a
transparent metadata relay.</t>
        <t>This forward-compatibility rule applies to non-critical fields.  The critical
extension rules below take precedence for decisions depending on an extension.
Required fields MUST NOT be null or of a different type.  Optional null values
are invalid unless an extension explicitly defines their meaning.  Missing
optional arrays mean no additional entries; an empty <spanx style="verb">bindings</spanx> array does not
satisfy D0.  Absence of assurance data does not mean that a claim was verified.</t>
      </section>
      <section anchor="identifier-and-name">
        <name>Identifier and Name</name>
        <t>The <spanx style="verb">id</spanx> field MUST be stable for the lifecycle of the agent registration.  It
MAY be a URI, DNS-based name, registry-local identifier, or another
profile-defined identifier.  This profile does not define or reserve a new URI
scheme; when URIs are used, their schemes are defined outside this document.
Discovery services MUST NOT assume that the human-readable <spanx style="verb">name</spanx> field is
globally unique.</t>
        <t>Identifiers MUST be compared as exact strings unless a shared identifier
binding specifies another rule; arbitrary case folding or URL rewriting is
not permitted.  Scoped identifiers require an agreed namespace and issuance
scope.  An optional external-identifier
association extension can retain a native value, namespace or issuance scope,
relationship type, and evidence reference.  A resolver location is not by
itself proof of either namespace authority or ownership.  Locally scoped values
need their original scope to avoid collisions.</t>
        <t>An association declaration is not necessarily an identity-equivalence claim.
Matching external identifiers MUST NOT alone merge ownership or authorization
records.  Extensions using DID-specific equivalence terms MUST follow those
terms' applicable specifications rather than infer equivalence from an alias.</t>
      </section>
      <section anchor="description">
        <name>Description</name>
        <t>The <spanx style="verb">description</spanx> field provides broad semantic context.  It SHOULD describe:</t>
        <t><list style="symbols">
            <t>the agent's primary purpose;</t>
            <t>supported domains;</t>
            <t>important input and output types;</t>
            <t>operational limitations; and</t>
            <t>safety or policy-relevant boundaries.</t>
          </list></t>
        <t>Descriptions SHOULD be written for discovery and interoperability, not
marketing.  They SHOULD avoid unsupported superlatives such as "best",
"perfect", or "guaranteed".</t>
      </section>
      <section anchor="capability-tags">
        <name>Capability Tags</name>
        <t>The <spanx style="verb">tags</spanx> field contains normalized labels.  Tags SHOULD be selected from one
or more declared taxonomies when possible.</t>
        <t>Tags SHOULD be concise, lowercase, and stable.  A tag SHOULD represent a
capability, domain, task family, data type, industry, protocol, or language.
Examples:</t>
        <figure>
          <sourcecode type="json">
["translation", "finance", "invoice-processing", "json-output"]
</sourcecode>
        </figure>
        <t>Discovery services MAY expand tags using taxonomy relationships or synonym
maps.  If expansion is used, the response SHOULD distinguish directly matched
tags from expanded or inferred tags.</t>
        <t>A binding profile using governed tags MUST identify the taxonomy and version
used.  Hard-filter expansion requires defined semantics or explicit client
selection; an implementation MUST NOT silently treat a parent tag, inferred
label, or same-named tag from a different taxonomy as an exact match.</t>
        <t>Without a declared taxonomy binding, tags are compared as case-sensitive exact
strings.  The lowercase recommendation is a publisher convention, not permission
for receivers to change an existing tag's meaning.</t>
      </section>
      <section anchor="example-tasks">
        <name>Example Tasks</name>
        <t>The <spanx style="verb">examples</spanx> field preserves fine-grained capability signals.  Each example
SHOULD describe a concrete task the agent can handle.</t>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>id</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Stable example identifier</c>
          <c>text</c>
          <c>string</c>
          <c>MUST</c>
          <c>Example task or request</c>
          <c>tags</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Tags associated with the example</c>
          <c>input_schema</c>
          <c>object</c>
          <c>MAY</c>
          <c>Expected input shape</c>
          <c>output_schema</c>
          <c>object</c>
          <c>MAY</c>
          <c>Expected output shape</c>
          <c>language</c>
          <c>string</c>
          <c>MAY</c>
          <c>Language tag</c>
        </texttable>
        <t>Example tasks SHOULD be specific.  For a multi-purpose agent, publishers
SHOULD include examples for distinct capability modes rather than averaging
all capabilities into one broad description.</t>
      </section>
      <section anchor="protocol-bindings">
        <name>Protocol Bindings</name>
        <t>The <spanx style="verb">bindings</spanx> field tells a client how the agent can be contacted or invoked
after discovery.</t>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>protocol</c>
          <c>string</c>
          <c>MUST</c>
          <c>Case-sensitive protocol token; <spanx style="verb">https</spanx> denotes an HTTPS endpoint</c>
          <c>endpoint</c>
          <c>string</c>
          <c>MUST</c>
          <c>Endpoint reference or URI</c>
          <c>media_types</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Supported request or response media types</c>
          <c>interaction_model</c>
          <c>string</c>
          <c>MAY</c>
          <c>
            <spanx style="verb">request-response</spanx>, <spanx style="verb">streaming</spanx>, <spanx style="verb">batch</spanx>, or profile-defined value</c>
          <c>priority</c>
          <c>integer</c>
          <c>MAY</c>
          <c>Non-negative preference value; lower values preferred, ties unordered</c>
        </texttable>
        <t>An <spanx style="verb">https</spanx> binding uses an absolute HTTPS URI as its endpoint; application
operations and authentication still require the endpoint's native contract.
Other tokens require a shared binding defining their meaning.  An unknown token
can be retained as metadata, but MUST NOT be invoked without that contract.
Missing priority expresses no preference.</t>
        <t>Discovery clients MUST verify that a binding is acceptable under local policy
before invocation.</t>
        <t>Binding extensions MAY advertise protocol versions, supported operations, and
security profile identifiers.  Transport support, mutual authentication,
terminal stream integrity, and per-event authentication are separate claims.
Clients MUST NOT infer one from another.  A security claim's publisher and
verification scope remain subject to the provenance rules below.  This profile
does not define the corresponding handshake or invocation protocol.</t>
        <t>The <spanx style="verb">auth</spanx> object describes access requirements, not an access grant, and MUST
NOT contain reusable secrets.  A binding locates an interaction with this
agent; an independently versioned Skill or descriptor is not automatically a
callable endpoint.  Optional typed relations can reference such objects without
reducing their identity and version to an unqualified tag.</t>
      </section>
      <section anchor="versioning-and-extensions">
        <name>Versioning and Extensions</name>
        <t>Metadata publishers SHOULD include a <spanx style="verb">version</spanx> field and SHOULD update it
whenever the meaning of capabilities, examples, or bindings changes.</t>
        <t>The base profile has no in-object declaration of critical extensions.  Its
unknown fields are non-critical and follow the compatibility rule above.
An extension profile needing mandatory processing MUST provide an explicit
profile-selection or criticality mechanism understood before those objects
are accepted.  A receiver MUST reject an unsupported required profile rather
than process its object as a base-profile object.  An unknown constraint remains
an unsupported hard filter, not a ranking preference.</t>
        <t>A transparent relay MUST preserve the signed representation, including unknown
signed fields.  Redaction or transformation is permitted when required by
policy, but the relay MUST NOT claim that an original signature covers the
transformed object.  It can instead provide a verifiable reference to the
original object and separately identify its derived summary.</t>
        <t>Private extension fields SHOULD use collision-resistant names, such as
reverse-DNS names or URIs.  Extensions that affect ranking, authorization, or
wire compatibility SHOULD be documented in a stable specification.</t>
      </section>
      <section anchor="status-and-freshness">
        <name>Status and Freshness</name>
        <t>Timestamp fields use RFC 3339 <xref target="RFC3339"/> date-time strings with a UTC offset.
Receivers compare instants, not lexical spellings.  The applicable binding
defines acceptable clock tolerance.</t>
        <t>The <spanx style="verb">status</spanx> field SHOULD use one of:</t>
        <t><list style="symbols">
            <t><spanx style="verb">active</spanx></t>
            <t><spanx style="verb">inactive</spanx></t>
            <t><spanx style="verb">suspended</spanx></t>
            <t><spanx style="verb">deprecated</spanx></t>
            <t><spanx style="verb">testing</spanx></t>
          </list></t>
        <t>The <spanx style="verb">version</spanx> field identifies a source revision, but arbitrary version strings
are not necessarily ordered.  Update bindings MUST define a source-scoped
revision comparison or conditional-update mechanism.  <spanx style="verb">updated_at</spanx> alone MUST
NOT override that mechanism or order revisions across independent sources.
Discovery services SHOULD expose when a result was indexed and whether the
source metadata is older than a client-supplied freshness constraint.</t>
        <t>If <spanx style="verb">expires_at</spanx> is present, discovery services SHOULD stop returning the
record after that time unless local policy explicitly allows stale results.
Such historical or stale results MUST be identified as such and MUST NOT be
represented as satisfying a current-use freshness constraint.  Source update,
local receipt, indexing, and response generation times are distinct; refreshing
the index or response MUST NOT renew source evidence validity.  Stable identity,
registration lifetime, credential validity, and observed endpoint availability
are also distinct.
Publishers SHOULD refresh records before expiration and SHOULD use random
jitter for large fleets to avoid synchronized refresh bursts.</t>
      </section>
      <section anchor="metadata-example">
        <name>Metadata Example</name>
        <figure>
          <sourcecode type="json">
{
  "id": "https://agents.example.net/id/hr-core-automator",
  "name": "HR Core Automator",
  "description": "Optimizes HR workflows and onboarding checks.",
  "tags": ["hr", "workflow", "onboarding", "hcm", "api-automation"],
  "examples": [
    {
      "id": "ex-1",
      "text": "Prepare a new-employee onboarding workflow.",
      "tags": ["onboarding", "workflow"]
    },
    {
      "id": "ex-2",
      "text": "Check an employee record for missing payroll fields.",
      "tags": ["employee-record", "validation"]
    }
  ],
  "bindings": [
    {
      "protocol": "https",
      "endpoint": "https://agents.example.net/hr-core/invoke",
      "media_types": ["application/json"],
      "interaction_model": "request-response"
    }
  ],
  "status": "active",
  "version": "1.0.0",
  "updated_at": "2026-05-08T00:00:00Z"
}
</sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="discovery-request">
      <name>Discovery Request</name>
      <t>A Discovery Request asks a discovery service to return candidate agents.
It MUST be a single JSON object unless another serialization is explicitly
selected by a binding profile that preserves the data model defined in this
document.</t>
      <section anchor="request-fields">
        <name>Request Fields</name>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>query</c>
          <c>string</c>
          <c>MUST</c>
          <c>Natural-language intent or task description</c>
          <c>required_tags</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Tags that candidates must satisfy</c>
          <c>preferred_tags</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Tags that increase ranking score</c>
          <c>excluded_tags</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Tags that candidates must not contain</c>
          <c>protocols</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Acceptable protocols</c>
          <c>constraints</c>
          <c>object</c>
          <c>MAY</c>
          <c>Policy, region, cost, latency, or freshness constraints</c>
          <c>limit</c>
          <c>integer</c>
          <c>MAY</c>
          <c>Maximum number of candidates</c>
          <c>include_evidence</c>
          <c>boolean</c>
          <c>MAY</c>
          <c>Whether matching evidence is requested</c>
          <c>detail</c>
          <c>string</c>
          <c>MAY</c>
          <c>
            <spanx style="verb">minimal</spanx>, <spanx style="verb">summary</spanx>, or <spanx style="verb">full</spanx> response detail</c>
          <c>client_context</c>
          <c>object</c>
          <c>MAY</c>
          <c>Client-side hints such as locale or domain</c>
        </texttable>
        <t>The <spanx style="verb">query</spanx> value MUST contain non-whitespace text.  Other supplied values
MUST match their declared types; null is invalid.  Unknown top-level fields
are non-critical unless a selected extension defines otherwise.  Duplicate
JSON member names MUST cause rejection of metadata, requests, or responses,
so parsing cannot select different meanings for the same object.</t>
        <t>A discovery service MUST apply <spanx style="verb">required_tags</spanx> and <spanx style="verb">excluded_tags</spanx> as hard
filters under the applicable taxonomy.  All required tags must match and no
excluded tag may match; preferred tags affect ranking only.  A tag appearing
in both required and excluded sets MUST cause <spanx style="verb">invalid_request</spanx>.  When
<spanx style="verb">protocols</spanx> is present, at least one returned binding MUST match one listed
protocol.  An empty protocol list is invalid.</t>
        <t>An unsupported hard filter MUST cause <spanx style="verb">unsupported_filter</spanx>; reporting the
limitation while returning apparently conforming candidates is insufficient.
Constraint extensions MUST define whether their fields are hard requirements
or preferences; an unknown constraint is treated as an unsupported hard filter.
A separately specified, explicitly requested best-effort extension MAY return
non-conforming alternatives, but MUST identify them as alternatives rather than
as satisfying the original requirements.</t>
        <t>When omitted, tag sets and constraints impose no additional restrictions,
<spanx style="verb">include_evidence</spanx> is false, and <spanx style="verb">detail</spanx> is <spanx style="verb">summary</spanx>.  A supplied <spanx style="verb">limit</spanx> MUST
be a positive integer; the service MUST NOT return more candidates than it.
An unrecognized <spanx style="verb">detail</spanx> value MUST cause <spanx style="verb">invalid_request</spanx>.
Bindings MUST document their default and maximum limits and input-size limits.
Requests exceeding a declared hard limit require a structured error rather
than silent reinterpretation.  Supporting bindings SHOULD expose limits and
query capabilities without requiring clients to know the internal search engine.</t>
        <t>Constraints such as <spanx style="verb">region</spanx> and <spanx style="verb">max_results_age_seconds</spanx> require a
constraint binding specifying respectively the region vocabulary and the age
basis.  In particular, a freshness binding MUST distinguish source update age
from time since authoritative current-state observation.  These names do not
by themselves define global geographical or freshness semantics; a service
without that binding rejects them as unsupported rather than guessing.</t>
        <t>The <spanx style="verb">detail</spanx> field controls metadata minimization.  A value of <spanx style="verb">minimal</spanx>
requests only identifiers, status, and enough endpoint data to continue
resolution.  A value of <spanx style="verb">summary</spanx> requests the normal candidate summary.  A
value of <spanx style="verb">full</spanx> requests complete metadata where policy permits.  Discovery
services MAY redact fields even when <spanx style="verb">full</spanx> is requested.</t>
      </section>
      <section anchor="request-example">
        <name>Request Example</name>
        <t>This request uses only base-profile fields and exact tag matching.</t>
        <figure>
          <sourcecode type="json">
{
  "query": "Find an agent for onboarding validation and API setup.",
  "required_tags": ["hr"],
  "preferred_tags": ["onboarding", "api-automation"],
  "protocols": ["https"],
  "limit": 10,
  "detail": "summary",
  "include_evidence": true
}
</sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="discovery-response">
      <name>Discovery Response</name>
      <t>A Discovery Response contains ranked candidates.
It MUST be a single JSON object unless another serialization is explicitly
selected by a binding profile that preserves the data model defined in this
document.</t>
      <section anchor="response-fields">
        <name>Response Fields</name>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>request_id</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Identifier for tracing the request</c>
          <c>candidates</c>
          <c>array of object</c>
          <c>MUST</c>
          <c>Ranked candidate agents</c>
          <c>applied_filters</c>
          <c>object</c>
          <c>SHOULD</c>
          <c>Filters applied by the discovery service</c>
          <c>unsupported_filters</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Unapplied filters only in an explicitly selected best-effort extension, not a base-profile success</c>
          <c>warnings</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Limitations or policy warnings</c>
          <c>generated_at</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Response generation timestamp</c>
        </texttable>
        <t>Every candidate MUST contain <spanx style="verb">id</spanx>; other fields follow the requirements below.
An empty <spanx style="verb">candidates</spanx> array is a successful query with no matching visible
candidates.  Inability to execute the query is an error, not an empty success.
Returned fields MUST match their declared types; null is invalid unless a
selected extension defines its meaning.  Unknown non-critical fields follow
the metadata compatibility rules.  A redacted response still MUST satisfy the
request's hard filters; omission of a field does not waive its constraint.</t>
        <texttable>
          <ttcol align="left">Field</ttcol>
          <ttcol align="left">Type</ttcol>
          <ttcol align="left">Requirement</ttcol>
          <ttcol align="left">Description</ttcol>
          <c>id</c>
          <c>string</c>
          <c>MUST</c>
          <c>Agent identifier</c>
          <c>name</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Human-readable name</c>
          <c>description</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Short description or summary</c>
          <c>bindings</c>
          <c>array of object</c>
          <c>SHOULD</c>
          <c>Usable protocol bindings</c>
          <c>score</c>
          <c>number</c>
          <c>SHOULD</c>
          <c>Overall ranking score</c>
          <c>score_components</c>
          <c>object</c>
          <c>MAY</c>
          <c>Structured score details</c>
          <c>matched_tags</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>Tags matched directly or by expansion</c>
          <c>matched_examples</c>
          <c>array of object</c>
          <c>MAY</c>
          <c>Examples that matched the query</c>
          <c>credential_refs</c>
          <c>array of string</c>
          <c>MAY</c>
          <c>References for verification</c>
          <c>redacted</c>
          <c>boolean</c>
          <c>MAY</c>
          <c>Whether fields were omitted by policy</c>
          <c>status</c>
          <c>string</c>
          <c>SHOULD</c>
          <c>Operational status</c>
          <c>freshness</c>
          <c>object</c>
          <c>SHOULD</c>
          <c>Index and metadata freshness</c>
        </texttable>
        <t>Scores are local to the discovery service.  Clients MUST NOT compare scores
from different discovery services unless a common scoring profile is
explicitly defined.</t>
        <t>Scores are not success probabilities, identity assurances, or access grants.
Missing evidence or an unavailable score component MUST NOT be fabricated as
a measured zero.  Authorization and hard filters MUST hold regardless of score.</t>
      </section>
      <section anchor="score-components">
        <name>Score Components</name>
        <t>When <spanx style="verb">score_components</spanx> is returned, the following component names are
RECOMMENDED:</t>
        <texttable>
          <ttcol align="left">Component</ttcol>
          <ttcol align="left">Meaning</ttcol>
          <c>tag</c>
          <c>Match between query-derived tags and agent tags</c>
          <c>context</c>
          <c>Semantic match against descriptions or broad context text</c>
          <c>example</c>
          <c>Match against one or more example tasks</c>
          <c>protocol</c>
          <c>Compatibility with requested protocol bindings</c>
          <c>freshness</c>
          <c>Penalty or bonus based on metadata age</c>
          <c>policy</c>
          <c>Local policy, trust, region, or entitlement signal</c>
        </texttable>
        <t>Implementations MAY add deployment-specific components.  Clients ignore unknown
components for score interpretation; transparent relays still preserve signed data.</t>
      </section>
      <section anchor="response-example">
        <name>Response Example</name>
        <figure>
          <sourcecode type="json">
{
  "request_id": "req-123",
  "generated_at": "2026-05-08T00:00:01Z",
  "applied_filters": {
    "required_tags": ["hr"],
    "protocols": ["https"]
  },
  "candidates": [
    {
      "id": "https://agents.example.net/id/hr-core-automator",
      "name": "HR Core Automator",
      "description": "Optimizes onboarding workflows.",
      "bindings": [
        {
          "protocol": "https",
          "endpoint": "https://agents.example.net/hr-core/invoke"
        }
      ],
      "score": 0.91,
      "score_components": {
        "tag": 0.95,
        "context": 0.83,
        "example": 0.96
      },
      "matched_tags": ["hr", "onboarding", "api-automation"],
      "matched_examples": [
        {
          "id": "ex-1",
          "score": 0.96,
          "text": "Prepare a new-employee onboarding workflow."
        }
      ],
      "status": "active",
      "freshness": {
        "metadata_updated_at": "2026-05-08T00:00:00Z",
        "indexed_at": "2026-05-08T00:00:00Z"
      }
    }
  ]
}
</sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="discovery-processing-model">
      <name>Discovery Processing Model</name>
      <t>This section describes a recommended indexing and ranking model; implementations
can use other algorithms.  The result, access-control, and fallback requirements
below apply regardless of the algorithm selected.</t>
      <section anchor="index-construction">
        <name>Index Construction</name>
        <t>A discovery service can build three complementary indices:</t>
        <dl>
          <dt>Tag index:</dt>
          <dd>
            <t>An inverted index from capability tag to agent identifiers.  This supports
fast filtering and high-recall candidate generation.</t>
          </dd>
          <dt>Context index:</dt>
          <dd>
            <t>A semantic index over descriptions, generated summaries, or other broad
context fields.  This supports natural-language recall when user wording
differs from tags.</t>
          </dd>
          <dt>Example index:</dt>
          <dd>
            <t>A fine-grained index over individual example tasks.  This preserves distinct
capability modes for multi-purpose agents.</t>
          </dd>
        </dl>
        <t>Discovery services MAY augment descriptions with synthetic queries or other
derived text.  If derived text materially affects ranking, implementations
SHOULD retain provenance so that debugging and abuse review are possible.</t>
      </section>
      <section anchor="query-processing">
        <name>Query Processing</name>
        <t>A discovery service following the recommended model processes a request as
follows:</t>
        <t><list style="numbers" type="1">
            <t>Validate the request and apply authentication or rate limits.</t>
            <t>Normalize tags and constraints against supported taxonomies.</t>
            <t>Derive query features, such as predicted tags, query embeddings, or
symbolic constraints.</t>
            <t>Retrieve candidates from the tag index and context index.</t>
            <t>Merge and deduplicate candidates.</t>
            <t>Re-rank candidates using example-level, policy, freshness, and operational
signals.</t>
            <t>Return candidates with matching evidence and warnings.</t>
          </list></t>
        <t>The service SHOULD bound the number of candidates entering expensive
re-ranking stages.  The service SHOULD return partial results with warnings
when a non-critical ranking component is unavailable.</t>
        <t>Fallback MUST retain hard filters, access control, and required freshness.
Index acceptance, semantic-index readiness, and successful query execution are
different states.  An unavailable search function MUST NOT be reported simply
as an authoritative empty match set.  Partial federation, candidate truncation,
or an updating index SHOULD be identified when they limit result coverage.
This document does not require any particular internal filtering order.</t>
      </section>
      <section anchor="example-level-matching">
        <name>Example-Level Matching</name>
        <t>For multi-purpose agents, example-level matching is RECOMMENDED.  The service
SHOULD preserve separate example vectors or features rather than representing
all examples only as one averaged vector.  This allows a query to match one
specific capability even when the agent has other unrelated capabilities.</t>
        <t>A discovery service MAY compute the final score using a weighted combination
of tag, context, example, freshness, and policy components.  This document does
not define the weights.</t>
      </section>
      <section anchor="privacy-defaults-and-redaction">
        <name>Privacy Defaults and Redaction</name>
        <t>Discovery services SHOULD minimize results by default.  Unless <spanx style="verb">detail=full</spanx>
is requested and authorized, responses SHOULD omit sensitive endpoint details,
private examples, internal system names, billing hints, and non-public
credential references.</t>
        <t>If fields are omitted due to policy, the candidate SHOULD include
<spanx style="verb">"redacted": true</spanx> and the response SHOULD include a warning or policy reason
when doing so does not reveal sensitive information.</t>
        <t>Cached responses and pagination MUST preserve the caller's access scope.
Pagination bindings MUST define query and authorization-scope binding and
integrity protection for continuation tokens.  Reusing a token or cached full
response MUST NOT expose another caller's private metadata.  A <spanx style="verb">minimal</spanx>
result can provide an authorized-resolution reference rather than a public
endpoint; <spanx style="verb">full</spanx> never overrides access policy.</t>
        <t>Three scopes remain separate: what a directory is authorized to publish, what
the current caller may see, and what the target allows the caller to execute.
Where applicable, discovery MUST enforce both publication scope and caller
visibility independently of relevance scores.  A valid signed candidate or a
successful discovery request does not grant invocation permission.</t>
      </section>
    </section>
    <section anchor="matching-evidence">
      <name>Matching Evidence</name>
      <t>Matching evidence helps clients decide whether a result is useful and helps
operators debug search behavior.</t>
      <t>When <spanx style="verb">include_evidence</spanx> is true, a discovery response SHOULD include applicable
items below; D2 services follow the stronger conformance requirement above:</t>
      <t><list style="symbols">
          <t>matched tags;</t>
          <t>matched examples;</t>
          <t>matched description snippets;</t>
          <t>score components;</t>
          <t>applied filters;</t>
          <t>limitations on result coverage; or</t>
          <t>freshness indicators.</t>
        </list></t>
      <t>Evidence MUST NOT disclose private metadata or private user queries from other
clients.</t>
      <section anchor="matching-and-trust-evidence">
        <name>Matching and Trust Evidence</name>
        <t>Matching evidence explains relevance.  Trust evidence supports a particular
claim about a subject, authority, control relationship, or signed object; the
two MUST NOT be conflated.  Optional assurance extensions expose typed evidence
references and, where available, verification results under a stated policy.</t>
        <t>Authenticated publisher, verified organization, endpoint control, and tested
capability are distinct assertions.  Crawler-provided descriptions MUST NOT
be presented as provider-authorized merely because a directory signed its
own response.  Derived descriptions, translations, or snippets MUST be
distinguished from original signed metadata.  An original signature does not
cover a modified summary; a directory can retain a verifiable original reference
and separately describe its transformation.</t>
        <t>Such an extension can reference provider attestations, endpoint-control checks,
capability-inventory baselines, build provenance, or runtime appraisal results.
It MUST identify the claim type,
subject and revision or deployment scope, evidence source, and applicable
validity or observation time.  A returned verification result MUST additionally
identify the verifier and verification policy and MUST distinguish passed,
failed, unperformed, unavailable, and stale checks.  A reference alone conveys
no verification result.  This profile defines neither those evidence formats
nor a universal assurance hierarchy.</t>
        <t>If a capability inventory is summarized for search, its baseline revision and
covered scope MUST remain distinguishable from the live observation.  Search
tags are not a substitute for a complete tool inventory.  An implementation
change can require refreshed metadata or assurance without creating a new
stable agent identity.</t>
        <t>Freshness of a response, metadata, and authoritative resource status are distinct.
An extension returning current-status evidence MUST retain its authority,
state revision, covered package, observation time, and validity conditions.
It MUST NOT use <spanx style="verb">generated_at</spanx> or local indexing time to renew that evidence.
If a requested hard assurance or freshness constraint cannot be evaluated,
the service MUST return <spanx style="verb">unsupported_filter</spanx> when unsupported, or an explicit
processing error when the required check is unavailable.  A relevance score
cannot substitute for the missing check.</t>
      </section>
    </section>
    <section anchor="registration-and-update-behavior">
      <name>Registration and Update Behavior</name>
      <t>Discovery quality depends on fresh metadata.  Registries or agents SHOULD
submit incremental updates when:</t>
      <t><list style="symbols">
          <t>endpoints change;</t>
          <t>protocol bindings change;</t>
          <t>capability tags change;</t>
          <t>examples are added or removed;</t>
          <t>operational status changes; or</t>
          <t>credentials are revoked or renewed.</t>
        </list></t>
      <t>Discovery services SHOULD support sequence numbers, timestamps, entity tags,
or equivalent freshness mechanisms.  A stale update MUST NOT replace a newer
record.</t>
      <t>Registration bindings MUST define the authoritative source, stable update
key, revision comparison, and conflict rules.  Endpoint changes alone MUST NOT
be treated as creation of a new identity.  An identical revision and content
SHOULD be idempotent; the same revision with different content MUST conflict.
New ownership claims MUST NOT silently replace an existing control relationship.
If partial updates are supported, the binding MUST define field deletion and
conditional-update semantics; complete-object replacement is also permitted.</t>
      <t>Incremental exchange MUST preserve withdrawal or inactive-state meaning and
define duplicate, out-of-order, gap-recovery, and checkpoint behavior.  A scan
checkpoint that can pass rejected records MUST NOT imply that every preceding
record was accepted.  This profile does not mandate a registry topology or
an identity-transfer protocol.</t>
    </section>
    <section anchor="federation">
      <name>Federation</name>
      <t>Discovery services MAY federate results from other discovery services or
registries.  Federated results MUST include provenance sufficient for a client
or local policy engine to determine the origin of the data.</t>
      <t>Federated candidate metadata SHOULD include:</t>
      <texttable>
        <ttcol align="left">Field</ttcol>
        <ttcol align="left">Description</ttcol>
        <c>origin_service</c>
        <c>Discovery or registry service that supplied the record</c>
        <c>origin_authority</c>
        <c>Authority or domain responsible for the record</c>
        <c>origin_signature</c>
        <c>Signature or reference covering the transferred metadata</c>
        <c>received_at</c>
        <c>Time the local discovery service received the record</c>
      </texttable>
      <t>Federation MUST NOT remove freshness, redaction, or credential information
that a client needs to make a trust decision.</t>
      <t>Origin publisher, source authority, and responding directory can differ.
Federation MUST preserve these distinctions and applicable source revisions.
Local reranking MUST NOT be presented as the origin's score.  Conflicting
bindings, control claims, or lifecycle states MUST NOT be silently combined
solely because stable identifiers match.  Revisions from independent authorities
are not a global order, and local receipt time does not renew source validity.</t>
      <t>Federation does not establish transitive trust among authorities.  Acceptance
of one source's claims remains scoped by local policy; a source's withdrawal
is not automatically an authoritative revocation in every other domain.
Requests SHOULD disclose only authorized context and MUST NOT forward reusable
caller credentials to another domain without explicit authorization.</t>
    </section>
    <section anchor="interoperability-considerations">
      <name>Interoperability Considerations</name>
      <t>This profile is intended to map cleanly to existing agent metadata formats.
Where another format already defines fields such as agent cards, tool lists,
OpenAPI descriptions, or protocol-specific manifests, implementers SHOULD map
those fields into <spanx style="verb">description</spanx>, <spanx style="verb">tags</spanx>, <spanx style="verb">examples</spanx>, <spanx style="verb">bindings</spanx>, and
<spanx style="verb">constraints</spanx> rather than duplicating incompatible metadata.</t>
      <t>The following mapping is typical:</t>
      <texttable>
        <ttcol align="left">Source Concept</ttcol>
        <ttcol align="left">Profile Field</ttcol>
        <c>Agent card name</c>
        <c>
          <spanx style="verb">name</spanx></c>
        <c>Agent card description</c>
        <c>
          <spanx style="verb">description</spanx></c>
        <c>Skill or capability list</c>
        <c>
          <spanx style="verb">tags</spanx></c>
        <c>Tool examples or prompts</c>
        <c>
          <spanx style="verb">examples</spanx></c>
        <c>Endpoint or transport binding</c>
        <c>
          <spanx style="verb">bindings</spanx></c>
        <c>Authentication metadata</c>
        <c>
          <spanx style="verb">auth</spanx></c>
        <c>Rate or region limits</c>
        <c>
          <spanx style="verb">constraints</spanx></c>
      </texttable>
      <t>The Skill-list mapping applies to capability labels within an agent.  An
independently identified or versioned Skill needs a typed relation or artifact
reference if its identity must be preserved; it cannot be reduced to a tag
without losing that information.  Format mapping does not transfer credentials,
ownership, or invocation permission.  External identifiers remain in their
native namespace, with explicit association evidence where required.</t>
    </section>
    <section anchor="error-model">
      <name>Error Model</name>
      <t>If this profile is carried over a request/response protocol, errors MUST be
returned as JSON objects with a string <spanx style="verb">code</spanx> and the optional fields below.
Error objects are distinct from successful Discovery Responses.</t>
      <texttable>
        <ttcol align="left">Field</ttcol>
        <ttcol align="left">Requirement</ttcol>
        <ttcol align="left">Description</ttcol>
        <c>code</c>
        <c>MUST</c>
        <c>Stable machine-readable error code</c>
        <c>message</c>
        <c>SHOULD</c>
        <c>String containing a human-readable explanation</c>
        <c>correlation_id</c>
        <c>SHOULD</c>
        <c>String identifier for tracing and support</c>
        <c>retry_after</c>
        <c>MAY</c>
        <c>Non-negative integer delay in seconds</c>
      </texttable>
      <t>The following error codes are RECOMMENDED:</t>
      <texttable>
        <ttcol align="left">Code</ttcol>
        <ttcol align="left">Meaning</ttcol>
        <c>invalid_request</c>
        <c>Required field missing or malformed</c>
        <c>unsupported_filter</c>
        <c>The service cannot apply a requested hard filter</c>
        <c>unauthorized</c>
        <c>Authentication is required or failed</c>
        <c>forbidden</c>
        <c>Authenticated client lacks permission</c>
        <c>conflict</c>
        <c>Registration conflicts with an existing record</c>
        <c>not_found</c>
        <c>Requested agent or record was not found</c>
        <c>stale_metadata</c>
        <c>Candidate or registration failed freshness checks</c>
        <c>rate_limited</c>
        <c>Client exceeded rate or quota limits</c>
        <c>unavailable</c>
        <c>Required query processing or evidence service is unavailable</c>
      </texttable>
      <t>Where a rule above requires <spanx style="verb">invalid_request</spanx> or <spanx style="verb">unsupported_filter</spanx>, that
code is mandatory.  Other categories use these codes when applicable; bindings
define their transport mapping and any additional codes.</t>
      <t>HTTP bindings, if used, SHOULD map these errors to conventional HTTP status
codes using the semantics in <xref target="RFC9110"/>; 429 (Too Many Requests) is defined
in <xref target="RFC6585"/>.  A 401 response requires the applicable authentication
challenge.  A binding MAY use 404 to conceal a forbidden resource's existence.
Stale metadata does not by itself imply 410 (Gone), which concerns likely
permanent unavailability of the target resource.  The profile's <spanx style="verb">retry_after</spanx>
field is a delay in seconds; it does not redefine the HTTP Retry-After field,
which also permits an HTTP-date.</t>
    </section>
    <section anchor="test-vectors">
      <name>Test Vectors</name>
      <t>This section is non-normative.</t>
      <t>The following examples can be used as minimal parser and interoperation tests.</t>
      <section anchor="minimal-d0-metadata">
        <name>Minimal D0 Metadata</name>
        <figure>
          <sourcecode type="json">
{
  "id": "https://example.net/agents/minimal",
  "name": "Minimal Agent",
  "description": "Answers short factual questions.",
  "bindings": [
    {
      "protocol": "https",
      "endpoint": "https://example.net/agent/invoke"
    }
  ]
}
</sourcecode>
        </figure>
        <t>This object satisfies the D0 structural requirements.  Authorization to publish
or use it remains subject to the selected binding and local policy.</t>
      </section>
      <section anchor="minimal-d1-query">
        <name>Minimal D1 Query</name>
        <figure>
          <sourcecode type="json">
{
  "query": "answer a short factual question",
  "protocols": ["https"],
  "limit": 1
}
</sourcecode>
        </figure>
        <t>The expected D1 outcome contains at most one candidate, possibly none;
<spanx style="verb">include_evidence</spanx> is not required.</t>
      </section>
      <section anchor="unsupported-hard-filter">
        <name>Unsupported Hard Filter</name>
        <figure>
          <sourcecode type="json">
{
  "query": "find a translation agent",
  "required_tags": ["translation"],
  "constraints": {
    "unsupported_private_filter": "example"
  }
}
</sourcecode>
        </figure>
        <t>Without a defined extension classifying this constraint as a preference, the
service MUST return <spanx style="verb">unsupported_filter</spanx>.  A normal success response listing
it only in <spanx style="verb">unsupported_filters</spanx> is not conforming to the base profile.</t>
      </section>
      <section anchor="additional-interoperation-cases">
        <name>Additional Interoperation Cases</name>
        <t>The following cases have deterministic semantic outcomes, independent of ranking:</t>
        <t><list style="symbols">
            <t>a tag required and excluded in one query produces <spanx style="verb">invalid_request</spanx>;</t>
            <t>unknown required security capabilities produce <spanx style="verb">unsupported_filter</spanx>;</t>
            <t>regenerated response timestamps do not make expired source metadata fresh;</t>
            <t>a transformed summary cannot inherit the original object's signature coverage;</t>
            <t>unavailable ranking components do not relax hard filters or fabricate scores;</t>
            <t>equal local identifiers in different namespaces do not establish equivalence;</t>
            <t>conflicting revisions from different authorities retain their provenance; and</t>
            <t>continuation tokens cannot bypass the current caller's access scope.</t>
          </list></t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Discovery is security-sensitive.  A malicious discovery result can steer a
client to an attacker-controlled agent.</t>
      <dl>
        <dt>Metadata authenticity:</dt>
        <dd>
          <t>Clients SHOULD verify signatures, credentials, or registry attestations
before invoking an agent returned by discovery.</t>
        </dd>
        <dt>Capability fraud:</dt>
        <dd>
          <t>Agents can exaggerate descriptions, tags, or examples.  Discovery services
SHOULD distinguish self-asserted metadata from verified metadata.</t>
        </dd>
        <dt>Prompt injection in metadata:</dt>
        <dd>
          <t>Descriptions and examples are untrusted text.  Discovery services using
language models MUST treat them as data, not as instructions authorizing tool
use, data disclosure, or changes to ranking policy.  Implementations SHOULD
isolate model processing from privileged tools and enforce disclosure and
access constraints outside the model; prompt wording alone is not a security
boundary or a guarantee of injection resistance.</t>
        </dd>
        <dt>Ranking manipulation:</dt>
        <dd>
          <t>Attackers may stuff tags, generate misleading examples, or create many
similar agents.  Discovery services SHOULD apply abuse detection, duplicate
detection, rate limits, and provenance checks.</t>
        </dd>
        <dt>Stale or revoked results:</dt>
        <dd>
          <t>Discovery services SHOULD expose freshness data.  Clients MUST check
applicable credential and resource status before invocation and authenticate
the selected endpoint using its native protocol.  Record freshness is not
evidence of endpoint liveness.</t>
        </dd>
        <dt>Federation trust:</dt>
        <dd>
          <t>Federated discovery can amplify false metadata.  Discovery services MUST
preserve origin and signature information and SHOULD apply local trust policy
before merging remote candidates into local results.</t>
        </dd>
        <dt>Filter bypass:</dt>
        <dd>
          <t>A discovery service that silently ignores unsupported hard filters can return
unsafe candidates.  Services MUST reject unsupported hard filters unless an
explicitly selected extension defines visibly non-conforming alternatives.</t>
        </dd>
        <dt>Sensitive intent leakage:</dt>
        <dd>
          <t>Discovery requests can reveal user goals.  Discovery services MUST protect
requests in transit and SHOULD minimize retention.</t>
        </dd>
        <dt>Result authorization:</dt>
        <dd>
          <t>A discovery response is not an authorization decision.  The target agent
MUST still enforce its own access control policy.</t>
        </dd>
      </dl>
      <t>Verification inputs and external references require bounded processing.
Implementations SHOULD constrain object size, depth, reference recursion,
redirects, retrieval time, and permitted destinations.  An external descriptor
MUST NOT implicitly authorize access to protected internal or cloud metadata
services or disclosure of credentials across origins.  Required verification
that exceeds limits fails explicitly; it is not skipped to obtain a match.</t>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>Agent metadata may reveal private business capabilities.  Publishers SHOULD
avoid exposing internal system names, customer identifiers, private schemas, or
secrets in descriptions and examples.</t>
      <t>Discovery services SHOULD evaluate these risks using the general privacy
guidance for Internet protocols in <xref target="RFC6973"/>.</t>
      <t>Example tasks can reveal sensitive use cases.  Publishers SHOULD provide
representative but sanitized examples.</t>
      <t>Discovery services SHOULD minimize query logging, support deletion or
retention policies, and avoid using private discovery requests to train models
without explicit authorization.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document defines profile-local field names, string values, and error
codes only.  It does not create new registries, media types, URI schemes, HTTP
fields, or protocol parameter values.  It makes no IANA requests.</t>
    </section>
    <section anchor="implementation-checklist">
      <name>Implementation Checklist</name>
      <t>An implementation can be reviewed against the following checklist:</t>
      <t><list style="symbols">
          <t>supported conformance level;</t>
          <t>accepted metadata serialization;</t>
          <t>required and optional fields validated;</t>
          <t>unknown-field behavior documented;</t>
          <t>freshness and expiration checks implemented;</t>
          <t>hard-filter failure behavior implemented;</t>
          <t>score components documented;</t>
          <t>redaction behavior documented;</t>
          <t>federation provenance preserved; and</t>
          <t>security controls for metadata injection and ranking abuse documented.</t>
        </list></t>
    </section>
  </middle>
  <back>
    <references title="References" anchor="sec-combined-references">
      <references title="Normative References" anchor="sec-normative-references">
        <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="RFC8259">
          <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="RFC3339">
          <front>
            <title>Date and Time on the Internet: Timestamps</title>
            <author fullname="G. Klyne" initials="G." surname="Klyne"/>
            <author fullname="C. Newman" initials="C." surname="Newman"/>
            <date month="July" year="2002"/>
            <abstract>
              <t>This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3339"/>
          <seriesInfo name="DOI" value="10.17487/RFC3339"/>
        </reference>
      </references>
      <references title="Informative References" anchor="sec-informative-references">
        <reference anchor="RFC9110">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC6585">
          <front>
            <title>Additional HTTP Status Codes</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <date month="April" year="2012"/>
            <abstract>
              <t>This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety of common situations. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6585"/>
          <seriesInfo name="DOI" value="10.17487/RFC6585"/>
        </reference>
        <reference anchor="RFC6973">
          <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>
      </references>
    </references>
    <?line 1120?>

<section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>The authors thank participants in discussions on agent discovery, metadata
profiles, and efficient retrieval for large agent ecosystems.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9V96Xcb15Xn9/dX1DAf1J0GaFG2k1icnhlasmPlyJKaktMz
6ckhC0ABqLBQhdRCCraUv33u/u6rAiln6XN6fBKbAGp5y11/d3nz+Tz0ZV8V
T7OT74s+X+V9nuX1Kvu3oWgP2Zu2WZdVka2bNvtmvS6XZVH32cUG//287JbN
LVx1EvLFoi1u4RGjX/T+k7BqlnW+g7es2nzdz98P80IfN8/xpvlKb5rv+ab5
47OwzPti07SHp1lZr5vQDYtd2XVlU7877Av8clXsC/hX3Ydy3z7N+nbo+ieP
H3/1+EnI2yKHIf22qIs2r07CXdPebNpm2MOXL+KN2Vt76Enoepj7VV41dUEP
KwIsCPz55PGTX83PzuZnX4Z9+TRkWd8s5YIs65q2b4t1F7847NznfOi3TYs3
zeH/GQwafvndafa/B/rIy/K7sq7KvN7ot027yevyx7yHYT3Nnl28ePaOvi92
eVk9zd4Pf5Ib/tcyL5f9ab48XdZ0RQdjKfqn2avmNPvyySz7bsgPQ17D57bf
ZpdNvqLLlmUPq/p1UcKDNvRNW2zoZd/l5QqejLvYt/BsvrxZwSjPHj8+++pM
vhjqHjfm2bas83RyX59mL0s3ua/hFX8u9btPTK0qF3T5f8WJXZ5mf9j6bbsc
6pu8tC8/MbUft0NLN/wXmdscmB//leULuCuHu8K7bdllwKzDDlljVazLuuiy
PNt52fBnkg17JxuMmTNj46xZI+k3dbNrhg6YZN3fAUtmxO3daZa92xb2jFXR
LdtyAa/aNndySbYfFlXZbUEI7PNFWcHc4zCGDlYgK97vK3hvn/X5ppvBnvQD
sPq8Ar4Y4CHy2D1uRzcLxft8t4eX9Xl3A1fDu4GLmyoDelvB0+ArnFyzB3GB
d+QVrFeNC1PygF/0WV51TdBV+d3b169sRDM387aAFep6fp7/utvDA4usWfyp
WMIE+23eh6LOF7gCdllXtLflEp7fNzCAHYyuQPoYljC5YpXBevVFC+OdwZW7
vO7LJTwZNr24zatZwFfi8OYbHDdcv8v75RYX626LK72HUeAL4AsgF5hZ0dKM
F/SbrEg3tOt8WZwiPbhNamBQddPDI2sUi0AW3b5YlrD18BW+pJhXRd7W+PAd
0F41A8pfFCtc3SBf4Fot8q6YAbNkbV7f0EgqEPJlv93hKsOSF/lqlsG2kjjO
21X5Iy4HDEVXm6YJMxmqPituS5DjyyKri2IFE14csmVVEgWl628L2zW09PDT
el20pDyQMJDkaee7bJmsDUyVF68BUtqVP+KQYTRlmzV3dVbB7/XyMAvdMq+E
UHnrdXp/HnL88pSZbVeuVlURwi9gqn3brGBj4Z0hsO4slk13gBXYdURGJXJM
dpcfkBpgX1ewN2VPuyVcsm6bHYyhBXKn6R5AMpVLYBogatqlriDq/eY9MHhW
Nc3NsMc1wkXrYe+KNit5W7tBufgp8FfR0voFeQ2wb1Ejw8Gqd7Q2MNiyVp7L
lOdmslT5LYg8P064temKyMwlbARz8bbAhYarChQUKFiBFRPWFf4WBgZWVkoV
ngVNvm9gTEYfsNTRCBlvLnD0qog8A0zWAWdvgF3gvzLD8haG03Wn4V2+Ocpy
bnzGYjIYHiWwwm1R2W84ZCRUZGkdDtJkuQFB02V3QP3N0MueE09k3TZHhlcq
KuoNcNjpvTK6dlKY1tyRvrIwkX1X7HMk6o73NgpVWMHm+PiehvDLKG2dQMaN
IQ2wzrv+qJg6hzsfFMx0+6IFHRdXV1ftnF7rxDa/y8s3IUV/h8mxhDZUzNMj
wDZcbmUS50Tnv7xP8tP1Xb4uMs9TVUFsOxKRicAS/YUyeKo9WXih0gLOI2ES
SODgy3GgKKechExpGN76i1+gcQ38tcvewpf0m8qQuO/bHMj9jje16PFBIlR2
hem0HZjM2aJwlA9r1gybbQBqoGWd7h/uha68ck7Kxsz1zBElvyQskPrrJXCe
voIJ0pnxE2ZFSVy8h72qN0WyjgHXEYWIsg6yi0hm2K5dMWWcb96DdUTKqcAH
lt2Ony8bld0VC9yXZmiXKIJEXxixNm1HWqtvmioAoZZrUPLw1WKgHTwAT9Ju
gnCFjzugkVsYHvMnjSq6OKo3Ayt4miuI2DFnzYQvUmE4smPWMOQtCqtZMF2v
OjHqoWJl9gfKXdaTPUoSoV0ghn+XlcxxWDsYkfw0O6ZEC7gYdAeL9WwPWhD4
ZDePFoHuVdMG2PGhhQnuc9g03Re2f0xXw0bg4oFAJhZDDbAYNrTgSL0gCiei
DwdQwFuL+w0Fx3Fi1BjHRX6LquAYm13sUezJtsgQlN/hz1x+xg1pyB5HC5xU
GPDZEqiGPuzy9qboYZmItDYwQ1DqsGUwvaoBw+GoAYjrg1YNP5nWMMog1f/w
hJxoITBDMleLTqevVvoEej3SD1gCTv8jzVcDznhm4jJ0xXJoyZSBF8AeOw8d
nnoLYyaiNU3Mi/XbBrTFaJFICG3RUaiq5g7Jc9OoThHuACYc6SK2kaO1g9Pc
lpvtHIQ0ElqOFp+NCKV+N+z34C5liwZcpmOaiGhhIspEinVguC63rD3IQi5S
NeM4U3U2DmkHQryc74eWuIC35DzOa+ITZGK4siMAq1+tZJ/RN/KCEKRBXh/A
bQPSB5U4gIk3tZfxVTmuaupmoGbBHS/rZTWAzTGRCzQMkMVr+ShT8stYoqAm
Vqic27VH0utUY6pNo7RCj9235W2+PGSbAegUH47rNKVuppdXTT0/RjPma/BC
Eq3kwAt3aL3VHY1QSe/cfvvh8kXWLUH2FvwdOyoNLQrxJZrR+6ZqNofJBbK0
SFuw1uOfzY9Rx8boRz7DHG+J283D4UcA0w0sTTK2689RIP6Sna8JF7Ez/R6W
k/QUmzw5mN5uBXnhLp0ez17KYNgYuQFVdNe0QFgn3//w9t3JjP+bvXpNf19+
828/vLj85jn+/fa7i5cv7Q++IsCH1z+8lN/xr3jns9fff//Nq+d8M3ybjb76
/uL/nJDOCSev37x78frVxcsT9BL6RG4jqQN1Lpj52j0aBKss7wwGQKsu+/rZ
m+zsi/DTT//t8ttnT87Ovvr4MeMPvzn79Rfw4W5b1OKz19VBPpIiBpkM7IwP
AeZA1gUhQr5CF7ot+myoOHAds3dFuytrogixnp6Gp9kF3BihCzT/il05P4Zm
8J4yB7MqhOuB8VE0gGIC9k0cHmI72PqFmpAon5rWkcKpGnGKxtJ4vDwTycge
rOEmKkEfdSLZUXL7d89gLOZA/bXgRwjPovwDl0gGtUU2rFEaV6B5V8AUC3B5
2KZT9YLoURSeoBWbHTxzhrJuQI7EcZE52R/2jAo0ZFhEY6mFlboFvwAHDeMj
R/pZA5Tzvs+eR8uIx/SQq8Ey1dZJpDYYestmL6aSSL9iJaPqEk/ykoU4v0kl
eoe7BcZULqYMToGVGdB4PpV8+HWz6GERiDpSdT56HesJfZ9oDdgYvJusebbs
JkYBTmUi9MkCZtPxHUwt2cPxqqmNiStGYIADtQiu7xvG7e37kJFtjDu5z3u0
rJgQUPPzlWWXmCNgga8qHNT3OtBvZKA4sueobtjmYVv1npVEpxQWA7ifdsAW
4g54PTMmgz0ewI8BEUOrggMg81o/RcaAV7TspAMbkwcD4hqUcANG3kFsCdJd
Fht5fYujKe5ST1A9rxRhExuUbR9cmZTXhbdnznXEmQsC0zrrUjUwPmNCn7T9
UzJS3HFmDhU8vujvioIo8UHMTPxcMlgYovFYR2cyXqcPJMP4qEjsJ1+C+D4N
r4m14aElSgxx8UBpoEBUpyR3Kj7O+aCSKgr7gJPXbx0MMsD4FuVmQEG9A1Ug
at0PfoZ+BrgiKHNAMuZti8Z4XCCc21Df1KAr5nzbotjmt2XTykKggnfoNb8b
x6PYLltCzRI9ani/IhsdPAjMNXZC8jp89+7dmwhRoKWNOy9Wga0DmPQXNlMU
URXK1bhM6zbfIf4UzC8R6csPmqE22+I39hlG5xyXqtyVBAe8KRD2Y64JJYk1
shI3Qys+aguG1qbpS/p4DotkElOhhZVDWvKyCgobVQdCIUEAdLTt+WqlBjD5
eBFwQY9eFjViQmCcsqMkrIhqFEQiRTuIYKsGuIs074BCHb1y8SlBgeTvgSPb
VWRgIk4jXzK+qwoVEkzs1rEK3r9sD+D9gyew34Jj2yOHsa1nbGGeDS1VgVL1
DhUf0Fe5nPqV6qH5V9KrAilT/AhP/stf/gISa1mC5dFyQMf+MYPckQteweJk
/sA//8MJhrfM3Pro/5t96p8PNopPXvsBNqDEvRUwK47/U7feuqned+2/JHP6
F78499zyASU+OVjvMz+R+2/5QIoWjYxy9X50x/FbPpjaPHLH0VsemAfdMv4C
HjJxKSfX8Ao+Y2PkrycFufG/P3DnxO7opoPIsmixEENP7BEkcOafqWYnnYAE
ZGh1NoFHKfKhaF8w6D/LviUninaCwki7crPt5XHsdxUksJga1mS2sAUcop8X
f0zRNxKd9Qjl90/qbjTSKFHOzo3d7HiWOShd0L9HOwtncofxHgXkyM8DQ9fg
jpf4romnbMqnLcg2tMtpaJ34F9GZz1fNXjyND/xIINxXCJh+SL3KD/A7bnby
b/ju+WP4YCbLh+yNwKcjW4Y2/bpcXc+ya1S6+F+3lNeylD2ME2MH6DVdq+a4
Bp0IOv+U33cGL3kbHaBItfC1oBUTG0i0CDK9qGJxsFkBCA5DkNqEmOW1T+D5
apLOv867+1595h92HGoxjDbjpQFlrOxbrM4Npxkbn3whfh7IQxbTDDQdqm0c
ZngxwsvFY+8wJkAkhaAZaiwmVHKPRWWTVQGzNO4Lxn0IF+TLZbHvcbcTMLWL
0xYE/hx5jGBKJGeNmOZBjdj2VIUK23poG4K6BENQKJRmmSj3Pbrliq3jaAKC
DXnXDTsJYuU4MHuDjqqLuQlieRkLyruA68J6qJfRyaXMB9H0BmTF0MtcorfZ
EoSGmVSo+b8l5BUWUJYN6Fs28ko3/18xA+ia13NPsd4ipfhohBl4PzfKKRFa
oDWnkISjopK5nEwygoxy8G7UW4qxXzQ01rSRcI8ubQsLgVsRbaYZS1G/+c2u
ZIjBBZKJocDHQlpBH/FOQv1kpBPxo1xs26adweKRpQ9PAPoFB40hErLYje5x
6Wyu4K+pZbsi9yqVJiFc1MedpSMYSIo4srVFs1ogWSJVVOKdyCOGusIVyutm
6p+gnRZN2AjboKcS1CZP4qsKILNDQEMlkNBM2jEgxpL+XbOfszj+lqxiFM/0
F8gaTHdLxTN8ctjHcVltErvEZ6CpDEP9wEuBEpVsfxcHECXEa4j31awVxnd+
N4CCmbcFbAM+ga+Cyz3UMr3r1RhjUPNqNZoHxZQ/ZOSU4ZjsQSLbPmBalEJO
41g0PsDMevcQ2Wn3kG+SuHJjCIfCF/ws82WOPUtm9ubheDM+Bh0wuHI6iovE
M0vCs3Sj94vc/ShHkR425M4xa88ok4F4j4E0Ir3kAeEDaYah8/tjY3nt0D+9
jJZzD0PqrvI+2VUawTf4Gyx9uSvOKROmtfiDxpWNwAjihedWTC3Am92IUmwk
xuN6EXqIcaftVngMhyRWo9HZk97ByOCduz1DACZBl9tieSMrgsEPNC2mC/zW
fsIBgPGBU8kNNY2aETTxtx4bQTUOFsO8Q2+X/DmQQsdVNbwCtb7ADeISBxpt
096h00rxz75UBFV1YoxUpfeyPgWlRqEiGExgpCBvkwgbesUHjanKq+bJq7J2
qERFcTpa3dRzYNWefFp+mSTy6bdg+oqDTzcL3AE8dkOpZ8uCpT2b1cuSkQAO
ejG2w7a1POM0XCqmIFPTQAYSVj1UFeHFawIHJZeLMB0Y1eu9UDJdRnBPFzjI
RjHmKPTj+7ygd6BO2cKq5TVbE9+XZFeERp/P4BFdAQuEsEYpv6ANK1hdVuz2
sKDOwGVponGu0MGqd+sDWDVoli06WiacGdg8LQc7cdNiDh6+TiwhVrCoQYEx
iNNYo7yIoh0lE9r47G+hVS5wmOrFLoZZUQdU5bpYHpaMAEelIGBcRDGCgHc5
xt5m2fNXb+cLspSRD2YG3s3Zuou6huST6FtFreamH+0yoq77w4IstZkHLAIY
JALIbABfMDsivDiT3eQr+Ht9aTP0HcYyR5r5+TQsbzTo7VEytVO9yF6PrHPZ
hU3VLPIKSGuoS9A0sEdxgzrbCEl2IGHJkXoWap0RrCaGxWUyO0SyL4poyyAX
AgG2ixK2rT2QVEK8aiWW2w+XL2EJ75B90entArmkZH6DVIX1f4vBEf8yl5iI
9lZbyG6DgBFvBzhkQJINFFhBeq4zYxdkNnSF5274sJDNkiFFx4yM8GGoAzeX
cTni45l7Hzq38jqJ4wQUbCRht+VeokqkmNXUbAuSFEsaGSc/3BachqEGH6fx
BHBBimqN1Idaf605L262lNsvDgNIYFgdeCk89yXSO5qLvHoifjiXgzNH23JT
kqLFKyhUdNuUKOurisXiKdm8fmlAYlZ5mwyyLtC2z9uyOhC0IaG/Oe4QvJTm
S+LhNIZZdAeSPY1EjcUPIF4wodRmRNzKc2WrGBZ5iSHmFNLlfM7nL57HNCA/
EHjtTt7EiCmsBeaE0vePPCCtt4um9N4EuD6YduQeSzgQ0mJV5pJW4ExjkXge
eRCWlOyFbpx8KHYp+w2ipNXJsMCNBRHbcod8JcFEl0EBW82xTkqrKHf4XU5J
s/uBQzQgcvBPCkKcjxIQCZLn6WusB3MQmdLY3ouB0UUzYPpTSXGa5z63UoYP
cgVZHFN402wMYtcYohILAxUSJyyZB33QRzGZetwf/iraivizszjbCThkPSYT
YL4OmFQnJPFPwPIHbdYDH5wIvpXElTvZLTTldZsk3NlNAs1ke6DNHycZg+pI
E0DIQQLxwjsU+HuPUXzKHEQFAbvWlQuC20YPw1zFEkMJBFYsKWmdvPGe0RcQ
HggvyQ1tQeZYTelzR+LdFBld5zvgVM6CF9FkcXDDqGil1Es61ZgtxgwxIvCn
Dmj6P07IpGM5h4kXoMNQBOKfmEsAemoeMRD8Fm+bM8Gd/JGR12OqDbQ52EA4
S/KmmKFlyQ6Zl6ycF3EAk/CwA2LZdww20N2dSCjTuREKVn7iTMwBcUPOkwMB
JtHYwEnFuIM8FtTOLTN+K6FbFI7Z2Pvm0W5wTrVcx9JGBB3lZcbZ4CzFkwg4
UpjAd2gDM0ToZiL6rpvGpDJCmjUtmjCuYLnBZPelkZ8oZjsYcI2T7sFeQCNO
zHMY9MymGojOiR4Q456j4qF5iczzVq/NSkxatBxoQWGpLLFzwgYWVuUce3Zc
nAWSOjH82CAGiZj+xh0Z6oQdzHVlKip3EB2wEwJP5LCakUF1d4EzspdFidtB
dS+c70sTkZxdGN6jzuxwkh0+m0Elh/r+UcgrGPOJdD7UZIiiyQPCSPAT8CW5
y5yuYkYx2imWzPCfhNmYPyuoTQw0mYlP0AniKVPoxUMdHul4EG1hD5hkohoh
sHCMqm/jCGisqNKuyKrOp070N+/3LJRZ84H1uufbWBx9+j7Rk/FGg5AmeMTL
mKG+Qac8BXmcohADQ6JF+bFEzpiG0XZKDorUG8Qk6hRIdJkURiDilxouOcGm
6DpKUlpMC6PCCzS7JunelunPANPX4j4KsUdvkom9L6qqi4lIW7KwPJkuJHuI
l5Xzzm5AzkxTDP9hdGyRlylZPkuFi13Zw5hAel5v+34PcwMSb3qGdzFd4m2E
2Aidsg9TstefzOJnj+cF3QiitMyvyPh6gP7fJukNyDTsc7I2o2dk8gxiBFjH
nKT/FWO+Ewq9lufM9SEYF8P6T0rhwA8LlNrXnHc98ow5a4WXtWTHg1+6QQEg
b8Cc2rrY5LKoNne6+VxCL+yRyM8tqWmqyAIja1Wg8P9A7ofugaraoROcfUEp
44XsCK4paIsS67xk0c/Vnicj3Exbjryl+SiwRGVVmVtJ0kWe8qhTz08jNZpE
RETii+TEK04SgmKlXgRwLmrDy+gZQRiDXU1We7Gq08A2AZ2EY6zqhGsYbGyC
DsXtkaoagi3cZiR5fpp6Re8hCOeg0I7OBnUpxeNI+oO1X7RJxCwsuBAiSSQV
aRFdajbw8hXGv8vOcZyYQZj/ZvQet4wzei02Nk4ywnwaMAUsG0keMQOZ2g8I
kKXJR+TulRIMB6pn+m2tahJeO6cQ1ZhKKN9WswHIqQUz8JlfO9wj9g9RmIpf
SDgIWes2A7r5UeeME5wgg2dKkuSWt1i5DR8GybltiDjRcSzI3vYg5wirCmOs
Cu8En5nZnvYFjQag2ptCRfEoG1yyi65xHa6PhLs4rudDBppXpr9t0NniZbUo
qvhTcN/QsbNdoFnTJUlmBIYwqzuZptq/lNJBtnBj0UJl0DzQz9ubkvHZWD+l
qAVmUmP0kjES9JcqrhVVtvf4LUrXVXQ9BBZSoUb+pibdCVMGkAPDMvK+oiLe
4ifEBSUBhXcpOgEmA6vb3/MlWjISAY4Qvk8Sr8g0yEamQZ5dyztULeND5CKO
VoCgDOh8FrdFK+VKOYdS12nOtktMxSJJjSixedwdy0XEvNMa007nRi8RNMLH
K3wfhQIBHV0YBRE4PcXh/ZTHoLBNkR2LFCwaTFy78CCejguhL4qYWEmFy47U
+DgVk+QRhjdk2HwqjsPwiLghgFTysUzs+qbBXE2ShQQuKW0Q9M8ilDy9C3M4
+O1tQatFJHEkpVGnwQZdIINOJkBaTxYbnS/aD21iIj+kaieG5ETAwOjS97pc
RWFpK1BJdMhF5kM7FNEZhYYosg8eDk1GEApJAmWCJa3OAwtyoUV2LotVbstO
b4ppByjpFCaOCS2c/3kIGpGU2kg/NJJBlhKAKx6xUAu3kWak4Euw91rtAyNz
XKNPzQIi7UgEhIRJFBIst4O9R3erjull1SGiBLihQExAHAhu7RDfg7V+g3VN
WLlqtC2coqxNqfmC3qJ1V3aE90nCsQBjAdMvWiCQ56/eSrCQbdIRlMprs0bo
TLd+lkKwlJlOCWMpK0YnR6MYnHKQa4wnAVdZ4r3laC8uyLcaIgXhEmOnPFOc
4uW3z7LPP//8K8nsxj8/fkRAq5hjFNiiFZIt8sO7ZyB21l3RYzBPXXyBGGj/
ctNbFTj7KGlggLCMEWFwwLCIQOvB4YyiJegscMubqqB4mSpPDmSrKHZ7RWU6
awJ0r5HKb4tr/BMIJH7oho5U24o+rZCBUC/yR0wERpNdXjQS+kkBjCTwwN4T
dTBfxKCM6iRZu6CpgR7dF7scluQH1iGmDYirtJBSXjXnwEPQN8qKl52IULRA
WL/ORSWZJIU3XMeg+rUEBMx8QMZsOVCW907+YgAEh2iTxM1pG0pWilWNUlx9
NK4meyMVxRzE1iYfGNykJEtJg4NfxbMugixubGMALFWtzO0W83qu2UU+CcAE
MQbj1ogeaarDNQk4lpdH658t0a7ZS/qTGBwSGpGyPQ4OImNI+C7Jc3PxZirj
1PwIyaE4DW9RaoC9hWXEeB8igf4KCxuOsixI2IjVJ65LMPkv13DEmXtNgGGM
KmSOjHF0fbLsLS8zk8ZMkvFJie77GW+O9cAwB3lD3be4mqG0kKvgJecoovFl
yNGoJTiN1jvYNn4YXXGnfGShPIrkY2uVLE1nAl8i+Fg1xbNxADOfxaF3S+3b
gjSmy+CRHiZc+E32Q9U1NvrT8GZiA8p8MomOqSVCZCVOTJ0IIRBVq2YX/oRq
lBI+pJXLuioKruHleEt3qJfbFmzSH0mR81sWAxg8EvEyw1QQLxcs+Clk2Um5
OnmanZA3//Szz6TYTKzL07roPytXn23bOSagzsU8b9oTrOo6QS2FN393mT3D
2VykPzu0Cq96zT1yYKvheuy5tia65jLNRYNF+kBxnH5zyk9ACBJu/Y+TbYuh
Cr0J/4634Kftcof/yfeljhFf+kd6iFrK+CDKRv9JctJl6sX7+Rm9jr5DoBS/
fdMWpIgoe2BewBOaQ1H4kepoTt3NOt50dDbuP9KFH2f3DOPJdBjPcDkkTYRH
IEKEaswVU8gPLdgXap4dGY/ePee7cVDST4HWiYcF/+YVUwUyXTF1QI1k4ruU
OT5BTUJKnzFcEm93oBuN2GFEnyGx8mbyeo2xNHzlGDw7Gc2JtT1eyVqcCUz0
K359dvr49DF/G5Uc/kAt/h5/OX/8m3ePHz+l//3hJHzkUNkvpgnmaHwfqbyj
gu3jpYr3dHA4DT49Nfu70lNDkp46CZD9VempIU1P1Rn+w5NTOWP7Z+SLSqcG
rTIdp42q+3H1cyIaDNtZxj8nK2oOFuOrAoz+/MdRkUXexcYznM7PKZSEDfwd
Y6M6NEFuPKz+0NMuonHsLv9UUukbcd1aSS7lpFLtcpalWZSj5FLKWjgCSX+f
vy93wy6rh92CE43d/Bg4TxPn4Z5FA6Z8Xtsz/l1MvmmFRdm5pHJORIZ1Ooa9
78q63OUVQe7s2DHOfr0equo6mh36AFwrsh6vNFl5slzPxLpEk3hLC6EpEGQh
EbbHOQAIqZOnQBR/LWA+UbvuLAIud9uyl/QiSUORqlm1XyWZiG7k/kwMc8XY
LiWUcOIjFV2TEkDPwXDvvRQuSbbpBOyJuWYqUKLbq74XSaO7ssNUiOcDy/Ei
SFdE2mf2b3mGOZk7hLIIFBVBdtk9RrmsTdEMLHsMi5Pyk1JOHo6Lewty1lnm
IrV+EpwAZfSR2jKqboHFPHAwxoTGNVkp1wmzXuNOIhwTtHKIwfc+9Us1nI5A
TwxlSA4CMTDvFLWgaYK+gsKUu1xSH86j1JFofOL/U+WzpZ1wjwu0nIFuqOeN
vZQrs+UN2P7Pb8G1kMOVLPo1Nn7CauprkxGp75PUq8SKfFEtjgrxd7CHsXmC
IdiEe3HuqwUb8BpPlxRougf9Skburrnin6/RhcBv1PeKaVPShzC6ZrBgBJNV
B62SE7pSOURDik0QT7HJhOJ0PoTi3G3nhpatR05pCh6ZDxTNU0SKc4KP4IFl
xwkh7KLdjwqehgsPXWne52rmXcooFDEZCzsuY3gmMjIKMF6fQMwfVyWvKEWQ
UrpcDMzn0exogO46H+wOqX9JhfEKviUd6EJA2qNyI2rTgJRNFCsNiky7YP5c
V4wSrLX+m4JUYVJ9RXS8BqdNEreuWazT1yb/OTKksvWaCIgrtgLZY/BaDk+L
TjufFkuxf8rlf1TAF2mKUxb7UyZxNMs37MPZWLwWuIdBNZCntOf6n5HYX+cI
kXDPD9azXNAv2X37AdXTj1bmH6xEEoSEwPIuM4iojBW5C67G8kuq8EqAcM5l
gqutnY8miEv0HN9gcFUK88SRBjYEk8SIaVtMjZWCPY3MkzFsoNW11MQrNvx7
5ghItfI12zUi62HBrgRKuQIb86orEBrrruPUg+PONM2aSBu1VUGuRnUQpBsf
n2Ewb4FNuzjqJGkYYZF3JQVcatfXC6jT2VSJZPV5cp0HYOhpXAFNqGtZu3Rk
iZgLpsO1oAxv6MZwTSTrZ25bGI62LeSc9WxTaPsDxqDiaGN7BjIWuIo8CY7r
fFj3dyY7kjiLy5PZDFK5aZm7zCgxG7RFO9bgPrLpxBsiZmaOAgPDzL2gBgY3
D3GB65kUOmkfWWpKaQAQp2k29NKyHhBC0055ozepNDFThnacM1Z931CJJsDN
Id6sxqfcyR1Ye4do3mG/qlFtLBpd48LdTkQ6Rm1UG2EoncFUeY+3llPXzqAj
imNrvsvAPa1g3ZLAlio77gKz7MWUYdv8dAw/EW+jm/1tyfXzsVDTYS0RrKDn
Xrx5gcpg2AtOlBhrChix35+6a0fAmaOYkVk8/DBCOvgXEksn2DxdMC6kQRy/
7CAPaKxwTqTl/1HUgK3aMWyQ9nTqjhSj//8CD8hM/uH4gNDh1T0Jka7Iac1R
So38J2mO3t+8v5Lz8p5+WlTCySbClfoBx6o5v9XuAmJOsEw94oNQ5eLEnH3I
mf+h1ofqtSzLah8wTwqUj9l8Gk1OWBlUIwWycVBS1P3QSF7G0oRYjOBuhKcI
7H9/WeblfQECCjdi4iZnRtlGJG4y1q+dS584kUMuMyGpoeXUnGBeyHUkBK3B
ozxlWQMQkQJIUfyybiLcgFEtrNP3fSJAj1v1cSONGznmzg8pO1cTL6k5PA55
Hxpj4lH5Cse/wq039g8PuOpoYsUMOIUBjpRzyjqGpIfuNNWjkwyKFWeSGm7C
iXw0BQXTOCJGjPioS5ownaPZ33WCBuSi4C1t6i4nq7sfhen+c4viucXAKKt6
XAZvVPxXFsLHJG5qupd0JmzVNvh01bk95ocuPbYhqTgX8FEhN1/mjYnICFJM
YEr668r1H5kWREc/gG9jzcivlPqNnwVyauc9K/7A/KaDK7rwD3ywoF+TxeUS
Dktrlz/jRNIBFvq7wvN5HhjipTnqpFSSzEDWSUL598OUWouNlpu4tzhBkZZ/
WyV+NLuPKZ8XFD0lN1A5190QwlvcMIYnOHgr6YwT7eT7tVjGjmRs0K537HlE
FO5IfNwQROkljjd6YwMsiEm1NdqjbpR8KIV0L2nBEYl5cTGlT+ujGTz0eY9d
TMc1qJiqjrFDoB1PMeq5kyT7rvNFS6gmojEBT8HJO6L9H4u2QRHo83Fo5b18
40dtmwoF5AZ+oAVBYsNXSuINvf2ZcZzgIddjThSznVXFbNROOw7eug8E15j3
KQpNewUSqmQbjuQjF4MQWo/aR1pDMv/MNR+KcUm04TdSrmQhBcHH3yaHONjx
AMmRD3big97G98beHTYKvd011R2dCDEqMniWKCvS4hEHOy4qPVu9KYDnuMpy
0dTAd1zOjqd8WBekjaTgCytzsa814aAzyGL4BCvEajpijTQUVxsd69zEqdlY
/YFB3B157lpFGwnB8WbaOCI4sU0nViw5H9wjMufTdMFOdLYlDEoOoJyi4i37
ezILon0uAdr52ZPP2T/yZuDxGOvZH/jKkXENF3Mw+gGf7z7/LUjo/SQaavfl
BPwt6RB0+8MpEXTJvWkRR3ILfDB/EpX34/5EdP7viNDbEz7KXzEQT5QET3t8
+tVZ+qUTULZjmpHAN3wZh3YivE4//OZz94MMi+/4lXz/MeYMOLPCpYl82r9P
7p7kh0zW9UieyHj+v0p++FuSSB5a52O5C/SLCah0lVUiXf2MTAa33JJH92De
gx8jZVccwzTeuAxuhAgEOOokxOcqFWJpqLZd1OR6NUIJYzgfH/9CtTmUrEk2
lZ17oJmhDN3ORO3PBRxkMG8NNu4iX96kYRjuR8PRv1QrE0SrLzA3WjqpkGnF
cLKd13XEradSIuozqe0Y/WFK0rjyKVWa8zJIt/lxS0q0rtLOVpQKNnJOOi05
0e53sFF0DlN65AUdm4GJq5WHIqPj7dqpxzHFdgiSlIeZ8mknTJPu4rqUYoPx
XpF+x77S8mjXLsiNeNp5XAZKiCU1HsejDEo67pDtTW38yVXgWuDpRj46HspG
j8sPduBAxQ/OgoiFO4p8aYqfb9+vJZ33nfpxem9BfT5s5KQuZwGRYdIdalgr
XGQ9zEiXL5i9JZ0o1pn/Bm0rgvkwcZSCxF3MEh/zkOUmEnbiipfsHDw8aWej
5JIvOFKPPc3JDHcdEoAV7GBYYf3jjBCNU0ZkIvczmCi1EyIbNHcq8G3IIWcw
6d/LWUAJmKetqw/j8jAOSsUo1xN4gjWKi3arDyqqcRkDEbE7xGn4HCF2WnTx
IdcFFSfEZH4kGWDp3vrJ83XWRFa7x9ORsAu0D9NTFb6gGgs6fCiJGlpn29iz
WIYeufQ0fIndqAo7+K9YaQ5Ggh7/it4xR+rwr9ADNF0X29hHLh4pNT4Vgicj
FfPh1zz+JKutu6fbL6dtC0gosR2lFi1ZwDYmHDg5lieEmcstj3qP+NYtAktz
QzFgrbTj7vjBEpyliBuHjSl3mgaqQwqScJ6AYvrw6GFhV4voPWIXUFUzUkZE
TObdQNVOWaKdLFnD1vo0iAPPWVt0epcK4TkTASJNZdyXCWYpJ8dwrWSI7jlF
ADstQnK+L8dLtR9q4vtyXgUKd5Qnh8DpCGmEkaFM9vOwwiPL3sgSr4uV0MzM
6RxQnrVWgYonjpZLae2WY+2Ky2enjaHGtRqVppIA7UN6Oj4QUQHE2Kbq4A9R
smhx1JJUuJD0lJBOnNoziZu9HhP7s5SHIt3DkJwPntKliuTodGlZqyom6S9P
sVaROkmQ1HL5tZ+AQWQUFcj5FBpuOYApY/Q4VXRSapAL1dgxf9gvJ7qcUfHF
EGLsJoB1hqzoMa2hIjPAh+7vy70CfSj9jBnE0B5YrbZvybO7Avt1F6vMHY4X
0EDD1igiA23ZJ8JKjwfwHvOUQMKoMJff2Wm7BT7B6jlnVrDesFq4o3peNlRi
0bE8Y3HQ/AzC3cnWlIj2v1I4NiTJi1obj6AS4jzxyD55AfXldf1YLFLNMCye
AKFValo4GrMj+KwiqUeDjaqoCLm0cxpR9PGBAsFVScSkJS6ScVlOimuuBkpw
NgRk68/KTMtjw/WJgqcSLb22BIlxk6BYUetaDcv+YqYt7AVR5aohBdB41r8t
KB+ktuQdq1ykw4wIHY6rS4SDzTlcl56khBJt0qJ9ZEXX3NkuvIn3HC3HYgbz
u0oXc3WWxV8x+cWK4AmjEg9qzaVamHsgITJqekBaV7mFvuL+qDQppKowrZ+R
dBsNEtt8lF5c+/yLJHGCZS2Xu2p9biTRecyIcPWWSdsTOaMixMYQkojA5c9a
T9alfarJQkAXipaqs0p8EZRPQR5RgwQ9ZJFjbTYuIkcuz5nRpRTRkowYmT0l
XnaFJIfdaRfHHgtwehWScfNdhO8UUdrWJ4D6EjFa8wIJDpaCMjP9oS689XwQ
GD42UFyRBW1aSg8iTzq8LRV316wTrAhinC7yGSrU4EyC6dmDxh4EjycdB6wX
E/XenpzI5A5pMntuW1T7zvKxsJvrKiZEWuEedwHD8ZArivdIMxBUb+R5qBni
jthhEPxoPh+KjFlSYnGv2Ii91Us6UJt8/3PXsT0JG4NZ3tQbblRlZyg47IDL
26le1B8ide4+q9D13/koX1eX+33BJ0SOe/3TcYFphB+/qnywvR7bPnKYoG8M
v0JC46NpdPeiFJCe78WE7bnZDH9HXrc6pNxIj1xS2WqpN1N6wG19h5D3g8Qi
x3R1kaKpZQjeZtcYJpA7cy1wqTisPfUvk04cs9h5c6Z2ddKdjnumMYtwpOyc
i8nvmsTKxb0m48V3nIg9d13arwhQ7kZhR5hE5YgLMZNMLbOwZ2noUK0CTiHP
2S5fRYnnmoHj11peOLO+vjCrTV5bAbip/8S16MmWcE0Ik6JLnB22f+HGD8/a
/A6E0FyEe3rUsK0UZsImtaNyeTt3EncHM8cksYLTWL1olo0oMQ36rjaGNf96
fMKxa27IkJIyjiZCBZcXad0efReBYpVotKM9Bqz3MnFTRnlOvMoSij9PJpG0
o3VtBlxis9BCGDUWsB5ymMyQtlHAgCfX6k4a36oy1bXOsC191+uq6N4r6Ckl
lTO37/OSOu7h4DGKVaHrOBN8MsJAXHQx1JRHChKozcsuOskx/SxpoigNHLCD
ZdDuOOzWSr059X3RQJaesBhZnVJZx+eQBS3IJRgs5qtSZpBknEiyzBG2kroO
yw4HnzUZsvBQq11g4v1iUlq9tE+63SO7rGYBjzJDi3yo5QBi/uA4XVqDYicC
Lm7lAes2chk9NUE8oPtxbAqTdteSvlNL42HuaGKryFSED0PqHWrqrZDIry3M
F3XrgU13fxJnFomD8FhCcJGPKXhIGnlGBKukE/cW7VXiGc4C2ReKfZCJ5laP
W4ormFXxwWo+DfktvSdY60lOTgOCgkf06CPy6daWEYtHr8eBM2encGeQ1pHM
QwwASL20kwlkLNkqaboylu9x03wM5ARpl+FRdzp71DpkcNqSSrOZK2hyFr9A
JXquvKZzeJE8apkTS1Z8BvfQxY33UBNlz5syDJzsHRtN6D7t8+UNzGQ24Sse
rHGedYZwnI+6kioTfDz3OrOjyy2gQyKEKl3ppGY6FNcOH32xjlivlhnEPbin
rFDrvhZI9nk14MtnYVKBIQDfsQohiSTEH6T1fNJkSMNYXNtgUIeBdMTRY+yP
+Tsx0IOWqaUUTNl0kopCjyIr+9I3KMBNkMYeX4sd7IEGPYSI/QMyBbkHgNNy
l3Y6qB1Bq7gBymhEDvw5YHKWN82WrFrVKNpfig9DHydMxN/GR6/EX5JzFUEi
c7NJeDNMZjXudC3ELT2txKKN+AM/BAia2u7RY4C4KDB3Pw6jh1R1SG64Owwo
o2mhSaakQnsdPOGR1lS8d7RoHU5YoLOElxoMV/0D5u1SIsBgKnP9PQwx2eOj
EAFBaomoUOUo8offFW4KqsmdtHOZaWhgXeFJmJqdab0vZV1dGxe16FyhGUs+
TcRE5jV5xzJ2xWZplSgBBuPqPiSwLTg0PfWGs2pMu4cP9jRYWm633F6awWl4
Ba+Pnee50d+Rxsm25q5J8DFXgCSPQv9K9JTKFiVC706S9ZsjKanA5H1UfJPW
Oa4GRjWVdl+TQe4kdEANROLpCqCUHUPqqbwj+AkXbQVmOlfeaHsiqerRxnE4
MhmzhYFm2Dh33qznBG/Psk2+p8YQyDFCNSiL5LQidb6JyEGMBfejVqSTNSSF
PISfcZeT2HsRIwUq9/kcNjzyBTFq6WeBfXxcF7bjh3twj7iC1IUc/ts3ezqk
HaWDP+eAremi9T0Tf5F9a9GHe4OyEqCISG10dI9lMzZtiIcvY9NguX1l97ON
LNCDD7JaQakaM9wmvGlHrYCoaA2156rgDpmFq5vUBAVJy4qvj/iP2TYpDPLU
p0w/kB2N/ZjpVVdWo+BSPfxBzNbSAvfZKic1ztuu/LPiARkfNFuSzXspiRfj
qfRnz0yf4k9oSo5kiuY1jVPjzUoVrTf5OG+XOpBJWcI7Mle2mg47jVbo5emw
QiQvrwFQuflgRKsBg9no8CiHRQc7wYcIBJskdhyPuSnoIOyBMif5oCTY99dM
DA4ZEKvSwSGx/xL3wU0cWBa+p5MpeLC7i5ZpaQ173dkcaS8zsBNfSisojZZ6
gCWBDSI9P+okCzajE05R8KOUUA0ZQR0W/3wkgp1JxPHM5D2mFjhoVKxC11Qe
j+jGx91JDjoZTtqxjISA71em61oWsStbrlWRIldxfZJuWGwHu2CEa11lHasS
MrJrCxomOp5Ewxy8YDLIdw0K+jggFNUWK8YAGSp4fs2jTvWmNJjUg2gWh0Tq
nFvDuEedUzTheJ/WcfgXjTI9M6cWiS8SlLjbVRrHYx8Yf+QoZQSPNLUh6Vmm
559pp9ogQLw3DqmNq3+peXN2LkMSeiH98GJ04glldpW6G+MTdqnWpufsFeJN
NEpA71ZS9CO2B/uJMfWenXMLFcgg+WswBDCWH08Zk6Ca5pVox3bQrjN2erFp
Alipr4EwsSwyxcuaqP9izjBoUWAY6qphLrJrVQbTCIwnyLupCf3ohF4+iGXm
jlWYua7z3Bf62qW0XCehH7VEOL6vVUSVCzaNj0+HQe0leC5Hp5P6ktZzsEt0
JC2duEhbI3ptoskubP20eEcO4xr9mBbqpIcE4aXWw9j5OtS+4oOeUYNXvcMN
igF42ozdnspn3HkUeKVZ5dpPlbwUtTw/+I7+NNI0wymqMu0JjRddSvBHCs+l
oB4uSfZFes/QhOY0BV1rd76fnyWdsEPMxCWGRJLkDYQ0TOUyNbhUJun/zCot
H3VxJgcVj9PF40SiEi/XBGdYcYceIanaaUVHDUdIgPo8M1fm6MZZ4TnIGLYF
qC1TRFvptIddHidvgtcMSSdcZsHckNm4RXcMmHHb1smBWoKGUbVsUbZB2tjb
2WEz9oailPJnoNmpuCQ7FIYg2fUNQRSSb/tizefVOVEFdN3SXtxKGI4k8GcW
JIunDBHYESF1w1ZB/rjyYuvkKlVKQFYrF7O3c91Eiki9JY9Sn5DEH0jHujjl
tBq6S8r8/sr6PqpFWRWxpE8aQ+5yDEkVsVqPsR6+lo6D6Do+UsSdtdKqU5nz
WQL5+Iw/imvVsTCMGrwzjXPB8vhhrrTQlyv7k7XZUAVL+4pbiB4910E7bK2o
sTJFxqlzhTJ6lKlxnrwR08ogXq17i4JG/UjilkjNqkFbmCKVV9Kq+XiFM1rd
DrwTVpZ8zjE6qLfQk5yxMBGMpXXBJxnEWD2X9jTtolzBmqc3ocXBJjd45zed
Y2ctZmI05UMK0un3yhMOeXBOC8zoak2pjB+0tUKh9VJ80JF6wjh3uZLrAavi
ygn5Zz62n7QzlRkePc4W/cIr0gK0VFwtJK1euNUGPe/PQwMvUW3BS2yJgW6L
xweqU0GTxXFkH1NkFGlQrB7XGF63qJt2uKEWbEew21nGR5AjhZZd7B1vPdFw
KzFjv+De1Oy8MKlzOqe5LeeGvoUIvJVeC5s+pAYVB99niJ4IQgkPO8mijwLq
ik84iyaVDEFEK7cOkVOv4Dl0P+OdgUcpB6xtHYiEzPzTT//z8ttnX52dPf74
8Tz74slX2T+BkZF9j+NSm/qfcUmkbjLYPb/68jdffvxIKM4Xj89iboQt/qhx
WZpEjdETMLHrTZGcBoHyB9f3i8dfyJyWmF6VO/bS+MajjnmCMf+3hJYaSZu2
XVCTdTxbkyGjL84eZ//0WzAb/hlD6CUYwfQOPIS7Km/AjQvIoTll4BqhsaEi
wIhk7egwJN9S9OIjavtjEvU66Jms1PcoFaBkYjjfzcG0tH2Yr32YX5BkpsfM
Ao/YYXt2VtEcuZfU9juUnL/nrM5RnQw5WyDa2Uq5LSZWsZmWclINEh2dUsNZ
WtQjT+Ka8SxHDvAUsUGwXPz8sfUKfrhHsC8W42DCZ/LCtC2wPpjM6qMtgS/q
7g5Noo7K3tHmwxoMomICEE7+se1oJwNPatySaibaB4FquWFBKSwCy6Q9r8Y9
y8Z1vzHVDEE95JOyj353enRM7M4Rc/8Sj3y0WWdcb3FvO52clpZOPzq2tic/
t81NXBCyaXiM8HYwpsFvc/1p0HZupB7XsMeZ1ogckJKL83tasbmkbKmr+sH1
gMKzF6WByr3TXVP3IJ8fwnr1vv5A/pRMnrFzimKRqVc9kgUlKogrArk8EQtL
dZ38iYrcFselb1Rgy5fa+a5Mwpl0QEjsAzjjBvY/M5RJMll6SmldvAn4ig2R
UPbWGObIMzrbCNftT2jTnyPD23MRVeCLVLDg0W3dWE7hIZDY4uO2MAwbB7WM
tWRCTt0sAdkw0ZGhQ4pDkisXDbqkmyUi4ZZXC2NF/++IQYExRu2uaA+Kxz/5
FnPykOPdJeExYHdZnZstdowiSvc0Rmz5+IBVNj6RgOy0c56aO81EO36IFVzW
YNKUfdotkYUTwqXp2Sg5R1q91TUpVrHBoUvyPu1NQGaydDeQ5FKK3GKgORuf
1k42SYzbmQ9rL4iwpTuYmWLEEdyNiHE26h7hME3NamDjLIZR9AzkI9nQhgcc
KDo1zfOdZG2DOn6rtDBG/qI3yhqaroqHFBILYknZsmyGLk1C1URpMH5QJEu+
pBw0lfc9eBpFq+lalboEp+5QKTPG4J1Yy6iV/mJfytFwRgndLEErkiCNTxYD
weWOh7thtSMOSWzoekjOf3TnMq/bfFhRaSWnFCz5fNnNhgNoo9S9nKvezGjx
feosngYjOnIQMBqEc05PLJImJkAtlgHpsMM3BLPBpLSpcBkxMhxvchK2NKqL
eQlDTbh6rLE8Eikk8xwGa9WpVL0omAmf3KvtDDnxh7xZ6iOrhcIxK51FbYM1
dAOmC7FJzIg47CaHiSRaj0k0euAT2wVZNm4YIakdGVBqU1EE0JdW4q20cqjQ
QKJvCCfDzonc6ZDT0+PricEyV6tmVZIgtDs+8KXQMm0GOLU0V3ILNGhgbIN0
xyeTU8gvz+z0bxT5cdv0rCQ6tOdSC8LzutwPrLuJ+ISBOk7b74f1WohN5TPi
EBVVyG1c+QvH3uhn8J4CVi/uSqwDk7Ldo/uuZ50zLkEFsajRJJxnEXasSY5f
u+pTKUWKUWBJCQziERGnckaLxI+JXj91Jk709yXlJ2nTQ+/ALYzenYs6Slgw
SUKbHBo5PpwTZ5iYrZZxzI5r2dv5nK7l86WcXRGz0jnPNnN9eNbxUZgXyAWQ
PiRGzImrEmPdUdqiCMINRnFIDX59HtSxiD+2881ilFOC6oS6mV51QLE/poWJ
QDomUSROjtw0qbor2g0ruF2TVN9yTEVjg5JPG9jGFX3FJetHzoug4LoGNbnV
S3dfN2g9FJFaOWd4Vb5OqoAx09IthaRw3P84aymJe3akt+C0wxx3xztkDzSS
Rup3BVmU+gP8immJKfXHTqg0KyrloqKETcMHdd+zw1o6BYO2R6AtwZFUv6eu
Tq9ndIZytUiFJ+HC8faYBajCrk6vj8F6BiC0mAhlDQyLO+NRwx2VwHR64F09
KhKO3uDvfZowNXNWXSZBB1eCoAmvJHW53dFSm+ke1x5R0JsbDMsywzzDfjvz
JV0o0ymlFE/XpJwCynGg4nXkDEsljacCruiAtFxrDSTJlQYdzwQNSfaQHoal
YK8uC/rYvLnFKlY0omyvmiEaBcEl7HjdRgdfuoxCPpiMpQCX04mP4JOyOTmD
gdNOkdI1dbuLPEFwkRBDd4NVChSOahZSKMA5BmhyalXp2OK8SOPGqN2E5rUg
Z4HClojDF9hm2eT8qcCHRZG24KDr0dLPJQgx8MLatBGyvo2PY+fWBXI0LJn/
9xlTDyZiatKu4KJtiR27IujJqltmCiIV7MBVLqnt7HLWRe8OL4kw51e//vzj
x9PxAe9OYMTaTzqYEV3TY0um5RXBn455W1DP+w5MkJ4iDj9rriZU2DutGuqp
YUcqxzRCSiYTucOMTq1TSPfSBg56hjRtyKSQj9iBmZbt0fBzch4uXl0cz3OI
hdEiy/XUVVZcjJXqKZYcxeIjSKRpNmLdAmfLCRUvHIIqxhemwMQMupk/OX1G
x4cT2eEHxE0ZoE0zGxDmhEH0dng5vwgdbzryliaoK8RTTkReRodsIUxCB06k
ZQMKrXLbE/LNuDXIqNOePoKAiqg8fckg9QEgZ1/yHCNvJ62ZGVxwIMc4lCrd
sDljWtCMOe+GZmu6Iz7PkzpAZlA7dU7CQzEPhC5HlT+XIBvKNZSU9uTRteNy
xdGbLdnt3qFFy86ZxS6wz/59xGi0zzv127GjHc1n8L2jxEC398HmY+wSu3Ig
GVwscenA4d5IDyiCrZhD+ISGGyk4LPd5LdIOeG7oOi27ZF/ZGDGWeugJxcoL
lusZNWM81I+fAsYxi2Mg0v8HNuXnTH+9AAA=

-->

</rfc>
