AD review of draft-ietf-xmpp-websocket

I have reviewed this draft in preparation for IETF LC.  Overall, it looks
to be in good shape.  Thanks for a nice document.  I've requested last
call, and there are a few minor comments below to consider along with LC
comments.

Thanks,
--Richard


MINOR

S3.1. "WebSocket messages sent or received will conform"
Should this be "MUST conform"?

S3.6.1. "a different transport, such as BOSH"
How is the recipient of one of these messages supposed to tell what
transport?  Does the use of an http- or https-schemed URI imply BOSH?

S3.7. "[Streams implicitly closed]"
Does this usage map cleanly to the TCP case?  That is, would a </stream>
element be sent in this closure case?  I'm just imagining that if you have,
say, a relatively naïve gateway that translates <stream> to <open> and
</stream> to <close>, this could cause problems.

_______________________________________________
xmpp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/xmpp