IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Thu, 03 October 2013 14:26 UTC

Return-Path: <ekr@rtfm.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 39CF021F96ED for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 07:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 JHG0L2jBe0YP for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 07:26:10 -0700 (PDT)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id 663B421F9901 for <rtcweb@ietf.org>; Thu, 3 Oct 2013 07:19:14 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id ez12so40510wid.15 for <rtcweb@ietf.org>; Thu, 03 Oct 2013 07:19:13 -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:from:date :message-id:subject:to:cc:content-type; bh=jxYy4G4l7Ia2Gouq7PAYFjn0oUPl2xXtoR9vWM1eslM=; b=Wf2/vR57/fs4ySsbLJklNT4uRShNbZyAoMAzeL57lYUUq0AHoMwaKiL2P00nKUOlnz GgUWGGTT6TIuJIcftpvPJW41m7pwpXp+fy8DXfPw+MkrIg1L53R5iM5v0JL+kOs1VdfR KAbPKbVvwPAXo/waCiNxla6VV4kTUXo+2NdjZ8JiithEPwu7s9tla3UoL6FDChFRkIFK 13TXKVvsMAoIS46/VN8g2a13RdolOzcrgUTdxC+YRzmT4FT/mrt45L1vzjn/1ZHiiv+m mlgsXsAOBLIahaJeVOsVOELo/E4zzmn7NRTkjwtdjR0bWFcTwA63ajZyOddQEKEgQ7hW dS+w==
X-Gm-Message-State: ALoCoQkeU2evXvtVVucdqPxNptpR3qtKH1oNpaK/LqHcXKWi5yJAWgvO8PpKfXdnenF8dD1mUndr
X-Received: by 10.194.77.41 with SMTP id p9mr1725440wjw.66.1380809953546; Thu, 03 Oct 2013 07:19:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.152.137 with HTTP; Thu, 3 Oct 2013 07:18:33 -0700 (PDT)
X-Originating-IP: [88.128.80.2]
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4B37B8@ESESSMB209.ericsson.se>
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>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 03 Oct 2013 16:18:33 +0200
Message-ID: <CABcZeBOM3XSgAwCPNs-X73ScrO1QYpzz=nePDBa8V+gRwLdpOQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7bfcfc6cc8ab6104e7d6de7a"
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 14:26:23 -0000

On Thu, Oct 3, 2013 at 4:10 PM, Christer Holmberg <
christer.holmberg@ericsson.com> 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.
>

I assumed he meant "browser".

-Ekr



>  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
>
>

v2.23.0 | Report a Bug | By Email