Mike Bishop

The point of the idle timeout was so that an endpoint need not wake its radio to send closing packets -- it can just let the connection fade away. I...

I think we're bringing a few different assumptions to this conversation, which is helpful. (And of course, if my assumptions are wrong, I'll happily learn better.) I'm assuming that sending...

If so, I think I would make that an explicit statement that there is no distinction between probing/non-probing frames or packets once this extension is negotiated. However, 4.3.5 does still...

Will be resolved by #426.

The closest I see is in 9.3, where this statement occurs: > Receiving a packet from a new peer address containing a non-probing frame indicates that the peer has migrated...

While there are larger issues in this issue that it sounds like we've decided to live with, one that we can close trivially is the question of "EVERY address" and...

I can imagine two ways in which conditional requests might be used: - Don't execute the query if the state of the underlying resource (database) hasn't changed since it was...

> Otherwise I suppose the server might need to act as an authoritative source of time and block anything too far in the future? Yes, I think this is the...

I think there's value in adding an explicit signal of FIN/RST inside the stream without closing the stream, to leave room for future work communicating information from the proxy later....

@bemasc: Right, which means that the signal can't be sent until you've sent all the post-connection frames you wish to. That may well be acceptable, certainly given that we don't...