Re: [dhcwg] draft-ietf-dhc-l2ra-00 comments

[Bharat Joshi <bharat_joshi at infosys.com>]

Hi David,

> > 4.2.2. Issues due to introduction of Layer 2 Relay Agent
> >
> > o Suggest adding (in addition to similar 4.1.2 issues):
> >
> >    Layer 2 relay agents which maintain persistent state, such as
> >    updating filters or client registration, must be prepared to handle
> >    potentially conflicting responses from different DHCP Servers.
> >    Some Layer 2 relay agents instead use "the most recent DHCP
> >    packet", and this is not necessarily a reflection of which state a
> >    client has actually adopted.  Even where a client requests a single
> >    address, and two servers ack the single address, they MAY differ
> >    for example in lease times.  If the relay agent selects the server
> >    reply which has a shorter lease time, it would expire its state
> >    possibly before the client even has a chance to renew it.
> >    Therefore, Layer 2 relay agents SHOULD select the longest lease
> >    time of two conflicting but similar replies, by discarding replies
> >    that shorten the lease time.
> >
> > Or possibly this should be an expanded discussion of 4.2.1's point?
>
>
> Ok. This point seems to require some discussion.
>
> We feel that when client receives multiple OFFER messages, it will
> choose only one of the server and will send REQUEST message identifying
> that server. Now Layer 2 Relay Agent should typically extract/glean
> Lease Information to install filters etc when it sees an Ack from the
> Server.
>
> So my question is that we won't have a case where two servers are acking
> for the same request. I am not sure if I am missing something here.
>

I was discussing this and realize that we have already mention something similar for REBIND case in point 3 under section 4.3.2.

We can enhance this point to reflect your suggestion.

If it is something else, please do let us know.

Thanks,
Bharat

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg