Network Working Group                                        S. Cheshire
Request for Comments: 5227                                    Apple Inc.
Updates: 826                                                   July 2008
Category: Standards Track
Network Working Group                                        S. Cheshire
Request for Comments: 5227                                    Apple Inc.
Updates: 826                                                   July 2008
Category: Standards Track

IPv4 Address Conflict Detection


Status of This Memo


This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

本文件规定了互联网社区的互联网标准跟踪协议,并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态,请参考当前版本的“互联网官方协议标准”(STD 1)。本备忘录的分发不受限制。



When two hosts on the same link attempt to use the same IPv4 address at the same time (except in rare special cases where this has been arranged by prior coordination), problems ensue for one or both hosts. This document describes (i) a simple precaution that a host can take in advance to help prevent this misconfiguration from happening, and (ii) if this misconfiguration does occur, a simple mechanism by which a host can passively detect, after the fact, that it has happened, so that the host or administrator may respond to rectify the problem.


Table of Contents


   1. Introduction ....................................................2
      1.1. Conventions and Terminology Used in This Document ..........4
      1.2. Relationship to RFC 826 ....................................5
           1.2.1. Broadcast ARP Replies ...............................7
      1.3. Applicability ..............................................7
   2. Address Probing, Announcing, Conflict Detection, and Defense ....9
      2.1. Probing an Address ........................................10
           2.1.1. Probe Details ......................................10
      2.2. Shorter Timeouts on Appropriate Network Technologies ......11
      2.3. Announcing an Address .....................................12
      2.4. Ongoing Address Conflict Detection and Address Defense ....12
      2.5. Continuing Operation ......................................14
      2.6. Broadcast ARP Replies .....................................14
   3. Why Are ARP Announcements Performed Using ARP Request
      Packets and Not ARP Reply Packets? .............................15
   4. Historical Note ................................................17
   5. Security Considerations ........................................17
   6. Acknowledgments ................................................18
   7. References .....................................................18
      7.1. Normative References ......................................18
      7.2. Informative References ....................................19
   1. Introduction ....................................................2
      1.1. Conventions and Terminology Used in This Document ..........4
      1.2. Relationship to RFC 826 ....................................5
           1.2.1. Broadcast ARP Replies ...............................7
      1.3. Applicability ..............................................7
   2. Address Probing, Announcing, Conflict Detection, and Defense ....9
      2.1. Probing an Address ........................................10
           2.1.1. Probe Details ......................................10
      2.2. Shorter Timeouts on Appropriate Network Technologies ......11
      2.3. Announcing an Address .....................................12
      2.4. Ongoing Address Conflict Detection and Address Defense ....12
      2.5. Continuing Operation ......................................14
      2.6. Broadcast ARP Replies .....................................14
   3. Why Are ARP Announcements Performed Using ARP Request
      Packets and Not ARP Reply Packets? .............................15
   4. Historical Note ................................................17
   5. Security Considerations ........................................17
   6. Acknowledgments ................................................18
   7. References .....................................................18
      7.1. Normative References ......................................18
      7.2. Informative References ....................................19
1. Introduction
1. 介绍

Historically, accidentally configuring two Internet hosts with the same IP address has often been an annoying and hard-to-diagnose problem.


This is unfortunate, because the existing Address Resolution Protocol (ARP) provides an easy way for a host to detect this kind of misconfiguration and report it to the user. The DHCP specification [RFC2131] briefly mentions the role of ARP in detecting misconfiguration, as illustrated in the following three excerpts from RFC 2131:


o the client SHOULD probe the newly received address, e.g., with ARP

o 客户端应探测新收到的地址,例如,使用ARP

o The client SHOULD perform a final check on the parameters (e.g., ARP for allocated network address)

o 客户端应对参数进行最终检查(例如,分配网络地址的ARP)

o If the client detects that the address is already in use (e.g., through the use of ARP), the client MUST send a DHCPDECLINE message to the server

o 如果客户端检测到地址已在使用中(例如,通过使用ARP),则客户端必须向服务器发送DHCPDecend消息

Unfortunately, the DHCP specification does not give any guidance to implementers concerning the number of ARP packets to send, the interval between packets, the total time to wait before concluding that an address may safely be used, or indeed even which kinds of packets a host should be listening for, in order to make this determination. It leaves unspecified the action a host should take if, after concluding that an address may safely be used, it subsequently discovers that it was wrong. It also fails to specify what precautions a DHCP client should take to guard against pathological failure cases, such as a DHCP server that repeatedly OFFERs the same address, even though it has been DECLINEd multiple times.


The authors of the DHCP specification may have been justified in thinking at the time that the answers to these questions seemed too simple, obvious, and straightforward to be worth mentioning, but unfortunately this left some of the burden of protocol design to each individual implementer. This document seeks to remedy this omission by clearly specifying the required actions for:


1. Determining whether use of an address is likely to lead to an addressing conflict. This includes (a) the case where the address is already actively in use by another host on the same link, and (b) the case where two hosts are inadvertently about to begin using the same address, and both are simultaneously in the process of probing to determine whether the address may safely be used (Section 2.1.).

1. 确定地址的使用是否可能导致地址冲突。这包括(a)地址已被同一链路上的另一主机积极使用的情况,以及(b)两台主机无意中即将开始使用同一地址的情况,并且两台主机同时处于探测过程中,以确定地址是否可以安全使用(第2.1节)。

2. Subsequent passive detection that another host on the network is inadvertently using the same address. Even if all hosts observe precautions to avoid using an address that is already in use, conflicts can still occur if two hosts are out of communication at the time of initial interface configuration. This could occur with wireless network interfaces if the hosts are temporarily out of range, or with Ethernet interfaces if the link between two Ethernet hubs is not functioning at the time of address configuration. A well-designed host will handle not only conflicts detected during interface configuration, but also conflicts detected later, for the entire duration of the time that the host is using the address (Section 2.4.).

2. 网络上的另一台主机无意中使用相同地址的后续被动检测。即使所有主机都遵守预防措施以避免使用已在使用的地址,如果在初始接口配置时两台主机失去通信,仍可能发生冲突。如果主机暂时超出范围,则无线网络接口可能会出现这种情况;如果两个以太网集线器之间的链路在地址配置时不起作用,则以太网接口可能会出现这种情况。设计良好的主机不仅可以处理在接口配置期间检测到的冲突,还可以在主机使用该地址的整个过程中处理以后检测到的冲突(第2.4节)。

3. Rate-limiting of address acquisition attempts in the case of an excessive number of repeated conflicts (Section 2.1.).

3. 在重复冲突次数过多的情况下,地址获取尝试的速率限制(第2.1节)。

The utility of IPv4 Address Conflict Detection (ACD) is not limited to DHCP clients. No matter how an address was configured, whether via manual entry by a human user, via information received from a DHCP server, or via any other source of configuration information,


detecting conflicts is useful. Upon detecting a conflict, the configuring agent should be notified of the error. In the case where the configuring agent is a human user, that notification may take the form of an error message on a screen, a Simple Network Management Protocol (SNMP) notification, or an error message sent via text message to a mobile phone. In the case of a DHCP server, that notification takes the form of a DHCP DECLINE message sent to the server. In the case of configuration by some other kind of software, that notification takes the form of an error indication to the software in question, to inform it that the address it selected is in conflict with some other host on the network. The configuring software may choose to cease network operation, or it may automatically select a new address so that the host may re-establish IP connectivity as soon as possible.


Allocation of IPv4 Link-Local Addresses [RFC3927] can be thought of as a special case of this mechanism, where the configuring agent is a pseudo-random number generator, and the action it takes upon being notified of a conflict is to pick a different random number and try again. In fact, this is exactly how IPv4 Link-Local Addressing was implemented in Mac OS 9 back in 1998. If the DHCP client failed to get a response from any DHCP server, it would simply make up a fake response containing a random 169.254.x.x address. If the ARP module reported a conflict for that address, then the DHCP client would try again, making up a new random 169.254.x.x address as many times as was necessary until it succeeded. Implementing ACD as a standard feature of the networking stack has the side effect that it means that half the work for IPv4 Link-Local Addressing is already done.

IPv4链路本地地址分配[RFC3927]可视为该机制的一种特殊情况,其中配置代理是一个伪随机数生成器,在收到冲突通知时,它采取的行动是选择一个不同的随机数并重试。事实上,这正是1998年Mac OS 9中IPv4链路本地寻址的实现方式。如果DHCP客户端无法从任何DHCP服务器获得响应,它只会生成一个包含随机169.254.x.x地址的假响应。如果ARP模块报告该地址存在冲突,则DHCP客户端将重试,根据需要多次创建新的随机169.254.x.x地址,直到成功。将ACD实现为网络堆栈的标准功能会产生副作用,这意味着IPv4链路本地寻址的一半工作已经完成。

1.1. Conventions and Terminology Used in This Document
1.1. 本文件中使用的约定和术语

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 "Key words for use in RFCs to Indicate Requirement Levels" [RFC2119].


Wherever this document uses the term 'sender IP address' or 'target IP address' in the context of an ARP packet, it is referring to the fields of the ARP packet identified in the ARP specification [RFC826] as 'ar$spa' (Sender Protocol Address) and 'ar$tpa' (Target Protocol Address), respectively. For the usage of ARP described in this document, each of these fields always contains an IPv4 address.


In this document, the term 'ARP Probe' is used to refer to an ARP Request packet, broadcast on the local link, with an all-zero 'sender IP address'. The 'sender hardware address' MUST contain the hardware address of the interface sending the packet. The 'sender IP address' field MUST be set to all zeroes, to avoid polluting ARP caches in

在本文档中,术语“ARP Probe”用于指在本地链路上广播的ARP请求数据包,其“发送方IP地址”为零。“发送方硬件地址”必须包含发送数据包的接口的硬件地址。“发送方IP地址”字段必须设置为全零,以避免污染中的ARP缓存

other hosts on the same link in the case where the address turns out to be already in use by another host. The 'target hardware address' field is ignored and SHOULD be set to all zeroes. The 'target IP address' field MUST be set to the address being probed. An ARP Probe conveys both a question ("Is anyone using this address?") and an implied statement ("This is the address I hope to use.").


In this document, the term 'ARP Announcement' is used to refer to an ARP Request packet, broadcast on the local link, identical to the ARP Probe described above, except that both the sender and target IP address fields contain the IP address being announced. It conveys a stronger statement than an ARP Probe, namely, "This is the address I am now using."


The following timing constants used in this protocol are referenced in Section 2, which describes the operation of the protocol in detail. (Note that the values listed here are fixed constants; they are not intended to be modifiable by implementers, operators, or end users. These constants are given symbolic names here to facilitate the writing of future standards that may want to reference this document with different values for these named constants; however, at the present time no such future standards exist.)


PROBE_WAIT 1 second (initial random delay) PROBE_NUM 3 (number of probe packets) PROBE_MIN 1 second (minimum delay until repeated probe) PROBE_MAX 2 seconds (maximum delay until repeated probe) ANNOUNCE_WAIT 2 seconds (delay before announcing) ANNOUNCE_NUM 2 (number of Announcement packets) ANNOUNCE_INTERVAL 2 seconds (time between Announcement packets) MAX_CONFLICTS 10 (max conflicts before rate-limiting) RATE_LIMIT_INTERVAL 60 seconds (delay between successive attempts) DEFEND_INTERVAL 10 seconds (minimum interval between defensive ARPs) 1.2. Relationship to RFC 826

探测等待1秒(初始随机延迟)探测数量3(探测数据包数量)探测最少1秒(重复探测之前的最小延迟)探测最多2秒(重复探测之前的最大延迟)宣布等待2秒(宣布之前的延迟)宣布数量2(宣布数据包数量)宣布间隔2秒(公告数据包之间的时间)最大冲突10(速率限制前的最大冲突)速率限制间隔60秒(连续尝试之间的延迟)防御间隔10秒(防御ARP之间的最小间隔)1.2.与RFC 826的关系

This document does not modify any of the protocol rules in RFC 826. It does not modify the packet format, or the meaning of any of the fields. The existing rules for "Packet Generation" and "Packet Reception" still apply exactly as specified in RFC 826.

本文档不修改RFC 826中的任何协议规则。它不会修改数据包格式或任何字段的含义。“包生成”和“包接收”的现有规则仍然完全适用于RFC 826中指定的规则。

This document expands on RFC 826 by specifying:

本文件在RFC 826的基础上进行了扩展,具体说明如下:

(1) that a specific ARP Request should be generated when an interface is configured, to discover if the address is already in use, and

(1) 配置接口时应生成特定的ARP请求,以发现地址是否已在使用,以及

(2) an additional trivial test that should be performed on each received ARP packet, to facilitate passive ongoing conflict detection. This additional test creates no additional packet overhead on the network (no additional packets are sent) and negligible additional CPU burden on hosts, since every host implementing ARP is *already* required to process every received ARP packet according to the Packet Reception rules specified in RFC 826. These rules already include checking to see if the 'sender IP address' of the ARP packet appears in any of the entries in the host's ARP cache; the additional test is simply to check to see if the 'sender IP address' is the host's *own* IP address, potentially as little as a single additional machine instruction on many architectures.

(2) 对每个接收到的ARP数据包进行额外的简单测试,以便于进行被动冲突检测。由于每个实现ARP的主机*已经*需要根据RFC 826中规定的数据包接收规则处理每个接收到的ARP数据包,因此该附加测试不会在网络上产生额外的数据包开销(不会发送额外的数据包),主机上的CPU负担可以忽略不计。这些规则已经包括检查ARP数据包的“发送方IP地址”是否出现在主机ARP缓存中的任何条目中;额外的测试只是检查“发送方IP地址”是否是主机的*自己的*IP地址,在许多体系结构上可能只有一条额外的机器指令。

As already specified in RFC 826, an ARP Request packet serves two functions, an assertion and a question:

如RFC 826中所述,ARP请求包提供两个功能,一个断言和一个问题:

* Assertion: The fields 'ar$sha' (Sender Hardware Address) and 'ar$spa' (Sender Protocol Address) together serve as an assertion of a fact: that the stated Protocol Address is mapped to the stated Hardware Address.

* 断言:字段“ar$sha”(发送方硬件地址)和“ar$spa”(发送方协议地址)一起作为一个事实的断言:声明的协议地址映射到声明的硬件地址。

* Question: The fields 'ar$tha' (Target Hardware Address, zero) and 'ar$tpa' (Target Protocol Address) serve as a question, asking, for the stated Protocol Address, to which Hardware Address it is mapped.

* 问题:“ar$tha”(目标硬件地址,零)和“ar$tpa”(目标协议地址)字段用作问题,询问所述协议地址,它映射到哪个硬件地址。

This document clarifies what it means to have one without the other.


Some readers pointed out that it is probably impossible to ask any truly pure question; asking any question necessarily invites speculation about why the interrogator wants to know the answer. Just as someone pointing to an empty seat and asking, "Is anyone sitting here?" implies an unspoken "... because if not then I will," the same is true here. An ARP Probe with an all-zero 'sender IP address' may ostensibly be merely asking an innocent question ("Is anyone using this address?"), but an intelligent implementation that knows how IPv4 Address Conflict Detection works should be able to recognize this question as the precursor to claiming the address.


Consequently, if that implementation is also, at that exact moment, in the process of asking the very same question, it should recognize that they can't both sit in the same seat, so it would be prudent to ask about some other seat.


1.2.1. Broadcast ARP Replies
1.2.1. 广播ARP应答

In some applications of IPv4 Address Conflict Detection (ACD), it may be advantageous to deliver ARP Replies using broadcast instead of unicast because this allows address conflicts to be detected sooner than might otherwise happen. For example, "Dynamic Configuration of IPv4 Link-Local Addresses" [RFC3927] uses ACD exactly as specified here, but additionally specifies that ARP Replies should be sent using broadcast, because in that context the trade-off of increased broadcast traffic in exchange for improved reliability and fault-tolerance was deemed to be an appropriate one. There may be other future specifications where the same trade-off is appropriate. Additional details are given in Section 2.6, "Broadcast ARP Replies".


RFC 826 implies that replies to ARP Requests are usually delivered using unicast, but it is also acceptable to deliver ARP Replies using broadcast. The Packet Reception rules in RFC 826 specify that the content of the 'ar$spa' field should be processed *before* examining the 'ar$op' field, so any host that correctly implements the Packet Reception algorithm specified in RFC 826 will correctly handle ARP Replies delivered via link-layer broadcast.

RFC 826意味着对ARP请求的回复通常使用单播发送,但也可以使用广播发送ARP回复。RFC 826中的数据包接收规则规定,在*检查“ar$op”字段之前,*应处理“ar$spa”字段的内容,因此任何正确实现RFC 826中指定的数据包接收算法的主机都将正确处理通过链路层广播发送的ARP回复。

1.3. Applicability
1.3. 适用性

This specification applies to all IEEE 802 Local Area Networks (LANs) [802], including Ethernet [802.3], Token-Ring [802.5], and IEEE 802.11 wireless LANs [802.11], as well as to other link-layer technologies that operate at data rates of at least 1 Mb/s, have a round-trip latency of at most one second, and use ARP [RFC826] to map from IP addresses to link-layer hardware addresses. Wherever this document uses the term "IEEE 802", the text applies equally to any of these network technologies.

本规范适用于所有IEEE 802局域网(LAN)[802],包括以太网[802.3]、令牌环[802.5]和IEEE 802.11无线局域网[802.11],以及以至少1 Mb/s的数据速率运行、具有最多1秒的往返延迟且使用ARP[RFC826]的其他链路层技术从IP地址映射到链路层硬件地址。本文件使用术语“IEEE 802”时,本文本同样适用于任何此类网络技术。

Link-layer technologies that support ARP but operate at rates below 1 Mb/s or latencies above one second will still work correctly with this protocol, but more often may have to handle late conflicts detected after the Probing phase has completed. On these kinds of links, it may be desirable to specify different values for the following parameters:

支持ARP但以低于1 Mb/s的速率运行或延迟超过1秒的链路层技术仍能正确使用此协议,但更多情况下可能需要处理探测阶段完成后检测到的延迟冲突。在这些类型的链路上,可能需要为以下参数指定不同的值:

(a) PROBE_NUM, PROBE_MIN, and PROBE_MAX, the number of, and interval between, ARP Probes, explained in Section 2.1.

(a) PROBE_NUM、PROBE_MIN和PROBE_MAX,ARP探测的数量和间隔,如第2.1节所述。

(b) ANNOUNCE_NUM and ANNOUNCE_INTERVAL, the number of, and interval between, ARP Announcements, explained in Section 2.3.

(b) 通告数量和通告间隔,ARP通告的数量和间隔,如第2.3节所述。

(c) RATE_LIMIT_INTERVAL and MAX_CONFLICTS, controlling the maximum rate at which address claiming may be attempted, explained in Section 2.1.

(c) RATE_LIMIT_INTERVAL和MAX_冲突,控制可能尝试地址声明的最大速率,如第2.1节所述。

(d) DEFEND_INTERVAL, the time interval between conflicting ARPs below which a host MUST NOT attempt to defend its address, explained in Section 2.4.

(d) Defense_INTERVAL,冲突ARP之间的时间间隔,低于此时间间隔主机不得尝试保护其地址,如第2.4节所述。

Link-layer technologies that do not support ARP may be able to use other techniques for determining whether a particular IP address is currently in use. However, implementing Address Conflict Detection for such networks is outside the scope of this document.


For the protocol specified in this document to be effective, it is not necessary that all hosts on the link implement it. For a given host implementing this specification to be protected against accidental address conflicts, all that is required is that the peers on the same link correctly implement the ARP protocol as given in RFC 826. To be specific, when a peer host receives an ARP Request where the Target Protocol Address of the ARP Request matches (one of) that host's IP address(es) configured on that interface, then as long as it properly responds with a correctly-formatted ARP Reply, the querying host will be able to detect that the address is already in use.

为了使本文档中指定的协议生效,链路上的所有主机都不必实现该协议。对于实现本规范的给定主机,要防止意外地址冲突,所需的只是同一链路上的对等方正确实现RFC 826中给出的ARP协议。具体来说,当对等主机接收到ARP请求时,如果ARP请求的目标协议地址与该接口上配置的主机IP地址(其中一个)匹配,则只要该主机以正确格式的ARP应答正确响应,查询主机将能够检测到该地址已在使用中。

The specifications in this document allow hosts to detect conflicts between two hosts using the same address on the same physical link. ACD does not detect conflicts between two hosts using the same address on different physical links, and indeed it should not. For example, the address [RFC1918] is in use by countless devices on countless private networks throughout the world, and this is not a conflict, because they are on different links. It would only be a conflict if two such devices were to be connected to the same link, and when this happens (as it sometimes does), this is a perfect example of a situation where ACD is extremely useful to detect and report (and/or automatically correct) this error.


For the purposes of this document, a set of hosts is considered to be "on the same link" if:


- when any host, A, from that set, sends a packet to any other host, B, in that set, using unicast, multicast, or broadcast, the entire link-layer packet payload arrives unmodified, and

- 当来自该集合的任何主机A使用单播、多播或广播向该集合中的任何其他主机B发送分组时,整个链路层分组有效载荷未经修改地到达,并且

- a broadcast sent over that link by any host from that set of hosts can be received by every other host in that set.

- 任何主机通过该链路从该主机集中发送的广播都可以被该主机集中的所有其他主机接收。

The link-layer *header* may be modified, such as in Token Ring Source Routing [802.5], but not the link-layer *payload*. In particular, if any device forwarding a packet modifies any part of the IP header or IP payload, then the packet is no longer considered to be on the same link. This means that the packet may pass through devices such as repeaters, bridges, hubs, or switches and still be considered to be on the same link for the purpose of this document, but not through a device such as an IP router that decrements the TTL or otherwise modifies the IP header.


Where this document uses the term "host", it applies equally to interfaces on routers or other multi-homed hosts, regardless of whether the host/router is currently forwarding packets. In many cases a router will be critical network infrastructure with an IP address that is locally well known and assumed to be relatively constant. For example, the address of the default router is one of the parameters that a DHCP server typically communicates to its clients, and (at least until mechanisms like DHCP Reconfigure [RFC3203] become widely implemented) there isn't any practical way for the DHCP server to inform clients if that address changes. Consequently, for such devices, handling conflicts by picking a new IP address is not a good option. In those cases, option (c) in Section 2.4 ("Ongoing Address Conflict Detection and Address Defense") applies.


However, even when a device is manually configured with a fixed address, having some other device on the network claiming to have the same IP address will pollute peer ARP caches and prevent reliable communication, so it is still helpful to inform the operator. If a conflict is detected at the time the operator sets the fixed manual address, then it is helpful to inform the operator immediately; if a conflict is detected subsequently, it is helpful to inform the operator via some appropriate asynchronous communication channel. Even though reliable communication via the conflicted address is not possible, it may still be possible to inform the operator via some other communication channel that is still operating, such as via some other interface on the router, via a dynamic IPv4 link-local address, via a working IPv6 address, or even via some completely different non-IP technology such as a locally-attached screen or serial console.


2. Address Probing, Announcing, Conflict Detection, and Defense
2. 解决探测、宣布、冲突检测和防御问题

This section describes initial probing to safely determine whether an address is already in use, announcing the chosen address, ongoing conflict checking, and optional use of broadcast ARP Replies to provide faster conflict detection.


2.1. Probing an Address
2.1. 探查地址

Before beginning to use an IPv4 address (whether received from manual configuration, DHCP, or some other means), a host implementing this specification MUST test to see if the address is already in use, by broadcasting ARP Probe packets. This also applies when a network interface transitions from an inactive to an active state, when a computer awakes from sleep, when a link-state change signals that an Ethernet cable has been connected, when an 802.11 wireless interface associates with a new base station, or when any other change in connectivity occurs where a host becomes actively connected to a logical link.


A host MUST NOT perform this check periodically as a matter of course. This would be a waste of network bandwidth, and is unnecessary due to the ability of hosts to passively discover conflicts, as described in Section 2.4.


2.1.1. Probe Details
2.1.1. 探测细节

A host probes to see if an address is already in use by broadcasting an ARP Request for the desired address. The client MUST fill in the 'sender hardware address' field of the ARP Request with the hardware address of the interface through which it is sending the packet. The 'sender IP address' field MUST be set to all zeroes; this is to avoid polluting ARP caches in other hosts on the same link in the case where the address turns out to be already in use by another host. The 'target hardware address' field is ignored and SHOULD be set to all zeroes. The 'target IP address' field MUST be set to the address being probed. An ARP Request constructed this way, with an all-zero 'sender IP address', is referred to as an 'ARP Probe'.


When ready to begin probing, the host should then wait for a random time interval selected uniformly in the range zero to PROBE_WAIT seconds, and should then send PROBE_NUM probe packets, each of these probe packets spaced randomly and uniformly, PROBE_MIN to PROBE_MAX seconds apart. This initial random delay helps ensure that a large number of hosts powered on at the same time do not all send their initial probe packets simultaneously.

当准备好开始探测时,主机应等待在0到PROBE_wait秒范围内均匀选择的随机时间间隔,然后发送PROBE_NUM PROBE数据包,这些数据包中的每个数据包随机均匀地间隔,PROBE_MIN到PROBE_MAX秒间隔。此初始随机延迟有助于确保同时通电的大量主机不会同时发送其初始探测数据包。

If during this period, from the beginning of the probing process until ANNOUNCE_WAIT seconds after the last probe packet is sent, the host receives any ARP packet (Request *or* Reply) on the interface where the probe is being performed, where the packet's 'sender IP address' is the address being probed for, then the host MUST treat this address as being in use by some other host, and should indicate to the configuring agent (human operator, DHCP server, etc.) that the proposed address is not acceptable.


In addition, if during this period the host receives any ARP Probe where the packet's 'target IP address' is the address being probed for, and the packet's 'sender hardware address' is not the hardware address of any of the host's interfaces, then the host SHOULD similarly treat this as an address conflict and signal an error to the configuring agent as above. This can occur if two (or more) hosts have, for whatever reason, been inadvertently configured with the same address, and both are simultaneously in the process of probing that address to see if it can safely be used.


NOTE: The check that the packet's 'sender hardware address' is not the hardware address of any of the host's interfaces is important. Some kinds of Ethernet hub (often called a "buffered repeater") and many wireless access points may "rebroadcast" any received broadcast packets to all recipients, including the original sender itself. For this reason, the precaution described above is necessary to ensure that a host is not confused when it sees its own ARP packets echoed back.


A host implementing this specification MUST take precautions to limit the rate at which it probes for new candidate addresses: if the host experiences MAX_CONFLICTS or more address conflicts on a given interface, then the host MUST limit the rate at which it probes for new addresses on this interface to no more than one attempted new address per RATE_LIMIT_INTERVAL. This is to prevent catastrophic ARP storms in pathological failure cases, such as a defective DHCP server that repeatedly assigns the same address to every host that asks for one. This rate-limiting rule applies not only to conflicts experienced during the initial probing phase, but also to conflicts experienced later, as described in Section 2.4 "Ongoing Address Conflict Detection and Address Defense".


If, by ANNOUNCE_WAIT seconds after the transmission of the last ARP Probe no conflicting ARP Reply or ARP Probe has been received, then the host has successfully determined that the desired address may be used safely.


2.2. Shorter Timeouts on Appropriate Network Technologies
2.2. 在适当的网络技术上缩短超时时间

Network technologies may emerge for which shorter delays are appropriate than those required by this document. A subsequent IETF publication may be produced providing guidelines for different values for PROBE_WAIT, PROBE_NUM, PROBE_MIN, and PROBE_MAX on those technologies.


If the situation arises where different hosts on a link are using different timing parameters, this does not cause any problems. This protocol is not dependent on all hosts on a link implementing the


same version of the protocol; indeed, this protocol is not dependent on all hosts on a link implementing the protocol at all. All that is required is that all hosts implement ARP as specified in RFC 826, and correctly answer ARP Requests they receive. In the situation where different hosts are using different timing parameters, all that will happen is that some hosts will configure their interfaces more quickly than others. In the unlikely event that an address conflict is not detected during the address probing phase, the conflict will still be detected by the Ongoing Address Conflict Detection described below in Section 2.4.

议定书的同一版本;实际上,该协议根本不依赖于实现该协议的链路上的所有主机。所需要的只是所有主机按照RFC 826中的规定实现ARP,并正确地响应它们接收到的ARP请求。在不同主机使用不同定时参数的情况下,只会出现一些主机比其他主机更快地配置其接口的情况。在地址探测阶段未检测到地址冲突的不太可能的情况下,仍将通过下面第2.4节中描述的持续地址冲突检测来检测冲突。

2.3. Announcing an Address
2.3. 发表演说

Having probed to determine that a desired address may be used safely, a host implementing this specification MUST then announce that it is commencing to use this address by broadcasting ANNOUNCE_NUM ARP Announcements, spaced ANNOUNCE_INTERVAL seconds apart. An ARP Announcement is identical to the ARP Probe described above, except that now the sender and target IP addresses are both set to the host's newly selected IPv4 address. The purpose of these ARP Announcements is to make sure that other hosts on the link do not have stale ARP cache entries left over from some other host that may previously have been using the same address. The host may begin legitimately using the IP address immediately after sending the first of the two ARP Announcements; the sending of the second ARP Announcement may be completed asynchronously, concurrent with other networking operations the host may wish to perform.

在探测以确定所需地址是否可以安全使用后,实施本规范的主机必须通过广播annound_NUM ARP announces来宣布其开始使用该地址,广播间隔为秒。ARP公告与上述ARP探测相同,只是现在发送方和目标IP地址都设置为主机新选择的IPv4地址。这些ARP公告的目的是确保链路上的其他主机没有从以前可能使用相同地址的其他主机遗留的过时ARP缓存项。在发送两个ARP公告中的第一个之后,主机可以立即开始合法使用IP地址;第二个ARP公告的发送可以异步完成,与主机可能希望执行的其他联网操作同时完成。

2.4. Ongoing Address Conflict Detection and Address Defense
2.4. 正在进行的地址冲突检测和地址防御

Address Conflict Detection is not limited to only the time of initial interface configuration, when a host is sending ARP Probes. Address Conflict Detection is an ongoing process that is in effect for as long as a host is using an address. At any time, if a host receives an ARP packet (Request *or* Reply) where the 'sender IP address' is (one of) the host's own IP address(es) configured on that interface, but the 'sender hardware address' does not match any of the host's own interface addresses, then this is a conflicting ARP packet, indicating some other host also thinks it is validly using this address. To resolve the address conflict, a host MUST respond to a conflicting ARP packet as described in either (a), (b), or (c) below:


(a) Upon receiving a conflicting ARP packet, a host MAY elect to immediately cease using the address, and signal an error to the configuring agent as described above.

(a) 在接收到冲突的ARP分组时,主机可以选择立即停止使用该地址,并如上所述向配置代理发送错误信号。

(b) If a host currently has active TCP connections or other reasons to prefer to keep the same IPv4 address, and it has not seen any other conflicting ARP packets within the last DEFEND_INTERVAL seconds, then it MAY elect to attempt to defend its address by recording the time that the conflicting ARP packet was received, and then broadcasting one single ARP Announcement, giving its own IP and hardware addresses as the sender addresses of the ARP, with the 'target IP address' set to its own IP address, and the 'target hardware address' set to all zeroes. Having done this, the host can then continue to use the address normally without any further special action. However, if this is not the first conflicting ARP packet the host has seen, and the time recorded for the previous conflicting ARP packet is recent, within DEFEND_INTERVAL seconds, then the host MUST immediately cease using this address and signal an error to the configuring agent as described above. This is necessary to ensure that two hosts do not get stuck in an endless loop with both hosts trying to defend the same address.

(b) 如果主机当前有活动的TCP连接或出于其他原因希望保留相同的IPv4地址,并且在最后的保护间隔秒内没有看到任何其他冲突的ARP数据包,那么它可以选择通过记录接收冲突的ARP数据包的时间来尝试保护其地址,然后广播一个ARP公告,给出自己的IP和硬件地址作为ARP的发送方地址,“目标IP地址”设置为自己的IP地址,“目标硬件地址”设置为全零。完成此操作后,主机可以继续正常使用该地址,而无需任何进一步的特殊操作。但是,如果这不是主机看到的第一个冲突ARP数据包,并且前一个冲突ARP数据包记录的时间是最近的,在保护间隔秒内,则主机必须立即停止使用此地址,并如上所述向配置代理发送错误信号。这是必要的,以确保两台主机不会陷入一个无休止的循环,因为两台主机都试图保护相同的地址。

(c) If a host has been configured such that it should not give up its address under any circumstances (perhaps because it is the kind of device that needs to have a well-known stable IP address, such as a link's default router or a DNS server) then it MAY elect to defend its address indefinitely. If such a host receives a conflicting ARP packet, then it should take appropriate steps to log useful information such as source Ethernet address from the ARP packet, and inform an administrator of the problem. The number of such notifications should be appropriately controlled to prevent an excessive number of error reports being generated. If the host has not seen any other conflicting ARP packets recently, within the last DEFEND_INTERVAL seconds, then it MUST record the time that the conflicting ARP packet was received, and then broadcast one single ARP Announcement, giving its own IP and hardware addresses. Having done this, the host can then continue to use the address normally without any further special action. However, if this is not the first conflicting ARP packet the host has seen, and the time recorded for the previous conflicting ARP packet is within DEFEND_INTERVAL seconds, then the host MUST NOT send another defensive ARP Announcement. This is necessary to ensure that two misconfigured hosts do not get stuck in an endless loop flooding the network with broadcast traffic while they both try to defend the same address.

(c) 如果主机已配置为在任何情况下都不应放弃其地址(可能是因为它是一种需要具有众所周知的稳定IP地址的设备,如链路的默认路由器或DNS服务器),那么它可能会选择无限期地保护其地址。如果这样的主机接收到冲突的ARP数据包,那么它应该采取适当的步骤记录有用的信息,例如来自ARP数据包的源以太网地址,并将问题通知管理员。应适当控制此类通知的数量,以防止生成过多的错误报告。如果主机最近在最近的保护间隔秒内没有看到任何其他冲突的ARP数据包,则必须记录接收冲突ARP数据包的时间,然后广播一个ARP公告,给出其自己的IP和硬件地址。完成此操作后,主机可以继续正常使用该地址,而无需任何进一步的特殊操作。但是,如果这不是主机看到的第一个冲突ARP数据包,并且前一个冲突ARP数据包记录的时间在防御间隔秒内,则主机不得发送另一个防御ARP公告。这是必要的,以确保两个配置错误的主机不会陷入一个无限循环中,当它们都试图保护同一地址时,网络中充斥着广播流量。

A host wishing to provide reliable network operation MUST respond to conflicting ARP packets as described in (a), (b), or (c) above. Ignoring conflicting ARP packets results in seemingly random network failures that can be hard to diagnose and very frustrating for human users.


Forced address reconfiguration may be disruptive, causing TCP (and other transport-layer) connections to be broken. However, such disruptions should be exceedingly rare, and if inadvertent address duplication happens, then disruption of communication is inevitable. It is not possible for two different hosts using the same IP address on the same network to operate reliably.


Before abandoning an address due to a conflict, hosts SHOULD actively attempt to reset any existing connections using that address. This mitigates some security threats posed by address reconfiguration, as discussed in Section 5.


For most client machines that do not need a fixed IP address, immediately requesting the configuring agent (human user, DHCP client, etc.) to configure a new address as soon as the conflict is detected is the best way to restore useful communication as quickly as possible. The mechanism described above of broadcasting a single ARP Announcement to defend the address mitigates the problem somewhat, by helping to improve the chance that one of the two conflicting hosts may be able to retain its address.


2.5. Continuing Operation
2.5. 持续经营

From the time a host sends its first ARP Announcement, until the time it ceases using that IP address, the host MUST answer ARP Requests in the usual way required by the ARP specification [RFC826]. Specifically, this means that whenever a host receives an ARP Request, that's not a conflicting ARP packet as described above in Section 2.4, where the 'target IP address' of the ARP Request is (one of) the host's own IP address(es) configured on that interface, the host MUST respond with an ARP Reply as described in RFC 826. This applies equally for both standard ARP Requests with non-zero sender IP addresses and Probe Requests with all-zero sender IP addresses.

从主机发送其第一个ARP公告开始,直到停止使用该IP地址为止,主机必须按照ARP规范[RFC826]要求的常规方式响应ARP请求。具体而言,这意味着每当主机接收到ARP请求时,该请求不是上文第2.4节所述的冲突ARP数据包,其中ARP请求的“目标IP地址”是在该接口上配置的主机自己的IP地址之一,主机必须按照RFC 826中所述的ARP回复进行响应。这同样适用于具有非零发送方IP地址的标准ARP请求和具有所有零发送方IP地址的探测请求。

2.6. Broadcast ARP Replies
2.6. 广播ARP应答

In a carefully-run network with manually-assigned addresses, or a network with a reliable DHCP server and reliable DHCP clients, address conflicts should occur only in rare failure scenarios, so the passive monitoring described above in Section 2.4 is adequate. If two hosts are using the same IP address, then sooner or later one host or the other will broadcast an ARP Request, which the other will see, allowing the conflict to be detected and consequently resolved.


It is possible, however, that a conflicting configuration may persist for a short time before it is detected. Suppose that two hosts, A and B, have been inadvertently assigned the same IP address, X. Suppose further that at the time they were both probing to determine


whether the address could safely be used, the communication link between them was non-functional for some reason, so neither detected the conflict at interface-configuration time. Suppose now that the communication link is restored, and a third host, C, broadcasts an ARP Request for address X. Unaware of any conflict, both hosts A and B will send unicast ARP Replies to host C. Host C will see both Replies, and may be a little confused, but neither host A nor B will see the other's Reply, and neither will immediately detect that there is a conflict to be resolved. Hosts A and B will continue to be unaware of the conflict until one or other broadcasts an ARP Request of their own.


If quicker conflict detection is desired, this may be achieved by having hosts send ARP Replies using link-level broadcast, instead of sending only ARP Requests via broadcast, and Replies via unicast. This is NOT RECOMMENDED for general use, but other specifications building on IPv4 ACD may choose to specify broadcast ARP Replies if appropriate. For example, "Dynamic Configuration of IPv4 Link-Local Addresses" [RFC3927] specifies broadcast ARP Replies because in that context, detection of address conflicts using IPv4 ACD is not merely a backup precaution to detect failures of some other configuration mechanism; detection of address conflicts using IPv4 ACD is the sole configuration mechanism.

如果需要更快的冲突检测,这可以通过让主机使用链路级广播发送ARP应答来实现,而不是仅通过广播发送ARP请求,通过单播发送应答。这不建议用于一般用途,但基于IPv4 ACD的其他规范可能会选择指定广播ARP应答(如果适用)。例如,“IPv4链路本地地址的动态配置”[RFC3927]指定广播ARP应答,因为在该上下文中,使用IPv4 ACD检测地址冲突不仅仅是检测某些其他配置机制故障的备份预防措施;使用IPv4 ACD检测地址冲突是唯一的配置机制。

Sending ARP Replies using broadcast does increase broadcast traffic, but in the worst case by no more than a factor of two. In the traditional usage of ARP, a unicast ARP Reply only occurs in response to a broadcast ARP Request, so sending these via broadcast instead means that we generate at most one broadcast Reply in response to each existing broadcast Request. On many networks, ARP traffic is such an insignificant proportion of the total traffic that doubling it makes no practical difference. However, this may not be true of all networks, so broadcast ARP Replies SHOULD NOT be used universally. Broadcast ARP Replies should be used where the benefit of faster conflict detection outweighs the cost of increased broadcast traffic and increased packet processing load on the participant network hosts.


3. Why Are ARP Announcements Performed Using ARP Request Packets and Not ARP Reply Packets?

3. 为什么使用ARP请求数据包而不是ARP回复数据包来执行ARP公告?

During IETF deliberation of IPv4 Address Conflict Detection from 2000 to 2008, a question that was asked repeatedly was, "Shouldn't ARP Announcements be performed using gratuitous ARP Reply packets?"


On the face of it, this seems reasonable. A conventional ARP Reply is an answer to a question. If in fact no question had been asked, then it would be reasonable to describe such a reply as gratuitous.


The term "gratuitous reply" would seem to apply perfectly to an ARP Announcement: an answer to an implied question that in fact no one asked.


However reasonable this may seem in principle, in practice there are two reasons that swing the argument in favor of using ARP Request packets. One is historical precedent, and the other is pragmatism.


The historical precedent is that (as described above in Section 4) Gratuitous ARP is documented in Stevens Networking [Ste94] as using ARP Request packets. BSD Unix, Microsoft Windows, Mac OS 9, Mac OS X, etc., all use ARP Request packets as described in Stevens. At this stage, trying to mandate that they all switch to using ARP Reply packets would be futile.

历史先例是(如上文第4节所述),Stevens Networking[Ste94]将无偿ARP记录为使用ARP请求数据包。BSD Unix、Microsoft Windows、Mac OS 9、Mac OS X等都使用Stevens中描述的ARP请求包。在这个阶段,试图强制要求他们全部改用ARP应答包将是徒劳的。

The practical reason is that ARP Request packets are more likely to work correctly with more existing ARP implementations, some of which may not implement RFC 826 entirely correctly. The Packet Reception rules in RFC 826 state that the opcode is the last thing to check in packet processing, so it really shouldn't matter, but there may be "creative" implementations that have different packet processing depending on the 'ar$op' field, and there are several reasons why these are more likely to accept gratuitous ARP Requests than gratuitous ARP Replies:

实际原因是,ARP请求包更有可能在更多现有ARP实现中正常工作,其中一些可能无法完全正确地实现RFC 826。RFC 826中的数据包接收规则规定,操作码是数据包处理中最后一个要检查的内容,因此这并不重要,但根据“ar$op”字段的不同,可能存在具有不同数据包处理的“创造性”实现,与免费ARP回复相比,他们更愿意接受免费ARP请求的原因有几个:

* An incorrect ARP implementation may expect that ARP Replies are only sent via unicast. RFC 826 does not say this, but an incorrect implementation may assume it; the "principle of least surprise" dictates that where there are two or more ways to solve a networking problem that are otherwise equally good, the one with the fewest unusual properties is the one likely to have the fewest interoperability problems with existing implementations. An ARP Announcement needs to broadcast information to all hosts on the link. Since ARP Request packets are always broadcast, and ARP Reply packets are not, receiving an ARP Request packet via broadcast is less surprising than receiving an ARP Reply packet via broadcast.

* 不正确的ARP实现可能期望ARP回复仅通过单播发送。RFC 826没有这样说,但是一个不正确的实现可能会假定它;“最少意外原则”规定,如果有两种或两种以上的方法可以解决同样好的网络问题,那么具有最少不寻常属性的方法可能是与现有实现具有最少互操作性问题的方法。ARP公告需要向链路上的所有主机广播信息。由于ARP请求数据包始终是广播的,而ARP应答数据包则不是广播的,因此通过广播接收ARP请求数据包比通过广播接收ARP应答数据包更令人惊讶。

* An incorrect ARP implementation may expect that ARP Replies are only received in response to ARP Requests that have been issued recently by that implementation. Unexpected unsolicited Replies may be ignored.

* 不正确的ARP实现可能期望仅在响应该实现最近发出的ARP请求时接收ARP回复。意外的主动回复可能会被忽略。

* An incorrect ARP implementation may ignore ARP Replies where 'ar$tha' doesn't match its hardware address.

* 如果“ar$tha”与其硬件地址不匹配,则错误的ARP实现可能会忽略ARP回复。

* An incorrect ARP implementation may ignore ARP Replies where 'ar$tpa' doesn't match its IP address.

* 如果“ar$tpa”与其IP地址不匹配,则错误的ARP实现可能会忽略ARP回复。

In summary, there are more ways that an incorrect ARP implementation might plausibly reject an ARP Reply (which usually occurs as a result of being solicited by the client) than an ARP Request (which is already expected to occur unsolicited).


4. Historical Note
4. 历史笔记

Some readers have claimed that "Gratuitous ARP", as described in Stevens [Ste94], provides duplicate address detection, making ACD unnecessary. This is incorrect. What Stevens describes as Gratuitous ARP is the exact same packet that this document refers to by the more descriptive term 'ARP Announcement'. This traditional Gratuitous ARP implementation sends only a single ARP Announcement when an interface is first configured. The result is that the victim (the existing address holder) logs an error, and the offender continues operation, often without even detecting any problem. Both machines then typically proceed to try to use the same IP address, and fail to operate properly because they are each constantly resetting the other's TCP connections. The human administrator is expected to notice the log message on the victim machine and repair the damage after the fact. Typically this has to be done by physically going to the machines in question, since in this state neither is able to keep a TCP connection open for long enough to do anything useful over the network.


Gratuitous ARP does not in fact provide effective duplicate address detection and (as of January 2008) many of the top results for a Google search for the phrase "Gratuitous ARP" are articles describing how to disable it.


However, implementers of IPv4 Address Conflict Detection should be aware that, as of this writing, Gratuitous ARP is still widely deployed. The steps described in Sections 2.1 and 2.4 of this document help make a host robust against misconfiguration and address conflicts, even when the other host is *not* playing by the same rules.


5. Security Considerations
5. 安全考虑

IPv4 Address Conflict Detection (ACD) is based on ARP [RFC826] and it inherits the security vulnerabilities of that protocol. A malicious host may send fraudulent ARP packets on the network, interfering with the correct operation of other hosts. For example, it is easy for a host to answer all ARP Requests with Replies giving its own hardware address, thereby claiming ownership of every address on the network.


This specification makes this existing ARP vulnerability no worse, and in some ways makes it better: instead of failing silently with no indication why, hosts implementing this specification either attempt to reconfigure automatically, or at least inform the human user of what is happening.


If a host willingly selects a new address in response to an ARP conflict, as described in Section 2.4, subsection (a), this potentially makes it easier for malicious attackers on the same link to hijack TCP connections. Having a host actively reset any existing connections before abandoning an address helps mitigate this risk.


6. Acknowledgments
6. 致谢

This document arose as a result of Zeroconf Working Group discussions on IPv4 Link-Local Addressing [RFC3927], where it was not clear to many participants which elements of link-local address management were specific to that particular problem space (e.g., random selection of an address), and which elements were generic and applicable to all IPv4 address configuration mechanisms (e.g., the detection of address conflicts). The following people made valuable comments in the course of that work and/or the subsequent editing of this document: Bernard Aboba, Randy Bush, Jim Busse, James Carlson, Alan Cox, Spencer Dawkins, Pavani Diwanji, Ralph Droms, Donald Eastlake III, Alex Elder, Stephen Farrell, Peter Ford, Spencer Giacalone, Josh Graessley, Erik Guttman, Myron Hattig, Mike Heard, Hugh Holbrook, Richard Johnson, Kim Yong-Woon, Marc Krochmal, Rod Lopez, Rory McGuire, Satish Mundra, Thomas Narten, Erik Nordmark, Randy Presuhn, Howard Ridenour, Pekka Savola, Daniel Senie, Dieter Siegmund, Valery Smyslov, Mark Townsley, Oleg Tychev, and Ryan Troll.


7. References
7. 工具书类
7.1. Normative References
7.1. 规范性引用文件

[RFC826] Plummer, D., "An Ethernet Address Resolution Protocol -- or -- Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware", STD 37, RFC 826, November 1982.

[RFC826]Plummer,D.“以太网地址解析协议——或——将网络协议地址转换为48位以太网地址,以便在以太网硬件上传输”,STD 37,RFC 826,1982年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月。

7.2. Informative References
7.2. 资料性引用

[802] IEEE Standards for Local and Metropolitan Area Networks: Overview and Architecture, ANSI/IEEE Std 802, 1990.


[802.3] ISO/IEC 8802-3 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, (also ANSI/IEEE Std 802.3-1996), 1996.

[802.3]ISO/IEC 8802-3信息技术-系统间远程通信和信息交换-局域网和城域网-通用规范-第3部分:带冲突检测的载波侦听多址(CSMA/CD)访问方法和物理层规范(也可称为ANSI/IEEE Std 802.3-1996),1996年。

[802.5] ISO/IEC 8802-5 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 5: Token ring access method and physical layer specifications, (also ANSI/IEEE Std 802.5-1998), 1998.

[802.5]ISO/IEC 8802-5信息技术-系统间远程通信和信息交换-局域网和城域网-通用规范-第5部分:令牌环访问方法和物理层规范(也叫ANSI/IEEE Std 802.5-1998),1998年。

[802.11] Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, IEEE Std. 802.11-1999, 1999.


[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996.

[RFC1918]Rekhter,Y.,Moskowitz,B.,Karrenberg,D.,de Groot,G.,和E.Lear,“私人互联网地址分配”,BCP 5,RFC 1918,1996年2月。

[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.


[RFC3203] T'Joens, Y., Hublet, C., and P. De Schrijver, "DHCP reconfigure extension", RFC 3203, December 2001.

[RFC3203]T'Joens,Y.,Hublet,C.,和P.De Schrijver,“DHCP重新配置扩展”,RFC32032001年12月。

[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic Configuration of IPv4 Link-Local Addresses", RFC 3927, May 2005.

[RFC3927]Cheshire,S.,Aboba,B.和E.Guttman,“IPv4链路本地地址的动态配置”,RFC 3927,2005年5月。

[Ste94] W. Stevens, "TCP/IP Illustrated, Volume 1: The Protocols", Addison-Wesley, 1994.


Author's Address


Stuart Cheshire Apple Inc. 1 Infinite Loop Cupertino California 95014 USA

Stuart Cheshire Apple Inc.美国加利福尼亚州库珀蒂诺无限环路1号95014

   Phone: +1 408 974 3207
   Phone: +1 408 974 3207

Full Copyright Statement


Copyright (C) The IETF Trust (2008).


This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

本文件受BCP 78中包含的权利、许可和限制的约束,除其中规定外,作者保留其所有权利。



Intellectual Property


The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围,或此类权利下的任何许可可能或可能不可用的程度,不采取任何立场;它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息,请参见BCP 78和BCP 79。

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at


The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at