Re: [dhcwg] lease query question

Ralph,

Thanks!  That's a great problem statement.

Thomas,

Would replacing the current problem statement with this one
suggested by Ralph be sufficient to meet (enough of) your
concerns to allow the draft to proceed?

Is there something instead of or in addition to that change that
you would suggest we do in order to move forward here?

Thanks -- Kim

At 12:51 PM 2/19/2003, Ralph Droms wrote:
>Kim,
>
>Based on the discussion and current draft of the spec, it looks to me like the protocol has evolved beyond simply reporting lease information into a mechanism for populating an access concentrator with device identity and location information.  It's more than a mere formality to ensure that the problem statement and design motivation match the protocol itself - those readers who have not been part of the evolution need to be able match up the problem statement and the protocol spec to effectively evaluate the correctness and applicability of the protocol.
>
>For example, I think the following problem statement more accurately reflects the current protocol and the problem that is causing its evolution:
>
>        Router-type devices which want to enforce some level of access
>        control over which IP addresses are allowed on their links
>        need to maintain information concerning IP<->MAC/client-id
>        mappings.  One way in which these devices can obtain
>        information about IP<->MAC/client-id bindings is through "DHCP
>        gleaning", in which the device extracts useful information
>        from DHCP messages exchanged between hosts and DHCP servers.
>
>        However, these devices don't typically have stable storage
>        sufficient to keep this information over reloads.  There may
>        be additional information that is useful to the device that
>        cannot be obtained through DHCP gleaning.  The leasequery
>        request message described in this document allows a device to
>        obtain information about IP<->MAC/client-id bindings from a
>        DHCP server.  This information may include currently active
>        bindings, bindings involving previously assigned addresses for
>        which the lease on the address has expired and static bindings
>        for devices that are otherwise configured and not using DHCP
>        for address assignment.
>
>- Ralph
> 

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