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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Fri, 20 September 2013 20:33 UTC

Return-Path: <sergio.garcia.murillo@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 5159521F9E3F for <pntaw@ietfa.amsl.com>; Fri, 20 Sep 2013 13:33: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=[BAYES_00=-2.599]
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 7DWdE5OO5fc9 for <pntaw@ietfa.amsl.com>; Fri, 20 Sep 2013 13:33:24 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id A81FB21F9E3A for <pntaw@ietf.org>; Fri, 20 Sep 2013 13:33:23 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id u57so993922wes.37 for <pntaw@ietf.org>; Fri, 20 Sep 2013 13:33:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=SsxWLjEh6egngeD03DeHyR3acHu3ltndEaHpf/JDzv4=; b=DwqUFSPgGIbRo5Qk+eBlMuNxThRdHgIKKXc0gcsOkttMX2razuP4dX6vXI0HSMQ6zA sBoNCmStPpLn7qOQp8xDK1zW+0zNUVwFCle+9UL3Hg2di4bK0zNYADdo6+WJ9KvaXC4H fLA8ig2QiXczwCTUlqeP/Zgjgmjy+Kiqfxrkz57Rj9HGXbpCPAQR4kSEjWlqCb48vXhy 7fVBkDozIPwHfGo832EYrV439vhSyp+aYy+B3+6s5bvd25UDt4Iidg+3U54zxT9fzEoy A+/ckjcsYoTQNBwYCqSkJATI/LaG+6rL6DVfeLscnsxz88olfFXGtHAVGtJ3Vw4YQJuO pOKg==
X-Received: by 10.180.208.49 with SMTP id mb17mr4167321wic.64.1379709202868; Fri, 20 Sep 2013 13:33:22 -0700 (PDT)
Received: from [192.168.1.2] (171.pool85-51-25.dynamic.orange.es. [85.51.25.171]) by mx.google.com with ESMTPSA id i8sm7520920wiy.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Sep 2013 13:33:22 -0700 (PDT)
Message-ID: <523CB114.20106@gmail.com>
Date: Fri, 20 Sep 2013 22:33:24 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
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>
In-Reply-To: <523CAC92.2070102@petit-huguenin.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Victor Pascual Avila <victor.pascual.avila@gmail.com>, Oleg Moskalenko <mom040267@gmail.com>, "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 20:33:25 -0000

El 20/09/2013 22:14, Marc Petit-Huguenin escribió:
> On 09/20/2013 12:57 PM, Oleg Moskalenko wrote:
>> On Fri, Sep 20, 2013 at 11:59 AM, Marc Petit-Huguenin
>> <marc@petit-huguenin.org <mailto:marc@petit-huguenin.org>> wrote:
>>
>>
>> OK so I suggest to say in the draft that a new Websocket connection will
>> be created for each TCP peer, because that have an impact on implementation
>> design.
>>
>>
>> ... for RFC 6062 TURN TCP, of course. The key key words here are "TCP
>> peers" (as in RFC 6062, unlike "UDP peers" in RFC 5766). That may be worth
>> mentioning, indeed.
>>
>> This draft is mostly driven by the necessity of enhanced connectivity of
>> the clients (browsers) in WebRTC environment. So the question of
>> multiplicity of TCP / Websocket connections is not very important in this
>> context.
> If having TCP peers is not important, then remove RFC 6062 from this draft.
>
> Also, the draft does not explain the procedures related to SRV and NAPTR RRs:
>
> example.net.
> IN NAPTR 100 10 "" RELAY:turn.ws "" websocket.example.net.
>
> websocket.example.net.
> IN NAPTR 100 10 S RELAY:turn.ws "" _turn._ws.example.net.
>
> _turn._ws.example.net.
> IN SRV   0 0 80 a.example.net.
>
> a.example.net.
> IN A     192.0.2.1
>
>

Hi Marc

It was my error to keep the websocket support  for RFC 6062 in the draft 
(against Oleg recommendations, by the way).  I agree with both of you 
that it will be better to remove it from the draft, as it is causing 
most of the discussions and will not provide anything to webrtc.

Regarding the SRV and NAPTR RRs, for webrtc are not needed AFAIK, but we 
could add it to the draft for completeness. Would you be willing to 
collaborate in order to write that chapter?

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.

Best regards
Sergio