%% You should probably cite rfc9527 instead of this I-D.
@techreport{ietf-homenet-naming-architecture-dhc-options-03,
    number =    {draft-ietf-homenet-naming-architecture-dhc-options-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-ietf-homenet-naming-architecture-dhc-options/03/},
    author =    {Daniel Migault and Tomek Mrugalski and Chris Griffiths and Ralf Weber and Wouter Cloetens},
    title =     {{DHCPv6 Options for Homenet Naming Architecture}},
    pagetotal = 28,
    year =      2015,
    month =     oct,
    day =       19,
    abstract =  {Customer Premises Equipment (CPE) devices are usually constrained devices with reduced network and CPU capabilities. As such, a CPE exposing the authoritative naming service for its home network on the Internet may become vulnerable to resource exhaustion attacks. One way to avoid exposing CPE is to outsource the authoritative service to a third party, e.g. ISP. Such an outsource requires setting up an architecture which may be inappropriate for most end users. This document defines DHCPv6 options so any agnostic CPE can automatically proceed to the appropriate configuration and outsource the authoritative naming service for the home network. In most cases, the outsourcing mechanism is transparent for the end user.},
}