<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-cui-dawn-mdi-model-03" category="info" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Minimum Public Discovery Information">Minimum Public Discovery Information: Requirements and Common Semantics</title>
    <seriesInfo name="Internet-Draft" value="draft-cui-dawn-mdi-model-03"/>
    <author initials="Y." surname="Cui" fullname="Yong Cui">
      <organization>Tsinghua University</organization>
      <address>
        <postal>
          <city>Beijing</city>
          <code>100084</code>
          <country>China</country>
        </postal>
        <email>cuiyong@tsinghua.edu.cn</email>
        <uri>http://www.cuiyong.net/</uri>
      </address>
    </author>
    <author initials="C." surname="Du" fullname="Chenguang Du">
      <organization>Zhongguancun Laboratory</organization>
      <address>
        <postal>
          <city>Beijing</city>
          <code>100094</code>
          <country>China</country>
        </postal>
        <email>du_chenguang@outlook.com</email>
      </address>
    </author>
    <author initials="K." surname="Yao" fullname="Kehan Yao">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>yaokehan@chinamobile.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <workgroup>DAWN</workgroup>
    <keyword>discovery</keyword>
    <keyword>agents</keyword>
    <keyword>AI agents</keyword>
    <keyword>AI resources</keyword>
    <keyword>named entities</keyword>
    <keyword>information model</keyword>
    <keyword>metadata</keyword>
    <abstract>
      

<t>The charter of the Discovery of Agents With Names (DAWN) working group asks
it to specify the minimum public discovery information that a client obtains
when it discovers an AI resource. An individual draft on DAWN terminology
calls this Minimum Discoverable Information (MDI) but gives only examples of
its content. Individual drafts on the DAWN problem statement and
requirements call for a standardized minimum structure; without one,
emerging discovery formats risk each defining its own minimal metadata,
with descriptors that do not interoperate across organizational or protocol
boundaries.</t>
      <t>This document proposes a procedure that derives what is minimal from the
scope of the charter, applies it to the charter's three deployment contexts
(a local network, an organization, and the domain of a cooperating party),
and proposes the resulting elements and the minimal constraints that hold
among them as an information model in the sense of RFC 3444. It considers
this information both as a publisher provides it and as a client obtains
it; a value can come from the discovery response, from context the client
already has, or from binding rules. This document is input to the
charter's architecture and protocol deliverables and a mapping target for
existing discovery mechanisms.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    Discovery of Agents With Names Working Group mailing list (dawn@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/dawn"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/nxbrowning/MDI"/>.</t>
    </note>
  </front>
  <middle>
    

<section anchor="introduction">
      <name>Introduction</name>
      <t>Clients often need to discover information about AI resources, such as AI
agents, before interacting with them <xref target="DAWN-CHARTER"/>, and often have no
pre-configured relationship with them. Before any interaction can begin, a
client needs a small amount of information about the AI resource: what it
is, what it does, how to reach it, and what assurances, if any, accompany
those claims. <xref target="I-D.farrel-dawn-terminology"/> defines
Minimum Discoverable Information (MDI) as the minimum amount of information
an entity needs to provide to become discoverable, and does not define its
content; <xref target="I-D.king-dawn-requirements"/> requires each discovery mechanism to
define the MDI, including at least the entity's type, the services it offers,
its reachability information, and the communication protocols and any
security parameters needed to interact with it, and to indicate whether
discovery information is static or dynamic;
<xref target="I-D.akhavain-moussa-dawn-problem-statement"/> calls directly for a
standardized structure carrying the minimum information a discovery response
returns; and <xref target="I-D.moussa-dawn-gap-analysis"/> sketches a provisional baseline
without normalizing it. Mechanism-specific drafts define such fields for
their carriers (<xref target="I-D.jakab-dawn-agent-discovery-mdns"/>,
<xref target="I-D.blwm-dawn-common-discovery-parameters"/>); none defines MDI content
independently of a carrier.</t>
      <t>The DAWN charter <xref target="DAWN-CHARTER"/> places this information at the center of
the working group's scope: discovery is limited to a client requesting and
obtaining the minimum public discovery information for an AI resource (for
example, its type, reachability information, communication protocol, and
services) within a local network, within an organization, or between
cooperating parties with trust relationships over the public Internet. The
charter assigns this information to two deliverables: the Discovery
Architecture captures the requirements behind it, and the Protocol
specifications, possibly one per deployment context, define it. This document
uses "MDI" as shorthand for the information the charter calls minimum public
discovery information; where the two might differ, the charter's wording
governs.</t>
      <t>Meanwhile, the gap is being filled independently and incompatibly by adjacent
ecosystems: DNS-based bootstrap (<xref target="I-D.mozleywilliams-dawn-dnsaid"/>),
well-known JSON manifests, agent cards, and signed capability documents each
carry a slightly different minimal field set with slightly different
semantics, each bound to its own substrate. A descriptor that is minimal and
sufficient in one system is unreadable in another.</t>
      <t><xref target="I-D.farrel-dawn-terminology"/> distinguishes the input of discovery, the
Minimum Viable Dataset (MVD), from MDI, which it defines by what an entity
provides to become discoverable and describes as what a lookup returns. This
document considers MDI at both points, publication and response, and relates
it to the input. Following the distinction
<xref target="RFC3444"/> draws between information models and data models, it describes
the information involved in discovery (<xref target="flow"/>), proposes how to decide
what is minimal (<xref target="minimality"/>), applies that procedure to the charter's
three deployment contexts (<xref target="derivation"/>), and describes the elements
of the common discovery header and the minimal constraints that hold among
them (<xref target="model"/>), leaving encodings to bindings. <xref target="open-issues"/> lists the
points on which input is sought.</t>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        

</section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>This document uses the terms defined in <xref target="I-D.farrel-dawn-terminology"/>,
including AI Resource, Entity, Discovered Entity, Discovering Entity,
Discovery, Discovery Information, Discovery Scope, Discoverable Object,
Capability Card, Trust Indicator, and, centrally, Minimum Discoverable
Information (MDI); readers are assumed to be familiar with that document. The
elements defined here are the normalized slots through which a minimal subset
of an entity's Properties is conveyed as Discovery Information.</t>
      <t>The entity that MDI describes is a Discovered Entity, which in DAWN is an AI
system or AI resource <xref target="I-D.farrel-dawn-terminology"/>; the charter's AI
resource "may be an individual named agent or a service such as a catalog
that will further the discovery process" <xref target="DAWN-CHARTER"/>. In this document,
"resource" is short for AI resource. The client, as the charter calls it, is
the Discovering Entity; this document also calls it the discovering party.
In addition:</t>
      <dl>
        <dt>Discovery response:</dt>
        <dd>
          <t>What a discovery mechanism returns to a client; it may carry element
values for one or more entities.</t>
        </dd>
        <dt>Known context:</dt>
        <dd>
          <t>Information the client already has when it interprets a discovery
response, such as the Discovery Scope it searched, the name it started
from, or the
network it is attached to. Some of it is part of the MVD (<xref target="flow"/>).</t>
        </dd>
        <dt>Minimum Viable Dataset (MVD):</dt>
        <dd>
          <t>As defined in <xref target="I-D.farrel-dawn-terminology"/>, "the data that must be
provided to the discovery mechanism to enable it to return indications of
Discovered Entities" (<xref target="flow"/>).</t>
        </dd>
        <dt>MDI instance:</dt>
        <dd>
          <t>The collection of element values for one entity, as a publisher provides
it or as a consumer obtains it (<xref target="flow"/>). A consumer's instance takes
each value from the discovery response, known context, or a binding rule.</t>
        </dd>
        <dt>Consumer:</dt>
        <dd>
          <t>The party that interprets an MDI instance, typically the client that
performed discovery.</t>
        </dd>
      </dl>
    </section>
    <section anchor="scope">
      <name>Scope and Non-Goals</name>
      <t>This document defines the abstract content of the MDI common header, and
proposes how it is derived (<xref target="minimality"/>), within the initial discovery that the
DAWN charter scopes <xref target="DAWN-CHARTER"/>. It does NOT define:</t>
      <ul spacing="normal">
        <li>
          <t>a discovery, query, resolution, or transport protocol, and it does not bind
MDI to DNS or to any other carrier;</t>
        </li>
        <li>
          <t>a wire format, serialization, or schema; representations are illustrative
(<xref target="example"/>);</t>
        </li>
        <li>
          <t>a new capability card, or a replacement for any existing descriptor;</t>
        </li>
        <li>
          <t>identity verification, authentication, authorization, policy evaluation, or
attestation procedures;</t>
        </li>
        <li>
          <t>capability exchange, negotiation, selection, registration, or invocation
semantics;</t>
        </li>
        <li>
          <t>open-ended search, semantic matchmaking, ranking, indexing or searching
across the wider Internet, or trust management and trust evaluation beyond
the secure exchange of discovery information, all of which the charter
places out of scope.</t>
        </li>
      </ul>
    </section>
    <section anchor="design-principles">
      <name>Design Principles</name>
      <dl>
        <dt>Encoding-neutral model:</dt>
        <dd>
          <t>Per <xref target="RFC3444"/>, one information model can be carried by many concrete data
models -- a JSON object, a CBOR map, a set of DNS records. Those are
carriers; MDI is the shared meaning they carry.</t>
        </dd>
        <dt>Information, not fields:</dt>
        <dd>
          <t>Information that initial discovery needs can be carried in a discovery
response, supplied by known context (such as the scope searched or the
name the client started from), or fixed by a binding. Necessary
information therefore need not be repeated in every record.</t>
        </dd>
        <dt>Thin core, rich references:</dt>
        <dd>
          <t>MDI is a header. Rich or sensitive structures -- capability cards, proofs,
certificates, policy documents -- are referenced, not embedded, and fetched
only when needed. A binding can carry small items beyond the minimum, such
as coarse capability labels, directly as an Extension (<xref target="beyond"/>).</t>
        </dd>
        <dt>Discovery-time only:</dt>
        <dd>
          <t>MDI carries what lets a discovering party identify an entity, decide
whether follow-up is worthwhile, and dereference the next object safely.</t>
        </dd>
      </dl>
      <t>Freshness and rate of change matter -- elements are marked static,
mainly-static, or dynamic, and validity information is first-class -- but
detailed cache behavior belongs to bindings (<xref target="bindings"/>).</t>
    </section>
    <section anchor="flow">
      <name>Information in the Discovery Flow</name>
      <t>Discovery moves information through four stages, and each stage holds
different information:</t>
      <dl>
        <dt>Publication:</dt>
        <dd>
          <t>A publisher makes information about an entity available to a discovery
system. The publisher can be the entity or a system that maintains
information on its behalf, such as an orchestration system
<xref target="I-D.dunbar-dawn-infra-assisted-discovery"/>. Published information
contains the published MDI instance and can include more,
such as administrative or policy data that is never returned to clients.</t>
        </dd>
        <dt>Serving:</dt>
        <dd>
          <t>A system that answers lookups, such as an authoritative DNS server, a
registry, a catalog, or a responder on the local link, holds the published
information. It can generate or transform parts of the output, for
example when an mDNS responder renames an instance after a name conflict
or a Discovery Proxy answers unicast queries with the results of mDNS
queries <xref target="I-D.jakab-dawn-agent-discovery-mdns"/>, and it can add
information of its own or hold different views for different audiences.
A serving system outside the publisher's administrative domain, such as a
gateway or a third-party catalog, is an intermediary.</t>
        </dd>
        <dt>Lookup input:</dt>
        <dd>
          <t>The MVD: the data the discovery mechanism needs to return results. The
client supplies some of it in its query, such as a name, a protocol, or a
scope; other mechanisms can supply the rest, such as context derived from
the client's network attachment. Depending on the mechanism, a lookup can
enumerate a scope or target a narrower set.</t>
        </dd>
        <dt>Response:</dt>
        <dd>
          <t>The MDI instances returned for the entities found, interpreted together
with known context and binding rules.</t>
        </dd>
      </dl>
      <figure anchor="fig-flow">
        <name>Information in the discovery flow</name>
        <artwork><![CDATA[
+-----------+  published MDI and more   +-----------------+
| publisher |-------------------------->|                 |
+-----------+                           |  serving system |
                                        |                 |
+-----------+   lookup input (MVD)      |  can generate,  |
|  client   |-------------------------->|  transform, or  |
|           |<--------------------------|  add            |
+-----------+   response (MDI)          |  information    |
      |                                 +-----------------+
      |  follow-up at an Endpoint: description retrieval,
      v  interaction, or further discovery
]]></artwork>
      </figure>
      <t>This document proposes that MDI be considered at publication as well as in
the response. The individual terminology draft
<xref target="I-D.farrel-dawn-terminology"/> defines MDI by what an entity needs to
provide to become discoverable and describes a lookup that returns it, and
the individual requirements draft <xref target="I-D.king-dawn-requirements"/> asks each
mechanism to define the MDI "that every discoverable entity provides"; the
charter defines discovery by what a client obtains. The model of <xref target="model"/>
describes MDI instances at both points: published MDI instances, which
publishers provide, and the instances consumers obtain. The correspondence
need not be one to one. One published MDI instance can yield several
obtained instances, as when a Discovery Proxy relays an advertisement
(<xref target="derivation"/>), and an entity can have several published MDI instances,
per protocol or per publisher; a binding states how they correspond. A
published and an obtained instance have the same elements and can differ in
which values they carry and in the values themselves: a serving system can
generate or transform values, as in the examples above; a binding can fix a
value, such as an Endpoint purpose; and known context can supply one, such
as a protocol named in the query. Every other value comes from a publisher.</t>
      <t>Considered at publication, the analysis of <xref target="minimality"/> also
indicates what a publisher has to provide, which each binding states
(<xref target="bindings"/>). Origin and attribution are assessed per value. A value can be
verified to the name that a validated key is authorized for, the zone for
DNSSEC or the origin for TLS, whoever operates the server. Protection
applied at publication, such as a signature by a key that the binding ties
to the publisher's name through an authenticated property of the carrier,
covers only values that serving systems pass on unchanged. A value that a
serving system generates or transforms, as a catalog or a Discovery Proxy
does, can be verified at most to that serving system, and only where that
system is authenticated; <xref target="derivation"/> applies this to the deployment
contexts. A consumer generally obtains only its own instance, so a binding
states which values a serving system can generate or transform, and those
values are attributable to the serving system unless protection applied at
publication covers them.</t>
      <t>How published information reaches a serving system, for example by zone
provisioning, DNS Update, SRP registration, or a registry interface, is a
registration mechanism. <xref target="I-D.farrel-dawn-terminology"/> lists registration
as a function separate from the discovery lookup and places it out of scope
for DAWN, while noting that "the information that can be discovered and the
trust with which that information is treated are key to any complete
system". This document defines no registration mechanism (<xref target="scope"/>).</t>
      <t>The MVD and MDI can share attributes, such as a protocol that a client asks
for and a response reports, and each has items the other lacks, such as a
search scope in the input and endpoints in MDI. The sources of the input, how it is conveyed, and
how it corresponds to published information are stated for each deployment
context and binding. A catalog reached through an Endpoint whose purpose is
continuing discovery can return MDI instances for the resources it lists;
how it selects them is outside this document (<xref target="scope"/>). The individual
use-cases draft <xref target="I-D.kay-dawn-use-cases"/> leaves to the DAWN architecture which query
properties belong in the minimum (<xref target="open-issues"/>).</t>
    </section>
    <section anchor="minimality">
      <name>Determining What Is Minimal</name>
      <t>The charter gives examples of the minimum public discovery information
(type, reachability information, communication protocol, and services) but
no list <xref target="DAWN-CHARTER"/>. This document uses one question to decide what
belongs: what does a client need to know to use a discovery result? Using a
result means the subsequent interactions that the charter names, "such as
selection, invocation, or communication": determining which Endpoint and
agent protocol to use, then fetching its description, talking to it, or
asking a catalog for more results.</t>
      <t>An example shows how the question works. A client on a shop's network looks
for agents and receives three results. To choose one and talk to it, the
client has to tell the three apart, so each result needs a name. It has to
know where to connect, such as a host and port or a URL, and which agent
protocol to speak there, such as A2A or MCP. It has to know what it will
find there: the agent itself, or a description of the agent, such as an
agent card. And it has to know whether the result is still current. Other
information helps only in some situations: a short description when a
person, not software, makes the choice; an authentication scheme when the
client talks to the agent directly without reading a description first;
and a stable identifier when the client wants to recognize the same agent
later or in another result. The rest, such as the full list of what the
agent can do, can be read from its description after the choice is made,
and is not part of the minimum.</t>
      <t>Not everything a client needs has to be in every result. A client that
asked for A2A agents already knows the protocol, and a discovery mechanism
can fix defaults, such as where an agent card is found. For each piece of
information, this document therefore records two things: whether a client
needs it, and where the client gets it, which is from the result, from its
own query, from the rules of the discovery mechanism, or later from a
description.</t>
      <t>The analysis has four steps:</t>
      <ol spacing="normal" type="1"><li>
          <t>List the candidates: the charter's examples and the information that
existing discovery mechanisms carry (<xref target="mapping-notes"/>).</t>
        </li>
        <li>
          <t>For each candidate and each deployment context of the charter, ask: if
this were missing, could the client still use the result? If not, the
client needs it in that context.</t>
        </li>
        <li>
          <t>For each candidate the client needs, ask whether the client can know it
without the result telling it. If not, results have to carry it, and
the publisher provides it unless a serving system generates it
(<xref target="flow"/>).</t>
        </li>
        <li>
          <t>Where a candidate is needed only in some situations, state the
situation.</t>
        </li>
      </ol>
      <t>What existing mechanisms carry is evidence for step 1: information that all
of them carry can be required at little cost, and information that only
some of them carry still has to pass step 2. The charter also requires
integrity of all discovery information exchanged; protecting it, and the
origin of the information where <xref target="tab-derivation"/> marks this, is an
obligation on the binding in every context (<xref target="bindings"/>).</t>
    </section>
    <section anchor="derivation">
      <name>Applying the Procedure</name>
      <t>This section applies <xref target="minimality"/> to the three deployment contexts of the
charter. The charter's examples enumerate all agents in a scope; a lookup
can also return a narrower set, such as the agents that speak one protocol,
and the analysis applies to each result in the same way. The DNS-based
mechanisms below are representative; the same model applies to registry
and catalog interfaces.</t>
      <dl>
        <dt>Local network:</dt>
        <dd>
          <t>The charter's example is "discover all agents in this shop". The client
knows only its network attachment and possibly the agent protocol it
wants; it has no name, registry, or prior relationship. DNS-SD over
multicast DNS, as the individual draft
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/> profiles it for agents, is a
representative mechanism. The next step is to tell the candidates
apart, choose one, and retrieve its description or interact with it.</t>
        </dd>
        <dt>Within an organization:</dt>
        <dd>
          <t>The charter's example is "discover all agents available to employees
within their employer's infrastructure". In the case tested here, the
client is attached to the organization's network, possibly through a
VPN, and can learn from that attachment where to look: DNS-SD domain
enumeration queries names derived from a domain name received through
DHCP and from the client's address prefixes (<xref section="5.2" sectionFormat="comma" target="RFC8766"/>).
Representative mechanisms extend those of the other two contexts: DNS-SD
beyond the link, through Discovery Proxies <xref target="RFC8766"/> or registration
with the Service Registration Protocol (SRP) <xref target="RFC9665"/>, as
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/> describes for enterprise campus
and branch networks, and DNS records in internal zones, which the
individual draft <xref target="I-D.mozleywilliams-dawn-dnsaid"/> provides for. The
next step is to choose an agent and retrieve its description or interact
with it, or to continue discovery at a catalog.</t>
        </dd>
        <dt>Known domain of a cooperating party:</dt>
        <dd>
          <t>The charter's example is "discover all agents of example.org, for all its
customers/members", between cooperating parties with trust relationships
over the public Internet. The client knows the party's domain name and
possibly the protocol, and has an organizational trust relationship;
knowing the name does not show that information came from that party, and
"for all its customers/members" names an audience for the results.
DNS records under the party's domain, as proposed in the individual drafts
<xref target="I-D.mozleywilliams-dawn-dnsaid"/> and
<xref target="I-D.blwm-dawn-common-discovery-parameters"/>, are representative. To find
all of a domain's agents, these drafts locate an organizational index at a
well-known name such as <tt>_index._agents.&lt;domain&gt;</tt>, so the next step is
further discovery at that index; a client that already knows an agent's
name queries its records directly, then reaches the agent or retrieves its
description.</t>
        </dd>
      </dl>
      <table anchor="tab-derivation">
        <name>Derivation for the three deployment contexts</name>
        <thead>
          <tr>
            <th align="left">Information</th>
            <th align="left">If missing</th>
            <th align="left">Other source</th>
            <th align="left">Result</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Name of each result</td>
            <td align="left">Results cannot be told apart</td>
            <td align="left">The query, when it names one entity</td>
            <td align="left">Needed in every context</td>
          </tr>
          <tr>
            <td align="left">Endpoint location</td>
            <td align="left">Client cannot connect</td>
            <td align="left">Partly: owner name, default path</td>
            <td align="left">Needed in every context</td>
          </tr>
          <tr>
            <td align="left">Agent protocol</td>
            <td align="left">Client cannot talk to the endpoint</td>
            <td align="left">The query, when the binding ties the protocol to it</td>
            <td align="left">Needed in every context</td>
          </tr>
          <tr>
            <td align="left">Endpoint purpose</td>
            <td align="left">Next step unknown</td>
            <td align="left">Protocol or well-known name, via the binding</td>
            <td align="left">Needed in every context</td>
          </tr>
          <tr>
            <td align="left">Freshness</td>
            <td align="left">Stale data not recognized</td>
            <td align="left">Record lifetime</td>
            <td align="left">Needed in every context</td>
          </tr>
          <tr>
            <td align="left">Entity type</td>
            <td align="left">Kinds of resource cannot be told apart</td>
            <td align="left">Carrier name or Endpoint purpose, via the binding</td>
            <td align="left">When kinds are told apart</td>
          </tr>
          <tr>
            <td align="left">Display name</td>
            <td align="left">Only a person choosing is affected</td>
            <td align="left">DNS-SD instance name</td>
            <td align="left">When a person chooses</td>
          </tr>
          <tr>
            <td align="left">Authentication hint</td>
            <td align="left">Next step can fail</td>
            <td align="left">Description or protocol handshake</td>
            <td align="left">When neither supplies the scheme first</td>
          </tr>
          <tr>
            <td align="left">Stable identifier</td>
            <td align="left">Results cannot be correlated</td>
            <td align="left">None</td>
            <td align="left">When results are correlated</td>
          </tr>
          <tr>
            <td align="left">Services</td>
            <td align="left">Covered by Endpoint protocols and Entity Type</td>
            <td align="left">Description</td>
            <td align="left">Left to the WG</td>
          </tr>
          <tr>
            <td align="left">Origin</td>
            <td align="left">Publisher unknown</td>
            <td align="left">DNSSEC or TLS, to the zone or origin; none for mDNS or SRP advertisers</td>
            <td align="left">Protection goal</td>
          </tr>
          <tr>
            <td align="left">Coarse capability labels</td>
            <td align="left">Nothing; the client chooses by protocol and type</td>
            <td align="left">Description</td>
            <td align="left">Beyond the minimum</td>
          </tr>
          <tr>
            <td align="left">Trust material, publisher name</td>
            <td align="left">Nothing beyond what origin provides</td>
            <td align="left">Binding and carrier</td>
            <td align="left">Beyond the minimum</td>
          </tr>
          <tr>
            <td align="left">Scope or audience hint</td>
            <td align="left">Nothing; the audience applies to the lookup</td>
            <td align="left">Query and deployment</td>
            <td align="left">Beyond the minimum</td>
          </tr>
          <tr>
            <td align="left">Availability</td>
            <td align="left">The connection fails and the client tries another result</td>
            <td align="left">Follow-up connection</td>
            <td align="left">Beyond the minimum</td>
          </tr>
        </tbody>
      </table>
      <t>In the Result column, "Protection goal" marks an obligation on the binding
(<xref target="bindings"/>), "Left to the WG" marks a question in <xref target="open-issues"/>, and
"Beyond the minimum" marks information a client does not need for its next
step, which is therefore not part of MDI (<xref target="beyond"/>). The Other source
column reflects the representative mechanisms above.</t>
      <t>The results are the same in all three contexts; what differs is where the
client gets each item. On a local network, each result carries the name,
the endpoint location, and the protocol. A query for a known name, as under
a cooperating party's domain, supplies the name, and a query for one
protocol supplies the protocol. The binding supplies defaults, such as the
protocol's default path, and usually the endpoint purpose, which follows
from the protocol or from a well-known name such as an index label.
Freshness comes from the lifetime of the records a result is built from.</t>
      <t>The conditional items depend on the next step. A display name matters when
a person chooses among results. An authentication hint matters when the
client interacts directly and neither a description nor the agent
protocol's own handshake supplies the scheme first. A Stable Identifier
matters when results are correlated, as when a client within an
organization sees the same agent both through multicast DNS on its link and
through a Discovery Proxy (<xref target="constraints"/>). Entity type matters when the
client has to tell kinds of AI resource apart to choose its next step, and
is usually implied by the carrier, such as a well-known name, or by the
endpoint purpose. Whether services are covered by Endpoint protocols and
Entity Type is asked in <xref target="open-issues"/>. Information beyond the minimum can help
but is not needed for this initial step: the client chooses by protocol and type, learns the
details from the description, and learns availability at the follow-up
connection.</t>
      <t>Where the results are meant for an audience, as "available to employees"
and "for all its customers/members" suggest, the restriction applies to the
lookup, for example through split-view DNS or a VPN, and the result carries
nothing that enforces it; where this requester context belongs is asked in
<xref target="open-issues"/>.</t>
      <t>Origin is where the contexts differ most. Under a party's domain,
DNSSEC-validated records and TLS-authenticated origins tie the information
to the party. A catalog or a Discovery Proxy that relays information can be
authenticated only as itself, and on a local link multicast DNS does not
authenticate advertisements, so the agent is authenticated only at the
follow-up connection <xref target="I-D.jakab-dawn-agent-discovery-mdns"/>. How the
charter's integrity requirement is met for such advertisements is asked in
<xref target="open-issues"/>.</t>
      <t>Compared with REQ-PROP-1 of the individual requirements draft
<xref target="I-D.king-dawn-requirements"/>, reachability and protocol are needed in
every context, type and security parameters (an authentication hint)
under a condition, and services are a question for the working group.</t>
    </section>
    <section anchor="model">
      <name>MDI Information Model</name>
      <t>An MDI instance is the common header published or obtained for one entity.
Its elements follow the results of <xref target="derivation"/> (<xref target="tab-derivation"/>):</t>
      <ul spacing="normal">
        <li>
          <t>Information needed in every context becomes the mandatory Name and
Endpoint (location, agent protocol, and purpose) and the Freshness
element. Freshness is <bcp14>SHOULD</bcp14> because its meaning is obtainable from the
carrier lifetime; a binding whose carrier provides no lifetime <bcp14>MUST</bcp14> carry
it.</t>
        </li>
        <li>
          <t>Information needed only under a condition becomes an element with Status
<bcp14>MAY</bcp14>: Entity Type, Display Name, Authentication Hint, and Stable
Identifier. A publisher cannot always know whether the condition holds
for a given consumer; a binding or profile for deployments where it holds
can make the element <bcp14>MUST</bcp14>; for example, a binding for exchange between
gateways or catalogs can make the Stable Identifier <bcp14>MUST</bcp14>.</t>
        </li>
        <li>
          <t>Services, left to the working group, are covered by Endpoint protocols
and Entity Type (<xref target="services"/>).</t>
        </li>
        <li>
          <t>Origin is a protection goal, met by the binding (<xref target="bindings"/>), and is
not an element.</t>
        </li>
        <li>
          <t>Information beyond the minimum is not an element of MDI. A binding can
still carry it as an Extension, and <xref target="beyond"/> names the kinds that
existing formats and individual drafts carry, so that bindings agree on
their meaning.</t>
        </li>
      </ul>
      <t>Mandatory elements keep the record very small; in constrained carriers, a
binding can derive their values from the carrier or from known context
(<xref target="bindings"/>). All Status values are provisional.</t>
      <t>Status key words in this document place obligations on the publishers and
bindings that claim to carry MDI, and key words addressed to consumers apply
to implementations of a binding. Status says how strongly the meaning of an
element has to be obtainable by the consumer, from the response, from known
context, or from binding rules; whether each response carries a value
explicitly is a binding decision. Status applies to the instance a consumer
obtains; a publisher provides every value that the binding neither derives
nor fixes and that no serving system generates (<xref target="flow"/>). Cardinality
governs how many values of an element may be carried. Obligations specific
to binding documents are collected in <xref target="bindings"/>.</t>
      <section anchor="structure">
        <name>Structure</name>
        <t><xref target="fig-structure"/> shows the elements and their shapes. Composite members
marked "?" are optional, and freshness, whose members are all optional, is
present only when at least one member is present; all other structure is
given by the cardinalities.</t>
        <figure anchor="fig-structure">
          <name>Elements of the MDI model</name>
          <artwork><![CDATA[
+--------------+   describes exactly one
| MDI Instance |--------------------------->  Entity
+--------------+
  |- name                                        (1)
  |- endpoint { locator-type, locator,
  |             protocols (1..n), purpose?,
  |             digest? }                        (1..n)
  |- freshness { version?, valid-from?,
  |              valid-until?, refresh-hint? }   (0..1)
  |- entity-type                                 (0..1)
  |- display-name                                (0..n)
  |- authentication-hint { scheme, metadata? }   (0..n)
  |- stable-identifier                           (0..1)
  |- extension { name, value }                   (0..n)

  Reference = { ref-type, locator, digest? }
]]></artwork>
        </figure>
        <t>A Reference is a typed pointer, used by the Authentication Hint and by
information beyond the minimum: the ref-type says how to interpret the
locator, and the optional digest is an integrity digest over the object the
locator identifies (<xref target="constraints"/>). Information carried directly, rather
than through a Reference, is covered by the integrity protection of the
binding (<xref target="bindings"/>).</t>
      </section>
      <section anchor="elements">
        <name>Elements</name>
        <table>
          <thead>
            <tr>
              <th align="left">Element</th>
              <th align="left">Status</th>
              <th align="left">Class</th>
              <th align="left">Result in Table 1</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Name</td>
              <td align="left">
                <bcp14>MUST</bcp14></td>
              <td align="left">varies</td>
              <td align="left">Needed in every context</td>
            </tr>
            <tr>
              <td align="left">Endpoint</td>
              <td align="left">
                <bcp14>MUST</bcp14></td>
              <td align="left">mainly-static</td>
              <td align="left">Needed in every context (location, protocol, purpose)</td>
            </tr>
            <tr>
              <td align="left">Freshness</td>
              <td align="left">
                <bcp14>SHOULD</bcp14></td>
              <td align="left">dynamic</td>
              <td align="left">Needed in every context; carrier lifetime</td>
            </tr>
            <tr>
              <td align="left">Entity Type</td>
              <td align="left">
                <bcp14>MAY</bcp14></td>
              <td align="left">static</td>
              <td align="left">When kinds are told apart</td>
            </tr>
            <tr>
              <td align="left">Display Name</td>
              <td align="left">
                <bcp14>MAY</bcp14></td>
              <td align="left">static</td>
              <td align="left">When a person chooses</td>
            </tr>
            <tr>
              <td align="left">Authentication Hint</td>
              <td align="left">
                <bcp14>MAY</bcp14></td>
              <td align="left">mainly-static</td>
              <td align="left">When neither description nor handshake supplies it</td>
            </tr>
            <tr>
              <td align="left">Stable Identifier</td>
              <td align="left">
                <bcp14>MAY</bcp14></td>
              <td align="left">static</td>
              <td align="left">When results are correlated</td>
            </tr>
            <tr>
              <td align="left">Extension</td>
              <td align="left">
                <bcp14>MAY</bcp14></td>
              <td align="left">varies</td>
              <td align="left">Mechanism for information beyond the minimum</td>
            </tr>
          </tbody>
        </table>
        <t>A static value is not expected to change while the resource keeps its
identity. A mainly-static value changes only through deliberate
administrative or deployment action. A dynamic value can change in normal
operation and is evaluated together with Freshness. The stability of a Name
varies with the carrier and is stated by the binding.</t>
        <t>The following elements are needed in every context.</t>
        <dl>
          <dt>Name:</dt>
          <dd>
            <t>The name under which a result is found, such as a DNS-SD service instance
name or a DNS owner name, which lets a client tell results apart and
refer back to them. It is often implicit in the carrier and is
interpreted within its naming scope (<xref target="constraints"/>). One resource can be
found under several Names, for example one per protocol, and a Name can
change, as when multicast DNS renames an instance after a conflict. A
Name that the binding states to be stable also serves as the Stable
Identifier; such a name is the stable name by which
<xref target="I-D.farrel-dawn-terminology"/> identifies a Named Entity.</t>
          </dd>
          <dt>Endpoint:</dt>
          <dd>
            <t>Where follow-up can proceed, for what purpose, and in which agent
protocol; the locator is the charter's "reachability information", and
the protocols member its "communication protocol". In this document,
"agent protocol" means the application protocol that an AI resource
speaks at the endpoint, such as A2A or MCP, whether or not the resource
is an agent. The locator-type and locator members say where to go; a binding
can carry the locator as one value, such as a URI, or assemble it from
several fields, such as a target host and port plus a path. The protocols
member names the agent protocols reached there, such as A2A or MCP; the
protocol negotiated on the underlying TLS or QUIC connection, such as an
HTTP version identified by ALPN <xref target="RFC7301"/>, is different information
unless the agent protocol runs directly over TLS or QUIC. A protocols
value can name a version or versions of the agent protocol; where it does
not, the binding states how a client learns which version to use, for
example from the description or through the protocol's own negotiation.
The purpose
member says what the follow-up is: retrieving a description of the
resource (for example, an agent card), interacting with the resource, or
continuing discovery at another discovery service, such as a catalog.
When the purpose is not carried, the binding states how it follows from
the protocol. An Endpoint for description retrieval is how MDI points to
a fuller capability description, such as a Capability Card; its
protocols member names the agent protocol of the described resource, the
description is fetched as the locator implies (for an https URI, with an
HTTP GET), and the Endpoint can carry a digest of the description. An
entity can have Endpoints with different protocols and purposes.</t>
          </dd>
          <dt>Freshness:</dt>
          <dd>
            <t>Version, validity window, and refresh hint for the instance. A version
need not change when the resource's description changes; the digest of a
description Endpoint changes when the description does, but it is not a
protocol version or a trust signal (<xref target="constraints"/>).</t>
          </dd>
        </dl>
        <t>The following elements are needed under the conditions that <xref target="derivation"/>
states.</t>
        <dl>
          <dt>Entity Type:</dt>
          <dd>
            <t>The kind of AI resource: for example an individual named agent or a
service such as a catalog that furthers discovery, the two kinds the
charter names <xref target="DAWN-CHARTER"/>, or another AI resource such as an AI
inference service <xref target="I-D.farrel-dawn-terminology"/>. It lets a client
triage before fetching anything, and is needed when the client has to
tell kinds of AI resource apart to choose its next step. It is usually
implied by the carrier, such as a well-known name, or by the Endpoint
purpose, and the binding states how. The value space is left to DAWN,
bindings, or profiles to define.</t>
          </dd>
          <dt>Display Name:</dt>
          <dd>
            <t>A short human-readable name or description for a person choosing among
results, with no machine semantics. In DNS-SD the Name often serves;
under unicast owner names, a binding carries one, as the title parameter
of <xref target="I-D.blwm-dawn-common-discovery-parameters"/> does, or takes it from
the description. Language handling, if any, is a binding matter.</t>
          </dd>
          <dt>Authentication Hint:</dt>
          <dd>
            <t>The authentication scheme(s) a discovering party would need for
follow-up, optionally with a Reference to authentication metadata. Never
credentials, never authorization logic.</t>
          </dd>
          <dt>Stable Identifier:</dt>
          <dd>
            <t>A name for the resource itself that stays the same across results,
protocols, and time within its naming scope, so that a client can
correlate results and recognize the resource later. Where the naming scope
is itself globally unique, such as a DNS domain or a URN namespace, the
Stable Identifier is globally unique. Like a Name, it is a name, not a
verified identity, key, or proof.</t>
          </dd>
          <dt>Extension:</dt>
          <dd>
            <t>An extension named by a binding, profile, or future registry, carrying
type-specific or ecosystem-specific information, including the
information beyond the minimum of <xref target="beyond"/>. An Extension does not alter
core element semantics and does not reintroduce a non-goal of
<xref target="scope"/>.</t>
          </dd>
        </dl>
      </section>
      <section anchor="beyond">
        <name>Information Beyond the Minimum</name>
        <t><xref target="tab-derivation"/> finds that a client does not need the following
information for its next step, so it is not part of MDI; REQ-PROP-1 of the
individual requirements draft <xref target="I-D.king-dawn-requirements"/> likewise
states that "Properties beyond the MDI are optional". Existing formats and
individual drafts carry it (<xref target="mapping-notes"/>). A binding that carries it
does so as an Extension, with the following meanings:</t>
        <dl>
          <dt>Capability Summary:</dt>
          <dd>
            <t>Coarse, machine-readable capability tags for discovery-time filtering and
triage; they are not sufficient for selection, negotiation,
authorization, or invocation. The value space is not yet defined
(<xref target="services"/>).</t>
          </dd>
          <dt>Trust Reference:</dt>
          <dd>
            <t>A Reference to a trust indicator, such as a signature, certificate,
attestation, trust manifest, or key set.</t>
          </dd>
          <dt>Provenance:</dt>
          <dd>
            <t>Who published this discovery information and, optionally, the party
responsible for the entity -- information-layer provenance, not verified
identity.</t>
          </dd>
          <dt>Scope Hint:</dt>
          <dd>
            <t>An opaque hint about discovery scope, audience, jurisdiction, or
visibility. It is not access control (<xref target="privacy"/>).</t>
          </dd>
          <dt>Operational Hint:</dt>
          <dd>
            <t>A coarse availability or health class, or a Reference to richer
operational state, or both.</t>
          </dd>
        </dl>
      </section>
      <section anchor="services">
        <name>Services</name>
        <t>The charter lists "services" among its examples <xref target="DAWN-CHARTER"/>, and
REQ-PROP-1 of <xref target="I-D.king-dawn-requirements"/> requires the MDI to include
"the services it offers"; neither says what a service is. This document
covers services with existing elements, so there is no separate Services
element:</t>
        <ul spacing="normal">
          <li>
            <t>The agent protocols a resource offers, such as A2A or MCP, are the
protocols of its Endpoints. The per-protocol DNS-SD subtypes proposed for
agents, such as "_a2a._sub._agents._tcp", name these protocols
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/>.</t>
          </li>
          <li>
            <t>A resource that is itself a service, such as a catalog that furthers
discovery, as the charter's scope notes, is identified by its Entity Type
and by an Endpoint whose purpose is continuing discovery.</t>
          </li>
        </ul>
        <t>Coarse labels for what a resource does are the Capability Summary, which
is beyond the minimum (<xref target="beyond"/>). The individual draft
<xref target="I-D.zhang-dawn-bgp-style-federated-discovery"/> makes such labels
mandatory, while <xref target="I-D.blwm-dawn-common-discovery-parameters"/> leaves
capabilities out of DNS records and notes that coarse categories, if ever
needed, could use DNS-SD subtypes. A shared vocabulary for the labels does
not yet exist, and labels used for more than triage would be capability
information beyond the minimum, which the charter places out of scope.
Whether this reading of "services" is right is asked in <xref target="open-issues"/>.</t>
      </section>
      <section anchor="constraints">
        <name>Minimal Constraints</name>
        <t>The following rules are part of the model. A binding <bcp14>MAY</bcp14> tighten them but
<bcp14>MUST NOT</bcp14> relax them.</t>
        <ol spacing="normal" type="1"><li>
            <t>An MDI instance describes exactly one entity. A discovery response may
carry information for several entities; aggregation is a carrier matter.</t>
          </li>
          <li>
            <t>Each Name and Stable Identifier is interpreted within a naming scope,
which by default is the publisher scope. A binding states the naming
scope and stability period of each Name and Stable Identifier it carries
and how values are compared, with exact match as carried as the default.
A Name distinguishes results only within its naming scope and stability
period, and one resource may be found under several Names. The host name
at which an endpoint is reached (such as an SVCB TargetName) belongs to
the Endpoint locator and names a host, even where the same string is
also a Name. Correlating results to one resource without a Stable
Identifier is heuristic. Within one naming scope, equal Stable
Identifiers denote the same resource; unequal ones do not by themselves
denote distinct resources, and across naming scopes this model makes no
sameness claim. Where a consumer holds several instances with the same
Stable Identifier, it reconciles them by Freshness only among instances
whose integrity and origin in that naming scope have been verified as
the binding defines, using only Freshness values that the same
verification covers; an instance that has not passed those checks does
not displace one that has, and other cases are left to the binding.</t>
          </li>
          <li>
            <t>Protocols attach to endpoints, not to the instance as a whole. A
protocols value names an agent protocol, not the protocol negotiated on
the underlying connection, such as an HTTP version, except where the two
coincide (<xref target="elements"/>). An instance-level protocol list, where a binding
offers one, is derived information (the union over all endpoints) and
cannot diverge from them. The model attaches no meaning to the order of
Endpoints; preference and selection are binding or carrier matters.</t>
          </li>
          <li>
            <t>A digest, when present, is a member of the Reference or of the
description-retrieval Endpoint it protects and covers exactly the object
located there. Integrity is not trust: a matching digest shows that the
bytes are intact, provided the digest itself was obtained with
integrity, and it does not show that the publisher or the entity should
be believed. A consumer <bcp14>MUST NOT</bcp14> use an object whose digest does not
match. How a digest value identifies its algorithm is defined by the
binding.</t>
          </li>
          <li>
            <t>A consumer <bcp14>MUST</bcp14> ignore unrecognized Extensions; their
presence is not an error. As an exception, a binding <bcp14>MAY</bcp14> mark an
Extension as mandatory, as SVCB does with its "mandatory" key
(<xref target="RFC9460"/>); unless the binding says otherwise, a consumer that does
not understand a mandatory Extension does not use the Endpoint or result
that carries it, as an SVCB client skips a record that lists a mandatory
key it does not support.</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="bindings">
      <name>Binding Expectations</name>
      <t>MDI reaches the wire through bindings: documents that map this model onto a
concrete encoding or discovery mechanism. Existing discovery formats already
approximate bindings (<xref target="mapping-notes"/>); normative bindings are expected in
separate documents. A binding that carries MDI <bcp14>MUST</bcp14> specify:</t>
      <dl>
        <dt>Encoding:</dt>
        <dd>
          <t>How each element is encoded and which value space it uses, defined by the
binding, a profile, or a future registry. Which values are implicit and
how they are derived from the carrier or from known context, for example a
Name taken from a DNS-SD service instance name; an implicit value counts
exactly as an explicit one. How unrecognized Extensions are carried and
skipped at the encoding level, and which Extensions, if any, are
mandatory.</t>
        </dd>
        <dt>Names and Endpoints:</dt>
        <dd>
          <t>The naming scope and stability period of each Name and Stable Identifier
it carries, and whether it carries a Stable Identifier at all. For each
Endpoint, how the locator is assembled, how the purpose is determined
when it is not carried, how protocol versions are expressed or learned,
and, where
connection-level protocols are also carried, how they are kept apart from
the protocols member. For an Endpoint for description retrieval, which
object a digest covers. For Endpoints whose purpose is continuing
discovery, the maximum referral depth, how loops are detected, and the
naming scope of the results obtained there.</t>
        </dd>
        <dt>Integrity and origin:</dt>
        <dd>
          <t>How the integrity and origin of the MDI it conveys are protected,
including how carried values are bound to the carrier fields and known
context they are interpreted with, for example that a response answers
the name or scope the client asked about, and where verification
material comes from. How the publisher scope is determined from an
authenticated property of the carrier, such as a DNSSEC-validated owner
name or a TLS-authenticated web origin, never from values the instance
asserts about itself, such as Provenance, and what publisher scope, if
any, applies where a
serving system generates the content from unauthenticated sources, as a
Discovery Proxy does. Whether information relayed by a catalog or other
intermediary is verified to the original publisher or only to the
intermediary. How a consumer treats failed verification, removed
elements, and expired information, and what successful verification
establishes and what it does not.</t>
        </dd>
        <dt>Sources and lifetimes of values:</dt>
        <dd>
          <t>Which values the publisher provides and which a serving system generates
or transforms, how a consumer tells them apart, how what an intermediary
adds or changes is attributed to it, and which publisher an obtained
instance derives from when several provide information for one entity.
How carrier lifetimes, such as a DNS TTL or an HTTP cache lifetime,
combine with Freshness, including which record lifetimes apply when a
result is assembled from several records, with the earliest applicable
expiry prevailing, and how stale or replayed information is detected.</t>
        </dd>
      </dl>
      <t>A binding <bcp14>MUST</bcp14> protect the integrity of all MDI it conveys, as the charter
requires <xref target="DAWN-CHARTER"/>; what meets this requirement where the carrier
does not authenticate advertisements is asked in <xref target="open-issues"/>. A binding
<bcp14>MAY</bcp14> tighten Status, cardinality, or constraints, including per entity type,
but <bcp14>MUST NOT</bcp14> relax a <bcp14>MUST</bcp14> element or a rule of <xref target="constraints"/>.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>MDI is advertised information; a consumer <bcp14>MUST</bcp14> treat it as unverified until
corroborated by mechanisms outside this document.</t>
      <ul spacing="normal">
        <li>
          <t>Values prove nothing by themselves. Any value can be forged by whoever
publishes or serves it: a Name or Stable Identifier is not proof of
identity, and an Endpoint does not prove that the reachable party is the
intended entity. A matching digest shows only that a referenced object is
the one the digest was computed over, and only if the digest was obtained
with integrity; it does not show that the publisher or the entity can be
trusted. A Display Name or other text chosen by the publisher can
imitate another entity, including through visually confusable
characters, or carry text aimed at automated consumers; a client presents
such text as unverified, does not use it to identify or authorize, and
does not treat it as instructions. An Authentication Hint, and any
metadata at its locator, is unverified; it does not lead a client to
weaken its authentication requirements or to send credentials to a party
named only by unverified MDI. A Trust Reference locates assurance
material but confers none until that material is verified by procedures
defined elsewhere.</t>
        </li>
        <li>
          <t>Protection comes from the binding and the carrier, value by value.
Integrity and origin, including protection against the removal of
optional elements, are properties of the binding and carrier (for example
DNSSEC, TLS); each binding states how it provides them and to whom origin
is verified (<xref target="bindings"/>). A serving system can generate, transform,
withhold, or replay values, and protection applied at publication covers
only the values it protects. A value derived from the carrier is as
trustworthy as that carrier, and a value taken from known context is no
more trustworthy than that context. A consumer <bcp14>SHOULD NOT</bcp14> draw
conclusions from the absence of an element. A referral to another
discovery service does not extend the referring publisher's naming scope
or protection to the results obtained there.</t>
        </li>
        <li>
          <t>Every locator in MDI, whether of an Endpoint, a Reference, or
authentication metadata, is supplied by an unverified party, and
following it carries the usual risks of contacting an untrusted party.
The usual dereferencing protections apply, such as limits on redirects
and response sizes. Which addresses a client connects to is a matter of
deployment policy, applied to the addresses a locator resolves to at
connection time, including after redirects. Link-local and internal
addresses are expected results of local and organizational discovery;
unless deployment policy permits otherwise, a client does not connect to
them when they appear in information obtained from outside that context.</t>
        </li>
      </ul>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>Publishing MDI can reveal entity names, endpoints, organizational structure,
capability hints, and scope information. Publishers <bcp14>SHOULD</bcp14> minimize public
MDI to what discovery requires and <bcp14>SHOULD</bcp14> place sensitive information --
detailed capabilities, policy, internal topology, operational state --
behind access-controlled references.</t>
      <t>A Stable Identifier lets any observer correlate an entity across results,
protocols, and time. Where an entity acts for an individual, its names,
identifiers, and Provenance can be personal data; publishers that do not
need correlation can omit a Stable Identifier. A Scope Hint is not access
control.</t>
      <t>Published information, including data never returned to clients, is
disclosed to every serving system that holds it, and views for different
audiences stay separate only as far as that system keeps them apart. A key
used to sign published MDI instances can be tracked like an identifier
(<xref section="7" sectionFormat="comma" target="RFC9665"/>): a key unique to an entity correlates that entity
as a Stable Identifier does, and a key shared by a publisher links the
entities it publishes.</t>
      <t>Results obtained under an audience restriction carry no marker of it; a
cache, intermediary, or consumer that passes them outside that audience
discloses internal names, endpoints, and topology. A Discovery Proxy makes
advertisements visible to whoever can query it, and the domain a result
appears under can reveal where a device, and a person it acts for, is
(<xref section="9.2" sectionFormat="comma" target="RFC8766"/>).</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>Future revisions or binding documents may request registries for selected
MDI value spaces, such as entity types or protocol identifiers; existing
registries are to be reused where applicable.</t>
    </section>
    <section anchor="open-issues">
      <name>Open Issues</name>
      <t>Input from the working group is sought on the following questions:</t>
      <ul spacing="normal">
        <li>
          <t>Is the procedure of <xref target="minimality"/> an acceptable basis for deciding what
belongs in the minimum public discovery information? Are the results of
<xref target="derivation"/> right, including the conditions under which an entity
type, a display name, an authentication hint, or a Stable Identifier is
needed, and is
the information that <xref target="tab-derivation"/> places beyond the minimum
correctly left out of MDI? If so, should this document keep naming that
information for bindings (<xref target="beyond"/>), or leave it to bindings and
profiles?</t>
        </li>
        <li>
          <t>Should MDI be defined only by what a client obtains, or also at
publication? This document proposes both points, with Status defined for
the instance a consumer obtains and a publisher's obligations derived
from it per binding (<xref target="flow"/>); an alternative is to set Status
separately for published MDI instances.</t>
        </li>
        <li>
          <t>Which items of the MVD should DAWN specify for each deployment context?
Is requester context, such as the audience that "available to employees"
or "for all its customers/members" implies, part of the MVD, and if so
who supplies it, or is it access control outside discovery? Is
information restricted to such an audience public in the charter's
sense?</t>
        </li>
        <li>
          <t>How should the charter's examples "type" and "services" be read? This
document makes Entity Type conditional and usually implied by the carrier
or the Endpoint purpose, covers services by the protocols of Endpoints
and by Entity Type, and places coarse labels (Capability Summary) beyond
the minimum (<xref target="services"/>); is that right?</t>
        </li>
        <li>
          <t>Where an agent's advertisement or registration is not authenticated to
its operator, as with multicast DNS, a Discovery Proxy relaying it, or
SRP, how is the charter's requirement for integrity of the information
exchanged met: by authenticating the agent at the follow-up connection,
by that together with protection of the hop that delivers the
information, such as a Discovery Proxy's DNSSEC signature, or only by
protecting the advertisement to its origin, for example with
authenticated DNS Update (<xref section="9.1" sectionFormat="comma" target="RFC8766"/>), which places a
requirement on registration (<xref target="flow"/>)? See <xref target="derivation"/>.</t>
        </li>
      </ul>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="I-D.farrel-dawn-terminology">
          <front>
            <title>Terminology for the Discovery of Agents With Names (DAWN)</title>
            <author fullname="Adrian Farrel" initials="A." surname="Farrel">
              <organization>Old Dog Consulting</organization>
            </author>
            <author fullname="Kehan Yao" initials="K." surname="Yao">
              <organization>China Mobile</organization>
            </author>
            <author fullname="Roland Schott" initials="R." surname="Schott">
              <organization>Deutsche Telekom</organization>
            </author>
            <author fullname="Nic Williams" initials="N." surname="Williams">
              <organization>Infoblox</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   The proliferation of distributed Artificial Intelligence (AI) systems
   and agents has created a need for interoperable mechanisms for
   components of AI systems to discover each other.

   This document defines terminology for Discovery of Agents With Names
   (DAWN), focusing on the terms necessary to describe the discovery of
   information about AI systems and resources (e.g., AI agents).  The
   intention is that this common set of terms can be used by other
   documents related to DAWN and so achieve consistency of meaning
   across the space.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-farrel-dawn-terminology-07"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="DAWN-CHARTER" target="https://datatracker.ietf.org/doc/charter-ietf-dawn/">
          <front>
            <title>Discovery of Agents With Names (dawn) Working Group Charter</title>
            <author>
              <organization>IETF</organization>
            </author>
            <date year="2026" month="October"/>
          </front>
        </reference>
        <reference anchor="I-D.king-dawn-requirements">
          <front>
            <title>Requirements for the Discovery of Agents With Names (DAWN)</title>
            <author fullname="Daniel King" initials="D." surname="King">
              <organization>Old Dog Consulting</organization>
            </author>
            <author fullname="Adrian Farrel" initials="A." surname="Farrel">
              <organization>Old Dog Consulting</organization>
            </author>
            <date day="19" month="October" year="2026"/>
            <abstract>
              <t>   The proliferation of distributed systems, Artificial Intelligence
   (AI) agents, and network services has created a need for
   interoperable mechanisms to discover entities across administrative
   and network boundaries.  Entities may include AI agents, software
   services, and other named resources that need to be found and
   characterised before interaction can begin.

   This document defines the requirements for Discovery of Agents With
   Names (DAWN) and sets out the objectives that a discovery mechanism
   for such entities must satisfy.  It describes what information must
   be discoverable, what properties a discovery mechanism needs to
   support, and what constraints apply to discovery in decentralised
   environments.

   This document does not specify any particular discovery protocol or
   solution.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-king-dawn-requirements-02"/>
        </reference>
        <reference anchor="I-D.kay-dawn-use-cases">
          <front>
            <title>Use Cases and Applicability for Discovery of Agents With Names</title>
            <author fullname="Daniel King" initials="D." surname="King">
              <organization>Lancaster University</organization>
            </author>
            <author fullname="Kehan Yao" initials="K." surname="Yao">
              <organization>China Mobile</organization>
            </author>
            <author fullname="Ken Adler" initials="K." surname="Adler">
              <organization>Indeed</organization>
            </author>
            <author fullname="Rajiv Ramdhany" initials="R." surname="Ramdhany">
              <organization>BBC</organization>
            </author>
            <author fullname="Loránd Jakab" initials="L." surname="Jakab">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Linda Dunbar" initials="L." surname="Dunbar">
              <organization>Futurewei</organization>
            </author>
            <date day="16" month="November" year="2026"/>
            <abstract>
              <t>   This document describes use cases and applicability for Discovery of
   Agents With Names (DAWN).  It illustrates how clients discover AI
   resources and obtain the minimum information needed for subsequent
   interaction within a local network, within an organisation, or
   between cooperating organisations with trust relationships.

   This document does not define a discovery protocol, a registration
   procedure, a selection algorithm, or an agent-to-agent communication
   protocol.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-kay-dawn-use-cases-02"/>
        </reference>
        <reference anchor="I-D.akhavain-moussa-dawn-problem-statement">
          <front>
            <title>Problem Statement for the Discovery of Agents, Workloads, and Named Entities (DAWN)</title>
            <author fullname="Arashmid Akhavain" initials="A." surname="Akhavain">
              <organization>Huawei Technologies Canada</organization>
            </author>
            <author fullname="Hesham Moussa" initials="H." surname="Moussa">
              <organization>Huawei Technologies Canada</organization>
            </author>
            <author fullname="Daniel King" initials="D." surname="King">
              <organization>Old Dog Consulting</organization>
            </author>
            <date day="19" month="July" year="2026"/>
            <abstract>
              <t>   Interacting entities such as agents, tasks, users, workloads, data,
   compute, etc., in AI ecosystem/network are proliferating, yet there
   is no standardised way to discover what entities exist, what
   attributes such as skills, capabilities, physical characteristics,
   etc., they posses, what services they offer, or how to reach them
   across organisational boundaries.

   Discovery today relies on proprietary directories or manual
   configuration, creating fragmented ecosystems that prevent cross-
   domain collaboration.

   This document describes the problem space that motivates Discovery of
   Agents, Workloads, and Named Entities (DAWN).  It clarifies the scope
   of work within entity ecosystems, identifies why current approaches
   are insufficient, and outlines the challenges a standardised
   discovery mechanism must address.  It does not propose a specific
   solution or protocol.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-akhavain-moussa-dawn-problem-statement-05"/>
        </reference>
        <reference anchor="I-D.moussa-dawn-gap-analysis">
          <front>
            <title>Gap Analysis and Applicability Statement for Discovery Protocols of Agents, Workloads, and Named Entities (DAWN)</title>
            <author fullname="Hesham Moussa" initials="H." surname="Moussa">
              <organization>Huawei Technologies Canada</organization>
            </author>
            <author fullname="Arashmid Akhavain" initials="A." surname="Akhavain">
              <organization>Huawei Technologies Canada</organization>
            </author>
            <date day="12" month="June" year="2026"/>
            <abstract>
              <t>   This Internet-Draft provides a gap analysis and applicability
   statement that maps existing Discovery Mechanisms and protocols to
   the DAWN problem statement and discovery requirements.  The analysis
   evaluates security, privacy, applicability, flexibility, and
   suitability of existing standardized, non-standardized, and proposed
   discovery solutions and protocols to the DAWN problem statement and
   REQ-DISC corpus.  It identifies high priority gaps, proposes
   mitigations and hybrid patterns, and serves as reference for future
   prototyping and development.  The intention is for this draft to
   evolve as new solutions come to existence.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-moussa-dawn-gap-analysis-01"/>
        </reference>
        <reference anchor="I-D.mozleywilliams-dawn-dnsaid">
          <front>
            <title>DNS for AI Discovery</title>
            <author fullname="Jim Mozley" initials="J." surname="Mozley">
              <organization>Infoblox, Inc.</organization>
            </author>
            <author fullname="Nic Williams" initials="N." surname="Williams">
              <organization>Infoblox, Inc.</organization>
            </author>
            <author fullname="Behcet Sarikaya" initials="B." surname="Sarikaya">
              <organization>Unaffiliated</organization>
            </author>
            <author fullname="Roland Schott" initials="R." surname="Schott">
              <organization>Deutsche Telekom</organization>
            </author>
            <author fullname="Jeffrey Damick" initials="J." surname="Damick">
              <organization>Amazon</organization>
            </author>
            <author fullname="Scott Courtney" initials="S." surname="Courtney">
              <organization>GoDaddy</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This document specifies DNS for AI Discovery (DNS-AID), a method for
   publishing AI agents in the Domain Name System (DNS) so that other
   agents can discover them.  It defines three discovery use cases,
   ordered by increasing latency and computational cost.  In the known-
   agent case, the requestor knows both the agent and its domain, and a
   single DNS query returns connectivity information and key metadata.
   In the known-organization case, the requestor knows the domain but
   not which agent provides a required capability, and queries a well-
   known organizational index to get connectivity information to enable
   a capability search of a catalog, agent registry or database.  In the
   known-capability case, the requestor knows only the required
   capability and must rely on an external directory or search service.
   This document addresses the known-agent and known-organization cases.
   The known-capability case is out of scope, but search and cataloging
   services can be built from the organizational index defined here.
   Once a client has learned an organization’s agents, later
   interactions can use the known-agent case, relying on a minimal,
   cacheable record set that each organization controls.  DNS-AID uses
   Service Binding (SVCB) records, optionally with DNS-Based Service
   Discovery (DNS-SD) labels, DNSSEC, and DANE TLSA records.  This gives
   agents direct connections that no third party mediates and works the
   same way on public and private networks.  No new resource record
   types, opcodes, or response codes are introduced.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-mozleywilliams-dawn-dnsaid-00"/>
        </reference>
        <reference anchor="I-D.jakab-dawn-agent-discovery-mdns">
          <front>
            <title>Zero-Configuration Agent Discovery</title>
            <author fullname="Loránd Jakab" initials="L." surname="Jakab">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Frank Brockners" initials="F." surname="Brockners">
              <organization>Cisco Systems</organization>
            </author>
            <date day="28" month="October" year="2026"/>
            <abstract>
              <t>   Protocols for communication between autonomous software agents
   typically discover agents through documents retrieved over HTTPS from
   a well-known URI.  This model requires a discovering party to already
   know an agent's host name or URL, or to consult a centralized
   catalog.  It provides no zero-configuration mechanism for enumerating
   agents that are present on a local network.

   This document describes how existing, widely deployed protocols,
   Multicast DNS (mDNS) and DNS-Based Service Discovery (DNS-SD), can be
   used to advertise and discover agents on a local link, with no new
   protocol machinery.  It presents a general, protocol-independent two-
   stage discovery model in which lightweight enumeration over DNS-SD is
   followed by obtaining full agent metadata over the agent's native
   transport, whether by retrieving a description document or by
   connecting to the agent and performing its native handshake.  The
   DNS-SD records carry a small set of discovery parameters that is
   shared with agent discovery in unicast DNS.  The document gives
   worked instantiations of that model for the Agent2Agent (A2A)
   protocol and the Model Context Protocol (MCP).

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-jakab-dawn-agent-discovery-mdns-01"/>
        </reference>
        <reference anchor="I-D.blwm-dawn-common-discovery-parameters">
          <front>
            <title>Common Agent DNS Discovery Parameters</title>
            <author fullname="Frank Brockners" initials="F." surname="Brockners">
              <organization>Cisco</organization>
            </author>
            <author fullname="Loránd Jakab" initials="L." surname="Jakab">
              <organization>Cisco</organization>
            </author>
            <author fullname="Nic Williams" initials="N." surname="Williams">
              <organization>Infoblox, Inc.</organization>
            </author>
            <author fullname="Jim Mozley" initials="J." surname="Mozley">
              <organization>Infoblox</organization>
            </author>
            <date day="27" month="October" year="2026"/>
            <abstract>
              <t>   This document defines parameters for AI agents that would be used in
   DNS and mDNS discovery processes.  It provides a set of common
   parameters for different DNS records to facilitate agents
   communicating over application layer protocols such as A2A or MCP.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-blwm-dawn-common-discovery-parameters-00"/>
        </reference>
        <reference anchor="I-D.zhang-dawn-bgp-style-federated-discovery">
          <front>
            <title>Federated Agent Metadata Synchronization Protocol (FAMS-P)</title>
            <author fullname="Bin Zhang" initials="B." surname="Zhang">
              <organization>Pengcheng Laboratory</organization>
            </author>
            <date day="14" month="October" year="2026"/>
            <abstract>
              <t>   This document specifies the Federated Agent Metadata Synchronization
   Protocol (FAMS-P), a normative protocol realization of the "BGP-like
   structured peering" federation mode (Mode B) defined in the two-layer
   DAWN discovery architecture (draft-zhang-dawn-agent-discovery-
   framework).  FAMS-P is a peer-to-peer unicast protocol for
   synchronizing agent discovery metadata between Federation Gateways
   (FGWs) across administrative domains, in deployments where the
   preferred DNS delegation model does not meet operational
   requirements, such as closed trusted federations of approximately 2
   to 200 sites.

   FAMS-P runs over mutually-authenticated TLS 1.3 sessions between
   peering gateways.  It supports initial full metadata synchronization
   and incremental updates for agent online, offline, and change events.
   Each gateway maintains a local Federated Agent Directory (FAD).  The
   protocol synchronizes only lightweight Federation Metadata Records
   (FMRs) — a concrete binding of the DAWN Minimum Discoverable
   Information (MDI) — and thus transfers only the minimum public
   discovery information permitted by the DAWN charter; richer
   capability retrieval is out of scope.

   The protocol defines complete message formats, a session state
   machine with connection collision resolution, timestamp-and-replay-
   protected conflict resolution, mandatory FMR origin signatures, time-
   to-live aging with bounded refresh jitter, and fine-grained per-peer
   export policy enforcement.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-zhang-dawn-bgp-style-federated-discovery-00"/>
        </reference>
        <reference anchor="I-D.zhang-dawn-agent-discovery-framework">
          <front>
            <title>A Framework for Agent Discovery in DAWN</title>
            <author fullname="Bin Zhang" initials="B." surname="Zhang">
              <organization>Pengcheng Laboratory</organization>
            </author>
            <author fullname="Linda Dunbar" initials="L." surname="Dunbar">
              <organization>Futurewei</organization>
            </author>
            <author fullname="Yixuan Yang" initials="Y." surname="Yang">
              <organization>Sun Yat-sen University</organization>
            </author>
            <date day="20" month="October" year="2026"/>
            <abstract>
              <t>   This document describes a two-layer reference architecture for
   discovering the minimum public information needed to reach AI agents.
   The Local Discovery Plane obtains discovery information within an
   administrative domain through mDNS/DNS-SD or infrastructure-assisted
   discovery.  For cross-domain discovery, the Federation Plane uses
   publication of policy-approved information in authoritative DNS zones
   and on-demand resolution as its baseline; Federation Gateways apply
   export policy and validate and cache accepted results.  The document
   also identifies optional functions that may complement this baseline
   where DNS publication and request-driven resolution do not meet
   deployment needs: recipient-specific sharing, proactive or multi-hop
   dissemination, and trusted aggregated directory queries.  In mixed-
   mode deployments, DNS may bootstrap an endpoint that provides one of
   these additional functions.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-zhang-dawn-agent-discovery-framework-09"/>
        </reference>
        <reference anchor="I-D.dunbar-dawn-infra-assisted-discovery">
          <front>
            <title>Infrastructure-Assisted Discovery for AI Agents</title>
            <author fullname="Linda Dunbar" initials="L." surname="Dunbar">
              <organization>Futurewei</organization>
            </author>
            <author fullname="Bin Zhang" initials="B." surname="Zhang">
              <organization>Pengcheng Lab</organization>
            </author>
            <date day="31" month="October" year="2026"/>
            <abstract>
              <t>   This document describes an infrastructure-assisted approach
   to the initial discovery of AI agents in managed enterprise,
   cloud, edge-computing, and communication-network
   environments. The approach treats infrastructure-provided
   resource state and requester context as possible inputs to
   the Minimum Viable Dataset (MVD) used by a discovery
   mechanism. These inputs can help keep minimum public
   discovery information current and can help determine the
   appropriate discovery scope or entry point without requiring
   the requester to understand deployment-specific network
   details. The document does not define registration, catalog
   search, semantic matchmaking, resource ranking, or selection,
   and does not define a new discovery wire protocol.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-dunbar-dawn-infra-assisted-discovery-03"/>
        </reference>
        <reference anchor="RFC3444">
          <front>
            <title>On the Difference between Information Models and Data Models</title>
            <author fullname="A. Pras" initials="A." surname="Pras"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <date month="January" year="2003"/>
            <abstract>
              <t>There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management. This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models. This memo documents the main results of the 8th workshop of the Network Management Research Group (NMRG) of the Internet Research Task Force (IRTF) hosted by the University of Texas at Austin. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3444"/>
          <seriesInfo name="DOI" value="10.17487/RFC3444"/>
        </reference>
        <reference anchor="RFC7301">
          <front>
            <title>Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension</title>
            <author fullname="S. Friedl" initials="S." surname="Friedl"/>
            <author fullname="A. Popov" initials="A." surname="Popov"/>
            <author fullname="A. Langley" initials="A." surname="Langley"/>
            <author fullname="E. Stephan" initials="E." surname="Stephan"/>
            <date month="July" year="2014"/>
            <abstract>
              <t>This document describes a Transport Layer Security (TLS) extension for application-layer protocol negotiation within the TLS handshake. For instances in which multiple application protocols are supported on the same TCP or UDP port, this extension allows the application layer to negotiate which protocol will be used within the TLS connection.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7301"/>
          <seriesInfo name="DOI" value="10.17487/RFC7301"/>
        </reference>
        <reference anchor="RFC8766">
          <front>
            <title>Discovery Proxy for Multicast DNS-Based Service Discovery</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>This document specifies a network proxy that uses Multicast DNS to automatically populate the wide-area unicast Domain Name System namespace with records describing devices and services found on the local link.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8766"/>
          <seriesInfo name="DOI" value="10.17487/RFC8766"/>
        </reference>
        <reference anchor="RFC9460">
          <front>
            <title>Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)</title>
            <author fullname="B. Schwartz" initials="B." surname="Schwartz"/>
            <author fullname="M. Bishop" initials="M." surname="Bishop"/>
            <author fullname="E. Nygren" initials="E." surname="Nygren"/>
            <date month="November" year="2023"/>
            <abstract>
              <t>This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9460"/>
          <seriesInfo name="DOI" value="10.17487/RFC9460"/>
        </reference>
        <reference anchor="RFC9665">
          <front>
            <title>Service Registration Protocol for DNS-Based Service Discovery</title>
            <author fullname="T. Lemon" initials="T." surname="Lemon"/>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <date month="June" year="2025"/>
            <abstract>
              <t>The Service Registration Protocol (SRP) for DNS-based Service Discovery (DNS-SD) uses the standard DNS Update mechanism to enable DNS-SD using only unicast packets. This makes it possible to deploy DNS-SD without multicast, which greatly improves scalability and improves performance on networks where multicast service is not an optimal choice, particularly IEEE 802.11 (Wi-Fi) and IEEE 802.15.4 networks. DNS-SD Service registration uses public keys and SIG(0) to allow services to defend their registrations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9665"/>
          <seriesInfo name="DOI" value="10.17487/RFC9665"/>
        </reference>
      </references>
    </references>
    

<section anchor="example">
      <name>Illustrative JSON Example</name>
      <artwork><![CDATA[
{
  "name": "invoice-bot",
  "entity_type": "agent",
  "endpoint": [
    { "locator_type": "uri",
      "locator": "https://example.com/.well-known/agent-card.json",
      "protocols": [ "a2a" ],
      "purpose": "description" },
    { "locator_type": "uri",
      "locator": "https://example.com/agent",
      "protocols": [ "a2a" ],
      "purpose": "interaction" }
  ],
  "freshness": { "valid_until": "2026-09-01T00:00:00Z" },
  "display_name": "Invoice assistant",
  "stable_identifier": "urn:example:agent:invoice-bot",
  "extension": [
    { "name": "capability-summary", "value": [ "invoicing" ] }
  ]
}
]]></artwork>
    </section>
    <section anchor="mapping-notes">
      <name>Mapping Notes</name>
      <t>The table sketches where the mandatory elements of MDI, Entity Type, the
Stable Identifier, the description Endpoint, and Freshness surface in the DNS and
DNS-SD parameters proposed in <xref target="I-D.blwm-dawn-common-discovery-parameters"/>
for SVCB records (<xref target="RFC9460"/>) and DNS-SD TXT records, as used by
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/>, and in the generic well-known-JSON
and agent-card patterns (no single specification is implied). Field names
are indicative; full mappings belong to binding documents.</t>
      <table>
        <thead>
          <tr>
            <th align="left">MDI element</th>
            <th align="left">DNS and DNS-SD</th>
            <th align="left">Well-known JSON</th>
            <th align="left">Agent Card</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Name</td>
            <td align="left">instance or owner name</td>
            <td align="left">(document URL)</td>
            <td align="left">(card URL)</td>
          </tr>
          <tr>
            <td align="left">Stable Identifier</td>
            <td align="left">none; shared desc-ref suggests one agent</td>
            <td align="left">identity</td>
            <td align="left">agent_id</td>
          </tr>
          <tr>
            <td align="left">Entity Type</td>
            <td align="left">(service type or name)</td>
            <td align="left">(metadata)</td>
            <td align="left">(metadata)</td>
          </tr>
          <tr>
            <td align="left">Endpoint locator</td>
            <td align="left">SRV/SVCB target and port, plus path or well-known</td>
            <td align="left">endpoints</td>
            <td align="left">endpoint.url</td>
          </tr>
          <tr>
            <td align="left">Endpoint protocols</td>
            <td align="left">proto</td>
            <td align="left">(in endpoints)</td>
            <td align="left">endpoint.protocol</td>
          </tr>
          <tr>
            <td align="left">Endpoint purpose</td>
            <td align="left">implied by proto, or by the <tt>_index</tt> label</td>
            <td align="left">(interaction)</td>
            <td align="left">(interaction)</td>
          </tr>
          <tr>
            <td align="left">Description Endpoint</td>
            <td align="left">desc-ref</td>
            <td align="left">descriptor URI</td>
            <td align="left">(the card itself)</td>
          </tr>
          <tr>
            <td align="left">Freshness</td>
            <td align="left">DNS TTL; desc-ref-digest as change signal</td>
            <td align="left">version</td>
            <td align="left">version</td>
          </tr>
        </tbody>
      </table>
      <t>In the DNS and DNS-SD column, proto carries the agent protocol; the alpn
parameter carries the protocol negotiated on the TLS or QUIC connection and
corresponds to no MDI element. <xref target="I-D.mozleywilliams-dawn-dnsaid"/> uses the
two parameters in the same way.</t>
      <t>Each record carries one proto value, so a resource that offers several
protocols appears in several records: in DNS-SD each has its own instance
name, while unicast SVCB records share one owner name. Each record supplies
the Endpoint for its protocol, and a desc-ref supplies an Endpoint for
description retrieval, whose description can be hosted elsewhere.
<xref target="I-D.blwm-dawn-common-discovery-parameters"/> and
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/> infer from a shared desc-ref that
records belong to one agent; <xref target="I-D.blwm-dawn-common-discovery-parameters"/>
states that desc-ref is neither a universal identifier nor authenticated.
The desc-ref-digest parameter is defined as a freshness signal, not a
security signal, and maps to Freshness; it is not the digest of the
description Endpoint (rule 4 of <xref target="constraints"/>).</t>
      <t>The locator is assembled from the SRV or SVCB target and port plus the path
or well-known parameter or, absent both, the protocol's default location
(for A2A, /.well-known/agent-card.json). Whether the advertised location
serves description retrieval or interaction follows from the protocol: for
A2A it serves the agent card, from which interaction URLs are taken, while
for MCP it is the interaction endpoint
<xref target="I-D.jakab-dawn-agent-discovery-mdns"/>.</t>
      <t>The individual drafts <xref target="I-D.zhang-dawn-bgp-style-federated-discovery"/> and
<xref target="I-D.zhang-dawn-agent-discovery-framework"/> define a TLV binding of MDI
elements for exchange between gateways, including an Entity-Identifier and a
Capability-Summary. In <xref target="I-D.zhang-dawn-bgp-style-federated-discovery"/>,
the Entity-Identifier, which together with the Origin-GW-ID keys a record,
can serve as the Name and corresponds to the Stable Identifier; the
Capability-Card-URI is an Endpoint for description retrieval; and the
Capability-Summary, Trust-Reference, and Provenance TLVs correspond to the
information of the same names beyond the minimum (<xref target="beyond"/>). That draft
makes the Capability-Summary mandatory, while <xref target="tab-derivation"/> places
coarse capability labels beyond the minimum.</t>
    </section>
    <section numbered="false" anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>The authors thank Lori Jakab and Sumit Ahuja for their comments on using
discovery scenarios to clarify requirements, and Adrian Farrel and Linda
Dunbar for their discussion of discovery inputs and outputs. They also
thank Aleksandr Artamokhov and Siyu Deng for comments on protocol versions,
description changes, and Entity Type, and Riccardo Di Nuzzo for reviewing
the proposed procedure.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAD5f/moAA61965bbRnbufzwFDvXDUkLSksfxjLsn4/RI8lgZWdJIbftM
srI8aBLsxjQIMACoNi05z3Ke5TzZ2d++VO0C0S05OVrJuEkCdd21L9++1GKx
yIZqqMuTfPZt1VTb/TZ/tb+oq1X+pOpX7duyO+TPmk3bbYuhapuT/HX5n/uq
K7dlM/R50azzx+122zb5m3JbNEO16mdZcXHRlW8/ssVZtm5XTbGlEay7YjMs
VvtqsS5umsV2XS227bqsFw9/k62Kobxsu8NJXtG7WbXrTvKh2/fDZw8ffvnw
s+ym7a4vu3a/o26fnP3wYpZdlwf6cn2S5fkiX1vX/Km4xOj5z7Nno09d2bf7
blXKFxjYOqffq6HSr6o49pyHx99uy6FYF0OR9QMtyo9F3TY0owO9s6swhKFd
0cjo84w+9G03dOWmd98ctv6LYj9ctd2J9kdf/3WZP95X9DnPZa3+2jaX4au2
uyya6mfdofO+ai6v9kX+XVPRlPtqOPBTK/rjJP9jWf2dfpdvaPjU5aOHDx/+
7vOZfrVvBizz46uqKfgr2tiqPslpXw7U6b8M2vyyXO+Xq4Yf2XfVSX41DLuT
Tz+9ublZ6rPLphw+jZN4vMyf7N0cHl+VzeW+oIno1+k8/u2KmsDvq32TPy8u
2q4Y2u4j5vLlB+ey3v+4ss7/pd0PddteL1ftNo71z8v8r0XrBvvn8qpownfp
SLn9/Nv2oqrLD/R8KNprtPQvK/yy5Ve450aI6m2JXX+2eLLcFF1HtM9HYSi7
bdW0dXt5OMkCAcqzoPbF42/OXp8/fX3CXdmBjuet3eRnTOX5D9Vwlb+gGfX5
fTT9IP+BTg4tYv4nnB4acNFRb7KAQ9FdloPsbE9bCwIfumJ1XXbLqhw2S1qG
T+n4frqStxb4kkf8Kb8fyRj/Fli1k/zZ0/Ov+RtqjUb52cPPvlg8eqiTxkhk
yp3jM7Yk18VBftz35WJV9GX4pbi+Kt4WFTGNdt/3hTy169qLutwu6EgO3JA9
7R+6LHaLoinqQ1/18fefa+IeVV1XxbaX59ZNX1Rre+LvxXVxIT8w+1gEBkNs
qwkNXdQ3W3lqxVzSPbYrOtoFWrTw8M9EFjr5i8sdjfpQl4tNuS6J7st1fHXi
+fEYNmgbLNGeXe+bi6KTh4l+umJR9DTho3Zff/34N59//rn++dvfPHykf/7u
t198oX9++fkXD+3PL774p5NssSCWetGDMoYsO78qc6UH0N1AHz9EiCDhB/mN
EiKz8bzor/usGohx5v2uXFWbAze1VZGyE5ESBp+w5eGqGPIiX9UVdZW3FwNR
Rp/d0InPqUV7B+LLc/xlfka/N+vqbbXeF7WIo5yaw/BydwRJGNV1T71UfW4i
zqZYEMV58Zbf//bJswf5xX7IL+nA9tRefcjLn4rtrsanDc2xJ37RDDTUJb2Z
do/nZQkxBiXoPBA0BHDmT0qOoeXUO02fJVHRraufSYTZutEu7VfDvitP8xva
AeJ91EM5z+j17hKrH1dU5tDnXdVf52WxusrX5YaaoYcw5vamkVZprCb95hka
pef6VVftiFv3shfrNm/agRaXVrHdMUHnxapr+z7hpNQSjZxmSdKyrbML4qI0
ARK8S5AVrTbxmj3Pm57ZtXT+aZr054pEUVdqV2XH63yDD/SKDXHTtVusZEbT
25VGmUqo87zY7Yha+lwozv30CabQlSU1vKvbA/fO2/UT6Qz3i7xuaclzEnQg
3zlIys9ozioSmlu3JAAa9EuE2coiYCmJDwyHB/MMz4VZ4QUiy33Nj5S1U7fC
IaBeaRw4dRV+48lftfU6I6lCL9FzWzpEGNCRxkLfcDt92fS8FHSUc5x7IkCe
XV/RMvYZU7h/+6Kl3S141XH++quSt4soVpYOA+SfR0evGk7py7dFvad1pRER
NyzDjjiSoznvqPdyLj/qOst2cItZUXdlsT7kV0U/B7Hwcxc4tTTnbk9napmn
pMJT2O1tX7O4r0VHQngo+Tjkuv5MebTXdaWHWVa9yLdEIehDZCIOR1b+RBw0
PTPbkppvqn4LkgVf3FbrNSkF2T062kPXrunw0UJm2WOeDhgAHXwiHzqiND5r
KFl00nxo9F41nef9fsUbcfYsE/V1nl+U9EopZ4wYMcbFh5EJ4d07ryb88ovQ
pXROkrOk45ntOhKqbbOpLmk91tRbzf33V9UutrQkpYv7KZpD7ItGiW29KImF
UNOZbj+mBWrot+BKRJd70MRmYnbYYTfDEz2+Q1bRzPRv2lJM/aq9wVJ1zJGq
QWbCj5BI23ekLuKpaoMR0o8rorUd/UnETEeLyKioaHNoQe7QsX75RVgdae8f
yd+LPpFOk1OlIy6WxEEXhmahhwd/XpR8KtauI5kbps3sU8YE5pupwDjVeUyr
TTQN/dgr/z6mU+o503YxAZoMrV2zqvd8oGhR67LoZX9k7OCHhx0NTRhI97Za
ydlvNxviGXOWZ7w5Bem2mKxbgsgOoQ/tm2oli2gHTw8b7VZfrsiooLejnsSr
JufECE/o0oiAf1ijzZIIoqRuumxaQSCeABlKCgSxkPWBFPFqdZrJWn6cKklr
K1rAmpZ3NdQHEbpZInSDsKVnu+5QCVsOVJIcgwkuSJKdXm76U56djO421ZXG
01+XA1k1KhPfVr1I1AvSk2va38zkPVsadfWzCPJl/q3RwkIULahVonsoYTCz
2VRlTTQLvkdzqDqeUoVtuS8j+4BKTDxHF/ijlOJffnlwSiNtSjuJIE3Tk8gE
Imlc0v80WHmRqTKcpSigrC6ZFjpmfvmuLlalKnDJJqioKRtRXjHTVC0l6mf9
4cRrnn1eV1sSJEyBQfbh6JUiH6CliSgck8CdaixTVKKi5vdF7rD2OGc1TA7j
7Qdu+qDxgcns+D7gc1SBCkfqjH0/1mpoZBf0TFk22ViZgRYl4gLwTCJGSNxB
uGEBdOLPsNLUG4R2EM1g5NVlM7FBEOE3bSKeT1ILIzvzQn1V7PBfU6icnnxR
0rzWkXXQ769M77RjIOOe56ST9dUFCI3IkeY6oQrOI3Me6R/ZHgrdjKh3BinR
k0FMqhp1id1Ft6nhEm0nYS8poUyzs1Nwu04YOJZnW11ewcwBQ56PdFlAYoBM
LtFKAy3l27Jobq6qWlk6MRVQ9EWJ/dyQCUxknR43DJ5EBMTqwMtyQd+t/17g
2GQkxPoD2ZVb2pgnL94swH3WpDe2AzTVnTGL2y1sOvhkRZR1vbhuYGL865uX
L0j5aqoNHSbaDOYtOO3rXrYOpEJd0FYb/dvSi9TLmPdCC6mxLjReWRk0E4wD
MDeSZipQjp+ko6Lw5lxEKdsmLHHUFOr3bAEPMCOdASR6ubND+NztN0RezCVg
EoDF8prhuX0DBZfVDD54LcQYbdMHFRbRRfdQynslLGi9xBwD0fAOB5Xm+4p7
eUJ2G2Z+/9vvnzxQxZvVACIK1rACB6Z9Fj3L9Jgs6P7T+ouoL7wWF5BLapWB
y7TXZOOrfJMTkwWNPRggzPPpBTY7dm3Feq6cBGXYzdrZDPKJ2E1pyEFYhmX+
dVvX7Y3xX1kt0cXfvVPUA6vYFTe9sbZjw0n0E1i6+nku66MzzMbnuWretvVb
PkGOx9MZ2NBYQOnR5FO1dk2sZ02yekQ19Ir+ScvOL5rByvTlbOCR8Zrdaryi
TTaWeajSZrJdrPOp6ZmZvSxgf5zLFRErOPbHWKY5W6YZGySYEFaQ+yUd8y0b
usRVwJ2EnsSoY12dJEyzqEi9L6HokOHJzZaZ0AQwEiVWJnlod+2eTjAdm3v3
Uo/F8wKo72UpasJ1eWCOCAb93Zvz2Vz+m794yX+/fvqX7569fvoEf7/55uz5
8/BHpk+8+ebld8+fxL/im49ffvvt0xdP5GX6Nk++ymbfnv11Jis+e/nq/NnL
F2fPZ2KXe+O16NQ2EJWXTDSoGQUdFt0mJq0/Pn71f//Po89pof4XkfJnjx59
SaskH3736Lega2BfavMBf5KPtIKHjOioLDrmNWSjERethgJ0LbKKGBtECy3k
P/w7VuY/TvLfX6x2jz7/g36BCSdf2polX/KaHX9z9LIs4sRXE92E1Uy+H610
Ot6zvyafbd3dl7//Cqpyvnj0u6/+kMFqP3ew3wiD2htSA0ZsyjLvxwd4NdlI
wcIi5e61Knfz/Clz1XnQZqi18Vd4R7/LnkS+Pula81+/gdY6T83Ylxd/Jz1p
nj2OovMxydV5fs6a2zOxpdqOCWfOanFHRELdTVnF2ZFVfAq1lPk4yBjW+VZ0
ZCLnDZlcJPs7QxYYJJSFFV0wgF62rqziFKrmmA0DI6tumRt0OPLKB4rAiCCW
ywHsK0gt0oJeMQrJqmrF6Ovb8sDnanoh1ahQ450HC8kUWWUFo2ti14wriT1S
KeKcqbQn7cDr9h+gmtORJkfthFdn2+KAVS0SAFucl6IwCSIs+n5Aj2A10Wlv
wZML6D7AjvcdNI4RMMcCpu9nR7YUIOuUZxFvs3HNmBVD42VtN8HazwOmNzf0
JNV8oZpXIlKPif90zCfrvg3vJWMPGOuSCJT01HXFPrssnp6gQZxkJ/kPoqBM
ISWqrXgj7xS9Ye1Fx1SazXKBOtlaZvWO/rMFaGaOZCKoP7N2q8IYPT8b2wFi
RjrAMzcPRpAFvR8qdRt1Idvi1P3CXAAt9CXAz3ItOj8Ihb8dsAFraghaIFt5
kLK52YPcN/U5DAVeppVY5m+g9AHo4p+w0oatkz7pVB1YGnconliBs1/FRPMZ
bzN0MabeLXjWBUarWunalKFp2Is2Q7TsQeBEbK7hR7D7YP/nR4eaNm82mhVx
gqoB7rNiCmLCJmWzFFyUFkPJYkwUpTKJW/B06rySc8sHlUZEpN4ZpI7f3DDI
5rAnPunDcPKhuOaG2GQR+P1O1P3aE+VcmIYH12m6j7UbmyqfLbVyHFk2uV+X
OWCKCufz4Gkbb2G/yg6kT0scxgTNTakVSsuLtln8qaVDnr+7x/jLL2NhbDYK
WjdfpMFFgSAZQWIFVtRWQUESFVzIWJxI6wm1WwERUfSJHOCoCwvJq4ATk8BP
POB+inMKpA3dRsdPbGnhj/Q8/889/wd8s94H7IWm19CedUMK6BhIzmgx9o0W
F5Mm+iZbnF9sGbhno9Igs1Pu84ZUZHX5zSEoKojXiPb0dOC3BSQ6bXBPi6qH
BAKZxMaebV9aM+qRFk0RKoB43HhT3ngDfcVaBlMXtQcwjvdQ8C54R82vEsxo
NFOtVQCDqxs8M+cgA/zgP7ddGPuuJWuR2gT1h+nQKImJlf0QUDExn3r04wZa
/gR+cUn025SXLe22NNCXerqxMZeVzF0XCiafDAVhPYYaoF02YoCirJX9zsPv
JEOG1dW2ANBIbRaN/AHc5ScsBDaAX5FoF3WdMjoJQznAaEoc4ITUMEl+cxLr
l3EViFMeWiYQwfFXMB5tugloMMLvSUWgX0WxcUIbx1hQ1VZAB6Z6PsZPSkA0
pHOR1lvB651lT9XQWzTlHjqlWNNgKa8Yrw0G+Zw55bEDU7xNSsFrIBNbUA4d
+BVMJBYLNCQ12hGfIEBSKyovfXz8x5ev4dSbs17EQ8YZ6coV7EHoJ3AXEXlT
MwZ1nwpTk5XvaeJwrJeFobqqBtCkEyUch1HQ82Mxz1xzzEbEOzSaYtXcIesZ
C+BlSDh4ft+rAeL4NsnvhDukv+PKqgWwpHggTtbqJ2k9SINl/qKEQljwUEYQ
ZiceQnZqMicC9kpW5iDTKFXoYKHFsY8Bd0CxQVT0NiC3VcnLpQteKMde5q/x
DJ+Hpq/AcaKXhTd6xGZ6hljaTT/HPkLnZ85R9oEzRLQQZNKVcQBr2btyS2b2
Gp8YtmUnCw5OsKTVMQUhbMKSndysE4rvswIiqmfOOwBEUcORhhlSdH3pJ1AX
F4wxBR+T+POf/jRg8jCz3r2TNkUVCYreYqigldEAbQ2FjBSAq1PNMajIymI3
h2gszQ2Rys2lRmwaSNpizzjxDeBshY8FPgrLJ6olyFBOXd4Xm7LG8fia9uqK
pLXAaRwNQsdPec8WnLnDZsS4hw5fd9fsUoPbbp4hmKI+LPSjc+PJMIjPVeuR
LwTD3VRdPyxWNRmj6OFiP2TrkhSqmhFk2lg4Boq3Ffs36nYERfF669+y4veS
86yKQdS3v6aFIpWFtTRvcWxbhKikx0bs1w2ZR5jkZanwNqtu/AVjaH0W0Wv3
PikOryIuysq0Uym3UAMnvO7RIQ2PZ83qMFs3ns+IsSoGW2xSuVP0C6uFKZat
KOSA/zj8I+UQWCjxwBT1Jloq7GOC/1KlqbZFL4sl8DEhbNCqXukY14nvPWee
yJrz4CayTtRUXvAVG9HAZ0o22sA4whjXOLem63CwkjKRYIZU8FPDyyUWhVgh
wllh9r2BCd5cyg751SKF7gZQiUDjfbIuqtIM0ivEFCx51l9ZELAKAkvC7Pmg
XEFEQEFQm1K8e3XVXM+FmtLFSDdKgoGo+8uykZAt0zzxCHOM3lRroqbdnuTq
hnUrVf+EOVIDW5GsNhgiXo7744W2ld+w40+EEaJQaFlhG/A84sF51bU/HcJa
sV+T1BooydHtGGKneHTom9qxRz7WV23qNOZfrNdjEt4Evw8NkLHteCzfVuWN
WHnxu2K/rlimLamlMwFiiOsaELQfeo4C8UfskyNykxAyRxnU1iXty02hp49M
k269EFYeKKHShYb1XK6rghWU5+KAYbzcLDkyw8WZqsQ8bTiH0BW1mHWpBbTL
gw6xV/dE7+ABOfdq0UQMCls+l6AFNWU4kiIXheVUjZUYWcV7wh0cbLOH2J6p
PmbCQYtRLVfG9kkf4AwBMgRzfMIeTla25ayEDufRYUU9g7wbGMAcw6hKFQ6G
xIVhOl3X3sDuK+GAeO3ApXM1Qo3q+8gkzBtsCBEEAUBXD/sP7aUEteRC6amu
B4JNA+Gy7L/+67+yf1zEf/+YjzgfXmJkKs/9c/p09t5x/PdHv4d/f3ifj/+9
H/d767/3+fg4vM/ueHz87gf7rR2pC9YU3vXMbY533wcCzj8038AImVzl3TiK
39/+Mj1HDOXuMZtur9Flfr6eDfG7t63E+N/U/oZ3o04n/t2nzZp9ayfBBkd/
RIbEREm3muubb3MfAyi2guLHUYUAEb47ye9tqssFNCHJT/jn2YTm5IKP6cHZ
EcrjAmQVg78og7sYWPeQuodJJJSIPITykymv4IUVdcZh5Q5blOinDzvcXVzS
kWc8sMns7gi/sYfcqJXnZ4CzBqmodzkMOYlnkWD1D0QDIqZeYiISIDSN/wOu
WgxqpSVj1akZQDk79fG0YT3iHoZVGYUDy+KLIU+iIXiCs7gQKZdMQwBObtHe
evW3ZIFn9TbWGOQTGzW8tNdhqUui7UxRoacyb8MCiaDVov8s85fNrTokmMpB
40mwcrWGfrFCGkZqaP6xcoMIhoOofeu3MFh7cSpMu+sjxaFfDuXVbm9dpWxX
xiB71mHx2dbs1EG+HO2ooQkMb4TFIVs3i+3rQI7mKeNh7AFqXRLHjuGKfoSz
KXiSAuQRStFYI24i/rjty/otIr+KseSAfJ7WVuXtubACkbSWg0G20NvSTxtD
21Q/kQ7CbyWquDFGWrAOrEhiM1NJ7PQT5FaIiV/0TsVR15yOhDWiZf5UMmSY
e2qofAs1mRF75yFQEH6S5Yk/x4JC9XQ5BJsdZZlFyYZ4nCjl4WaKccnmwZSQ
p4QqspEtnL/sqstKQnJIr6JjvBceLK5fMvZpsDubGrCSmA5wUWaC6UafjYJS
PDo25hk9QrwG9FmFeEVvkjn/jOMJ84P0/TdPHyu8Rf/hUUG9On/+BvNp2TrT
LJQ+hDEDW0IEoAC7WaGQ2nh5o9oKULPgKEMGxjA0w//DUnHSqM7IK/Y6OzH5
1cBTDLuUNJASOrwF3Qj8OM80bYmBp3AcimF0CuCF6zkoZt8IprKOyy1Lmo3O
jZ2ZPjk0/TxxEk/aYpkE5SscEHYR5n/bawzW0QjTSBTN3MliDFyyHIhx94zP
RT5VfXDxhfimzOKbvE9MJwj3k/nPuHcz4qKfqm8jI8iU/yXMaYrnTFvIJnSI
S2T2Mg6DHg5DW0IcfWxy39QAx3aBHPNIjplXcJQgODEjy74hPr2bQj8kPHhi
8GywB3Od6BinKAvR4+yEgO3+3W7NKvKb16+OPR5FQCBEGdwUWEhsY+afjQbV
h7MvJMLLvy38c7OXmD2aBkLFh0l3pqpQnNAjLgn4UZ1XIsOk4Yxj9lYjmmQQ
CJ8odXYck1sMRt/r6A1WhSITxwrbY+YUKRJojv0FnaDf2H9mFOKGQwxtTaad
kv5snLpkKlXT5tMrCUBS/KGMRqoVz2MT0LcRN0UgOp875MRRmjDJqZfijFsH
FKlnEL/tBo9LQloItM28lkUXLfm17yUTj4NaysF3utuLyVqqQGW5TIMWNUwT
nYwD8uNz56C1kB1RjPX7qJ6IDJs8ClgNPtdic2te45h7eGuaGYmyQDlIa8+7
g0Zwwx4j1QsQuoK2qmafZohhTxQ6SZVcQwBClhemxAfh1CYofkc571iFiBt5
qvE0MTJzspA4nRoMR3nVOINl8bYMDJY92knCnFA76y7ZLsZTCWxu+2zh6/dH
MZwP1DMoxx4rxIE3zzShlrTXd/ec3pJmFUsircuhTbq6K6Uiu/8/SJfIY7oE
/AZ0KLE7E379iTBBKCeSDiJZDOJUYfUrU0eD5ryx/z4cRUsMhIKJ/+7hk0xD
N/b18FX+Xc95Jpl8ZqekqjaIf6Oem8Fb6n1UVWxRGZKd5zM9t5nzcUeXNvP7
ZIlmQAjiLgpRhCOBwynxZ5HV8CRYZ2vEmWYJxQ5poJ+LmrNuOMKeXfbElXiO
4SxuLKrKIMgsO2uCMEPwajBd4toD9xPVQE1SmGD07M7BghAgygAvg73SlauS
6U4CqiPs2dIStjjx2GOWCjR0GzcbyNKTatYDAAmOGuV2CqC1rHYwJ9L9s8RJ
bArD8PJyxmSgKlMLJtiwNzty9CsoXSz5EBzCwvm7188tR5JDIzGlzG9HvyuL
a/HbusTSz87w+rePX7n+c+1f0jERLphtKpGDXSnYsew2bWcJ3w4PwCNIelb5
KW9XZTGtA2n4DL2nfZYhKlHXiHP4ELG42ncdQ7gvGRz1zP6qrHem6jWCRffV
IBEQYj9ycKIfoVjlsJF7c9737Wa4KbA64kiTY9MSKzgdKe+smiBSRn0fbvtB
FYGbymyDW9cy8xDpJzTuR8Q+y9NMhHEveqM6askqCB0ZRd8UHHTfsof9siEr
KVrgsvnIkOgkVsUSTHRRRV6kgDpe3uzrWrgdx35olJPtGRnybTABMAfRykZn
Wl08cfE4v6EgI5OnVknUkg8gVI5O5/pFq4DUcKU8wCcYK6FwkHyILpDpnCWh
ZsRCVOyDvO1wa4Al6Ez9YQnXnwwGzQwjIBWtACOI6yXHE3QRSJo9z8DzkYai
OseuIobC9R+8+EkleYyl0LAUTu/iNWBxIWfCViOT1Ygp0ZYTpktwCa8/ftWo
5D4qz7Jc87BvGYwiddTEh/ZO2k6sCR93oS2BLDK3+6qdBmQCe6a+7nLXn2TZ
o2X+vNJMY1rcNVv8mt0Xg54jaBPwvFRTBzB9Z16+AkuI7JOM/gWRnakkn7kN
CoOI6u5xFs1xHYn++iSvEDkqe3mDTdiS2sO21Krd1+s01gYcDFI9bsNX+bMN
zsJc43NSYhdHmhglMgYa928mx+364Xd5dAkr1V9BzMxmK14/Y0eO2UJqWb6w
jc6crALytbqwBlbneYp6JHUi1MA9sqUjDiEjSQJtP1+Skshny82xCmnht3D5
uWj7tpbhB2qQVc5ALEckQk2XGDGATPAMUGr+6GSi0gzJQaGDrb4aeCHD7wyH
kKo51ID0ej2fR81gApn5S11jQiMGzAHa4ZF8poC15cwiAt7S/TPoepecP4/M
h7qeVodDwN/6NIANvMkBL88UPwt2WHxX+Mu7dwM86R6fQaSOoDPqfM5aooHL
EPzhAbLAsEPE2nGEzRmQVEvcexUy3d7dc72qo6hP4JJ+DH6q9L09JU6maS6N
ZIE983EOYHiXRI5wgJ66rM2Pw2JCd4ZNvtQ9nApZbUfwMtbJON/YhFFmLC/w
0ACEpcqjFXeBwL8pDjKLkIubOTqH5XGjMW8xrBdgeGhAvDSuJ8N6MgHxRRUP
uE/PsQUuhTxExI9XEaQxC/VO0nVkzgmlfObzROj4iowO0N2xH191X83XjqpW
0HeZr7CKdGo6JhlyEoIQA2m4ChGCwHz2+pIX8c0TTmJHcCnK83D8CX0fkljG
BaRC/NIHY04wyE1VC4eM1odCaflojzycdm6BdswYqtTOiMIUYYZibkSLxbJm
2bFbHulsrCSmtTbAOCerAvz6rU6izsotzmPJw4xR9lVnP0hiw6YrQrznTJOP
MEdI0BLBYLnYMYOPRklzVtQvEAceTb+5px1FeKiZ71+9mAenVV0WdJBVKwL3
j8QXLDOc/hMjFwnbcXEjWFiLR5JIKB+sAoVTakWxl0DtzgA5ISflm8evJBbV
VLMQ2VKs151AxyWCdjliUau3zfM3yh3/afkZ89Y8f30LSWHrhtLQ6xDkJXrD
TRsYps2RmnKxrRJfZguYOgyEK+uQiOb5jDmYN49BXG80W+21hz6tSEN+/83r
Vw+kKVSh45Ct/lcctuhrZhhQwmwqjr/d7vZ8VgABop7QlZGHQp8uTpyDmjj4
ns47wHNzQisBHpWT+3D5g6go0cAsrGp8uvUAByvjYw+xrW+lqQKylVWz9xq9
YMHC2kOm2p31y3790UdalDyCIpLih5BAaSz9at8PLXzzn24Rfd31s3lIyv81
9UYQQHhXxRFjEM72w3Q+6ZMjKOpsIlVSE/HKwleTUnbH4zlVEWbKDLceEnZ6
AatG3oNVEUulFWIfH0zDnrlVm1izPIRZWvihB5kFMssTat5zfObxOrB00+Cb
4LYe03Y8fXeStwz9V5UCmk/oKIy8bSTHSZNSjHGCD6ropHHSMdFyRoh+ZXNu
vFOcZ8Nkj/MRa4/w/piK9rcf+bHlj9L28vfS2R/+xujdMBLByKEcR0JJfSHe
X2roNMIYakV4HMJO9ie9ZWiYxJD6WrJfhiApnGpuvqj3MHsVttDr2UqN8vdJ
APt7GHdqrdIHBtTUF0MfX4t++T5DaFzy/9QMSnnyqXaaqL3CIZsaRTNwIQiG
ed7zEVSYwXJbhWZjfiQ99UIMvCNbAd0GqLlWiJqefxysWvSpKCl9/4o6rQ8n
8Pgq4D03/IbonTjI3V2dpZrkuB+DfTm2xEZ1PMVxeEDCTgQ2/tgpm6sJjxvl
7Rsh3fdRUhINjGh6nr+timQkd/cY8zXe529onhoijFkHkHHNuw2yJPm/KTkB
5UPzkHT6ww5P/rmC244IKCS130IzjyUaQg4FzW28HFOT+wErf809SEWN2B4N
hDSUXV0cpEWiepgXRS4IsEhaNlXp3c2GKImnqrpdiHTSd3+QmC7/Lm0xU0+K
El8JdcSNY0CR1GG0ncruQBwoG9VfFdeho6as5ITuQ0hEafgzo8bc85sjyHjq
XLLztC5kdi9w/rQTg3mwcP4htGzl/2hX1C1+cXAbklT10+0+l+32c3yfPy83
oV7PD3/itjWc6H3I5+gcbccYHw7q0Td/1lR7wSy0fBx7iTT7FeELIaiu6/WQ
qFZ82ZIkQM+Pb8nD4nVh8PU0Ac90ky8OcafYVJ+a6B+PMsC4y3NN2Rw473bu
UDOlK+3YtGyG4BWaCeoita4EL6aKHJNb+3xjketBOTCa9JMMPzoIgHV8CbJ4
n/9lX2qcngNUbu30TCw+Wdb3GnHJ/Jk9HfRjhHZNOLLUS/0U9OrXIWLZNXBL
v4g+TmEqi0F+Er8x1ehWdAjhyGpvqiSkrd5vSTmajchophgYx0TeAn2N4ueo
kfQQhDai75KLIiRudFEEZ8eTtrfTEpO6okHjZO8y5i1gyk9DBlbkHATRAeF9
M4hbSDIPeR+9spDJyiCVMkQs3IpfaASmegg8uwkolFYnkq2x/ThVhzkHkXIN
luDyyLzLQwvFIoft5USJQ6+wWJakKefzLJHmdXCDG43aiYeniaW81t72srZQ
vTqbMJychp0wcX2T3U+xXQ3OEh6TPB/Hce4EX3jk2EuFRbKXPukTNUj63ff7
UK6hPBKxQiGSNdBnAYfwUcWKZdymTkupGlK7mbkuXU6oi3oVNEG1CUUhTPct
nCP4Yl/RH3hFqYhoRAq9FJZ7KxUM7RAGVZ2r9Xn5L+mnEp2dHUlyqa0dnP9n
R95f5qG+DU+OZoW7qrFYahPjqdu3UX6UOuw/kYDFqArcKvsxMxX9z4Loz5Kh
TYt2H5xuPmUD/DJvOeV9af0G57IE6hv2k0CklvgJeEjzGRRiO4qBJ+7iKsgx
i/Ha4m3r60Msrk2f9CWWROeL+InxvVz4HgaFEoxK+tU2pNUPLgzXhVsc6dXI
G+ans/GZYeeVsEjTmmTZP6A3ZV5vgg7KPuxjUbBMDLnjTHPJDyjrXXYhJfJM
AITkM661KrUIsBwnH6vkzAUSFZ4i2dTu+CZRPXhFHy68JqCxSCELKYsynf10
5sn2BIsYJ6sZEtQUpt3ZNK48Y5fFhzCTfn95yfEP2h+pH6lPScvIiwKUBtAa
QRM7qYYF8kCt7koRMWTnVVVxkzWq3UniDbZRwv9iYdeqt3rCyL1WI8oy1B1V
ZGOqyDJVpL14jA4vzcBArPYy/47Rn2IsmTSifhHD8AMLpumQAr5Iw9dFL+1h
3Y6dhiEWngtyubjKyTRfTYLidJgUEuOUgVGvjdRHsNAjiTAP4p6ZTsqOTA1K
GkqTbvqA7Whc0yg2XXuVcJjNlEb6kXD0Mv9GItXc9QTRh+vSuDhoRu4fUD6U
jPcDtPAYRXvBbhgwff30L4tXr1++WjyK/t07ssuyu7PLRlGVyX0KhZYDkXEl
UMBcWLrEVx7XfL9/HGAFEfsg2yuxBkmfxmhKqH3UnU27T6p5s3sZ2qxnnd+y
x/PdPUlK45jCJL9Ly78khaRcrHHbxTyotNLXMnsGbdSSoIRcErbG6TqJL/3+
sX/9AReJ8iNubgFZJN9QbyZAWXpcnyVAnYCwQeLcd5ptgnLJoqoIexD4V1DW
4NWSCS0dSkRLpGU7aQjFXgWtVcqpLOOOOXS4lyWU2Qkan8/JkuBqeyLYvByE
q/ohlyPlkAkunbacXiU+sUfEE9YK+XRaro3PCGlQA3uDvj3764nHMOYBNnrB
kn+E73xTNRpFIToY7mEKWtgyqc6hGExR34DRHYU7xjFK/Y9cTQxEQTchw8Wv
lWBGcCVLFYJgypoIqIbQFngpohpFz9eZYyVPvWSbu9blay3WYkXgQyECziBS
rt6nrR8po9wPtslwJGgS0QZOjur8w9qSuuy8voRQeG2bPZ6LPErDwufXwGqf
M2NVZc9mO7bSJVQRmHw7OGIZE9uE/qUqlyMwMaVHZYNQ90DCWjWcalz0R8YQ
zW9FzNGV6LwaBhcCm+weJwk6Gt8vxd2omCuGWOqmuIStzR5ZccPr8UXFw8BL
AjO7Lsuds85y5kNc+ug0r5pYDroMwBR8qZnPuBQfuHZmpRKDg1sPvtmVScLl
USriGS2fHNzcJV65SzFQiEV+jxWgj2ovc/KQA3DCXVwuvxh8NCyZBOXhgpkY
DseV1DlFNHSkPnqtDBOykKFfHqAgwezgZQ11KH3dLR13j6MGhyGtKymBaqgb
i+Vyt1ZC18XHOr5rRo32P0+CQf0lTLzU2crVhDy+c+k0cCxDUyRjyPAUvfsp
K38izXhVwfDlE2iNIB2i55IzOr0R2hjLxIQBa1Y1LkeZCjIUSehyHv2hNoNb
7wrD3Yu5hEuIgCtwScrtsYm+7iYKJtOKQuWxOxV4W7gcnRKfFh/W3dBSvVrX
bZm/dARmN09kseiUq08mHJAri5oJGMleap2/CTfOvLsX4mR+we0BqL4Qv/lF
8yMc1w/AKx2//qrY4SYt6IttXw2gLLaPMi3DNftqxsNpdwKyaG000wDmKq/1
LVHG4KQNjxMPVTTQ1VEL1w1BaZJ3uaisPHgqTYgNHeZJDYkkjFa6bkg1WQJF
K2zE8A8ScYzEAFx7r9qgUtsdJUAWf8hV0hy1nqF2iIBJH/nv/qMH8lIADd4J
1th2C7Ww5RPqbqSVPiJWcP/RctngRgFR1r46fnZdwbL9Kv/l9nGgCRlK2Esa
C5JMad++mksq9gIMYKJ9/XVPy1J/BXOA21hAX5dO7z9cLuNUsXg8vQ+vj3tP
wbrFx6wv3rP5pEYED4pmJoDZPFxgGMdp70nCxcJ5zz5unGUo0vfOfK7MjKYW
X/vjgCwrnvfP9B6t4Gj/4x4mZVXicVC/xlM70670LRs0cGKcuW6YDaOPtVTX
gCTY9xH0mlBrJTDqkCTaHOs7JypLZAZRXtntXahppEBKLDIvYWbKJHSuroCV
WMP6dQjs0eqCrq3o6+ynoMRnCZYg5TVjJAXxeKQR4ZKePCKUYcXmkn4a9FAR
TzY2p1JqLPG0IincOuzSu3vGhH9BSIZ+n9DIexONiDtAEHj84XWI+z1n0f7I
vZVN87D3R3/c8jn90eI8Rv/ei+2FP97yfZ3xh9sCAGRsUYufbi2p8nhHa85+
jZZrsFrTEIZkScVKfW/FIz807NMjG9VHMpx7XvYeFqP8ocMPP9wejZCEI/iV
/lBrR44K2/3JA+xaG69wElcwdkdMeB2qJMbgmeeSHxrzHYEFscJpQhbW3JjI
wg124sy82w57DwaoAxKWrJYZKaeiWbF/gM1bKQ+gSrG4EGDpSCiV1aOGAZcu
o1Y24TY0XN04Ca4uu2A9MjsuJumczpKny94pJU13e6oMrmr0GoxMnYp6IRLn
rXCdZ1czTtCMcAo0y34wtI5tDBBcpmsbonCN4LVlTZ1PrWR1um3CFUtJ5dZb
4Cmk9eFmdQ0dZXkuuIzd4RH9e1oMLzpeNPzGLrQw+8Bi5QROBvTuQr2kWa19
a8EFcBUFQuQzKNAYV7HNL4qVxXRtOQ+2shtb2Te0qkK2RbpMWZ4U7lP3GXub
aC9hU3DwxYRsQmEpHwElNxrw/HV1rLzTC0nY9v4Hu59unMDInESwBatnbi6+
FBK/qzKnFeVE6adcmjwyrLRgihibmqrK6S9cYae3HIkJSOxUN1fvolC3orTA
X3ExsYprJX+oeoiT/jJ3A4WWqDyuhe34ro+yc04nXm4uBQ8fKNaV4wuCz1tr
Ufk06qh/n2pUjOofyYUmn/T57LaKAzOL5fXu8z4YP0Qxs+mSBLOpm1fyfJbi
tzNXCoBt6lErGnqaXDIJBArpR7255cwqmcoOnwfLnz5zGKRjljgGMZRVeI63
a8QfqGtmtiJpijGR4rJ1wKbClQKs+OUuJGB0XK0r/+71M8lB73tqXO760Hqg
doqkMLt/SQt5ppn0u3rPiCHphloJ2aGOulkRh0v3oHdVQ27JsT9VBDzWB9Pr
BsoQscCHX/Lgzp+zT/Ev3z177FxNSTp9nn9zfv7KDLd4Iphznz1/9UIyJ377
m4eP4Lmp+nyyrDS1o6max9PKu33jAhlYHXcjY4zbLVIUXxJTH8ZGz+uffVIe
wB2tgFrDZSfY63yK78C+CKxd/cxavEk7s+oTaZ3iKWe1FBAToe3PpgZguPsg
EETPJCGMIhIE2zyWLZ+UTT+xqOzjbH81G/IoBe6nQLxPLH8wj1U93H3f4V29
62KyEA2fe0FT4pcqUP15CIkguahtw5UvcsNnXo2oW/eE89k4VMiX43WxU66K
jngsJmqOojM0BlNWKwYNLTB/rk7AfpR4A6gPOohTGV10dqoR8Uds97aTHJLf
w+V7caFl0/zIobfIZQEm94J42IryfF+jF66GgXRK5la8hfEA/+np+YNoGYdF
imywCObwZkzBWFfOOkvLQz4NBZe4r3ju03Bd3eLel+uH0PxeTtI8ltgnjW/d
3lgiIWM+EgYVb7gVVYKr0MnrnNKkpTWDrq3EZWv6SZrFpOq0CNo46WK06nGN
VP0O7fqnpGodR8KEYJjCM2DHnQrN5OGCf/WE0vYx2m/MrAn+PHUYpB5frTnH
mkowKk1Hhs04Cmk6SRTAu+9/y/Lbb4CTsWjKiiviKmcaOX/mXCpFi4xFg44q
IInMVd7iw69c7N/ZMymprjCUjesDqh3r4IkGD17SVQW7IjlQNZQUKhqpFmI+
O9uJcb0ULa2T/3fDxswu0KgxTOt/EDcW6BfE6DXPadYqyojI1n5XCKBnTlQu
cYfUTMWd5s4z3MfCv3JxSIAc9GoCLoxztd8WiPPQC4nNtkqq0/AJGSdLyE2v
uZlWytealgxl7E4Zb0ZiNVbNOcxR84hgY4nRcMpKyJrj/8VSiUZd7x3T5myS
rGa9mhNwaIwnQT7g5tflnimr4Arv15qbHWVYwm7tblnGSWq5wQmun8M89XZJ
+CLKVR1jM3bUJ4sK3e8fTF7bcsNlRSyaO3PlvOcBTdUyQx7K5DKEaT+Gg+N+
H8lyX3UlK498KazcbJHcsEVC7bJaiUM1hYCEkJhmxrXtNEpLmA5R88GHkcrl
VkY5Xj7rSQDsdotJHR3ZhStuwiqQAkzR2peiXq5EUhgdF7GxaiODgBOhCzFq
dAKXdXvBa0u0+Z+p8SEhZpI0K3W4XgjN7oqoLxzjZtT2qFEUxrku1ZSd2x2M
yjhMcIXKq4ZKzeFxthPfbiBQDFTjjWmch0IEhb/faW58Qmu6s28h1kdg3UMs
MthxC/Nb4uFwA3z8NilxFO++HTRF+k64js+rxTqIqhjGHRIZiloO94ov2VT0
PLAYyU6xZ7uSjlnXrvfsTm7o4HPmD9/2GConCj7vHQUux8LusXx3T8cF/+pR
GZRNCMa4LfNi8FpD4k7xORkam9y3TlVxmRinx2F82f+oSHxNxHZTkR1jYA5X
RX3lKzzGlcAVEs4NPFvS7hyHnWS3hJ3oJZZHhZhcRIxWX+009ZXLDXOR3nFQ
TLB9oh6m0RCoLuU0/zf77bboOGVdMr3mJpSioHOmxFBc2mUuyeVadDgG4cGK
37AWwtrpQRQ/pHTvN0T/vPUcsBlrKvr7BGHEpJcWtv4ewUkZj9YPpZWIxQDG
sU6ZJJUFbi/sOGX+qtlW8abnifrWc39vGg82Xp04j7cNVhsOm6ahI9RFLj8h
qnlbNnYz6g9XviirQFeTZYkKgL1RcM1jzHAW7saoLuooV9TGWSx8MwvSaDQk
RMYg3NI4JViPIfgkvRiQNQlMXKbdFcR7xZCR27KclSyiJgad/33fVf26Crdg
gCFXNEQmIVMQmVGtVpLiAhbEtsQOLGN1kC17aUA+HZQwFrsYLomYhzemJLZ3
lfNlZlpqMdld3KYnKo9rlQ+16Jukn2vQiMXMvrsXKCituCr1mGf260zzYMCi
QlGkYysAByNlTh9gPVa+KvAWdhbzVVwZ12UO0b2o6MxpX7PTmAUb4JZ403XV
j8qxWg310BLzjRArZ6abxX13ethiwWlbLIuu4mjc8wnQr4j6hAx1Gj7VPLcE
htDrpYKlrpBj2S2CfWoOkP0FBLArziAKoNU/sB5nPxafFcsf6fFQv+DHYbWb
zcPtj32KaX5s3DpN/ixO1G5AU+2ouANPSg1OGPHR5CzG8Lm4S1g+sC6d4pmy
VsFattIthzurM0+CYhwiz4dNU36DF8DtplToVc3wWLDYLSTV1H2PE3mTRwWj
ZOl/BnwhS39xuVv0w6EuFxvSxUGFyZV3WpWUV1iGnYVob6tw/utMHin9nAUp
yFbVfnxHquSutUFHCPdXDiTbIK/Z/GEzQkxvq3+IgPAR/S7Z5OTUBIi9i31d
aM4j42ayGYz+muDjI6sZRfLzXslfigJL/IZAA2IfXXi5/oHoFVfFJzDByftt
fwiR2pyiI/Vb6WfHK/FDdXk13Jm9xYzYal8/jvgS8WSPNo2hJqnJydGtvnAq
In28FgXP+YAxCPSx5QLWHGWBu6dhGP0kPk6uwznOeJiMlbOkBsmfHN0kjiBH
Ooam5Y00W/O9lHrX2Smxq0syLkK5/CK4U4Op/BlplggtteyFactpwulapPYh
RiVbe3EIWa9Veg+iXtntFzDowmYLop0+3E8eHenEpKt2HQqh3DXcmP+VC8cC
uu3ilVearDM3GYUibHxRNN9zp4FLyit1KkDpadjc7Vpk2h5TCva0Rlve4pBO
5oKmZDqWTeVMZI1ivdUxLbyNnWiQMDzFwXynTQx0rKJ37L6DB998//iP+Tl7
4tDcA3cbK5pKwPDgBQQ7Evc1dzwH72lc1hvDC0jo4yQUHlLN93284DLbjxUi
qGKGr973FKdtpVGL6MMekeBVCV2QzM5lrmXy0ECKUZCaU9STLQDyBkuN47Wu
T2mV5b2Wb9lq5VoqBg31QiQ0pa/L3q+GeJuAxgIIuOKHoxepSKFHESUNLzK6
l4RshLS74qt2qYrcIGrbHm8yCKZYrzt/RPyMYkCMNCvBIpknHVyUliTWiZZp
DcvZZfEdAu6YMDWnQ+uoJhTNLo8L1A2Ld9P0RkIx/Jzv2UDkI7Nv9B2H4m/a
8bPy19DrTSynSeQEvyEVJgcu3FpaQT2i99V1b+5M/l3iWld6zZi+qQdvkDSh
XhmDT5KJETi/WYaSP1bukNNfTYkU6+cooJ7haNrJUuI6nBYqFmesITZKDDNn
/7TP2pbYua2nXdWJo3qOzKJyN7hDO9wwMa5a3B6/5piZECvJUEFc8EVNpFjH
AdWsIWg9bhdEoPq4AMVVrL7o5dR9GTy7gKx0XVjKB1bhWFO3SIEriVUFP/LW
33CnlSfZigiXxVsRSr6bl6tFB2X/lIs3qhknKY21lbXtSp/klQrJXkokn6lv
TMtNaey8ItDq31Q1IVqLbRf9zh7TXkTva2C31WBRrnqRmxhUphoMISIXbUnJ
NY18WHLxPTm3ag8zeoBC/CzXRBdnz56lJ2huLTV1cRiU/nGtNK490GSPtfcI
quVxU/QxDRP8CC0ErhFu952ovZcqAim+QE+RIsmDAVOpUVZtndwzFXSqvVRn
1Nhk4Vo6xJB3TO3wtCX5N3hyNSgxBjFVXKUeOvVwtRWCZdDHSg3kuWMD/3Q8
nuqygUa8b1yxroCciUO16uTsg1giwARB3XWoQnkmmZF8OCUHLdEtkRUiXmuH
zhZ97uwQ+sRCnWevNSjJLg1PzAAboQGpWPrl5188pPN96uNPgjLGaYYgKeCU
cy+SBrtCxdgq8x+whzUTmSWuTWDIVoQ9EHpr1YaElyU45NzrKVbL/braidnP
KXD8hgAnrme0xbfYeeLb7xBkxNnIVsLpKQejalrQu3shdDzLoJr7Qn83VRcr
D9hzJy5tSC9j33k5T7YvKT7I6lpBWyYCX7XGViaq5jtY113RagCvFC7ElXko
8IoqVjGNcALePZWwVQ56jemGAO4tALdqsoC3hHncigpjQZjOxd9wOIHvXKYD
/Axni3Vx8wsgPha/6yVe7nY3g1fl0p758TkL3pEi8Y8UYw8JlCV/ZxyYlgWM
iugId2rit6T8r3MZT6c7pjGfRQjGJNWtsao7t8THsjQXJcWGYzdN7huOhTE2
XuiB16f40lOs5C1MRAwWM0l4hjgOO6l9LyxUKYyFtL+RJrYS/aXUHOKo7NRo
rLAVklNJ6UKHbzFhPt4cAxocSCpcoMGKV/w+qP1e55cLAOIFDFmU5fNw/5AL
DLVgxHX81aFSdpkS49NWE3McZoX3xpEq4Qhpbinu4kAEHD0vgJhqQhIOporY
SGOyRL2+TfsKhHoN3UyiISYCuSx+Stai+JigrnkI6lVJGaSgqBXSlAtZuh3F
SyFEhkGKnxhzY3UKJsqahn8lU6rbdtfr4RuY68Q7D/KUokLdKTWgTa0QnQY1
4Y6NEWM8w9UtxorLy+Kb63CdXUhT1gGxc9ScpRi0HTDHVi7YAFd90tiGBLVK
2jFn7+YhUyZs5RgqGVeyMcxT8Jyi6W8Eph2uYhyIrI+LpRF4i90l/hIabynx
sZY6h67SV6h/MgZh0jOh7K1Rj1msw3LblampPz6tYsNhJJnPGDiuZXNTXuiO
WfADjyDeRexTD3Cyu6FXd5EVorERvHJ+qMJqOI5mO5erY4QFaoaN2i8WvDWV
kKxhZQP7GTG+fZNOI2IAcpXAuNIOVJFYoCq9ORReNA0OcNV6WP3KNM1hW66r
Qm5MGd/jK4vnbqNmoSYpMW2IAIhtmC4cNTpcndlzachynVASMky3NAtwyui3
4ct6ftrxtStJ3EFYc9oQOOE2+3pMmCUnHAheFh53mhr8hHo3I+POmgPGDhsh
CXFzpndZT6WnR+l3+x04YIrpbbxXo6Up61qxE73X4cquZ9OESVtV0NR6LbU5
NCxS7kSQS0HXdl1dHFYcs7vYm/cqgMKcOy/0xoIq3DuuN96PYV9fCSfnbR4n
0/Xj+Jnz8+cSSygowQpab3h6zmxte4FwsjS7yQeZyHS6tDKxVluwy94sTi0R
zzIzm5T6PFycAQlXnM/B8ioEy2PSQx5oCW9tCD+USg2onMxWxU4O1eiWWJNE
iAyL5hU0W5UJI3GiV/ukMmTsPcuCU3XsoNX6mduyHPo8lBizOlOuWJjsUhaj
bW6vl3V3hbowq8w7JCSvde4y9w96z2Twe/gNRYJTGYsBzrme3ciXUcgXodAK
X1K8r0vxQSfhu2x1vbHKU3axuhheYmxhSjbJZM9O/WHkDplZac2WfRN4IWfE
ZwhBay/azhLoXAHUyYtcl/Asfy9shIMYcqsTl6C+gMAOLr2CUfnuUvrQ6845
mNQ4W9tZOlbF0MsLlX+THhWGLhFAJjBVjC5ji9qpeIE6ZKgBS9HEp1oDONTX
oly/gRHmsyinQCDNn1SFRCGrtSmMlSklgpsGlAUIEDwozN4g69yl49Vm/KTj
cIJN2CE7/W/ARCFtj9EtQYiSpF6TnzmrZCvotKF+RVIXioOJq0FuLZBXbP19
GJ3Y/m8rrVuJTL19rwwJbIBMOo4/UMzwIP0W1VbMMzrP7ZapMlSjcZcTKIKI
ZWbmLO96+p6nIErFKLPiVwepMC3RTaUlu4Xn/YGBaEEZA5w8xnVvLalF+hHU
SI1VzbmFPtZIqPzg0g2scTtlzP4EtHxTsuHMIFvaYRI7J7el9Kgh60JiJYrK
QpMkjpJJ7OLgGYCWeRpFZCk6yjJn36kSGZRjsDXsJMBVrmTOXMTQHH3Ia1xS
m1NuR5OLHgS9KOu+vBFbZeELno/q7JrACeW3TYUW1nKhPAaye8riSVi0u7j+
EkV6jBWQumahlqHKg1PdxPqxOENV5f24TGHwKVFZrqr9HPr7g1Ox9KezkIL+
JUqTWE7EI7c6CYntDSt6VFdqrKvhpJu+No+q2lzZCBxk8yjxVSfUmnpujXaS
L2D2QOJSwlI1iqurTukQeE6p4f25FUNiiWzM6KbthquDqAgBQussT1jLJUUg
KcGdRByARDm+wjWntTLclZQeg9YiC5DO6664EWOUSEVQizDe4kKw56Ra0pKj
i9R8x1lrzPA4ylmLhzzcXVXqu0yTxlc/6cfh3HrHgu6GGi63mfuL/Cn3GhCd
Rmp8hTTYjReL87R0iMRmTYfcM9/SugoWveRYSHLxTwwAqdKi5ZyEkndVf83n
B9uhuYHcmgokrb+aSd6ivLMuTbamJ1hV5aiZ15BIXAuN2CBnf1rlvYAW9MTq
e8NArdyZy7pXAIq5p/il2IMljMEVQdi1dBiCKRxsSt+ibQP83LXeV8/l71wN
VjYWHHuSjPYwesTXN9cLqRMrSd5yoZdYTdaVB6hdwc742uhSoUCgksDCXoyj
uUGbleVM3BmjaHG7wkbSlMC6LInpgLUhS0TuIYvWRCxBiuMV1cvk1th7JA04
+HSk9ubv7llUapbp9RtsipAyDI5Htk1p4TsHy8NxfubRQoTiRPPMxVVfVcFc
V6AnDn8ZL/0IlUQ5MAuZGsIiMw0P1SsAYgCSGjsM8sqb4lbvgTGzz8Gv02Kh
Fau5MGEMd5sH2gu3uw3tjrPQ5sfxtGjmoryqOMAC2MJCA3xrphU9/nxB/YSW
LflspMO3F6yXdy5ZhUNleJnHaTETSTEhRMO9NPRWIjvGGc4t8IfmmcXCVtpS
xKnMnJDkLpA0salTX/5Q3W3szeSUBht5pWWa2201TKHmXJw+hFyn0dGZLt4y
EN8YyolHWe4hYmBObljV8i18gDhWNANx1K2WWyyjxIhSXKItOJjFQBDU7raw
f82PzSzcm4ugHGJEsFWe3hRdEKzashSLiQgNpg03516Hgxh7FxLvo+56W33S
KlYwqGtOAnK5/F12P1x/GC93/C0qBOMGitLyh0RuBuPEaEtHKl9nxbRzQ5Lf
RDvgsH6J0WQ0MFoqKK4tZp2F9LGOYhYnbeTrsTTVCrzuajpfa12sFE4X7K5F
qKIaepExAjRPsK2AFUQHMMfa6LonvM86C0TRx/N9zMdEP5RTrzZcgppysFQ2
AkA47l8qz6vxzRspl3i4m5UtN8zK3GTCyO0OPsdnLYBlXUooteyGZlxWQzjk
TO1T931+qfd9EsN/dvbi7Ajk+Nqcl1IelW2d4+qTiPjTGvTm58RGx7wWsp5B
wM6T6vA8h9j0yaVWjv+chjj8zHUgJbLkOm0+N7oeAXXjib3ckUB8xkgTiS+P
O8FBs9sPUdFM6gqz0gXzebBCG1G3suLhvVTcDjet6AXUjCUl90uDnFcIkZAK
q0VfKQ8pV5WCkaybhML90qPFhusNlZM5MV/lZ6M7EDRhLck54zjjUYqdTzhP
6isZS9AkvrmkloabUKTUxHHpdfV4T6FFWZ5bpHeogySQ5eiq84l0OY2uPg7F
zjR5k93SHPqmEdhEbF/hvsK+nWtkToqfSVFi1fW1KPIYk/ZxCiEuf67O07eG
ZcQoBbkJVFOov0LpaukYhH9RBpPbIICbJPtPK9bKAnLk6WDA3Eo3+TytQCxJ
Hb1cqmJsydUlDx1K1kca2ReZonZsnMNZQr66sVqQMC9wVMDBy8gIYtFbjh/g
jMtGgjjkStq+HGK1dBOOtQTx3yLiYE2JkSB39JhT9PsntqFArC2uQxyUMO6P
L+f6CqjExB0ZoxvWTdZITuNt14SwRfihe0K0hsc8CbynkSvpgyzZg9/6WnmS
2dcL104ywUxMhcNPpN2PCNYkpOoOeznEYVLKPqwgmSXP8G6QVQZqhdMlHJXJ
q+1nYAUznoNLYWDmW6yFPhm/UwqVeGGXfJPcvFS4e6SmiyKoj8uHXYWqB+NM
LQNIfZpUiAyIST9uMIq0CGdZJYk9948Tdx4o89GD5DJ2XF7lqQDYuJgEvPYr
pmBVuvXC1tQlMr7hOui6iYOWLTu2A9m24HKoGiY3vmb+SA1hF61gAYowvHn9
SnyBR3XIvIdHaiU6Z9KIVbM3S9yFa6AUJ6z2OYGg8kVvoB5XOXLhvhB5CuGn
9QiPyqXSqHdqVZR19VZsjFGWeOIkTNeCZqhXQ7rsVfM3XxyEd3OPNvZkq9gL
2gdA0wdEaAxpumtwUX63QzTB5D3rXy4fsTRRj6qQoXgb4y7wuXbkEfnsV9RQ
OZLw8AktFlyXkNW5ut6HApL/+ubli/ypjvfdPR35L1IC+x11O4NYn53kM+QW
Ez0vSKzMuGicKAI/8tk/0Rpy9oscMPr63xG7mL/LZ4q5hMf3XcUP45/9iO+5
rNHJp5/aRd+rdvvpMpY++VRSCuH2W/69Ryk8ayMccfRKw/msmOX/EX8VBoEe
XEzRLP9l/v9jgHHuv24ooQ4XD4Ue4KdmoYw2PUMj4+iTHxnJx0ufPfzsi8XD
LxcPH50/fHjC//dvOpGZ6mI/2qY9k02Ds6CC/NQNkhqJP0Y1WibcnOikTnhC
J8dbblF3fmetr4jTLHphjrM5D35fyjpIc3SKaDVktplUpMaFOhLviXtEWRlP
4z8lg02Ux/6a62P5m6liiG7pSlgzwpowdnCFibSSIa3J4nFYkgQxp6PfdxsO
9RRhiYMM3U7DJt39Q/7S81+VRJmBe3B4sKVLJoHNPB7t7vx/n8f4gqK3+tvZ
R+bghsqUmAl7I0gLiMdsAb7AV5/F84ZChgPfVXAfuc20O9gNLdcRxJSK7AfL
/GsElImFnEnwGBcMIK5zytXXct3jXk0bpzS7AN5M6+uX4/LW720DbEX8Tz/E
WknM4ewiblRwC0/dUub6rnLWxz9NPXxbyWsaRtC0IWBCSSL+6X5QkL57/fwB
f8PLLp/CmCfLJtPDcPedGtYCcl505cZuppNalyJ03weHPP3JXxEjuLUkNYZh
zhIuv9nKkB/IT+aIeBAeHn2TT9y43nb68JvX33/K5K71M6105lxqZ/L96m1y
E/n7iLW4v5f7rh5dcx4UPvTDn452Q8ZbNT5Hxzcab22fukBd9zNqqPy4r8r1
tx/5stK/ifoofQV+/+D4c5Ze/Bx6fB+383j8xrio2+9eP+MZqaq81mjC22uZ
6xk6P39+GrpYaIADIiGkxp6WsHsfytu5v8LlxqOzaJccy8J7Z9O4TCd/V++a
LPDB5PE7iptOVzRllsy2P/xKa7YyiV05FrJUnrxtf67Lw01V11Wx7YVZEm8s
KtyPtFcsMEMVO8falWNyluVNwcWBixgq5qqJ6dStvGzriwGwrqr5ZBorFqH5
3DC9qhkHkp3gO11htmmv5O5CLi4aYkpD4eq6DNXPEpnCPILHGDmQZkrrPMz6
zBIjywoMjStFO2ajRusojDu7NYybM5x8vUaBr5GJmwYh/LpaBKCBjxSEUk/Q
UiDG7JMRIFu3KKYCMz39lfLdl0cKnXCZQbvNl3YMp6vwICfX0U+siCUrROMz
G4+Qy/dikydezCKn2WqAhdsT7WvsKMllPjaBZZy6fAIXA6XZf5OFNO9z5Nzn
E7FzVvpyKrsh4q0kGXLThUbCQWQDMweSD1kqH+ISsDl8wZcFAQmbJ+zE3V5t
t0BkHB9y9tnZPL/L4HgQQ54TW3AdG9JAuemCtGo/K9dPStwmI+QanRmKvlSD
hd5F/onhzC2MlrEw1yYpDIqAIyhDWQGrlt8+fqVbaUGh9o4JvY89NrqJxzW6
fnUhknhW3UvjTjfYVWDwqK3IhM2R99/HzFbW9zN3UebxhYPhusHEr9+o2rPw
6Tnga67+10LRHq47+WtnOFcuOuokVAtJwA08KtcNLv70w+LZEzjQYn4gnOFa
4tLgyZCdNJJ5fIjGmqKUDHfzgj68gN5QHTHtafo9DQkvx6szl1i1hYtdGfmG
acd6N1CL5k+CEDZRwEoa+UcUxAE35TI4Ai3i0ePh5RMFbm7xKGShLE3A+xQC
PB4Me5LOVmAWxMEuhf6ydyfNHqBvuf7n2aYgOTZTI1bCGlkENNf587ar8n/F
YZPggz1c32dX+78XVsem6vjWWDFqGyk2kPmqYrS0XdX24sGmPzfJ1b/qkTxb
dxXt79dcI5e/eU4Hp8ie7JuLonN9oeV93+tOeK/Sbq+52+1+wN+crn5gn0Qm
kzmry+ueniAu2g3Ftr2+at/KtKrDnlRbvQfUT+coIW2eTZRvnmsK3wijfV2t
wAfb/EmVv9j//HPLzcMjWXJxRGWnYooHF9wy+3+oeACAwOQAAA==

-->

</rfc>
