Re: [rtcweb] ice-lite in WebRTC ???

Harald Alvestrand <harald@alvestrand.no> Fri, 07 February 2014 01:59 UTC

Return-Path: <harald@alvestrand.no>
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 C13B11A058F for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 17:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.344
X-Spam-Level:
X-Spam-Status: No, score=0.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793] autolearn=no
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 u13RvnnVo6-R for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 17:59:19 -0800 (PST)
Received: from mork.alvestrand.no (unknown [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4D51A0587 for <rtcweb@ietf.org>; Thu, 6 Feb 2014 17:59:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id B524A7C4ACF for <rtcweb@ietf.org>; Fri, 7 Feb 2014 02:59:17 +0100 (CET)
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVe75VzAELrf for <rtcweb@ietf.org>; Fri, 7 Feb 2014 02:59:17 +0100 (CET)
Received: from [10.1.1.234] (64-71-23-98.static.wiline.com [64.71.23.98]) by mork.alvestrand.no (Postfix) with ESMTPSA id 39D017C4ACB for <rtcweb@ietf.org>; Fri, 7 Feb 2014 02:59:17 +0100 (CET)
Message-ID: <52F43DF3.1020401@alvestrand.no>
Date: Fri, 07 Feb 2014 02:59:15 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CANCLmwniOd1MmdubfhARB0iCZTK1BYW46fwpDvus=UvOE2ynZg@mail.gmail.com> <CALe60zDC8Y_CspF3rkvqqcbP0_yWVviiFqq31R9gjq+GOW=7Xw@mail.gmail.com> <3A5DAAA1FDD9764EAA3B2A633A91A0495F8B49D5@xmb-aln-x15.cisco.com>
In-Reply-To: <3A5DAAA1FDD9764EAA3B2A633A91A0495F8B49D5@xmb-aln-x15.cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] ice-lite in WebRTC ???
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: <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: Fri, 07 Feb 2014 01:59:22 -0000

On 02/07/2014 02:56 AM, Wilson Chen (weichen2) wrote:
> In case of negotiating with server (may be a gateway), IMHO, the server would like not to do connectivity check, it is simpler and faster to work in ice-lite and passive mode.

The server doesn't have to claim WebRTC conformance, it just has to
claim to interoperate with WebRTC endpoints.

>
> Thanks,
> Wilson Chen
>
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Justin Uberti
> Sent: 2014年2月7日 3:56
> To: Rachel Dvori; rtcweb@ietf.org
> Subject: Re: [rtcweb] ice-lite in WebRTC ???
>
> +rtcweb
>
> WebRTC endpoints must implement full ICE. Legacy (non-WebRTC) endpoints can use ICE Lite, but as mentioned in RFC5245, S 2.7, full ICE is preferred.
>
> On Tue, Jan 21, 2014 at 10:50 AM, Rachel Dvori <rachel.dvori@gmail.com> wrote:
> draft-ietf-rtcweb-jsep@tools.ietf.org
>  
>  
> Dear Person,
>  
> I have seen the below in the draft of:   http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-05
>  
> Attributes other than the ones specified above MAY be included,
> except for the following attributes which are specifically
> incompatible with the requirements of [I-D.ietf-rtcweb-rtp-usage],
> and MUST NOT be included:
>  
> o  "a=crypto"
> o  "a=key-mgmt"
> o  "a=ice-lite"
>  
>  
> But in draft of :  http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-11  
> There is no phrase that prevents a WebRTC user to be ice-lite
>  
>  
> Can you pls clarify:
> -          Where is it mentioned that ice-lite cannot be one of the participants of WebRTC
> -          What is the reason that no side can be ice-lite  (as if one side is full-ice, there is still STUN and connectivity checks etc.
>  
> Thanks
> RD
>  
> p.s. - what is the correct email address for this type of questions ?  (Thanks and sorry)
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


-- 
Surveillance is pervasive. Go Dark.