Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt

[Peter Dunkley <[e-mail]>]

I suppose you could have each peer implementing both the WebSocket client
and server so that they can both send and handle WebSocket handshakes, but
this isn't going to work particularly well when there are NAT devices in
between.  It certainly won't work for peers that are implemented using
Javascript and run in-browser at the moment as the browsers (as far as I
know) only implement the WebSocket client.

An MSRP relay that is a WebSocket can be used for NAT traversal (in the
same way that an ordinary MSRP relay can be) and that is the focus of this
draft.  In the 3GPP world MSRP is B2B'd through an SBC like device and in
that case the peer (which is not a client) could be a WebSocket server -
this is something that Christer may be providing language for in the draft.

Regards,

Peter


On 14 February 2014 21:42, Cullen Jennings <[e-mail]> wrote:

>
> On Feb 14, 2014, at 8:24 AM, Peter Dunkley <[e-mail]>
> wrote:
>
> > Because WebSockets is an asynchronous protocol two MSRP peers (that are
> clients) cannot use MSRP over WebSockets.
>
> Just sort of curios, why can't this work?
>
>
>


-- 
Peter Dunkley
Technical Director
Crocodile RCS Ltd