RFC 4436: Detecting Network Attachment in IPv4 (DNAv4)

The time required to detect movement between networks and to obtain (or to continue to use) an IPv4 configuration may be significant as a fraction of the…

Read RFC 4436 on the RFC Editor

Outgoing relationships (8 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2131: Dynamic Host Configuration Protocol
Normative reference — RFC 826: An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 792: Internet Control Message Protocol
Informative reference — RFC 3118: Authentication for DHCP Messages
Informative reference — RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
Informative reference — RFC 4039: Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)

Incoming relationships (7 related RFCs)

Normatively referenced by — RFC 5555: Mobile IPv6 Support for Dual Stack Hosts and Routers
Normatively referenced by — RFC 7513: Source Address Validation Improvement (SAVI) Solution for DHCP
Informatively referenced by — RFC 5844: IPv4 Support for Proxy Mobile IPv6
Informatively referenced by — RFC 6555: Happy Eyeballs: Success with Dual-Stack Hosts
Informatively referenced by — RFC 5218: What Makes for a Successful Protocol?
Informatively referenced by — RFC 6059: Simple Procedures for Detecting Network Attachment in IPv6
Informatively referenced by — RFC 6574: Report from the Smart Object Workshop