Resource Records for EUI-48 and EUI-64 Addresses in the DNS
RFC 7043
Document | Type |
RFC - Informational
(October 2013; No errata)
Was draft-jabley-dnsext-eui48-eui64-rrtypes (individual)
|
|
---|---|---|---|
Last updated | 2018-12-20 | ||
Stream | IETF | ||
Formats | plain text pdf html bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Joel Jaeggli | ||
Shepherd write-up | Show (last changed 2013-05-20) | ||
IESG | IESG state | RFC 7043 (Informational) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Joel Jaeggli | ||
IESG note |
Joe requested that I look at ad sponsoring this and it looks like a candidate for that path. Expert review of the request for code-point assignment has completed, and code-points have been assigned. |
||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) J. Abley Request for Comments: 7043 Dyn, Inc. Category: Informational October 2013 ISSN: 2070-1721 Resource Records for EUI-48 and EUI-64 Addresses in the DNS Abstract 48-bit Extended Unique Identifier (EUI-48) and 64-bit Extended Unique Identifier (EUI-64) are address formats specified by the IEEE for use in various layer-2 networks, e.g., Ethernet. This document describes two new DNS resource record types, EUI48 and EUI64, for encoding Ethernet addresses in the DNS. This document describes potentially severe privacy implications resulting from indiscriminate publication of link-layer addresses in the DNS. EUI-48 or EUI-64 addresses SHOULD NOT be published in the public DNS. This document specifies an interoperable encoding of these address types for use in private DNS namespaces, where the privacy concerns can be constrained and mitigated. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7043. Abley Informational [Page 1] RFC 7043 Resource Records for EUI-48, EUI-64 October 2013 Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The EUI48 Resource Record . . . . . . . . . . . . . . . . . . 3 3.1. EUI48 RDATA Wire Format . . . . . . . . . . . . . . . . . 4 3.2. EUI48 RR Presentation Format . . . . . . . . . . . . . . 4 3.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. The EUI64 Resource Record . . . . . . . . . . . . . . . . . . 4 4.1. EUI64 RDATA Wire Format . . . . . . . . . . . . . . . . . 4 4.2. EUI64 RR Presentation Format . . . . . . . . . . . . . . 5 4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Example Use Case: IP Address Tracking in DOCSIS Networks . . 5 6. DNS Protocol Considerations . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 8 Abley Informational [Page 2] RFC 7043 Resource Records for EUI-48, EUI-64 October 2013 1. Introduction The Domain Name System (DNS) is described in [RFC1034] and [RFC1035]. This base specification defines many resource record (RR) types, and subsequent specifications have defined others. Each defined RR type provides a means of encoding particular data in the DNS. 48-bit Extended Unique Identifier (EUI-48) [EUI48] and 64-bit Extended Unique Identifier (EUI-64) [EUI64] are address formats specified by the IEEE for use in various layer-2 networks, e.g., Ethernet. This document defines two new RR types, EUI48 and EUI64, for encoding EUI-48 and EUI-64 addresses in the DNS. There are potentially severe privacy implications resulting from the indiscriminate publication of link-layer addresses in the DNS (see Section 8). This document recommends that EUI-48 or EUI-64 addresses SHOULD NOT be published in the public DNS. This document specifies an interoperable encoding of these address types for use in privateShow full document text