RFC 7043: Resource Records for EUI-48 and EUI-64 Addresses in the DNS
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7043
- Published
- October 2013
- Authors
- J. Abley
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7448MIB Transfer from the IETF to the IEEE 802.3 WGCurrent
February 2015
- RFC 5171Cisco Systems UniDirectional Link Detection (UDLD) ProtocolCurrent
April 2008
- RFC 7042IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersObsoleted
October 2013
- RFC 7124Ethernet in the First Mile Copper (EFMCu) Interfaces MIBCurrent
February 2014
- RFC 5904RADIUS Attributes for IEEE 802.16 Privacy Key Management Version 1 (PKMv1) Protocol SupportCurrent
June 2010
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 5417Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP OptionCurrent
March 2009
- RFC 5416Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11Current
March 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?