Re: WGLC of draft-ietf-xmpp-websocket-02

Peter Saint-Andre <[email protected]>
Newsgroups gmane.ietf.xmpp
Message-ID <[email protected]>
On 4/23/14, 1:24 PM, Ben Campbell wrote:
>
> On Apr 22, 2014, at 6:29 PM, Lance Stout <[email protected]> wrote:
>
>>
>> On Apr 22, 2014, at 2:49 PM, Ben Campbell <[email protected]> wrote:
>>>
>>> The WGLC has completed. Authors, please let the list know when
>>> you believe all feedback has been addressed. (Note: "addressed"
>>> does not necessarily mean "accepted".)
>>
>> Draft -06 has been published, which I believe addresses all
>> feedback so far.
>>
>>
>> I note there is a pending question on connection managers, but I
>> don't believe that the use of a connection manager affects any of
>> the actions prescribed in the latest document. CMs should be
>> transparent.
>>
>>
>> We do have Security Considerations listed in XEP-0124 for BOSH
>> connection managers, which amount to 'use TLS from the CM to the
>> backend', and 'use e2e encryption on the client' because
>> guaranteeing anything about a CM's behaviour is beyond scope. I can
>> expand the Security Considerations for this document to do the
>> same, if people deem that necessary.
>
> So here's the basis of all of my connection manager questions. This
> may be based on a completely wrong understanding of connection
> managers on my part, so do not hesitate to tell me I am clueless if
> that's the case. :-)
>
> If an XMPP implementation, especially a server, is behind a
> connection manager, is it aware of that fact?

Connection managers are trusted server components, so the administrators 
of the service are aware that there is a CM in the mix, but the server 
need not be (all it knows is that sessions have been created and that 
some trusted entity did so).

> Is it assumed to
> implement this draft?

The server doesn't really need to implement the websocket aspect of 
things, since that's handled by the CM.

> Are we requiring special behavior of the
> server, without the server knowing it needs to do it?

Not as far as I can see.

BTW, I've updated the shepherd write up:

https://stpeter.im/files/writeup-ietf-xmpp-websocket.txt

Peter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.