%% You should probably cite rfc8552 instead of this I-D.
@techreport{ietf-dnsop-attrleaf-15,
    number =    {draft-ietf-dnsop-attrleaf-15},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/15/},
    author =    {Dave Crocker},
    title =     {{DNS Scoped Data Through "Underscore" Naming of Attribute Leaves}},
    pagetotal = 14,
    year =      2018,
    month =     nov,
    day =       3,
    abstract =  {Formally, any DNS resource record may occur under any domain name. However some services use an operational convention for defining specific interpretations of an RRset, by locating the records in a DNS branch, under the parent domain to which the RRset actually applies. The top of this subordinate branch is defined by a naming convention that uses a reserved node name, which begins with an \_underscore. The underscored naming construct defines a semantic scope for DNS record types that are associated with the parent domain, above the underscored branch. This specification explores the nature of this DNS usage and defines the "DNS Global Underscore Scoped Entry Registry" with IANA. The purpose of the Underscore registry is to avoid collisions resulting from the use of the same underscore-based name, for different services.},
}