DHCPv6 Request Retransmission
draft-george-dhc-request-retransmission-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robins George | ||
| Last updated | 2012-12-26 (Latest revision 2012-06-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The DHCP client sends SOLICIT message to get IP address from the server. If the address pool is empty, all address in the pool have allocated to the clients, the server will return error code. NoAddrsAvail (server has no address available to assign in the IA). Client retransmit the SOLICIT message (section 14 RFC 3315) and may get the same response. This draft defines a new suboption for the Dynamic Host Configuration Protocol (DHCP) to identify the retry time to sent next SOLICIT message. Hence, avoid unnecessary retransmit of SOLICIT messages. The suboption carries a value that identifies when an address will be available in the address pool.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)