%% You should probably cite draft-morrison-mcp-dns-discovery-09 instead of this revision.
@techreport{morrison-mcp-dns-discovery-06,
    number =    {draft-morrison-mcp-dns-discovery-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-morrison-mcp-dns-discovery/06/},
    author =    {Blake Morrison},
    title =     {{Discovery of Model Context Protocol Servers via DNS TXT Records}},
    pagetotal = 72,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document defines a DNS-based mechanism for discovering Model Context Protocol (MCP) servers, the identity of the organisations that operate them, and a cryptographic identity envelope bound to an individual Sovereign-tier \textasciitilde{}handle published under the same zone. Three TXT records are defined. \_mcp.\textless{}domain\textgreater{} advertises an MCP server's endpoint URL, agent protocol family, transport binding, cryptographic identity, and capability profile. \_org-alter.\textless{}domain\textgreater{} advertises the operator's canonical organisational identity, including its legal entity, registry identifier, regions of operation, and any regulatory framework under which it must refuse external automated access. \_alter.\textless{}domain\textgreater{} publishes an Ed25519-signed envelope binding a \textasciitilde{}handle to a public key, an IdentityLog root reference, and a revocation commitment. DNSSEC validation is REQUIRED for the envelope record, and a DANE TLSA pin on the MCP endpoint is REQUIRED where resolving an envelope and opening an MCP session are one recognition transaction. This revision (v06) adds a key continuity rule for the \_mcp record. It says what a client does when the key it pinned differs from the key DNS now serves, and when the published epoch goes down, neither of which any earlier revision covered. It also corrects two statements in the Implementation Status section. Revision 05 withdrew several claims that v04 could not support, marked publication of a per-individual envelope in DNS as NOT RECOMMENDED on enumeration, size, and erasure grounds, and separated the agent protocol family from the transport binding in the \_mcp record, aligning that vocabulary with neighbouring DNS agent-discovery drafts. All three record formats and all three procedures are given here in full, so no earlier revision need be fetched. The mechanism complements HTTPS-based discovery, and follows the precedent set by DKIM, SPF, DMARC, and MTA-STS. Provisional registration of a companion alter: URI scheme is requested of IANA, and is not yet granted.},
}