Re: Lease updates after Relay Agent crash
2008-02-01 21:00:06 GMT
BTW:
We probably made the original DHCPv6 bulk lease query (UDP based) more
complicated than it had needed to be. Part of the reason for that is the
DHCPv6 lease query is more client oriented and also the framework was
there to provide lots of different query types.
I haven't looked into it carefully, but it would seem that for DHCPv4 we
could just add a new lease query message which would be a
"DHCPLEASEQUERYNEXTADDRESS" which would interpret the existing "Query by
IP address" as specifying the last address returned and requesting that
the "next" address be returned.
This still has the performance (latency) issue of one request/response
per lease, but does avoid having to go to TCP.
Of course, I think the TCP approach used for DHCPv6 would be far
superior as there is one request with many potential responses flowing
over a TCP session.
---
I'm somewhat confused by the "TCP is a problem for a layer 2 device"
statement as so is UDP. Note the following text in RFC 4388:
o The giaddr MUST be set to the IP address of the requester (i.e.,
the access concentrator). The giaddr is independent of the
"ciaddr" field to be searched -- it is simply the return address
of the DHCPLEASEUNASSIGNED, DHCPLEASEACTIVE, or DHCPLEASEUNKNOWN
message from the DHCP server.
(Continue reading)
RSS Feed