Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-ietf-rtcweb-stun-consent-freshness-02.txt
Harald Alvestrand <harald@alvestrand.no> Sat, 12 April 2014 12:55 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 AC5FF1A0118 for <rtcweb@ietfa.amsl.com>; Sat, 12 Apr 2014 05:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level:
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 TMbESjU27ZNL for <rtcweb@ietfa.amsl.com>; Sat, 12 Apr 2014 05:55:40 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1B91A010E for <rtcweb@ietf.org>; Sat, 12 Apr 2014 05:55:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 977DB7C5150; Sat, 12 Apr 2014 14:55:37 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
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 T9EA5Ftzk3LG; Sat, 12 Apr 2014 14:55:36 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:8c75:c2ff:d7f9:c60e] (unknown [IPv6:2001:470:de0a:27:8c75:c2ff:d7f9:c60e]) by mork.alvestrand.no (Postfix) with ESMTPSA id CB5637C054B; Sat, 12 Apr 2014 14:55:35 +0200 (CEST)
Message-ID: <534937C6.5030403@alvestrand.no>
Date: Sat, 12 Apr 2014 14:55:34 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Karl Stahl <karl.stahl@intertex.se>, 'Christer Holmberg' <christer.holmberg@ericsson.com>, 'Martin Thomson' <martin.thomson@gmail.com>, "'Ram Mohan R (rmohanr)'" <rmohanr@cisco.com>
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>
In-Reply-To: <024c01cf5635$92835650$b78a02f0$@stahl@intertex.se>
Content-Type: multipart/alternative; boundary="------------030906040408020800070200"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/gnKGLl5ugsPG5254dz_6dNZ66PQ
Cc: rtcweb@ietf.org
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, 12 Apr 2014 12:55:44 -0000
On 04/12/2014 11:57 AM, Karl Stahl wrote: > > To avoid confusion… > > Gateways are not mentionedin 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 <mailto: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 > <mailto: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 <mailto:rtcweb@ietf.org> > https://www.ietf.org/mailman/listinfo/rtcweb > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. >
- [rtcweb] I-D Action: draft-ietf-rtcweb-stun-conse… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Ram Mohan R (rmohanr)
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Ram Mohan R (rmohanr)
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Karl Stahl
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Harald Alvestrand
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Ram Mohan R (rmohanr)
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Martin Thomson
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Karl Stahl
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Harald Alvestrand
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-c… Christer Holmberg
- Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-iet… Karl Stahl
- Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-iet… Harald Alvestrand
- Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-iet… Cullen Jennings (fluffy)
- Re: [rtcweb] ICE-Lite, Was: I-D Action: draft-iet… Karl Stahl