Return-Path: 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 C0F801A02D3 for ; Sat, 12 Apr 2014 02:57:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.899 X-Spam-Level: X-Spam-Status: No, score=-0.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001] 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 OQPAwIH2jNb9 for ; Sat, 12 Apr 2014 02:57:09 -0700 (PDT) Received: from smtp.it-norr.com (smtp.it-norr.com [80.244.64.163]) by ietfa.amsl.com (Postfix) with ESMTP id 071DD1A0179 for ; Sat, 12 Apr 2014 02:57:06 -0700 (PDT) Received: from ([90.229.134.75]) by smtp.it-norr.com (Telecom3 SMTP service) with ASMTP id 201404121157033593; Sat, 12 Apr 2014 11:57:03 +0200 From: "Karl Stahl" To: "'Christer Holmberg'" , "'Harald Alvestrand'" , "'Martin Thomson'" , "'Ram Mohan R \(rmohanr\)'" References: <20140411033753.19230.46577.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B1D2BD7C3@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D2BF6E5@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D2BFE90@ESESSMB209.ericsson.se> In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2BFE90@ESESSMB209.ericsson.se> Date: Sat, 12 Apr 2014 11:57:10 +0200 Message-ID: <024c01cf5635$92835650$b78a02f0$@stahl@intertex.se> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_024D_01CF5646.560C2650" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AQHPVTeOIZagSP6uQkS1AgMrcrQE2JsLugCAgABAKVD//9+CAIAAt9gAgAAIw4CAAEbFcIAAe6KAgABKBnCAABKvUA== Content-Language: sv Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/PDrQ8LlwEF9sUzgyQpAJvqzJVhk 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2014 09:57:11 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_024D_01CF5646.560C2650 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To avoid confusion=E2=80=A6 =20 Gateways are not mentioned in draft-ietf-rtcweb-transports-03 =20 Under 3.5. Middle box related functions=20 It too simply says: ICE [RFC5245] MUST be supported. The implementation MUST be a full ICE implementation, not ICE-Lite. =20 It needs to be said that gateways, i.e. devices having a media port on a = public IP address =E2=80=93 never behind a NAT/firewall =E2=80=93 SHOULD = implement ICE-Lite. (which browsers implementing full ICE correctly are = compatible with =E2=80=93 and has to be =E2=80=93 which we all have the = same understanding of, I believe) =20 =20 /Karl =20 =20 Fr=C3=A5n: rtcweb [mailto:rtcweb-bounces@ietf.org] F=C3=B6r Christer = Holmberg Skickat: den 12 april 2014 10:26 Till: Harald Alvestrand; Martin Thomson; Ram Mohan R (rmohanr) Kopia: rtcweb@ietf.org =C3=84mne: Re: [rtcweb] I-D Action: = draft-ietf-rtcweb-stun-consent-freshness-02.txt =20 Hi, =20 It=E2=80=99s not about running a browser on ice-lite =E2=80=93 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=E2=80=A6 =20 Regards, =20 Christer =20 From: Harald Alvestrand [mailto:harald@alvestrand.no]=20 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 =20 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 = wrote: Hi, With ICE-lite mode since the ICE-lite endpoint does not typically=20 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 _____ =20 rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb --=20 Sent from my Android device with K-9 Mail. Please excuse my brevity. ------=_NextPart_000_024D_01CF5646.560C2650 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

To= avoid confusion=E2=80=A6

 

Ga= teways are not mentioned in = draft-ietf-rtcweb-transports-03

 

Un= der 3.5.=C2=A0 Middle box related functions

It= too simply says:

ICE [RFC5245] MUST be = supported.=C2=A0 The implementation MUST be a = full

=C2=A0=C2=A0 ICE implementation, not = ICE-Lite.

 

It= needs to be said that gateways, i.e. devices having a media port on a = public IP address =E2=80=93 never behind a NAT/firewall =E2=80=93 SHOULD = implement ICE-Lite. (which browsers implementing full ICE correctly are = compatible with =E2=80=93 and has to be =E2=80=93 which we all have the = same understanding of, I believe)

 

 

/K= arl

 

 

Fr=C3=A5n: rtcweb = [mailto:rtcweb-bounces@ietf.org] F=C3=B6r Christer = Holmberg
Skickat: den 12 april 2014 10:26
Till: = Harald Alvestrand; Martin Thomson; Ram Mohan R = (rmohanr)
Kopia: rtcweb@ietf.org
=C3=84mne: Re: = [rtcweb] I-D Action: = draft-ietf-rtcweb-stun-consent-freshness-02.txt

 

Hi,

 

It=E2=80=99s not about running a browser on ice-lite =E2=80=93 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=E2=80=A6

 

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.or=
g/mailman/listinfo/rtcweb
<= p class=3DMsoNormal>
--
Sent from my Android = device with K-9 Mail. Please excuse my = brevity.

------=_NextPart_000_024D_01CF5646.560C2650--