RE: [dhcwg] dhcpv6-24: Elapsed Time option

["Bernie Volz (EUD)" <[e-mail]>]

So, I'm confused as to where you want to go with this?

If we want to be able to make this happen in the future, we have to have clear rules as to when the elapsed time starts for each transaction. We also likely have to make sure that the server sends the option back to the client such that the same value can be used in follow-on messages (really just in the Request(s) after an Advertise?).

Another question is whether single server messages (such as Renew, Decline, Release) should even make use of this option?


Also, we we do allow this option in the single server messages (those with a Server Identifier), what does mean for relays?

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:[e-mail]]
Sent: Thursday, May 09, 2002 1:44 PM
To: Bernie Volz (EUD)
Cc: 'Thomas Narten'; [e-mail]
Subject: Re: [dhcwg] dhcpv6-24: Elapsed Time option 


> I also agree that having the relay base the forwarding on the elapsed time 
> is likely bad - but again, that was assumed to happen with DHCPv4!!

I think it's useful to have the relay be able to do this, but I'm not 
convinced that it's actually going to get used.   There are relays that 
allow you to configure a delayed relay parameter, but do we know of any 
that are actually used this way?   I don't personally know of anybody who'
s doing this.   I suspect that this is something that's a good idea in 
theory, but not in practice, and because of that, I think it might be a 
better choice to simply leave it out of the spec.

The only reason to even *consider* putting it in the spec is that if it 
doesn't go in now, it will never be possible to do it - if clients and 
servers don't do the right thing from the outset, there's no way to 
retrofit this capability later.   I'm just really skeptical that we're ever 
going to need this, and furthermore I'm skeptical that something like this 
is going to get implemented correctly, when nothing will break immediately 
if either the server implementation or the client implementation is 
incorrect.