Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-ietf-rtcweb-stun-consent-freshness-02.txt

"Karl Stahl" <karl.stahl@intertex.se> Sat, 17 May 2014 21:40 UTC

Return-Path: <karl.stahl@intertex.se>
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 612B81A023F for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_LOW=-0.7] 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 pn1XT5c9hRKm for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:40:17 -0700 (PDT)
Received: from smtp.it-norr.com (smtp.it-norr.com [80.244.64.161]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA8DB1A023B for <rtcweb@ietf.org>; Sat, 17 May 2014 14:40:15 -0700 (PDT)
Received: from ([90.229.134.75]) by smtp.it-norr.com (Telecom3 SMTP service) with ASMTP id 201405172340127628; Sat, 17 May 2014 23:40:12 +0200
From: "Karl Stahl" <karl.stahl@intertex.se>
To: "'Cullen Jennings \(fluffy\)'" <fluffy@cisco.com>, <rtcweb@ietf.org>
References: <20140411033753.19230.46577.idtracker@ietfa.amsl.com> <CF6D6F0C.878CF%rmohanr@cisco.com> <7594FB04B1934943A5C02806D1A2204B1D2BD7C3@ESESSMB209.ericsson.se> <CF6D8F50.87A2E%rmohanr@cisco.com> <CF6E24CE.87C6C%rmohanr@cisco.com> <CABkgnnUHXXEyNrRetFMUvpqF5mreHWL4LijvhG+QSQAQxkzHZQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D2BF6E5@ESESSMB209.ericsson.se> <eb4ad62a-d30d-4a03-8c28-061cd0105d5f@email.android.com> <7594FB04B1934943A5C02806D1A2204B1D2BFE90@ESESSMB209.ericsson.se> <024c01cf5635$92835650$b78a02f0$@stahl@intertex.se> <534937C6.5030403@alvestrand.no> <E76CD81B-C5AC-47E5-A0BF-ACDEC4FFDDF4@cisco.com>
In-Reply-To: <E76CD81B-C5AC-47E5-A0BF-ACDEC4FFDDF4@cisco.com>
Date: Sat, 17 May 2014 23:40:10 +0200
Message-ID: <041601cf7218$94866150$bd9323f0$@stahl@intertex.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPchQvc/hqZUKEOUmQvfdXbbUnS5tFS+YA
Content-Language: sv
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/UGlX7--h4UW8bRg9qHicaUFJOi0
Subject: Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-ietf-rtcweb-stun-consent-freshness-02.txt
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: Sat, 17 May 2014 21:40:19 -0000


-----Ursprungligt meddelande-----
Från: Cullen Jennings (fluffy) [mailto:fluffy@cisco.com] 
Skickat: den 17 maj 2014 23:09
Till: rtcweb@ietf.org
Kopia: Karl Stahl; Christer Holmberg; Harald Tveit Alvestrand; Martin
Thomson; Ram Mohan R (rmohanr)
Ämne: Re: [rtcweb] ICE-Lite, Was: I-D Action:
draft-ietf-rtcweb-stun-consent-freshness-02.txt


A browser running full ICE needs to be able to connect with a device doing
ICE lite - that is in our requirements but to HTA point, it’s not obvious to
me that changes what the browser needs to implement to make this work other
than implement ICE. Is there something I am missing?

--- No, don't think so. I saw a clarifying text had been added to the draft
which could cause confusion.
/Karl


On Apr 12, 2014, at 7:55 AM, Harald Alvestrand <harald@alvestrand.no> wrote:

> On 04/12/2014 11:57 AM, Karl Stahl wrote:
>> To avoid confusion…
>>  
>> Gateways are not mentioned in draft-ietf-rtcweb-transports-03
>>  
>> Under 3.5.  Middle box related functions It too simply says:
>> ICE [RFC5245] MUST be supported.  The implementation MUST be a full
>>    ICE implementation, not ICE-Lite.
>>  
>> It needs to be said that gateways, i.e. devices having a media port 
>> on a public IP address – never behind a NAT/firewall – SHOULD 
>> implement ICE-Lite. (which browsers implementing full ICE correctly 
>> are compatible with – and has to be – which we all have the same 
>> understanding of, I believe)
> 
> I think we've been over this ground before.
> 
> At the moment, the RTCWEB protocol suite documentation deals with
requirements for browsers, not requirements for gateways.
> 
> If someone wishes to start a requirements-for-gateways documents, I think
they should be free to do that - but I hope we can finish this document set
before that.
> 
> 
>>  
>>  
>> /Karl
>>  
>>  
>> Från: rtcweb [mailto:rtcweb-bounces@ietf.org] För Christer Holmberg
>> Skickat: den 12 april 2014 10:26
>> Till: Harald Alvestrand; Martin Thomson; Ram Mohan R (rmohanr)
>> Kopia: rtcweb@ietf.org
>> Ämne: Re: [rtcweb] I-D Action: 
>> draft-ietf-rtcweb-stun-consent-freshness-02.txt
>>  
>> Hi,
>>  
>> It’s not about running a browser on ice-lite – it is about a browser 
>> being prepared to run with a remote endpoint that is running ice-lite 
>> (e.g. a gateway). Certain browser implementations have had some 
>> problems with that, afaik…
>>  
>> Regards,
>>  
>> Christer
>>  
>> From: Harald Alvestrand [mailto:harald@alvestrand.no]
>> Sent: 12 April 2014 08:59
>> To: Christer Holmberg; Martin Thomson; Ram Mohan R (rmohanr)
>> Cc: rtcweb@ietf.org
>> Subject: Re: [rtcweb] I-D Action: 
>> draft-ietf-rtcweb-stun-consent-freshness-02.txt
>>  
>> Seems we have another reason why running a browser on ice-lite is a bad
idea. Good that we do not allow that.
>> 
>> On 11. april 2014 22:37:55 CEST, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
>> Hi,
>>  With ICE-lite mode since the ICE-lite endpoint does not typically  
>> generate any binding requests, it may not generate STUN consent as well.
>> 
>> 
>> Wat?
>> 
>> Consent is generated by responding to connectivity checks.  An ICE-lite
endpoint has to do that.
>> 
>> 
>> Sure, but I guess what is meant is that the ICE-lite endpoint does not
generate STUN consent REQUESTS.
>> 
>> Regards,
>> 
>> Christer
>> 
>> 
>> rtcweb mailing list
>> 
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>> 
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb