Search results
Results from the WOW.Com Content Network
The Internet Engineering Task Force (IETF) has reserved the IPv4 address block 169.254.0.0 / 16 (169.254.0.0 – 169.254.255.255) for link-local addressing. [1] The entire range may be used for this purpose, except for the first 256 and last 256 addresses (169.254.0.0 / 24 and 169.254.255.0 / 24), which are reserved for future use and must not be selected by a host using this dynamic ...
Used for loopback addresses to the local host [1] 169.254.0.0/16 169.254.0.0–169.254.255.255 65 536: Subnet Used for link-local addresses [5] between two hosts on a single link when no IP address is otherwise specified, such as would have normally been retrieved from a DHCP server 172.16.0.0/12 172.16.0.0–172.31.255.255 1 048 576: Private ...
Mechanisms were introduced to handle this task automatically, and both IPv4 and IPv6 now include systems for address autoconfiguration, which allows a device to determine a safe address to use through simple mechanisms. For link-local addressing, IPv4 uses the special block 169.254.0.0 / 16, [1] while IPv6 hosts use the prefix fe80:: / 10.
The block 169.254.0.0 / 16 was allocated for this purpose. [6] [7] If a host on an IEEE 802 network cannot obtain a network address via DHCP, an address from 169.254.1.0 to 169.254.254.255 [Note 2] may be assigned pseudorandomly. The standard prescribes that address collisions must be handled gracefully.
Address block 169.254.0.0 / 16 is defined for the special use of link-local addressing for IPv4 networks. [14] In IPv6, every interface, whether using static or dynamic addresses, also receives a link-local address automatically in the block fe80:: / 10 . [ 14 ]
The definition of Auto-IP in the UPnP 1.1 Device Architecture specification explicitly states that Auto-IP is defined in RFC 3927, and also defines forwarding rules that are consistent with RFC 3927 which ensure that source and destination hosts on the same link which don't both have 169.254.0.0/16 addresses can still interoperate.
Used for loopback addresses to the local host [4] 169.254.0.0/16 169.254.0.0–169.254.255.255 65 536: Subnet Used for link-local addresses [10] between two hosts on a single link when no IP address is otherwise specified, such as would have normally been retrieved from a DHCP server 172.16.0.0/12 172.16.0.0–172.31.255.255 1 048 576: Private ...
This definition, from 1997, [8] remains the core of the standard for IPv4 networks. DHCPv6 was initially defined in 2003. [ 9 ] After updates by many subsequent RFCs, its definition was replaced in 2018, [ 10 ] where prefix delegation and stateless address autoconfiguration were now merged.