Document: draft-ietf-tcpm-tcp-lcd-02 Reviewer: Enrico Marocco Review Date: 2010-08-25 IESG Telechat date: 2010-08-26 Summary: Ready, with nits. Major issues: none. Minor issues: none. Nits: The term "TCP" is often used as an abbreviation for "TCP sender", "TCP stack" or "TCP implementation" (e.g. in S. 4.2. "Algorithm Details", paragraph 3: "a TCP implements", paragraph 6: "a TCP in steady-state", paragraph 7: "a TCP may implement", paragraph 8: "a TCP will proceed", S. 5.6. "Reaction in Steady-State", paragraph 1: "the originating TCP", paragraph 2: "a TCP has no means", S. 7.1. "Detection of TCP Connection Failures", paragraph 2: "a TCP employing", S. 10. "Security Considerations", paragraph 1: "a TCP modified with"). It may just be a convention I'm not used to, but it sounds quite weird to me. S. 5. "Discussion of TCP-LCD", paragraph 2: s/a the sequence/the sequence/ S. 5.6.. "Reaction in Steady-State", paragraph 2: the first sentence is too long and does not read well. I'd suggest to split it.