CurrentPROPOSED STANDARDIETF stream

RFC 4436: Detecting Network Attachment in IPv4 (DNAv4)

In plain English — editorial summary, not part of the RFC

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 total handover latency in moving between points of attachment. This document synthesizes, from experience in the deployment of hosts supporting ARP, DHCP, and IPv4 Link-Local addresses, a set of steps known as Detecting Network Attachment for IPv4 (DNAv4), in order to decrease the handover latency in moving between points of attachment. [STANDARDS-TRACK]

Document record

Document ID
RFC4436
Published
March 2006
Authors
B. Aboba; J. Carlson; S. Cheshire
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
15
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4436-detecting-network-attachment-in-ipv4-dnav4