]> TekSavvy Solutions, Inc.

470 Moore Street London ON N6C 2C2 Canada +1 519 670 9327 jabley@teksavvy.ca

48-bit Extended Unique Identifiers (EUI-48) and 64-bit Extended Unique Identifiers (EUI-64) are address formats specified by the IEEE for use in various layer-2 networks, e.g. ethernet. This document defines two new DNS resource record types, EUI48 and EUI64, for encoding ethernet addresses in the DNS.

The Domain Name System (DNS) is described in and . This base specification defines many Resource Record (RR) Types, and subsequent specifications have defined others. Each defined RRType provides a means of encoding particular data in the DNS. 48-bit Extended Unique Identifiers (EUI-48) and 64-bit Extended Unique Identifiers (EUI-64) 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.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The EUI48 RR is used to store a single EUI-48 address in the DNS. The Type value for the EUI48 RRType is 108 (decimal). The EUI48 RR is class-independent. The EUI48 RR has no special Time-to-Live (TTL) requirements.

The RDATA for an EUI48 RR consists of a single, 6-octet EUI48-Address field, encoded in network (big-endian) order.

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | EUI48-Address | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Address field MUST be represented as six two-digit hexadecimal numbers separated by hyphens. The hexadecimal digits "A" through "F" MAY be represented in either upper or lower case.

The EUI64 RR is used to store a single EUI-64 address in the DNS. The Type value for the EUI64 RR is 109 (decimal). The EUI64 RR is class-independent. The EUI64 RR has no special TTL requirements.

The RDATA for an EUI48 RR consists of a single, 8-octet Address field, encoded in network (big-endian) order.

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | EUI-64 Address | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Address field MUST be represented as eight two-digit hexadecimal numbers separated by hyphens. The hexadecimal digits "A" through "F" MAY be represented in either upper or lower case.

The following EUI48 RR stores the EUI-48 unicast address 00-00-5e-90-01-2a.

host.example. 86400 IN EUI48 00-00-5e-90-01-2a

The following EUI64 RR stores the EUI-64 address 00-00-5e-ef-00-00-00-2a.

host.example. 86400 IN EUI64 00-00-5e-ef-00-00-00-2a

IANA has assigned the RRType value 108 (decimal) for EUI48 and 109 (decimal) for EUI64. This document directs the IANA to confirm that the corresponding entries in the "Resource Record (RR) TYPEs" subregistry match the following data: Type Value Meaning Reference EUI48 108 an EUI-48 address this document EUI64 109 an EUI-64 address this document

The specification presented in this document presents no additional threat to the Internet.

The author acknowledges the contributions of Olafur Gudmundsson, Mark Smith, Andrew Sullivan and Roy Arends.

&rfc1034; &rfc1035; &rfc2119; IEEE

IEEE

This section (and sub-sections) to be removed prior to publication.

DNS RRTYPE PARAMETER ALLOCATION TEMPLATE A. Submission Date: 2013-03-18 B.1 Submission Type: [X] New RRTYPE [ ] Modification to RRTYPE B.2 Kind of RR: [X] Data RR [ ] Meta-RR C. Contact Information for submitter (will be publicly posted): Name: Joe Abley Email Address: jabley@teksavvy.ca International telephone number: +1 519 670 9327 Other contact handles: D. Motivation for the new RRTYPE application. The purpose of this RRTYPE application is to allow EUI-48 and EUI-64 addresses to be stored in the DNS. EUI-48 addresses are those used, for example, in ethernet. E. Description of the proposed RR type. See draft-jabley-dnsext-eui48-eui64-rrtypes for a full description. F. What existing RRTYPE or RRTYPEs come closest to filling that need and why are they unsatisfactory? The TXT record can be used to store arbitrary, unstructured data in the DNS and hence could be used to store EUI-48 and EUI-64 addresses. This approach is unsatisfactory for the usual reasons, i.e. there is no opportunity for validating data before it is stored, and typographical errors must consequently be detected after data retrieval. G. What mnemonic is requested for the new RRTYPE (optional)? EUI48 for EUI-48 addresses; EUI64 for EUI-64 addresses. H. Does the requested RRTYPE make use of any existing IANA registry or require the creation of a new IANA sub-registry in DNS Parameters? If so, please indicate which registry is to be used or created. If a new sub-registry is needed, specify the allocation policy for it and its initial contents. Also include what the modification procedures will be. No. I. Does the proposal require/expect any changes in DNS servers/resolvers that prevent the new type from being processed as an unknown RRTYPE (see [RFC3597])? No. J. Comments: See draft-jabley-dnsext-eui48-eui64-rrtypes for a complete specification.

Initial idea, circulated for the purposes of entertainment. Presentation format changed from colon-separated to hyphen-separated, to better match conventional usage for big-endian representations of EUI-48 and EUI-64 addresses. IEEE trademarks acknowledged. Code-points assigned by expert review. Other minor tweaks and fixes based on early review. Example EUI64 presentation format in text corrected (colons -> hyphens). Examples changed to use to-be-assigned addresses under the IANA OUI.