Re: [pntaw] New version of TURN over websockets draft

[Oleg Moskalenko <[e-mail]>]

On Fri, Sep 20, 2013 at 1:33 PM, Sergio Garcia Murillo <
[e-mail]> wrote:

> Also, I would like to introduce in next draft version how HTTP
> authentication/authorization (oAuth, cookies, etc) mechanisms could be used
> in the TURN over websocekt connection on top of the standard TURN
> authentication. That would remove the need for the current REST API fro
> access to TURN services. If anyone would be willing to collaborate on this
> (or any other subject) will be very welcome.
>

Sergio, regarding the authentication stuff that you are proposing: that may
change the nature of the draft. The current draft does not affect TURN
functionality - it only adds a new option for the client-server transport.
That may be a very good thing about the draft; it makes it acceptable, I
guess, to most of the concerned people. If you are going to introduce
changes in the TURN protocol (like new attributes and new behavior), then
the draft will get another dimension, and it may make it more difficult to
get accepted and approved (and implemented, too).

The original purpose of the draft was to allow WebRTC communications in
some very unforgiving strict corporate environments (correct me if this is
not true). A new authentication mechanism, strictly speaking, has nothing
to do with that original goal. It may be a nice thing - but it may be a
theme for an add-on next-step specification.

Just my opinion.

Regards,
Oleg