RE: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-05

If you want to do something like this, just set the lease time to a small
value - the client will then renew. This works just as well - it gets the
client the address quickly and recovers unused addresses relatively quickly
(most servers will hold offerred addresses for several minutes to allow a
client to request the address, so this isn't much different).

- Bernie

> -----Original Message-----
> From: Steve Gonczi [mailto:steve@relicore.com] 
> Sent: Tuesday, July 13, 2004 2:40 PM
> To: Bernie Volz
> Cc: dhcwg@ietf.org
> Subject: RE: [dhcwg] dhc WG last call on 
> draft-ietf-dhc-rapid-commit-opt-05
> 
> 
> Kudos to Samsung for the new IPR statement...
> 
> How do the authors feel about the following tweak 
> to the protocol:
> 
> When the Rapid commit client decides to accept an address
> sent via a Rapid Commit ack, it should send out a DHCPREQUEST 
> (perhaps with the rapid commit option), 
> similar to the classic DHC protocol. 
> 
> The sole purpose of this message is to notify any servers that 
> offered addresses to release those addresses not selected.
> 
> IMHO this is inexpensive to do, and solves the address 
> tie-up issue.
> 
> Cheers,
> 
> Steve Gonczi
> 

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg