Hi, Say the newly coined "overlay-reliability-timer" (ORT) in base-19 has a 3 second default.
Base-19 section 5.6.3.1 paragraph 6 describes an example of a 500ms RTO and re)transmission at 0ms, 500ms, 1500ms, 3500ms, 7500ms. One problem with this paragraph is that it is mixing receiving ACK with receiving a response of a request, which are two distinct steps. The second problem is obvious, the 4th transmission at 3.5 second overlaps the first ORT. The second paragraph of this section also says, "A node MUST NOT have more than one unacknowledged message on the DTLS connection at a time." This means RTO trumps ORT such that if a request originator has not received an ACK from its first hop peer, ORT must not fire or must start after ACK from the first hop is received. This does not apply to intermediate peers. If this is by design, then it is too important not to spell it out in the draft. I will come up with some text if everybody agrees on "RTO trumps ORT" or "ORT starts after ACK" for request originator. Thanks --Michael _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
