IETF Logo Mail Archive

Re: [rtcweb] No a=ice-lite in JSEP-04

Adam Roach <adam@nostrum.com> Thu, 03 October 2013 15:04 UTC

Return-Path: <adam@nostrum.com>
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 8C80F11E8122 for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 08:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.904
X-Spam-Level:
X-Spam-Status: No, score=-100.904 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 m8ZDOo0aVo2P for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 08:04:44 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D90A511E80AD for <rtcweb@ietf.org>; Thu, 3 Oct 2013 07:53:47 -0700 (PDT)
Received: from [192.168.0.191] (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r93ErhT3064327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Oct 2013 09:53:44 -0500 (CDT) (envelope-from adam@nostrum.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> <CALiegf=EmbKX7KPffa79eDn4zFxuZBkNFNsh-aX-iTecob7v6Q@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CALiegf=EmbKX7KPffa79eDn4zFxuZBkNFNsh-aX-iTecob7v6Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <54B5DF36-6BEE-4FA4-ACA1-D4912F9A49AB@nostrum.com>
X-Mailer: iPhone Mail (10B350)
From: Adam Roach <adam@nostrum.com>
Date: Thu, 03 Oct 2013 09:53:40 -0500
To: Iñaki Baz Castillo <ibc@aliax.net>
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: "rtcweb@ietf.org" <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 15:04:53 -0000

On Oct 3, 2013, at 9:31, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> If I implement my own WebRTC stack in a smartphone app, am I disallowed to do ICE-lite in my side??

I would hope so, yes. The chance that your smartphone app would have any hope if working if it did ice lite are as close to zero as to make no difference.

The fact that implementors apparently don't see this as an obvious fact tells me that we need pretty strong language around this prohibition, and "browser" is clearly too narrow a scope. 

/a

v2.23.0 | Report a Bug | By Email