%% You should probably cite draft-adpkja-dnsop-special-names-problem-06 instead of this revision.
@techreport{adpkja-dnsop-special-names-problem-03,
    number =    {draft-adpkja-dnsop-special-names-problem-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-adpkja-dnsop-special-names-problem/03/},
    author =    {Geoff Huston and Peter Koch and Alain Durand and Warren "Ace" Kumari},
    title =     {{Problem Statement for the Reservation of Top-Level Domains in the Special-Use Domain Names Registry}},
    pagetotal = 8,
    year =      2016,
    month =     may,
    day =       25,
    abstract =  {The dominant protocol for name resolution on the Internet is the Domain Name System (DNS). However, other protocols exist that are fundamentally different from the DNS, and may or may not share the same namespace. When an end-user triggers resolution of a name on a system that supports multiple, different protocols (or resolution mechanisms), it is desirable that the protocol used is unambiguous, and that requests intended for one protocol are not inadvertently answered using another. RFC 6761 introduced a framework by which a particular domain name could be acknowledged as being special. Various challenges have become apparent with this application of the guidance provided in RFC 6761. This document aims to document those challenges in the form of a problem statement in order to facilitate further discussion of potential solutions.},
}