Reviewer: Michael Tüxen Review result: Ready with Nits This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@xxxxxxxx if you reply to or forward this review. Addressing the following comments might help to improve the document: 1. In the first paragraph of Section 4, the term 'connection' is used. I guess this is referring to a 'transport connection'. If that is true, using 'transport connection' improves readability. 2. Section 4 talks about connection establishment. When should a connection be terminated? 3. Section 4 talks about connection establishment. What happens if a connection is terminated in a graceful or non-graceful way? 4. Section 6 provides values for timers. The minimum values for the Refresh Interval and the Retry Interval, both 1 second, might interfere with loss recovery timers of the underlying transport protocol. Is there any mechanism in the protocol to deal with this? 5. Section 9 describes that end points SHOULD use keep-alives, if available at the transport layer. Any recommendation regarding the time after which it should be sent and about the frequency? Best regards Michael -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
