Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 7043 Dyn, Inc.
Category: Informational October 2013
ISSN: 2070-1721
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
DNS中EUI-48和EUI-64地址的资源记录
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.
48位扩展唯一标识符（EUI-48）和64位扩展唯一标识符（EUI-64）是IEEE指定的地址格式，用于各种第2层网络，例如以太网。
This document describes two new DNS resource record types, EUI48 and EUI64, for encoding Ethernet addresses in the DNS.
本文档描述了两种新的DNS资源记录类型EUI48和EUI64，用于在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.
本文档描述了在DNS中不加选择地发布链接层地址可能导致的严重隐私问题。EUI-48或EUI-64地址不应在公共DNS中发布。本文档指定了这些地址类型的可互操作编码，以便在私有DNS名称空间中使用，在私有DNS名称空间中可以限制和缓解隐私问题。
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.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
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.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7043.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
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
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
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.
[RFC1034]和[RFC1035]中描述了域名系统（DNS）。此基本规范定义了许多资源记录（RR）类型，后续规范定义了其他类型。每个定义的RR类型都提供了一种在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.
48位扩展唯一标识符（EUI-48）[EUI48]和64位扩展唯一标识符（EUI-64）[EUI64]是IEEE指定用于各种第2层网络（如以太网）的地址格式。
This document defines two new RR types, EUI48 and EUI64, for encoding EUI-48 and EUI-64 addresses in the DNS.
本文档定义了两种新的RR类型EUI48和EUI64，用于在DNS中编码EUI-48和EUI-64地址。
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 private DNS namespaces, where the privacy implications can be constrained and mitigated.
DNS中不加选择地公布链路层地址可能会导致严重的隐私问题（见第8节）。本文件建议不在公共DNS中发布EUI-48或EUI-64地址。本文档指定了这些地址类型的可互操作编码，以便在私有DNS名称空间中使用，在私有DNS名称空间中可以限制和减轻隐私影响。
This document uses capitalized keywords such as MUST and MAY to describe the requirements for using the registered RR types. The intended meaning of those keywords in this document are the same as those described in [RFC2119]. Although these keywords are often used to specify normative requirements in IETF Standards, their use in this document does not imply that this document is a standard of any kind.
本文档使用大写关键字（如MUST和MAY）来描述使用注册RR类型的要求。本文件中这些关键字的预期含义与[RFC2119]中描述的相同。尽管这些关键字通常用于指定IETF标准中的规范性要求，但在本文件中使用这些关键字并不意味着本文件是任何类型的标准。
The EUI48 resource record (RR) is used to store a single EUI-48 address in the DNS.
EUI48资源记录（RR）用于在DNS中存储单个EUI-48地址。
The Type value for the EUI48 RR is 108 (decimal).
EUI48 RR的类型值为108（十进制）。
The EUI48 RR is class independent.
EUI48 RR与类别无关。
The EUI48 RR has no special Time-to-Live (TTL) requirements.
EUI48 RR没有特殊的生存时间（TTL）要求。
The RDATA for an EUI48 RR consists of a single, 6-octet Address field, encoded in network (big-endian) order.
EUI48 RR的RDATA由一个以网络（大端）顺序编码的6位八位组地址字段组成。
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-48 Address |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-48 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.
地址字段必须表示为六个由连字符分隔的两位十六进制数字。十六进制数字“A”到“F”可以用大写或小写表示。
The following EUI48 RR stores the EUI-48 unicast address 00-00-5e-00-53-2a.
以下EUI48 RR存储EUI-48单播地址00-00-5e-00-53-2a。
host.example. 86400 IN EUI48 00-00-5e-00-53-2a
host.example。86400英寸EUI48 00-00-5e-00-53-2a
The EUI64 RR is used to store a single EUI-64 address in the DNS.
EUI64 RR用于在DNS中存储单个EUI-64地址。
The Type value for the EUI64 RR is 109 (decimal).
EUI64 RR的类型值为109（十进制）。
The EUI64 RR is class independent.
EUI64 RR与类无关。
The EUI64 RR has no special TTL requirements.
EUI64 RR没有特殊的TTL要求。
The RDATA for an EUI64 RR consists of a single, 8-octet Address field, encoded in network (big-endian) order.
EUI64 RR的RDATA由一个8位字节的地址字段组成，按网络（大端）顺序编码。
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 |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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.
地址字段必须表示为八个由连字符分隔的两位十六进制数字。十六进制数字“A”到“F”可以用大写或小写表示。
The following EUI64 RR stores the EUI-64 unicast address 00-00-5e-ef-10-00-00-2a.
以下EUI64 RR存储EUI-64单播地址00-00-5e-ef-10-00-00-2a。
host.example. 86400 IN EUI64 00-00-5e-ef-10-00-00-2a
host.example。86400英寸EUI64 00-00-5e-ef-10-00-00-2a
Canadian cable Internet subscribers are assigned IP addresses using DHCP, using a DHCP server operated by a cable company. In the case where a cable company provides last-mile connectivity to a subscriber on behalf of a third-party company (reseller), the DHCP server assigns addresses from a pool supplied by the reseller. The reseller retains knowledge of the EUI-48 address of the DOCSIS modem supplied to the subscriber but has no direct knowledge of the IP addresses assigned. In order for the reseller to be able to map the IP address assigned to a subscriber to that EUI-48 address (and hence to the subscriber identity), the cable company can make available information from the DHCP server that provides (EUI-48, IP) address mapping.
加拿大有线互联网用户使用DHCP分配IP地址，使用由有线电视公司运营的DHCP服务器。在有线电视公司代表第三方公司（经销商）向用户提供最后一英里连接的情况下，DHCP服务器从经销商提供的池中分配地址。转售商保留向订户提供的DOCSIS调制解调器的EUI-48地址，但不直接知道分配的IP地址。为了使经销商能够将分配给订户的IP地址映射到该EUI-48地址（从而映射到订户标识），有线电视公司可以从提供（EUI-48，IP）地址映射的DHCP服务器提供信息。
Cable companies in Canada are required [NTRE038D] to make this address mapping available using the DNS. Zones containing the relevant information are published on DNS servers, access to which is restricted to the resellers corresponding to particular sets of subscribers. Subscriber address information is not published in the public DNS.
加拿大的电缆公司需要[NTRE038D]使用DNS使此地址映射可用。包含相关信息的区域发布在DNS服务器上，对该服务器的访问仅限于与特定订阅者集对应的经销商。订阅服务器地址信息未在公共DNS中发布。
Existing DNS schemas for the representation of (EUI-48, IP) mapping used by Canadian cable companies are varied and inefficient; in the absence of an RR type for direct encoding of EUI-48 addresses, addresses are variously encoded into owner names or are published in TXT records.
加拿大有线电视公司使用的（EUI-48，IP）映射表示的现有DNS模式多种多样且效率低下；在没有直接编码EUI-48地址的RR类型的情况下，地址以不同的方式编码为所有者名称或以TXT记录的形式发布。
The specification in this document facilitates a more efficient, consistent, and reliable representation of (EUI-48, IP) mapping than was previously available.
本文档中的规范有助于（EUI-48，IP）映射比以前更高效、一致和可靠的表示。
The specification of the new RR types in this document has no effect on the address resolution behavior of any previously existing network processes or protocols. Proposals or specifications to modify or augment address resolution processes or protocols by making use of these RR types should specify how any address conflicts or use of multiple EUI48/EUI64 RRs are handled.
本文档中新RR类型的规范对任何以前存在的网络进程或协议的地址解析行为没有影响。通过使用这些RR类型修改或扩充地址解析过程或协议的提案或规范应规定如何处理任何地址冲突或使用多个EUI48/EUI64 RRs。
IANA has assigned the RR type value 108 (decimal) for EUI48 and 109 (decimal) for EUI64. The corresponding entries in the "Resource Record (RR) TYPEs" subregistry (http://www.iana.org/assignments/ dns-parameters/) match the following data:
IANA为EUI48分配了RR类型值108（十进制），为EUI64分配了109（十进制）。“资源记录（RR）类型”子区域中的相应条目(http://www.iana.org/assignments/ dns参数/）与以下数据匹配：
+-------+-------+-------------------+---------------+
| Type | Value | Meaning | Reference |
+-------+-------+-------------------+---------------+
| EUI48 | 108 | an EUI-48 address | this document |
| EUI64 | 109 | an EUI-64 address | this document |
+-------+-------+-------------------+---------------+
+-------+-------+-------------------+---------------+
| Type | Value | Meaning | Reference |
+-------+-------+-------------------+---------------+
| EUI48 | 108 | an EUI-48 address | this document |
| EUI64 | 109 | an EUI-64 address | this document |
+-------+-------+-------------------+---------------+
There are privacy concerns with the publication of link-layer addresses in the DNS. EUI-48 and EUI-64 addresses with the Local/Global bit zero [RFC7042] (referred to in [RFC4291] as the universal/local bit) are intended to represent unique identifiers for network connected equipment, notwithstanding many observed cases of duplication due to manufacturing errors, unauthorized use of Organizationally Unique Identifiers (OUIs), and address spoofing through configuration of network interfaces. Publication of EUI-48 or EUI-64 addresses in the DNS may result in privacy issues in the form of unique trackable identities that in some cases may be permanent.
DNS中链接层地址的发布存在隐私问题。本地/全局位为零[RFC7042]（在[RFC4291]中称为通用/本地位）的EUI-48和EUI-64地址旨在表示网络连接设备的唯一标识符，尽管观察到许多由于制造错误、未经授权使用组织唯一标识符（OUI）而导致的重复情况，通过配置网络接口进行地址欺骗。在DNS中发布EUI-48或EUI-64地址可能会导致隐私问题，其形式为独特的可跟踪身份，在某些情况下可能是永久性的。
For example, although IP addresses and DNS names for network devices typically change over time, EUI-48 and EUI-64 addresses configured on the same devices are normally far more stable (in many cases, effectively invariant). Publication of EUI-48 addresses associated with user devices in a way that could be mapped to assigned IP addresses would allow the behavior of those users to be tracked by third parties, regardless of where and how the user's device is connected to the Internet. This might well result in a loss of privacy for the user.
例如，尽管网络设备的IP地址和DNS名称通常会随时间而变化，但在相同设备上配置的EUI-48和EUI-64地址通常要稳定得多（在许多情况下，有效不变）。以可映射到指定IP地址的方式发布与用户设备相关联的EUI-48地址将允许第三方跟踪这些用户的行为，而不管用户设备在何处以及如何连接到互联网。这很可能会导致用户失去隐私。
The publication of EUI-48 or EUI-64 addresses associated with deployed equipment, using the mechanism described in this document or any other mechanism, has the potential to facilitate Media Access Control (MAC) cloning -- that is, facilitate link-layer attacks against deployed devices, e.g., to disrupt service or intercept data.
使用本文档中描述的机制或任何其他机制发布与已部署设备相关联的EUI-48或EUI-64地址，有可能促进媒体访问控制（MAC）克隆——即，促进针对已部署设备的链路层攻击，例如中断服务或截获数据。
These concerns can be mitigated by restricting access to DNS zones containing EUI48 or EUI64 RRs to specific, authorized clients and by provisioning them in DNS zones that exist in private namespaces only.
通过将对包含EUI48或EUI64 RRs的DNS区域的访问限制到特定的授权客户端，并在仅存在于私有名称空间中的DNS区域中设置它们，可以缓解这些问题。
This document recommends that EUI-48 or EUI-64 addresses SHOULD NOT be published in the public DNS.
本文件建议不在公共DNS中发布EUI-48或EUI-64地址。
The author acknowledges the contributions of Olafur Gudmundsson, Mark Smith, Andrew Sullivan, Roy Arends, Michael StJohns, Donald Eastlake III, Randy Bush, and John Klensin.
作者感谢Olafur Gudmundsson、Mark Smith、Andrew Sullivan、Roy Arends、Michael StJohns、Donald Eastlake III、Randy Bush和John Klesins的贡献。
[EUI48] IEEE, "Guidelines for use of a 48-bit Extended Unique Identifier (EUI-48)", <http://standards.ieee.org/develop/regauth/tut/eui48.pdf>.
[EUI48]IEEE，“48位扩展唯一标识符（EUI-48）的使用指南”<http://standards.ieee.org/develop/regauth/tut/eui48.pdf>.
[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)", November 2012, <http://standards.ieee.org/develop/regauth/tut/eui64.pdf>.
[EUI64]IEEE，“64位全局标识符（EUI-64）指南”，2012年11月<http://standards.ieee.org/develop/regauth/tut/eui64.pdf>.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987.
[RFC1034]Mockapetris，P.，“域名-概念和设施”，STD 13，RFC 1034，1987年11月。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC7042] Eastlake 3rd, D. and J. Abley, "IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters", BCP 141, RFC 7042, October 2013.
[RFC7042]Eastlake 3rd，D.和J.Abley，“IEEE802参数的IANA考虑因素和IETF协议及文档使用”，BCP 141，RFC 7042，2013年10月。
[NTRE038D] CRTC Interconnection Steering Committee (CISC) Network Working Group, "Implementation of IP Address Tracking in DOCSIS Networks (TIF18)", NTRE038D Consensus Report, October 2006, <http://www.crtc.gc.ca/public/cisc/nt/NTRE038D.doc>.
[NTRE038D]CRTC互连指导委员会（CISC）网络工作组，“在DOCSIS网络中实施IP地址跟踪（TIF18）”，NTRE038D共识报告，2006年10月<http://www.crtc.gc.ca/public/cisc/nt/NTRE038D.doc>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月。
Author's Address
作者地址
Joe Abley Dyn, Inc. 470 Moore Street London, ON N6C 2C2 Canada
Joe Abley Dyn，Inc.位于加拿大N6C 2C2的伦敦摩尔街470号
Phone: +1 519 670 9327
EMail: jabley@dyn.com
Phone: +1 519 670 9327
EMail: jabley@dyn.com