Re: [rtcweb] Stephen Farrell's Discuss on draft-ietf-rtcweb-stun-consent-freshness-15: (with DISCUSS and COMMENT)
Xavier Marjou <xavier.marjou@gmail.com> Thu, 06 August 2015 08:34 UTC
Return-Path: <xavier.marjou@gmail.com>
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 9C11F1ACEE1; Thu, 6 Aug 2015 01:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 9PMhhewR4UA4; Thu, 6 Aug 2015 01:34:24 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D59E1ACEA2; Thu, 6 Aug 2015 01:34:24 -0700 (PDT)
Received: by wibxm9 with SMTP id xm9so13707981wib.1; Thu, 06 Aug 2015 01:34:23 -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=wlggN7DnTIAZwd7VO4u6nrXZWN3r4jVjVad63zg/l8A=; b=wju5JjR7Def6BDizPqaOot+mFBGtTMBFsCsF4Lt5gUfiKsRwIxdhflTUZLffKmpgaE vSqUYYfhuQ/p1kq5Xdgy5jjA/0PzxbqKBHk2TTdlc0e6hFMOBmUBiUNxZk3t7lPxzYQV 3d63eIMPW9DUTQWPWDgAyxuZb1lYPAzpdfw2jfeQtQ9Sipa9nX9zsgDruClQ/sYZc6k1 1nx8q/2Y4J9TIVXq0mtpYPRYSxWHKailwHIvR1Ww1IVOxdI36z4He7fyKcMrN39rNI6f JEXL0I/BHvLjf3MOP+OHuMWlbCayOj6qeeJoAWvhlkUoa+YV4A+HacO5pz6XWPMo7Ikk PsQA==
MIME-Version: 1.0
X-Received: by 10.180.83.72 with SMTP id o8mr328009wiy.27.1438850063196; Thu, 06 Aug 2015 01:34:23 -0700 (PDT)
Received: by 10.194.24.193 with HTTP; Thu, 6 Aug 2015 01:34:23 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B348E9691@ESESSMB209.ericsson.se>
References: <20150805130607.20844.70680.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B348E9691@ESESSMB209.ericsson.se>
Date: Thu, 06 Aug 2015 10:34:23 +0200
Message-ID: <CAErhfrysUBDS_RQQfoQSXkbGQv33j7Tmvvkgxf-gOVV6MzuwCQ@mail.gmail.com>
From: Xavier Marjou <xavier.marjou@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="f46d0442887ee6e8c3051ca06272"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/MDf-LhnINCT637qWFTrPmJMXU0o>
Cc: "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>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-rtcweb-stun-consent-freshness.ad@ietf.org" <draft-ietf-rtcweb-stun-consent-freshness.ad@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: Thu, 06 Aug 2015 08:34:26 -0000
>(2) WebRTC does not require STUN or TURN servers for some calls, even if it does for many. In a typical WebRTC communication with A and B as WebRTC endpoints: 1 - Optionally A and/or B can use a STUN server to discover a public IP address ("server reflexive" address as per rfc5245) 2 - Optionally A and/or B can use a TURN server to tunnel/relay WebRTC messages with the help of a TURN server (c.f. draft-ietf-tram-turnbis-05) 3 - A and B have to implement ICE (rfc5245) and thus have to exchange STUN connectivity check messages between their candidates (to try "open" flows", ... and maybe even to transport "consent" information). Therefore, there can be STUN messages transported in three different "sectors" : 1 - between the WebRTC endpoint and its STUN server, if used 2 - between the WebRTC endpoint and its TURN server, if used (draft-ietf-tram-turnbis-05 states that "Most, though not all, TURN messages are STUN-formatted messages" so there are precisely "STUN-formatted", not "STUN", but I mention them to be exhaustive with different sort of messages appearing as STUN messages in tools like Wireshark). 3 - between the WebRTC endpoints (in this case, the STUN connectivity check messages are in the same flow that transports SCTP/DTLS and SRTP messages). Some newcomers think that STUN messages only happen in cases 1 and/or 2, they forget case 3. Maybe this explains the misunderstanding. On Wed, Aug 5, 2015 at 3:22 PM, Christer Holmberg < christer.holmberg@ericsson.com> 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? > > If there are no NATs, the STUN requests can be sent between the endpoints, > without STUN or TURN servers. > > Regards, > > Christer > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
- [rtcweb] Stephen Farrell's Discuss on draft-ietf-… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Christer Holmberg
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Eric Rescorla
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Eric Rescorla
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Eric Rescorla
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Eric Rescorla
- [rtcweb] TURN permissions for private ips (was: R… Philipp Hancke
- Re: [rtcweb] [tram] TURN permissions for private … Simon Perreault
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Alissa Cooper
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti
- Re: [rtcweb] [tram] TURN permissions for private … Simon Perreault
- Re: [rtcweb] [tram] TURN permissions for private … Eric Rescorla
- Re: [rtcweb] [tram] TURN permissions for private … Philipp Hancke
- [rtcweb] Stephen Farrell's Discuss on draft-ietf-… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Muthu Arul Mozhi Perumal
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Christer Holmberg
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Christer Holmberg
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Xavier Marjou
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Alissa Cooper
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] [tram] TURN permissions for private … Emil Ivov
- Re: [rtcweb] [tram] TURN permissions for private … Jonathan Lennox
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti
- Re: [rtcweb] [tram] TURN permissions for private … Martin Thomson
- Re: [rtcweb] [tram] TURN permissions for private … Jonathan Lennox
- Re: [rtcweb] [tram] TURN permissions for private … Roman Shpount
- Re: [rtcweb] [tram] TURN permissions for private … Martin Thomson
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti
- Re: [rtcweb] [tram] TURN permissions for private … Emil Ivov
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti
- Re: [rtcweb] [tram] TURN permissions for private … Emil Ivov
- Re: [rtcweb] [tram] TURN permissions for private … Pal Martinsen (palmarti)
- Re: [rtcweb] [tram] TURN permissions for private … Emil Ivov
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Tirumaleswar Reddy (tireddy)
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Martin Thomson
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Muthu Arul Mozhi Perumal
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [rtcweb] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti
- Re: [rtcweb] [tram] TURN permissions for private … Cullen Jennings
- Re: [rtcweb] [tram] TURN permissions for private … Justin Uberti