Michael StJohns writes:
> Please, please get rid of activeRefreshOffset, clockskewDriftMargin
> and retryDriftMargin. Replace this with a single paragraph noting
> that the maximum time (assuming no retransmissions) a node has to wait
> after its holdDownTime expires is activeRefresh. (e.g. t
*pounds head on table* I'm really not sure how things get worse each
time but they appear to.
Please, please get rid of activeRefreshOffset, clockskewDriftMargin and
retryDriftMargin. Replace this with a single paragraph noting that
the maximum time (assuming no retransmissions) a node has
Sorry for the long delay to get this version out (vacation, family
issues, deadlines are all just excuses).
The -11 version of the document has a redesigned 6.1.6 that I'd love
everyone to concentrate on. Hopefully it more clearly articulates the
issues surrounding Mike's found need to wait yet
