WG consensus action: ACCEPT LL34 better transition to routable from v4LL using DHCP

Erik Guttman <[email protected]>
Newsgroups gmane.ietf.zeroconf,gmane.ietf.dhc
Message-ID <[email protected]>
Action: Accept the issue, with the text as modified during discussion

New text:

2.11  Transition from Link-Local IPv4 to Routable Address

As discussed in Section 1.7, use of a routable address is preferred to
assignment of a Link-Local IPv4 address.  A Link-Local IPv4 address can
be configured due to transient failures, such as incomplete link-layer
authentication, spanning tree convergence issues, or because a DHCP
server failed to respond to an initial query, or is inoperative for some 
time.

Where a Link-Local IPv4 address is assigned due to a transient failure,
experience has shown that five minutes (see Appendix A.2) may be
too long an interval to wait prior to attempting to configure with DHCP.
This document does not specify a strategy for quickly recovering a
routable address in situations where a Link-Local IPv4 address is
assigned due to a transient failure.  In situations where many hosts are
present on a single subnet, frequent attempts to contact the DHCP server
could result in a heavy traffic load.  Further discussion of this issue
is provided in [DNAv4].

[DNAv4]
Aboba, B., "Detection of Network Attachment (DNA) in IPv4",
draft-ietf-dhc-dna-ipv4-01.txt, Internet draft (work in progress),
September 2003.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.