draft-ietf-dhc-ipv4-autoconfig-03.txt   draft-ietf-dhc-ipv4-autoconfig-04.txt 
Dynamic Host Configuration WG Ryan Troll Dynamic Host Configuration WG Ryan Troll
Document: draft-ietf-dhc-ipv4-autoconfig-03.txt Carnegie Mellon Document: draft-ietf-dhc-ipv4-autoconfig-04.txt @Home Network
Expires July 30, 1999 January 25, 1999 Expires October 19, 1999 April 14, 1999
Automatically Choosing an IP Address in an Ad-Hoc IPv4 Network Automatically Choosing an IP Address in an Ad-Hoc IPv4 Network
<draft-ietf-dhc-ipv4-autoconfig-03.txt> <draft-ietf-dhc-ipv4-autoconfig-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC2026. Internet-Drafts are
and its working groups. Note that other groups may also distribute working documents of the Internet Engineering Task Force (IETF), its
working documents as Internet-Drafts. areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet- Drafts as at any time. It is inappropriate to use Internet- Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
To view the entire list of current Internet-Drafts, please check the To view the list Internet-Draft Shadow Directories, see
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/shadow.html.
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
Abstract Abstract
With operating systems appearing in more and more devices, as well With operating systems appearing in more and more devices, as well
as computers appearing in more and more aspects of everyday life, as computers appearing in more and more aspects of everyday life,
communication between networked devices is increasingly important. communication between networked devices is increasingly important.
The communication mechanism between these devices must be able to The communication mechanism between these devices must be able to
not only support the office LAN environment, but must also scale to not only support the office LAN environment, but must also scale to
skipping to change at page 3, line 17 skipping to change at page 3, line 13
DHCP Server A DHCP Server is an Internet host that returns DHCP Server A DHCP Server is an Internet host that returns
configuration parameters to DHCP Clients. configuration parameters to DHCP Clients.
1.3. Usage Clarification 1.3. Usage Clarification
This document describes a method by which a host may automatically This document describes a method by which a host may automatically
choose an IPv4 address in the absence of a central service to choose an IPv4 address in the absence of a central service to
maintain and hand out addresses. This is not designed to replace maintain and hand out addresses. This is not designed to replace
this functionality, but to basicly provide it in small networks. this functionality, but to basicly provide it in small networks.
This SHOULD not be used for large-scale networks. As more and more This SHOULD NOT be used for large-scale networks. As more and more
machines begin to use this mechanism on a network, startup times for machines begin to use this mechanism on a network, startup times for
these machines will begin to increase, as the chance of collisions these machines will begin to increase, as the chance of collisions
will rise. will rise.
Addresses allocated by this mechanism MUST NOT be routed by any Addresses allocated by this mechanism MUST NOT be routed by any
network device. The addresses are designed to be link local network device. The addresses are designed to be link local
addresses. Link local address are to be, by definition, restricted addresses. Link local address are to be, by definition, restricted
to the local network segment. Allocation of link-local addresses in to the local network segment. Allocation of link-local addresses in
an IPv6 network is described in [IPv6SAC]. an IPv6 network is described in [IPv6SAC].
skipping to change at page 4, line 28 skipping to change at page 4, line 23
back in the INIT state, refer to section 2.1 of this document. back in the INIT state, refer to section 2.1 of this document.
3. Choosing an IP Address 3. Choosing an IP Address
Once a DHCP Client has determined it must auto-configure an IP Once a DHCP Client has determined it must auto-configure an IP
address, it chooses an address. The algorithm for choosing an address, it chooses an address. The algorithm for choosing an
address is implementation dependant. The address range to use MUST address is implementation dependant. The address range to use MUST
be "169.254/16", which is registered with the IANA as the LINKLOCAL be "169.254/16", which is registered with the IANA as the LINKLOCAL
net. net.
If choosing an address in this range, the DHCP Client MUST not use If choosing an address in this range, the DHCP Client MUST NOT use
the first 256 or the last 256, as these are reserved for future use. the first 256 or the last 256, as these are reserved for future use.
When an address is chosen, the DHCP Client MUST test to see if the When an address is chosen, the DHCP Client MUST test to see if the
address is already in use. If the network address appears to be in address is already in use. If the network address appears to be in
use, the client MUST choose another address, and try again. The use, the client MUST choose another address, and try again. The
client MUST keep choosing addresses until it either finds one, or it client MUST keep choosing addresses until it either finds one, or it
has tried more then the autoconfig-retry count. The autoconfig- has tried more then the autoconfig-retry count. The autoconfig-
retry count is implementation specific, and should be based on the retry count is implementation specific, and should be based on the
algorithm used for choosing an IP address. This retry count is algorithm used for choosing an IP address. This retry count is
present to make sure that DHCP Clients auto-configuring on busy present to make sure that DHCP Clients auto-configuring on busy
skipping to change at page 8, line 41 skipping to change at page 8, line 39
[DHCPAC] Troll, R., "DHCP Option to Disable Stateless Auto- [DHCPAC] Troll, R., "DHCP Option to Disable Stateless Auto-
Configuration in IPv4 Clients", RFC Work in progress, January Configuration in IPv4 Clients", RFC Work in progress, January
1999 1999
<ftp://ds.internic.net/rfc/rfcWork in progress.txt> <ftp://ds.internic.net/rfc/rfcWork in progress.txt>
10. Author's Address 10. Author's Address
Ryan Troll Ryan Troll
Network Development @Home Network
Carnegie Mellon 425 Broadway
5000 Forbes Avenue Redwood City, CA 94063
Pittsburgh, PA 15213
Phone: (412) 268-8691 Phone: (650) 569-6031
EMail: ryan@andrew.cmu.edu EMail: rtroll@corp.home.net
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/