Hi, I would like to provide feedback on these two sections:
5.7.3. Handling of Idle Streams http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-09.html#streams-close-idle 12.7. Whitespace http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-09.html#xml-whitespace In 5.7.3, it says: "The typical method for detecting an idle TCP connection is to send a space character (U+0020) over the TCP connection between XML stanzas, which is allowed for XML streams as described under Section 12.7 (Whitespace)." Strictly speaking: - the sending entity does not detect the loss of connection when it sends whitespaces - the receiving entity detects the loss of connection only if it has a mechanism that detects the absence of whitespaces Thus I propose this change: "The typical method for maintaining a TCP connection is to send a space character (U+0020 [...]" What do you think ot it? Then, we have: "The sending of such a space character is called a WHITESPACE PING." Strictly speaking: - a ping mechanism is a request-response mechanism, it waits for a "pong" response, so this is not a ping, and I think this should better be named a "keepalive" (or sort of) - s/space character/whitespace/ because: 1.3. Conventions http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-09.html#intro-conventions "The term "whitespace" is used to refer to any character that matches production [3] content of [XML], i.e., any instance of SP, HT, CR, and LF." Thus I propose this change: "The sending of such a whitespac is called a WHITESPACE KEEPALIVE." What do you think ot it? Regards -- Nicolas Vérité - ProcessOne http://process-one.net Mobile: +33 6 20 88 63 04
