Am 28.01.2010 um 22:40 schrieb Dave Cridland:
So a note's needed at minimum to explain that this didn't used to be a requirement, and clients (and servers) SHOULD cope with no response as meaning unavailable.
The problem with that is: How do you figure out if you don't get a response or if you are just still waiting for it? We should define a sane timeout here, I guess, to prevent incompatibilities. This also means we need to figure out a sane value that even works with bad connections.
-- Jonathan
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.