Hi Michael, Thank you for your review, Responses below. Kent > On Feb 12, 2024, at 6:36 AM, Michael Tüxen via Datatracker <noreply@xxxxxxxx> wrote: > > 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. > > The document is well written, I only have the following two nits: > > * 2.1.5. Guidelines for Configuring TCP Keep-Alives > It seems that the item list at the end of the subsection provides > information related to "idle-time", "max-probes", and "probe-interval". > One item for one leaf, in the given order. > What confuses me is that the first item contains: > "but keep-alive messages SHOULD NOT be transmitted more frequently than > once every 15 seconds" > For me, this applies to not only to "idle-time" but also to "probe-interval". > However, for "probe-interval" you provide lower values. > Using > "A lower value MAY be configured, but idle intervals SHOULD NOT be smaller > than 15 seconds. Longer idle intervals SHOULD be used when possible." > would have avoided this confusion. I updated the document to use your text. Thanks for the suggestion! > * Acknowledgements > The authors would like to thank for following for lively discussions > should possibly read > The authors would like to thank the following for lively discussions Fixed (in all nine drafts) > Best regards > Michael Tüxen Thanks again, Kent -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
