Re: [rtcweb] ICE does not work if both peers are behind symmetric NAT

"Alfred E. Heggestad" <aeh@db.org> Sat, 24 September 2011 21:10 UTC

Return-Path: <aeh@db.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA5621F8B58 for <rtcweb@ietfa.amsl.com>; Sat, 24 Sep 2011 14:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 mO1RxMJQZ68m for <rtcweb@ietfa.amsl.com>; Sat, 24 Sep 2011 14:10:15 -0700 (PDT)
Received: from mailstore05.sysedata.no (mailstore05.sysedata.no [195.159.29.9]) by ietfa.amsl.com (Postfix) with ESMTP id ADE4021F8AF9 for <rtcweb@ietf.org>; Sat, 24 Sep 2011 14:10:15 -0700 (PDT)
Received: from [84.215.116.142] (helo=macbook.lan) by mailstore05.sysedata.no with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <aeh@db.org>) id 1R7ZWl-0002bv-6c; Sat, 24 Sep 2011 23:12:51 +0200
Message-ID: <4E7E47D1.9040100@db.org>
Date: Sat, 24 Sep 2011 23:12:49 +0200
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.22) Gecko/20110902 Thunderbird/3.1.14
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <CALiegfnf3=mPAupRtjoqz+fNfxT5V8yivoQB+bgrvAVWp5CVog@mail.gmail.com>
In-Reply-To: <CALiegfnf3=mPAupRtjoqz+fNfxT5V8yivoQB+bgrvAVWp5CVog@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] ICE does not work if both peers are behind symmetric NAT
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2011 21:10:16 -0000

On 9/24/11 10:33 PM, Iñaki Baz Castillo wrote:
> Hi, I expect this topic has already been addressed in this maillist.
> But it not, I would like to comment that ICE does not work when both
> peers are behind symmetric NAT (very common in home routers).
>
> In that case, the only solution is to use TURN by adding it the last
> candidate in the ICE SDP, but TURN requires authentication and, of
> course, a TURN server.
>
> Has been this topic discussed? If the website supposed to provide the
> WebRTC client with information about which TURN server to use and
> username:password for using it?
>


"ICE does not work" is not correct. ICE will still "work" even if both
peers are behind NAT. the media will simply be relayed via a TURN server,
and not flow directly between peers.


the TURN server credentials should be provisioned by the service provider



/alfred