Re: [rtcweb] Stephen Farrell's Discuss on draft-ietf-rtcweb-stun-consent-freshness-15: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 05 August 2015 16:55 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52FDF1A870B; Wed, 5 Aug 2015 09:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ypmbmqrzny3T; Wed, 5 Aug 2015 09:55:27 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 240581A8033; Wed, 5 Aug 2015 09:55:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D197CBE8E; Wed, 5 Aug 2015 17:55:25 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9e4TJo3aaqK7; Wed, 5 Aug 2015 17:55:25 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7A79BBE35; Wed, 5 Aug 2015 17:55:25 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1438793725; bh=PirNRDcV4JMcz4cbK9pRAbPBO9b+lyYWZe8am087+Qk=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=ReAyQ5EbRfxTXVIKl51gNluQzHFh8qAvK85p571BDdgzKo5Y+lJ0ITMb1CvCE1kHt 4bUW1t9zH9xT5HlMPtH2ncFW47Azb5j4bf9adTq24hBxkHWjtPu6wgZmbHXg61v02M QTLelXxHrAWI17yc+Fs3a5hKaLtfbZwjb3LacsmI=
Message-ID: <55C23FFD.8070201@cs.tcd.ie>
Date: Wed, 05 Aug 2015 17:55:25 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, The IESG <iesg@ietf.org>
References: <20150805130607.20844.70680.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B348E9691@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B348E9691@ESESSMB209.ericsson.se>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/pVtRntOPagQBTIP550tzg02t2hQ>
Cc: "draft-ietf-rtcweb-stun-consent-freshness.ad@ietf.org" <draft-ietf-rtcweb-stun-consent-freshness.ad@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "draft-ietf-rtcweb-stun-consent-freshness@ietf.org" <draft-ietf-rtcweb-stun-consent-freshness@ietf.org>, "rtcweb-chairs@ietf.org" <rtcweb-chairs@ietf.org>, "draft-ietf-rtcweb-stun-consent-freshness.shepherd@ietf.org" <draft-ietf-rtcweb-stun-consent-freshness.shepherd@ietf.org>
Subject: Re: [rtcweb] Stephen Farrell's Discuss on draft-ietf-rtcweb-stun-consent-freshness-15: (with DISCUSS and COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 05 Aug 2015 16:55:28 -0000

Hiya,

On 05/08/15 14:22, Christer Holmberg wrote:
> Hi Stephen,
> 
>> (2) WebRTC does not require STUN or TURN servers for some calls,
>> even if it does for many. Why is it ok to require such a server be
>> present in all calls (which I think this means) espcially when that
>> means exposing additional meta-data (calling parties in a case
>> where the servers weren't needed and call duration in all cases) to
>> those servers when that is not always necessary?
> 
> Could you please refer to the text which you think mandates STUN or
> TURN servers?

Sure, I think there were a couple of places, but I'd have to
track 'em down. I'll try update the ballot with that if it
turns out to be needed. (Be tomorrow before I get to that,
sorry.)

> 
> If there are no NATs, the STUN requests can be sent between the
> endpoints, without STUN or TURN servers.

Really - so browsers will be able to act like a STUN server or
something? I didn't know that. Where's that described?

S.


> 
> Regards,
> 
> Christer
>