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

Oleg Moskalenko <mom040267@gmail.com> Fri, 20 September 2013 23:14 UTC

Return-Path: <mom040267@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD6C21F9CED for <pntaw@ietfa.amsl.com>; Fri, 20 Sep 2013 16:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BN4wEX-SgHp1 for <pntaw@ietfa.amsl.com>; Fri, 20 Sep 2013 16:14:25 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 34CD221F9CC6 for <pntaw@ietf.org>; Fri, 20 Sep 2013 16:14:25 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fz6so1280214pac.17 for <pntaw@ietf.org>; Fri, 20 Sep 2013 16:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BzUfqQGBrx4s0XOpx/dh5s9KqVmuNIMEHQA6tgL9wr8=; b=BxSYidn9nWaXBOSdN2MARvK39G/4k6Q5AwUWp5nMWpxrTcUsdcRjhGpD2dRlxxe0cr HDONedZK9Xm0JE4vge/b8VrtsdeCQkbR2ZxPhrkn97dpvwOrR+5K5mcM5vm/bshkJppH jWsGfavjNhj8H1oryu2VFR4qXfR51N2WNsIQF0TPMeNBA4tOw72FCWBMTVr0DG21V7Dk BoG03lScak5ShybS9P7jhCyH0xxFoSlMDOMUnR4nbTn27OLJa8qOVFnQcUBjuNikOFtT gNfy1XlmIEtMzHKQ0nFzI0DWe/iwwpGDoNSREwb86qI4agLBhMXHRSO8EJ90w+sWKKXD WHwg==
MIME-Version: 1.0
X-Received: by 10.68.90.129 with SMTP id bw1mr10434992pbb.111.1379718864983; Fri, 20 Sep 2013 16:14:24 -0700 (PDT)
Received: by 10.68.129.138 with HTTP; Fri, 20 Sep 2013 16:14:24 -0700 (PDT)
In-Reply-To: <523CB114.20106@gmail.com>
References: <5232C18C.1030102@gmail.com> <523C8BDC.6050705@petit-huguenin.org> <CALDtMrKwygUqNWKcB81F+M7Y8wBmwZtTACeYChpJVvWKbXLTEw@mail.gmail.com> <523C9B03.2030002@petit-huguenin.org> <CALDtMrJBQQZP4bbkLh6OcZhmOGFrP5bAJ8BDr0AY1zKjPXChPw@mail.gmail.com> <523CAC92.2070102@petit-huguenin.org> <523CB114.20106@gmail.com>
Date: Fri, 20 Sep 2013 16:14:24 -0700
Message-ID: <CALDtMrJ2rLfpcNjVXNTx52XxA=4QAZ_ukBM7-QcnYcJ53pmjXA@mail.gmail.com>
From: Oleg Moskalenko <mom040267@gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d2470d65ff604e6d8d48b
X-Mailman-Approved-At: Fri, 20 Sep 2013 17:59:04 -0700
Cc: Victor Pascual Avila <victor.pascual.avila@gmail.com>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "pntaw@ietf.org" <pntaw@ietf.org>, Lorenzo Miniero <lorenzo@meetecho.com>, "Chenxin \(Xin\)" <hangzhou.chenxin@huawei.com>
Subject: Re: [pntaw] New version of TURN over websockets draft
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 23:14:25 -0000

On Fri, Sep 20, 2013 at 1:33 PM, Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> 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