Re: [rtcweb] No a=ice-lite in JSEP-04
Iñaki Baz Castillo <ibc@aliax.net> Thu, 03 October 2013 14:40 UTC
Return-Path: <ibc@aliax.net>
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 16D3821F8B4E for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 07:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level:
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 zFfLDFpt8BUS for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 07:40:33 -0700 (PDT)
Received: from mail-qe0-f49.google.com (mail-qe0-f49.google.com [209.85.128.49]) by ietfa.amsl.com (Postfix) with ESMTP id EE4F721F98AC for <rtcweb@ietf.org>; Thu, 3 Oct 2013 07:31:53 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id s14so1769128qeb.22 for <rtcweb@ietf.org>; Thu, 03 Oct 2013 07:31:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Nz+7vV4lfqIx0DCmlLoQInzaLIfMoRpQXYM/1gDGcRM=; b=AlX1AILQJP1C/WHB7k7y3uJT4adQ9Lh0DtSe0qeSNvQUCuu2GIRbxNHTaLKLBwQTY2 MZbyJ5/Sgc8mFY6ymg9M4e2aq5cNzFfikEh3/Su1/6/+wmEVt+H5gZTgrjQm3kqW5TnT m/YTUc1jyzx88hTzWF9c65wawPG3gNbOL2jS5GXyHl9ek8s6CWYNEGf3jVZCU7EEcPP7 G9vTYT8L/sta2MCpoMPNfyC+/Q+Nm/taJ5fC+8aKZ6d7LvarPz46m7P2XWCZm+qsTAlt vi0OaFz/eOFuw6QJxmwvrwlGVgziwIW9OzgAuQQgrRPffVVn9/LRsyj95wgtF3PqHBVf t90A==
X-Gm-Message-State: ALoCoQnbYjMq7Y+gF9rXXAmvndH8ePvmFZ6ItnzoMWaruWvtOI9m2dY0UmJxGSbcvq8t0RBMEa+Z
MIME-Version: 1.0
X-Received: by 10.224.165.136 with SMTP id i8mr10979670qay.82.1380810712259; Thu, 03 Oct 2013 07:31:52 -0700 (PDT)
Received: by 10.49.16.71 with HTTP; Thu, 3 Oct 2013 07:31:52 -0700 (PDT)
Received: by 10.49.16.71 with HTTP; Thu, 3 Oct 2013 07:31:52 -0700 (PDT)
In-Reply-To: <2F515906-BEC6-4ACA-BF2B-172E6ADBDAF1@phonefromhere.com>
References: <56C2F665D49E0341B9DF5938005ACDF811144C@DEMUMBX005.nsn-intra.net> <CALiegfn+u-LD=W1S2te6UB1+u6yd7xAbpKO_U=qUEsD-aWv6cw@mail.gmail.com> <CAOJ7v-2UHjitspwzJ_nzdDXwN_ZoVAk=86O98khhhoOdAtVhiA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C4B37B8@ESESSMB209.ericsson.se> <2F515906-BEC6-4ACA-BF2B-172E6ADBDAF1@phonefromhere.com>
Date: Thu, 03 Oct 2013 16:31:52 +0200
Message-ID: <CALiegf=EmbKX7KPffa79eDn4zFxuZBkNFNsh-aX-iTecob7v6Q@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: multipart/alternative; boundary="089e014938c801b41a04e7d70c8c"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] No a=ice-lite in JSEP-04
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: Thu, 03 Oct 2013 14:40:46 -0000
If I implement my own WebRTC stack in a smartphone app, am I disallowed to do ICE-lite in my side?? Let's focus. We can mandate constrains just into browsers so IMHO "WebRTC browser" is the appropriate name here. -- Iñaki Baz Castillo <ibc@aliax.net> El 03/10/2013 16:26, "Tim Panton" <tim@phonefromhere.com> escribió: > I'm starting to think that we need a less clumsy name for the webRTC media > wire protocol > ICE/STUN/TURN/SRTP/DTLS/RTCP/Opus/VP8/ etc... > > It looks likely to take on a life of it's own outside the browser. > > T. > > On 3 Oct 2013, at 15:10, Christer Holmberg wrote: > > Hi,**** > ** ** > Just to be clear, with “WebRTC endpoint” I guess you do not include > gateways?**** > ** ** > Maybe we should talk about “JSEP endpoints”, or something..**** > ** ** > Regards,**** > ** ** > Christer**** > ** ** > *From:* rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] *On > Behalf Of *Justin Uberti > *Sent:* 1. lokakuuta 2013 1:30 > *To:* Iñaki Baz Castillo > *Cc:* rtcweb@ietf.org > *Subject:* Re: [rtcweb] No a=ice-lite in JSEP-04**** > ** ** > Yes. In the offers and answers that WebRTC endpoints create, a=ice-lite is > prohibited, since WebRTC endpoints must support "Full" ICE. **** > ** ** > The remote endpoint may of course support only ICE Lite, and WebRTC > implementations must work properly with such endpoints.**** > ** ** > This isn't normatively indicated anywhere that I could find, so I plan to > add specifics on this to the next version of JSEP.**** > ** ** > ** ** > > ** ** > On Mon, Sep 30, 2013 at 8:32 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote: > **** > 2013/9/30 Rauschenbach, Uwe (NSN - DE/Munich) <uwe.rauschenbach@nsn.com>:* > *** > > > JSEP-04 prohibits the use of a=ice-lite. It is stated that it is > incompatible with I-D.ietf-rtcweb-rtp-usage. > > Can you point out which specific aspect of this draft ICE Lite is > incompatible with? > > > > In deployments where one endpoint is a browser and another one is a > gateway connected to the public Internet, it makes sense to allow ICE lite. > **** > Without reading JSEP-04 I expect that it is not allowed for a web > browser to indicate "a=ice-lite", but a server can do that. Anyhow, > AFAIR the usage of ICE lite is fully transparent for the non ICE lite > endpoint. > > > -- > Iñaki Baz Castillo > <ibc@aliax.net>**** > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb**** > ** ** > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > > >
- [rtcweb] No a=ice-lite in JSEP-04 Rauschenbach, Uwe (NSN - DE/Munich)
- Re: [rtcweb] No a=ice-lite in JSEP-04 Iñaki Baz Castillo
- Re: [rtcweb] No a=ice-lite in JSEP-04 Justin Uberti
- Re: [rtcweb] No a=ice-lite in JSEP-04 Christer Holmberg
- Re: [rtcweb] No a=ice-lite in JSEP-04 Eric Rescorla
- Re: [rtcweb] No a=ice-lite in JSEP-04 Tim Panton
- Re: [rtcweb] No a=ice-lite in JSEP-04 Iñaki Baz Castillo
- Re: [rtcweb] No a=ice-lite in JSEP-04 Cullen Jennings (fluffy)
- Re: [rtcweb] No a=ice-lite in JSEP-04 Adam Roach
- Re: [rtcweb] No a=ice-lite in JSEP-04 Iñaki Baz Castillo
- Re: [rtcweb] No a=ice-lite in JSEP-04 Matthew Kaufman
- Re: [rtcweb] No a=ice-lite in JSEP-04 Christer Holmberg
- Re: [rtcweb] No a=ice-lite in JSEP-04 Iñaki Baz Castillo
- Re: [rtcweb] No a=ice-lite in JSEP-04 Christer Holmberg
- Re: [rtcweb] No a=ice-lite in JSEP-04 Adam Roach
- Re: [rtcweb] No a=ice-lite in JSEP-04 Harald Alvestrand
- Re: [rtcweb] No a=ice-lite in JSEP-04 Justin Uberti
- Re: [rtcweb] No a=ice-lite in JSEP-04 Christer Holmberg
- Re: [rtcweb] No a=ice-lite in JSEP-04 Martin Thomson
- Re: [rtcweb] No a=ice-lite in JSEP-04 Justin Uberti
- Re: [rtcweb] No a=ice-lite in JSEP-04 Iñaki Baz Castillo