%% You should probably cite draft-morrison-mcp-dns-discovery-09 instead of this revision.
@techreport{morrison-mcp-dns-discovery-07,
    number =    {draft-morrison-mcp-dns-discovery-07},
    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/07/},
    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. 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.},
}