%% You should probably cite rfc8947 instead of this I-D. @techreport{ietf-dhc-mac-assign-09, number = {draft-ietf-dhc-mac-assign-09}, 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-dhc-mac-assign/09/}, author = {Bernie Volz and Tomek Mrugalski and Carlos J. Bernardos}, title = {{Link-Layer Address Assignment Mechanism for DHCPv6}}, pagetotal = 18, year = 2020, month = sep, day = 3, abstract = {In certain environments, e.g., large-scale virtualization deployments, new devices are created in an automated manner. Such devices may have their link-layer addresses assigned in an automated fashion. With sufficient scale, the likelihood of a collision using random assignment without duplication detection is not acceptable. Therefore, an allocation mechanism is required. This document proposes an extension to DHCPv6 that allows a scalable approach to link-layer address assignments where preassigned link-layer address assignments (such as by a manufacturer) are not possible or are unnecessary.}, }