Re: [Last-Call] Genart last call review of draft-ietf-v6ops-slaac-renum-03

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> In this case, timely is most about user perception. If the now dysfunctional
>> address remains in use long enough for the user to become annoyed (or arguably
>> even notice), then recovery is not timely. Since the definition of timely in
>> this case is actually subjective, I’m not sure that such clarification is
>> practical or useful.
> 
> I agree.  But if timliness has no really solid definition, why does the
> text firmly assert that certain particular values, without qualificaton,
> are not timely?

One can be quite certain that a user will not wait for 3 days for a web page to load without being certain whether the user will wait 30 seconds, 1 minute, 3 minutes, or even 1 hour.

It’s very easy to call 3 days untimely in such a case. It is very hard to draw a clear line among the lower values.

Owen

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux