RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
In plain English — editorial summary, not part of the RFC
To participate in wide-area IP networking, a host needs to be configured with IP addresses for its interfaces, either manually by the user or automatically from a source on the network such as a Dynamic Host Configuration Protocol (DHCP) server. Unfortunately, such address configuration information may not always be available. It is therefore beneficial for a host to be able to depend on a useful subset of IP networking functions even when no address configuration is available. This document describes how a host may automatically configure an interface with an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical (or logical) link. IPv4 Link-Local addresses are not suitable for communication with devices not directly connected to the same physical (or logical) link, and are only used where stable, routable addresses are not available (such as on ad hoc or isolated networks). This document does not recommend that IPv4 Link-Local addresses and routable addresses be configured simultaneously on the same interface. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3927
- Published
- May 2005
- Authors
- S. Cheshire; B. Aboba; E. Guttman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4388Dynamic Host Configuration Protocol (DHCP) LeasequeryUpdated
February 2006
- RFC 4698IRIS: An Address Registry (areg) Type for the Internet Registry Information ServiceCurrent
October 2006
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 3925Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)Current
October 2004
- RFC 3942Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) OptionsCurrent
November 2004
- RFC 3898Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
October 2004
- RFC 3957Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4Current
March 2005
- RFC 3963Network Mobility (NEMO) Basic Support ProtocolCurrent
January 2005
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?