[e2e] TCP Option Negotiation

Bob Braden braden at ISI.EDU
Thu May 17 13:01:35 PDT 2001

  *> it seems better to put the function at the client. Only the client 
  *> knows for sure whether it has enough retained state to safely ignore 
  *> a possible quiet time. Implementationally, it should be trivial for 
  *> any client that implements quiet times at all to add "new DHCP 
  *> address" to the list of things that trigger one.
  *> John


There is a difference.  Historically, many (most? all?) systems have
"implemented" quiet time implicitly by taking a long time to reboot.
DHCP-like mechanisms seem to force an explicit quiet time mechanism
where none may have previously existed.


More information about the end2end-interest mailing list