
From andrew.hutton@unify.com  Thu Jan  2 06:56:13 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203981AE0C4 for <pntaw@ietfa.amsl.com>; Thu,  2 Jan 2014 06:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.538] 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 dB5ssmnWyPUs for <pntaw@ietfa.amsl.com>; Thu,  2 Jan 2014 06:56:11 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 42B411AC440 for <pntaw@ietf.org>; Thu,  2 Jan 2014 06:56:11 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx12.unify.com (Server) with ESMTP id C10E423F0413; Thu,  2 Jan 2014 15:56:02 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.126]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Thu, 2 Jan 2014 15:56:02 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "sergio.garcia.murillo@gmail.com" <sergio.garcia.murillo@gmail.com>
Thread-Topic: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-considerations
Thread-Index: AQHOuEI3WdWGgMZKyk6WRTa2tHhJqppyI70g
Date: Thu, 2 Jan 2014 14:56:01 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C8FA6E@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17BCF3A5@MCHP04MSX.global-ad.net>, ,  <523CCD06.3030902@gmail.com>, <BLU169-W136A55AC013DA147313576D93220@phx.gbl>,	<523CD42E.8070102@gmail.com> <BLU169-W82036280852F26ED26283C93230@phx.gbl>,	<523D4F17.2040202@gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF17BD01A8@MCHP04MSX.global-ad.net> <52400320.2070404@gmail.com> <E44893DD4E290745BB608EB23FDDB7620A0C0990@008-AM1MPN1-043.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0C0990@008-AM1MPN1-043.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bernard_aboba@hotmail.com" <bernard_aboba@hotmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
Subject: Re: [pntaw] New version of	draft-hutton-rtcweb-nat-firewall-considerations
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 14:56:13 -0000

Hi Sergio,

Going back over some old mails with a view to restarting this discussion an=
d updating my draft.

With regard to the transparent proxy could you explain why there is an adva=
ntage to using the RTP over websockets approach as compared to the HTTP CON=
NECT mechanism as currently described in draft-hutton-rtcweb-nat-firewall-c=
onsiderations.

Regards
Andy





> -----Original Message-----
> From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com]
> Sent: 23 September 2013 10:46
> To: sergio.garcia.murillo@gmail.com; Hutton, Andrew
> Cc: bernard_aboba@hotmail.com; pntaw@ietf.org
> Subject: RE: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-
> considerations
>=20
> Hi,
>=20
> Sergio Carcia Murillo wrote:
> >
> > El 22/09/2013 0:48, Hutton, Andrew escribi=F3:
> > > I just don't see any advantage in the TURN over Websockets approach
> over
> > the HTTP Connect initiated tunnel which works without any new
> protocol and
> > therefore works with existing TURN servers.
> >
> > How about transparent proxying?
> >
>=20
> Can you elaborate on this?
>=20
> I think in either case the proxy sees possibly one transaction. In TURN
> over HTTP CONNECT established TLS connection, the proxy sees the HTTP
> CONNECT transaction and it's destination URI. If it's just
> "transparently" proxying, things will work, which is what we want. On
> the other hand, if there is some explicit policy, the proxy can also
> apply it - for instance if the destination domain is now allowed. I'm
> not sure if the TURN over WS has any advantages in this regard.
>=20
> The disadvantage is that TURN over WS would require a change to TURN
> servers. I know you have argued that it is a very trivial change and I
> believe you, but nevertheless all existing servers would need to be
> upgraded and that's the problem.
>=20
> Markus

From partha@parthasarathi.co.in  Fri Jan  3 08:00:25 2014
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7F81ADEB7 for <pntaw@ietfa.amsl.com>; Fri,  3 Jan 2014 08:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 xa5wp4n3RPmk for <pntaw@ietfa.amsl.com>; Fri,  3 Jan 2014 08:00:20 -0800 (PST)
Received: from smtp.mailhostbox.com (outbound-us3.mailhostbox.com [70.87.28.155]) by ietfa.amsl.com (Postfix) with ESMTP id 3FEC01ADFEC for <pntaw@ietf.org>; Fri,  3 Jan 2014 08:00:20 -0800 (PST)
Received: from userPC (unknown [122.178.197.124]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 46A50868604; Fri,  3 Jan 2014 16:00:10 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1388764812; bh=ErCAP7pthyJmz0+JUqXLhRfaYx9Qpsc4IwWLd1Y+rFM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=N8BSnL3CFdjbk0Ak5yZwvBxByWPS6Ihquvw+qE3wZl9s7rKfAmyeCTjTcy/eJxNBO 9Xf52jzfqp/IiYWH2QLozYrqRh9vsxhL4zc9DVXApB5GJ6LIn2Rdrtyn71mbVSZqJO qSNiUqfj5JNskpbLvAsKXUzX+oUCgKU7AMvhbeKM=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: <pntaw@ietf.org>
Date: Fri, 3 Jan 2014 21:29:54 +0530
Message-ID: <000601cf089c$d9fd4bd0$8df7e370$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac8IVQec1IvFm6HRSCyjWxeYfqUhwwARoLswAABLCdA=
Content-Language: en-us
X-CTCH-RefID: str=0001.0A02020A.52C6DE8C.0087, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 2
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.155
Cc: =?utf-8?Q?'Olivier_Cr=C3=AAte'?= <olivier.crete@collabora.com>
Subject: [pntaw] FW: [rtcweb] ICE TCP Candidates and SCTP DataChannels ?
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 16:00:25 -0000

Forwarding to PNTAW mailing alias for more discussion

-----Original Message-----
From: Parthasarathi R [mailto:partha@parthasarathi.co.in]=20
Sent: Friday, January 03, 2014 9:28 PM
To: 'Olivier Cr=C3=AAte'; 'rtcweb@ietf.org'
Subject: RE: [rtcweb] ICE TCP Candidates and SCTP DataChannels ?

Hi Olivier,

Irrespective of TURN or ICE-TCP, SCTP over DTLS over TURN/RFC 4571 over =
TCP has to be supported in case SCTP datachannel mechanism has to be =
traversed through firewall. The similar discussion happened earlier in =
PNTAW and the related mail thread is =
http://www.ietf.org/mail-archive/web/pntaw/current/msg00144.html.

I think that it is better to discuss in detail in pntaw alias about this =
issue. I'll forward this mail to pntaw alias for more discussion.

Thanks
Partha

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Olivier
> Cr=C3=AAte
> Sent: Friday, January 03, 2014 12:55 PM
> To: rtcweb@ietf.org
> Subject: [rtcweb] ICE TCP Candidates and SCTP DataChannels ?
>=20
> Hello,
>=20
> draft-ietf-rtcweb-transports-01 mentions ICE TCP Candidates [RFC6062],
> but there is no mention of how they integrated with the SCTP-based =
data
> channels? ICE-TCP seems to be a good match for ordered reliable
> channels, as I expect these will be the most common. Is there any =
plans
> to support those? Or to do something akin to RFC 4571 framing to put
> SCTP in an ICE-TCP connection? Then that raises the question of DTLS,
> would we want to do SCTP-over-DTLS-over-rfc4571-over-TCP or
> SCTP-over-rfc4571-over-TLS-over-TCP ?
>=20
> --
> Olivier Cr=C3=AAte
> olivier.crete@collabora.com
>=20
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


From andrew.hutton@unify.com  Mon Jan 20 04:09:43 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E5E1A00EF for <pntaw@ietfa.amsl.com>; Mon, 20 Jan 2014 04:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 jFq2IYTN7FeL for <pntaw@ietfa.amsl.com>; Mon, 20 Jan 2014 04:09:42 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5C41A0131 for <pntaw@ietf.org>; Mon, 20 Jan 2014 04:09:40 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 374371EB843E for <pntaw@ietf.org>; Mon, 20 Jan 2014 13:09:39 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.183]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Mon, 20 Jan 2014 13:09:39 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhA
Date: Mon, 20 Jan 2014 12:09:39 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 12:09:44 -0000

I updated draft-hutton-rtcweb-nat-firewall-consideration.

The main change is that the draft now explores the different options that a=
re available for handling such things as HTTP Proxies in a WebRTC environme=
nt and no longer recommends a specific solution.=20

Would be good to restart the discussion on these options and determining th=
e best way forward to ensuring we get some defined standardized behavior fo=
r WebRTC for these scenarios.

So please go ahead and make comments.

Regards
Andy



-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of inte=
rnet-drafts@ietf.org
Sent: 20 January 2014 11:35
To: i-d-announce@ietf.org
Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


        Title           : RTCWEB Considerations for NATs, Firewalls and HTT=
P proxies
        Authors         : Thomas Stach
                          Andrew Hutton
                          Justin Uberti
	Filename        : draft-hutton-rtcweb-nat-firewall-considerations-03.txt
	Pages           : 14
	Date            : 2014-01-20

Abstract:
   This document describes mechanism to enable media stream
   establishment for Real-Time Communication in WEB-browsers (WebRTC) in
   the presence of network address translators, firewalls and HTTP
   proxies.  HTTP proxy and firewall deployed in many private network
   domains introduce obstacles to the successful establishment of media
   stream via WebRTC.  This document examines some of these deployment
   scenarios and specifies requirements on WebRTC enabled web browsers
   designed to provide the best possible chance of media connectivity
   between WebRTC peers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-considera=
tions/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-=
03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firewall-conside=
rations-03


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From andrew.hutton@unify.com  Tue Jan 21 01:27:10 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EB51A0102 for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 VCW8TBBPPSLQ for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:27:08 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id D4A041A00A1 for <pntaw@ietf.org>; Tue, 21 Jan 2014 01:27:07 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx12.unify.com (Server) with ESMTP id 5C06823F0489; Tue, 21 Jan 2014 10:27:06 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.183]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 10:27:06 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "pntaw@ietf.org" <pntaw@ietf.org>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, Dan Wing <dwing@cisco.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "repenno@cisco.com" <repenno@cisco.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhAgAFk3hA=
Date: Tue, 21 Jan 2014 09:27:05 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17CBFB8C@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pntaw] I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 09:27:10 -0000

I probably should have referenced draft-penno-rtcweb-pcp-00 in our firewall=
 considerations draft.

However I just noticed it has expired do the authors intend to maintain thi=
s draft?

Regards
Andy



> -----Original Message-----
> From: pntaw [mailto:pntaw-bounces@ietf.org] On Behalf Of Hutton, Andrew
> Sent: 20 January 2014 12:10
> To: pntaw@ietf.org
> Subject: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-
> considerations-03.txt
>=20
> I updated draft-hutton-rtcweb-nat-firewall-consideration.
>=20
> The main change is that the draft now explores the different options
> that are available for handling such things as HTTP Proxies in a WebRTC
> environment and no longer recommends a specific solution.
>=20
> Would be good to restart the discussion on these options and
> determining the best way forward to ensuring we get some defined
> standardized behavior for WebRTC for these scenarios.
>=20
> So please go ahead and make comments.
>=20
> Regards
> Andy
>=20
>=20
>=20
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 20 January 2014 11:35
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
> 03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
>=20
>         Title           : RTCWEB Considerations for NATs, Firewalls and
> HTTP proxies
>         Authors         : Thomas Stach
>                           Andrew Hutton
>                           Justin Uberti
> 	Filename        : draft-hutton-rtcweb-nat-firewall-
> considerations-03.txt
> 	Pages           : 14
> 	Date            : 2014-01-20
>=20
> Abstract:
>    This document describes mechanism to enable media stream
>    establishment for Real-Time Communication in WEB-browsers (WebRTC)
> in
>    the presence of network address translators, firewalls and HTTP
>    proxies.  HTTP proxy and firewall deployed in many private network
>    domains introduce obstacles to the successful establishment of media
>    stream via WebRTC.  This document examines some of these deployment
>    scenarios and specifies requirements on WebRTC enabled web browsers
>    designed to provide the best possible chance of media connectivity
>    between WebRTC peers.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-
> considerations/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-
> considerations-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firewall-
> considerations-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From tireddy@cisco.com  Tue Jan 21 01:36:59 2014
Return-Path: <tireddy@cisco.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 726741A00AA for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 EhDRfR6z7z4Z for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:36:57 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 304E71A00A9 for <pntaw@ietf.org>; Tue, 21 Jan 2014 01:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4304; q=dns/txt; s=iport; t=1390297017; x=1391506617; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=FRybBnB2n1mhWPPrEx0pc0P8Nx/E58Yl6+iaSrwvc0w=; b=kyZscS7I+u0C4CY5HqD7QXGs8OmyeJKzeByU2/F3oeJ/V4xmDzFkmIlD IPFxaMVPlnQRj0PD5BKmR8D7CE4y9cAdh+yNgoE2/0QXTZuzEBq5aAWxZ eU3ZoaonrZXTpJsvkY35DGca3HaxksY3eqV6LXdtcZUWrjoiTSaH3YCH8 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMFAAA/3lKtJV2b/2dsb2JhbABZgws4UAa7XIEPFnSCJQEBAQMBAQEBNzQXBAIBCBEEAQELFAkHJwsUCQgCBAESCAESh2IICAXDeheOTjMFBoMegRQEmVSLLoU4gy2CKg
X-IronPort-AV: E=Sophos;i="4.95,695,1384300800"; d="scan'208";a="14315500"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-4.cisco.com with ESMTP; 21 Jan 2014 09:36:56 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0L9auA3017730 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 09:36:56 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.227]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 03:36:56 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>, "pntaw@ietf.org" <pntaw@ietf.org>, "Dan Wing (dwing)" <dwing@cisco.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhAgAFk3hCAAAHOIA==
Date: Tue, 21 Jan 2014 09:36:56 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A2428E3B9@xmb-rcd-x10.cisco.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17CBFB8C@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CBFB8C@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.58.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pntaw] I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 09:36:59 -0000

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@unify.com]
> Sent: Tuesday, January 21, 2014 2:57 PM
> To: pntaw@ietf.org; Tirumaleswar Reddy (tireddy); Dan Wing (dwing);
> mohamed.boucadair@orange.com; Reinaldo Penno (repenno); Reinaldo
> Penno (repenno)
> Subject: RE: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
> 03.txt
>=20
> I probably should have referenced draft-penno-rtcweb-pcp-00 in our firewa=
ll
> considerations draft.
>=20
> However I just noticed it has expired do the authors intend to maintain t=
his
> draft ?

Hi Andy,

Yes, we plan to the update the draft with a new section explaining how PCP =
can also be used to prioritize over-the-top WebRTC media in local and immed=
iately adjacent access networks.=20

Cheers,
-Tiru.

>=20
> Regards
> Andy
>=20
>=20
>=20
> > -----Original Message-----
> > From: pntaw [mailto:pntaw-bounces@ietf.org] On Behalf Of Hutton,
> > Andrew
> > Sent: 20 January 2014 12:10
> > To: pntaw@ietf.org
> > Subject: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-
> > considerations-03.txt
> >
> > I updated draft-hutton-rtcweb-nat-firewall-consideration.
> >
> > The main change is that the draft now explores the different options
> > that are available for handling such things as HTTP Proxies in a
> > WebRTC environment and no longer recommends a specific solution.
> >
> > Would be good to restart the discussion on these options and
> > determining the best way forward to ensuring we get some defined
> > standardized behavior for WebRTC for these scenarios.
> >
> > So please go ahead and make comments.
> >
> > Regards
> > Andy
> >
> >
> >
> > -----Original Message-----
> > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org
> > Sent: 20 January 2014 11:35
> > To: i-d-announce@ietf.org
> > Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
> > 03.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> >         Title           : RTCWEB Considerations for NATs, Firewalls and
> > HTTP proxies
> >         Authors         : Thomas Stach
> >                           Andrew Hutton
> >                           Justin Uberti
> > 	Filename        : draft-hutton-rtcweb-nat-firewall-
> > considerations-03.txt
> > 	Pages           : 14
> > 	Date            : 2014-01-20
> >
> > Abstract:
> >    This document describes mechanism to enable media stream
> >    establishment for Real-Time Communication in WEB-browsers (WebRTC)
> > in
> >    the presence of network address translators, firewalls and HTTP
> >    proxies.  HTTP proxy and firewall deployed in many private network
> >    domains introduce obstacles to the successful establishment of media
> >    stream via WebRTC.  This document examines some of these deployment
> >    scenarios and specifies requirements on WebRTC enabled web browsers
> >    designed to provide the best possible chance of media connectivity
> >    between WebRTC peers.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-
> > considerations/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-
> > considerations-03
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firewall-
> > considerations-03
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
> > tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw

From mom040267@gmail.com  Tue Jan 21 01:37:13 2014
Return-Path: <mom040267@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F33531A00AA for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:37:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 cCd-qwJApdr9 for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 01:37:10 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id B11611A00A9 for <pntaw@ietf.org>; Tue, 21 Jan 2014 01:37:10 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so4493310pbc.10 for <pntaw@ietf.org>; Tue, 21 Jan 2014 01:37:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SMbP+pmEiBjW8CC9bt3lnKc+7wM+YMAjDokTQTpzNNw=; b=FsUxIa/07T2qLYH3HA6zm7brKqTV6hlLAp5iJ/n7/anl8HET2tyMbH46BT0Rd9cqQd Fb88fx8IV9Lmlut7JNcZEmbIFcDn4pnaspP0vtJQI2zc23V3ZxR6f0Eca/40s6nXiy1+ sMtBveGcvSiX3t10fq3FbUsOe2mM/MebUxdsfwQhHKRR4MqTvfIamlm2nu/s+u0U2Dt9 aZ/iaJ/AeYOAsnmM1964NJRqzwaxmPklmKFD8A70tzZxwcxNV+LbG/z4i4COR3wx5NlM iTVNki0T7zhP71WWXAprNZCBNDnnDjGO2srpCK+R/mWCKdwanfjuhi9EYXpbYT+XeNAn mPhQ==
MIME-Version: 1.0
X-Received: by 10.66.228.37 with SMTP id sf5mr23718605pac.19.1390297030731; Tue, 21 Jan 2014 01:37:10 -0800 (PST)
Received: by 10.68.147.131 with HTTP; Tue, 21 Jan 2014 01:37:10 -0800 (PST)
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
Date: Tue, 21 Jan 2014 01:37:10 -0800
Message-ID: <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
From: Oleg Moskalenko <mom040267@gmail.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>
Content-Type: multipart/alternative; boundary=047d7b111dd9a62f3304f077c083
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 09:37:13 -0000

--047d7b111dd9a62f3304f077c083
Content-Type: text/plain; charset=ISO-8859-1

I have a comment on section 5 of the document.

One thing that I'd definitely like to see enforced in the browser's
implementation of the TURN client protocol is the support of 300 Alternate
Server error message. This is becoming an issue because of the possible
volume of the WebRTC media traffic. If the browsers are supporting the
error 300, then a TURN server administrator can relatively easy set a load
balancing scheme. If the browsers do not support it, then it becomes a more
complicated issue and an implementation-dependent procedure.

As far as I know, no current browser supports 300 response from TURN
server. It would be very nice if the TURN server administrator could rely
on that feature.

Oleg


On Mon, Jan 20, 2014 at 4:09 AM, Hutton, Andrew <andrew.hutton@unify.com>wrote:

> I updated draft-hutton-rtcweb-nat-firewall-consideration.
>
> The main change is that the draft now explores the different options that
> are available for handling such things as HTTP Proxies in a WebRTC
> environment and no longer recommends a specific solution.
>
> Would be good to restart the discussion on these options and determining
> the best way forward to ensuring we get some defined standardized behavior
> for WebRTC for these scenarios.
>
> So please go ahead and make comments.
>
> Regards
> Andy
>
>
>
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 20 January 2014 11:35
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : RTCWEB Considerations for NATs, Firewalls and
> HTTP proxies
>         Authors         : Thomas Stach
>                           Andrew Hutton
>                           Justin Uberti
>         Filename        :
> draft-hutton-rtcweb-nat-firewall-considerations-03.txt
>         Pages           : 14
>         Date            : 2014-01-20
>
> Abstract:
>    This document describes mechanism to enable media stream
>    establishment for Real-Time Communication in WEB-browsers (WebRTC) in
>    the presence of network address translators, firewalls and HTTP
>    proxies.  HTTP proxy and firewall deployed in many private network
>    domains introduce obstacles to the successful establishment of media
>    stream via WebRTC.  This document examines some of these deployment
>    scenarios and specifies requirements on WebRTC enabled web browsers
>    designed to provide the best possible chance of media connectivity
>    between WebRTC peers.
>
>
> The IETF datatracker status page for this draft is:
>
> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-considerations/
>
> There's also a htmlized version available at:
>
> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-03
>
> A diff from the previous version is available at:
>
> http://www.ietf.org/rfcdiff?url2=draft-hutton-rtcweb-nat-firewall-considerations-03
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>

--047d7b111dd9a62f3304f077c083
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I have a comment on section 5 of the document.<b=
r><br>One thing that I&#39;d definitely like to see enforced in the browser=
&#39;s implementation of the TURN client protocol is the support of 300 Alt=
ernate Server error message. This is becoming an issue because of the possi=
ble volume of the WebRTC media traffic. If the browsers are supporting the =
error 300, then a TURN server administrator can relatively easy set a load =
balancing scheme. If the browsers do not support it, then it becomes a more=
 complicated issue and an implementation-dependent procedure.<br>
<br></div>As far as I know, no current browser supports 300 response from T=
URN server. It would be very nice if the TURN server administrator could re=
ly on that feature.<br></div><div><br></div>Oleg<br></div><div class=3D"gma=
il_extra">
<br><br><div class=3D"gmail_quote">On Mon, Jan 20, 2014 at 4:09 AM, Hutton,=
 Andrew <span dir=3D"ltr">&lt;<a href=3D"mailto:andrew.hutton@unify.com" ta=
rget=3D"_blank">andrew.hutton@unify.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
I updated draft-hutton-rtcweb-nat-firewall-consideration.<br>
<br>
The main change is that the draft now explores the different options that a=
re available for handling such things as HTTP Proxies in a WebRTC environme=
nt and no longer recommends a specific solution.<br>
<br>
Would be good to restart the discussion on these options and determining th=
e best way forward to ensuring we get some defined standardized behavior fo=
r WebRTC for these scenarios.<br>
<br>
So please go ahead and make comments.<br>
<br>
Regards<br>
Andy<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: I-D-Announce [mailto:<a href=3D"mailto:i-d-announce-bounces@ietf.org"=
>i-d-announce-bounces@ietf.org</a>] On Behalf Of <a href=3D"mailto:internet=
-drafts@ietf.org">internet-drafts@ietf.org</a><br>
Sent: 20 January 2014 11:35<br>
To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt=
<br>
<br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : RTCWEB Considerations for NATs,=
 Firewalls and HTTP proxies<br>
=A0 =A0 =A0 =A0 Authors =A0 =A0 =A0 =A0 : Thomas Stach<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Andrew Hutton<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Justin Uberti<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-hutton-rtcweb-nat-firewall-=
considerations-03.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 14<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2014-01-20<br>
<br>
Abstract:<br>
=A0 =A0This document describes mechanism to enable media stream<br>
=A0 =A0establishment for Real-Time Communication in WEB-browsers (WebRTC) i=
n<br>
=A0 =A0the presence of network address translators, firewalls and HTTP<br>
=A0 =A0proxies. =A0HTTP proxy and firewall deployed in many private network=
<br>
=A0 =A0domains introduce obstacles to the successful establishment of media=
<br>
=A0 =A0stream via WebRTC. =A0This document examines some of these deploymen=
t<br>
=A0 =A0scenarios and specifies requirements on WebRTC enabled web browsers<=
br>
=A0 =A0designed to provide the best possible chance of media connectivity<b=
r>
=A0 =A0between WebRTC peers.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewal=
l-considerations/" target=3D"_blank">https://datatracker.ietf.org/doc/draft=
-hutton-rtcweb-nat-firewall-considerations/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-cons=
iderations-03" target=3D"_blank">http://tools.ietf.org/html/draft-hutton-rt=
cweb-nat-firewall-considerations-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firew=
all-considerations-03" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=
=3Ddraft-hutton-rtcweb-nat-firewall-considerations-03</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d=
-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_blank">=
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
_______________________________________________<br>
pntaw mailing list<br>
<a href=3D"mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/pntaw</a><br>
</blockquote></div><br></div>

--047d7b111dd9a62f3304f077c083--

From andrew.hutton@unify.com  Tue Jan 21 03:01:17 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77F231A0050 for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 03:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 muhpQeMfIWFJ for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 03:01:16 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id AF6FE1A009D for <pntaw@ietf.org>; Tue, 21 Jan 2014 03:01:15 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 5685E23F03F9; Tue, 21 Jan 2014 12:01:14 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.183]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 12:01:15 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Oleg Moskalenko <mom040267@gmail.com>
Thread-Topic: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhAgAFYAwCAACZ6MA==
Date: Tue, 21 Jan 2014 11:01:14 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17CBFD95@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
In-Reply-To: <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 11:01:17 -0000

Hi Oleg,

I am thinking this maybe should be a comment against http://tools.ietf.org/=
html/draft-ietf-rtcweb-transports-01#section-2.2 but would be happy to add =
it to draft-hutton-rtcweb-nat-firewall-considerations if people think it is=
 the right place.

Regards
Andy



> -----Original Message-----
> From: Oleg Moskalenko [mailto:mom040267@gmail.com]
> Sent: 21 January 2014 09:37
> To: Hutton, Andrew
> Cc: pntaw@ietf.org
> Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-
> considerations-03.txt
>=20
> I have a comment on section 5 of the document.
>=20
> One thing that I'd definitely like to see enforced in the browser's
> implementation of the TURN client protocol is the support of 300
> Alternate Server error message. This is becoming an issue because of
> the possible volume of the WebRTC media traffic. If the browsers are
> supporting the error 300, then a TURN server administrator can
> relatively easy set a load balancing scheme. If the browsers do not
> support it, then it becomes a more complicated issue and an
> implementation-dependent procedure.
> As far as I know, no current browser supports 300 response from TURN
> server. It would be very nice if the TURN server administrator could
> rely on that feature.
>=20
> Oleg
>=20
> On Mon, Jan 20, 2014 at 4:09 AM, Hutton, Andrew
> <andrew.hutton@unify.com> wrote:
> I updated draft-hutton-rtcweb-nat-firewall-consideration.
>=20
> The main change is that the draft now explores the different options
> that are available for handling such things as HTTP Proxies in a WebRTC
> environment and no longer recommends a specific solution.
>=20
> Would be good to restart the discussion on these options and
> determining the best way forward to ensuring we get some defined
> standardized behavior for WebRTC for these scenarios.
>=20
> So please go ahead and make comments.
>=20
> Regards
> Andy
>=20
>=20
>=20
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 20 January 2014 11:35
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
> 03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
>=20
> =A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : RTCWEB Considerations for NAT=
s, Firewalls and
> HTTP proxies
> =A0 =A0 =A0 =A0 Authors =A0 =A0 =A0 =A0 : Thomas Stach
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Andrew Hutton
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Justin Uberti
> =A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-hutton-rtcweb-nat-firewal=
l-
> considerations-03.txt
> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 14
> =A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2014-01-20
>=20
> Abstract:
> =A0 =A0This document describes mechanism to enable media stream
> =A0 =A0establishment for Real-Time Communication in WEB-browsers (WebRTC)
> in
> =A0 =A0the presence of network address translators, firewalls and HTTP
> =A0 =A0proxies. =A0HTTP proxy and firewall deployed in many private netwo=
rk
> =A0 =A0domains introduce obstacles to the successful establishment of med=
ia
> =A0 =A0stream via WebRTC. =A0This document examines some of these deploym=
ent
> =A0 =A0scenarios and specifies requirements on WebRTC enabled web browser=
s
> =A0 =A0designed to provide the best possible chance of media connectivity
> =A0 =A0between WebRTC peers.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-
> considerations/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-
> considerations-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firewall-
> considerations-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From harald@alvestrand.no  Tue Jan 21 06:46:04 2014
Return-Path: <harald@alvestrand.no>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D32D1A0163 for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 06:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 9MQ1M_RYHlvi for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 06:46:01 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [IPv6:2001:700:1:2:213:72ff:fe0b:80d8]) by ietfa.amsl.com (Postfix) with ESMTP id B72C41A015D for <pntaw@ietf.org>; Tue, 21 Jan 2014 06:46:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9164B39E1FC for <pntaw@ietf.org>; Tue, 21 Jan 2014 15:46:07 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ULl2lMpre-M for <pntaw@ietf.org>; Tue, 21 Jan 2014 15:46:05 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 252DF39E132 for <pntaw@ietf.org>; Tue, 21 Jan 2014 15:46:05 +0100 (CET)
Message-ID: <52DE8824.9010601@alvestrand.no>
Date: Tue, 21 Jan 2014 15:45:56 +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: pntaw@ietf.org
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF17CBFD95@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CBFD95@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 14:46:04 -0000

On 01/21/2014 12:01 PM, Hutton, Andrew wrote:
> Hi Oleg,
>
> I am thinking this maybe should be a comment against http://tools.ietf.org/html/draft-ietf-rtcweb-transports-01#section-2.2 but would be happy to add it to draft-hutton-rtcweb-nat-firewall-considerations if people think it is the right place.

It's not specifically a firewall issue (it applies every time you have a 
NAT), so I think -transport- is the right place for it (and discussion 
should be on the RTCWEB list).


>
> Regards
> Andy
>
>
>
>> -----Original Message-----
>> From: Oleg Moskalenko [mailto:mom040267@gmail.com]
>> Sent: 21 January 2014 09:37
>> To: Hutton, Andrew
>> Cc: pntaw@ietf.org
>> Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-
>> considerations-03.txt
>>
>> I have a comment on section 5 of the document.
>>
>> One thing that I'd definitely like to see enforced in the browser's
>> implementation of the TURN client protocol is the support of 300
>> Alternate Server error message. This is becoming an issue because of
>> the possible volume of the WebRTC media traffic. If the browsers are
>> supporting the error 300, then a TURN server administrator can
>> relatively easy set a load balancing scheme. If the browsers do not
>> support it, then it becomes a more complicated issue and an
>> implementation-dependent procedure.
>> As far as I know, no current browser supports 300 response from TURN
>> server. It would be very nice if the TURN server administrator could
>> rely on that feature.
>>
>> Oleg
>>
>> On Mon, Jan 20, 2014 at 4:09 AM, Hutton, Andrew
>> <andrew.hutton@unify.com> wrote:
>> I updated draft-hutton-rtcweb-nat-firewall-consideration.
>>
>> The main change is that the draft now explores the different options
>> that are available for handling such things as HTTP Proxies in a WebRTC
>> environment and no longer recommends a specific solution.
>>
>> Would be good to restart the discussion on these options and
>> determining the best way forward to ensuring we get some defined
>> standardized behavior for WebRTC for these scenarios.
>>
>> So please go ahead and make comments.
>>
>> Regards
>> Andy
>>
>>
>>
>> -----Original Message-----
>> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
>> internet-drafts@ietf.org
>> Sent: 20 January 2014 11:35
>> To: i-d-announce@ietf.org
>> Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
>> 03.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>          Title           : RTCWEB Considerations for NATs, Firewalls and
>> HTTP proxies
>>          Authors         : Thomas Stach
>>                            Andrew Hutton
>>                            Justin Uberti
>>          Filename        : draft-hutton-rtcweb-nat-firewall-
>> considerations-03.txt
>>          Pages           : 14
>>          Date            : 2014-01-20
>>
>> Abstract:
>>     This document describes mechanism to enable media stream
>>     establishment for Real-Time Communication in WEB-browsers (WebRTC)
>> in
>>     the presence of network address translators, firewalls and HTTP
>>     proxies.  HTTP proxy and firewall deployed in many private network
>>     domains introduce obstacles to the successful establishment of media
>>     stream via WebRTC.  This document examines some of these deployment
>>     scenarios and specifies requirements on WebRTC enabled web browsers
>>     designed to provide the best possible chance of media connectivity
>>     between WebRTC peers.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-
>> considerations/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-
>> considerations-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-hutton-rtcweb-nat-firewall-
>> considerations-03
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From simon.perreault@viagenie.ca  Tue Jan 21 07:06:31 2014
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC02D1A02BB for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 07:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] 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 sQgxORiExggO for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 07:06:30 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA0D1A0166 for <pntaw@ietf.org>; Tue, 21 Jan 2014 07:06:30 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 471F840367 for <pntaw@ietf.org>; Tue, 21 Jan 2014 10:06:30 -0500 (EST)
Message-ID: <52DE8CF5.1050609@viagenie.ca>
Date: Tue, 21 Jan 2014 10:06:29 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: pntaw@ietf.org
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
In-Reply-To: <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:06:32 -0000

Le 2014-01-21 04:37, Oleg Moskalenko a écrit :
> If the browsers are supporting the error 300, then a TURN server
> administrator can relatively easy set a load balancing scheme. If
> the browsers do not support it, then it becomes a more complicated
> issue and an implementation-dependent procedure.
>
> As far as I know, no current browser supports 300 response from TURN
> server. It would be very nice if the TURN server administrator could
> rely on that feature.

+1

In addition, I believe the missing keyword to understand the importance 
of this is "anycast".

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From mom040267@gmail.com  Tue Jan 21 09:31:52 2014
Return-Path: <mom040267@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48ABA1A01B4 for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 09:31:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 RRqopgploTGJ for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 09:31:49 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id ABF441A011D for <pntaw@ietf.org>; Tue, 21 Jan 2014 09:31:49 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id q10so6426155pdj.38 for <pntaw@ietf.org>; Tue, 21 Jan 2014 09:31:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p0hgv2kPEBkFf6Px7PsW4OXRGkDv8e38oR4AzsBsk5Y=; b=r80Sq6god8YAEhS4PpWSiICAnHS5MVwJpV7Yu4/qK4/Usoa3Gbqy3yaJu1JOw7Mdbh 8sySIPWQT9KK8m86lucj5fCXGfeI+PFSqjB86zCBXAAiZgiodquadNxbvZgFN45YRR3H TFA/qoItErMTH4eg2m0X2eOp6epUVlJfi6eT+sT2GvNyFcOe4uRPgSzGOYbZUSD0QGmx cZewxscA4i1vwrhje7TI5HNeG3c4vOuvw2t4xXMFelAyRv2A4lCIohIK1m6Y/W2j2J2K 6UlMZEo1PJahxkSiv7FY4fzujqd0KcQZy6UED14M1zoK8hIdNKaVB/mJ0sdKYDjjKhty oDMA==
MIME-Version: 1.0
X-Received: by 10.66.148.134 with SMTP id ts6mr25662428pab.113.1390325509592;  Tue, 21 Jan 2014 09:31:49 -0800 (PST)
Received: by 10.68.147.131 with HTTP; Tue, 21 Jan 2014 09:31:49 -0800 (PST)
In-Reply-To: <52DE8824.9010601@alvestrand.no>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF17CBFD95@MCHP04MSX.global-ad.net> <52DE8824.9010601@alvestrand.no>
Date: Tue, 21 Jan 2014 09:31:49 -0800
Message-ID: <CALDtMr+jp+9E0wsYM4ChQ7DSvaZEkdQ_cBjERLHFw+cvhpNt-g@mail.gmail.com>
From: Oleg Moskalenko <mom040267@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=047d7b6783001f1bac04f07e6209
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 17:31:52 -0000

--047d7b6783001f1bac04f07e6209
Content-Type: text/plain; charset=ISO-8859-1

Harald, if you think that your "transports" draft is the right place to
include the 300 response requirement, and you do not mind including it,
then I am fine with that.

Thanks
Oleg


On Tue, Jan 21, 2014 at 6:45 AM, Harald Alvestrand <harald@alvestrand.no>wrote:

> On 01/21/2014 12:01 PM, Hutton, Andrew wrote:
>
>> Hi Oleg,
>>
>> I am thinking this maybe should be a comment against
>> http://tools.ietf.org/html/draft-ietf-rtcweb-transports-01#section-2.2but would be happy to add it to draft-hutton-rtcweb-nat-firewall-considerations
>> if people think it is the right place.
>>
>
> It's not specifically a firewall issue (it applies every time you have a
> NAT), so I think -transport- is the right place for it (and discussion
> should be on the RTCWEB list).
>
>
>
>
>> Regards
>> Andy
>>
>>
>>
>>  -----Original Message-----
>>> From: Oleg Moskalenko [mailto:mom040267@gmail.com]
>>> Sent: 21 January 2014 09:37
>>> To: Hutton, Andrew
>>> Cc: pntaw@ietf.org
>>> Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-
>>> considerations-03.txt
>>>
>>> I have a comment on section 5 of the document.
>>>
>>> One thing that I'd definitely like to see enforced in the browser's
>>> implementation of the TURN client protocol is the support of 300
>>> Alternate Server error message. This is becoming an issue because of
>>> the possible volume of the WebRTC media traffic. If the browsers are
>>> supporting the error 300, then a TURN server administrator can
>>> relatively easy set a load balancing scheme. If the browsers do not
>>> support it, then it becomes a more complicated issue and an
>>> implementation-dependent procedure.
>>> As far as I know, no current browser supports 300 response from TURN
>>> server. It would be very nice if the TURN server administrator could
>>> rely on that feature.
>>>
>>> Oleg
>>>
>>> On Mon, Jan 20, 2014 at 4:09 AM, Hutton, Andrew
>>> <andrew.hutton@unify.com> wrote:
>>> I updated draft-hutton-rtcweb-nat-firewall-consideration.
>>>
>>> The main change is that the draft now explores the different options
>>> that are available for handling such things as HTTP Proxies in a WebRTC
>>> environment and no longer recommends a specific solution.
>>>
>>> Would be good to restart the discussion on these options and
>>> determining the best way forward to ensuring we get some defined
>>> standardized behavior for WebRTC for these scenarios.
>>>
>>> So please go ahead and make comments.
>>>
>>> Regards
>>> Andy
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
>>> internet-drafts@ietf.org
>>> Sent: 20 January 2014 11:35
>>> To: i-d-announce@ietf.org
>>> Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-
>>> 03.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>
>>>
>>>          Title           : RTCWEB Considerations for NATs, Firewalls and
>>> HTTP proxies
>>>          Authors         : Thomas Stach
>>>                            Andrew Hutton
>>>                            Justin Uberti
>>>          Filename        : draft-hutton-rtcweb-nat-firewall-
>>> considerations-03.txt
>>>          Pages           : 14
>>>          Date            : 2014-01-20
>>>
>>> Abstract:
>>>     This document describes mechanism to enable media stream
>>>     establishment for Real-Time Communication in WEB-browsers (WebRTC)
>>> in
>>>     the presence of network address translators, firewalls and HTTP
>>>     proxies.  HTTP proxy and firewall deployed in many private network
>>>     domains introduce obstacles to the successful establishment of media
>>>     stream via WebRTC.  This document examines some of these deployment
>>>     scenarios and specifies requirements on WebRTC enabled web browsers
>>>     designed to provide the best possible chance of media connectivity
>>>     between WebRTC peers.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-
>>> considerations/
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-
>>> considerations-03
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-hutton-rtcweb-nat-firewall-
>>> considerations-03
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>> _______________________________________________
>>> pntaw mailing list
>>> pntaw@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pntaw
>>>
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>>
>
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>

--047d7b6783001f1bac04f07e6209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Harald, if you think that your &quot;transports&quot;=
 draft is the right place to include the 300 response requirement, and you =
do not mind including it, then I am fine with that.<br><br></div>Thanks<br>
Oleg<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"=
>On Tue, Jan 21, 2014 at 6:45 AM, Harald Alvestrand <span dir=3D"ltr">&lt;<=
a href=3D"mailto:harald@alvestrand.no" target=3D"_blank">harald@alvestrand.=
no</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 01/21/2014 12:01 PM, Hu=
tton, Andrew wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Oleg,<br>
<br>
I am thinking this maybe should be a comment against <a href=3D"http://tool=
s.ietf.org/html/draft-ietf-rtcweb-transports-01#section-2.2" target=3D"_bla=
nk">http://tools.ietf.org/html/<u></u>draft-ietf-rtcweb-transports-<u></u>0=
1#section-2.2</a> but would be happy to add it to draft-hutton-rtcweb-nat-<=
u></u>firewall-considerations if people think it is the right place.<br>

</blockquote>
<br></div>
It&#39;s not specifically a firewall issue (it applies every time you have =
a NAT), so I think -transport- is the right place for it (and discussion sh=
ould be on the RTCWEB list).<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards<br>
Andy<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
-----Original Message-----<br>
From: Oleg Moskalenko [mailto:<a href=3D"mailto:mom040267@gmail.com" target=
=3D"_blank">mom040267@gmail.com</a>]<br>
Sent: 21 January 2014 09:37<br>
To: Hutton, Andrew<br>
Cc: <a href=3D"mailto:pntaw@ietf.org" target=3D"_blank">pntaw@ietf.org</a><=
br>
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-<u></u>firewal=
l-<br>
considerations-03.txt<br>
<br>
I have a comment on section 5 of the document.<br>
<br>
One thing that I&#39;d definitely like to see enforced in the browser&#39;s=
<br>
implementation of the TURN client protocol is the support of 300<br>
Alternate Server error message. This is becoming an issue because of<br>
the possible volume of the WebRTC media traffic. If the browsers are<br>
supporting the error 300, then a TURN server administrator can<br>
relatively easy set a load balancing scheme. If the browsers do not<br>
support it, then it becomes a more complicated issue and an<br>
implementation-dependent procedure.<br>
As far as I know, no current browser supports 300 response from TURN<br>
server. It would be very nice if the TURN server administrator could<br>
rely on that feature.<br>
<br>
Oleg<br>
<br>
On Mon, Jan 20, 2014 at 4:09 AM, Hutton, Andrew<br>
&lt;<a href=3D"mailto:andrew.hutton@unify.com" target=3D"_blank">andrew.hut=
ton@unify.com</a>&gt; wrote:<br>
I updated draft-hutton-rtcweb-nat-<u></u>firewall-consideration.<br>
<br>
The main change is that the draft now explores the different options<br>
that are available for handling such things as HTTP Proxies in a WebRTC<br>
environment and no longer recommends a specific solution.<br>
<br>
Would be good to restart the discussion on these options and<br>
determining the best way forward to ensuring we get some defined<br>
standardized behavior for WebRTC for these scenarios.<br>
<br>
So please go ahead and make comments.<br>
<br>
Regards<br>
Andy<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: I-D-Announce [mailto:<a href=3D"mailto:i-d-announce-bounces@ietf.org"=
 target=3D"_blank">i-d-announce-bounces@<u></u>ietf.org</a>] On Behalf Of<b=
r>
<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-draf=
ts@ietf.org</a><br>
Sent: 20 January 2014 11:35<br>
To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce=
@ietf.org</a><br>
Subject: I-D Action: draft-hutton-rtcweb-nat-<u></u>firewall-considerations=
-<br>
03.txt<br>
<br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : RTCWEB Considerations for NA=
Ts, Firewalls and<br>
HTTP proxies<br>
=A0 =A0 =A0 =A0 =A0Authors =A0 =A0 =A0 =A0 : Thomas Stach<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Andrew Hutton<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Justin Uberti<br>
=A0 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-hutton-rtcweb-nat-<u></u=
>firewall-<br>
considerations-03.txt<br>
=A0 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 14<br>
=A0 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2014-01-20<br>
<br>
Abstract:<br>
=A0 =A0 This document describes mechanism to enable media stream<br>
=A0 =A0 establishment for Real-Time Communication in WEB-browsers (WebRTC)<=
br>
in<br>
=A0 =A0 the presence of network address translators, firewalls and HTTP<br>
=A0 =A0 proxies. =A0HTTP proxy and firewall deployed in many private networ=
k<br>
=A0 =A0 domains introduce obstacles to the successful establishment of medi=
a<br>
=A0 =A0 stream via WebRTC. =A0This document examines some of these deployme=
nt<br>
=A0 =A0 scenarios and specifies requirements on WebRTC enabled web browsers=
<br>
=A0 =A0 designed to provide the best possible chance of media connectivity<=
br>
=A0 =A0 between WebRTC peers.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewal=
l-" target=3D"_blank">https://datatracker.ietf.org/<u></u>doc/draft-hutton-=
rtcweb-nat-<u></u>firewall-</a><br>
considerations/<br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-" ta=
rget=3D"_blank">http://tools.ietf.org/html/<u></u>draft-hutton-rtcweb-nat-<=
u></u>firewall-</a><br>
considerations-03<br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-hutton-rtcweb-nat-firew=
all-" target=3D"_blank">http://www.ietf.org/rfcdiff?<u></u>url2=3Ddraft-hut=
ton-rtcweb-nat-<u></u>firewall-</a><br>
considerations-03<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of<br>
submission<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-<u></u>drafts/</a><br>
<br>
______________________________<u></u>_________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announce@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" target=3D"_b=
lank">https://www.ietf.org/mailman/<u></u>listinfo/i-d-announce</a><br>
Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html" tar=
get=3D"_blank">http://www.ietf.org/shadow.<u></u>html</a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_blank">=
ftp://ftp.ietf.org/ietf/<u></u>1shadow-sites.txt</a><br>
______________________________<u></u>_________________<br>
pntaw mailing list<br>
<a href=3D"mailto:pntaw@ietf.org" target=3D"_blank">pntaw@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/pntaw</a><br>
</blockquote>
______________________________<u></u>_________________<br>
pntaw mailing list<br>
<a href=3D"mailto:pntaw@ietf.org" target=3D"_blank">pntaw@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/pntaw</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
pntaw mailing list<br>
<a href=3D"mailto:pntaw@ietf.org" target=3D"_blank">pntaw@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/pntaw</a><br>
</div></div></blockquote></div><br></div>

--047d7b6783001f1bac04f07e6209--

From hangzhou.chenxin@huawei.com  Wed Jan 22 03:47:53 2014
Return-Path: <hangzhou.chenxin@huawei.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3111A0436 for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 03:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level: 
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] 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 HBNywfLRXQ-t for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 03:47:51 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5BA1A009D for <pntaw@ietf.org>; Wed, 22 Jan 2014 03:47:50 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAH48928; Wed, 22 Jan 2014 11:47:48 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 11:47:33 +0000
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 11:47:45 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.191]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 19:47:38 +0800
From: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhAgAMSnnA=
Date: Wed, 22 Jan 2014 11:47:38 +0000
Message-ID: <9E34D50A21D1D1489134B4D770CE0397680AA8A5@SZXEMA504-MBX.china.huawei.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.17.195]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [pntaw] I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 11:47:53 -0000

SGksDQoNCiAgIEkgaGF2ZSBhIHF1ZXN0aW9uIG9uIHRoZSB0aGlzIGRyYWZ0Og0KDQogIDEuIFNl
Y3Rpb24gMi4zLiBOQVQvRmlyZXdhbGwgb3BlbiBvbmx5IGZvciBUQ1Agb24gcmVzdHJpY3RlZCBw
b3J0cw0KDQogICAgICAgSW4gdGhpcyBjYXNlIHRoZSBmaXJld2FsbCBibG9ja3MgYWxsIG91dGdv
aW5nIHRyYWZmaWMgZXhjZXB0IGZvciBUQ1ANCiAgIHRyYWZmaWMgdG8gc3BlY2lmaWMgcG9ydHMs
IGZvciBleGFtcGxlIHBvcnQgODAgKEhUVFApIGZvciBIVFRQIG9yIDQ0Mw0KICAgZm9yIEhUVFBT
KEhUVFBTKS4gIEEgVFVSTiBzZXJ2ZXIgbGlzdGVuaW5nIHRvIGl0cyBkZWZhdWx0IHBvcnRzICgz
NDc4DQogICBmb3IgVENQL1VEUCwgNTM0OSBmb3IgVExTKSB3b3VsZCBub3QgYmUgcmVhY2hhYmxl
IGluIHRoaXMgY2FzZS4NCiAgIEhvd2V2ZXIsIHRoZSBUVVJOIHNlcnZlciBjYW4gc3RpbGwgYmUg
cmVhY2hlZCB3aGVuIGl0IGlzIGNvbmZpZ3VyZWQNCiAgIHRvIGxpc3RlbiB0byBlLmcuIHRoZSBI
VFRQKFMpIHBvcnRzLg0KDQogICBJZiBJdCBpcyBwb3NzaWJsZSB0aGF0LCBOQVQvRmlyZXdhbGwg
Zm9yYmlkIG5vbmUtaHR0cCBkYXRhIG9uIDgwLzQ0Mywgd2hpY2ggd2lsbCBtYWtlIHRoZSBjbGll
bnQgZmFpbGVkIHRvIGNvbm5lY3QgdG8gdHVybiBzZXJ2ZXIuDQoNCiAgIEkgd2FudCB0aGVyZSBj
b3VsZCBiZSBhIGRpc2N1c3Npb24gb24gdGhhdCBzY2VuYXJpbyAtLQ0KICAgICAgJyBOQVQvRmly
ZXdhbGwgb3BlbiBvbmx5IGZvciBodHRwIHBhY2tldCBvbiByZXN0cmljdGVkIHBvcnRzIHdpdGhv
dXQgdGhlIHByZXNlbmNlIG9mIGh0dHAgcHJveHknDQogICBJcyBzdWNoIGtpbmQgb2Ygc2NlbmUg
Y29tbW9uIGFuZCB2YWx1YWJsZSB0byB3ZWJydGMgYXBwbGljYXRpb24/ICBOZWVkIHdlIGNvbnNp
ZGVyIHN1Y2ggbmF0L2Z3IGNhc2UgYW5kIHJlcXVpcmVtZW50PyBzaG91bGQgd2UgaGFuZGxlIHRo
aXMgbm93IG9yIGNvbnNpZGVyIGl0IGFzIGEgZnV0dXJlIHJlc2VhcmNoLg0KoaEgSSB0aGluayB0
aGlzIG1haWxpbmcgbGlzdCBpcyB0aGUgcmlnaHQgcGxhY2UgdG8gZGlzY3VzcyBpdC4NCg0KDQog
IDIuIFNlY3Rpb24gMy4zDQogICAgIEFsbCBzY2VuYXJpb3MgYmVzaWRlcyB0aGlzIGhhdmUgYSBz
b2x1dGlvbiB0byBtYWtlIHdlYnJ0YyBhcHBsaWNhdGlvbiBzdWNjZXNzZnVsLiBJIHN0aWxsIHRo
aW5rIHJlY29tbWVuZCBzb2x1dGlvbiBzaG91bGQgYmUgYWRkZWQuIEluIG15IG9waW5pb24sIGh0
dHAgY29ubmVjdGlvbiwgYWxwbiwgdHVybiBvdmVyIHdlYnNvY2tldCBhcmUgY2FuZGlkYXRlcy4g
DQoNCiAgMy4gUmVxdWlyZW1lbnRzIGZvciBSVENXRUItZW5hYmxlZCBicm93c2Vycw0KDQogICAg
IiBzdXBwb3J0IGEgbWVjaGFuaXNtIGZvciBjb25uZWN0aW5nIHRvIGEgVFVSTiBzZXJ2ZXIgaW4g
dGhlDQogICAgICBwcmVzZW5jZSBvZiBhIGZpcmV3YWxsIHRoYXQgb25seSBwZXJtaXRzIGNvbm5l
Y3Rpb25zIHRoYXQgb3JnaW5hdGUNCiAgICAgIGZyb20gYSBIVFRQIFByb3h5LiAgVGhlIG1lY2hh
bmlzbSBpcyBmb3IgZnVydGhlciBzdHVkeS4iDQoNCiAgICAgV2h5IGEgZnV0dXJlIHN0dWR5IG1l
Y2hhbmlzbSBiZWNvbWVzIGEgcmVxdWlyZW1lbnQ/ICBmb3Igc2VjdGlvbiAzLjM/DQoNCiAgICAi
dXNlIHRoZSBzYW1lIHByb3h5IHNlbGVjdGlvbiBwcm9jZWR1cmUgZm9yIFRVUk4gYXMgY3VycmVu
dGx5IGRvbmUNCiAgICAgIGZvciBIVFRQIChlLmcuIFdlYiBQcm94eSBBdXRvZGlzY292ZXJ5IFBy
b3RvY29sIChXUEFEKSBhbmQgLnBhYy0NCiAgICAgIGZpbGVzIGZvciBQcm94eS1BdXRvLUNvbmZp
ZykiDQoNCiAgICAgIEkgZG8gbm90IHVuZGVyc3RhbmQgIHdoeSB5b3UgcHV0IHRoaXMgcmVxdWly
ZW1lbnQgaW4gdGhlIGRyYWZ0LiBXaGljaCBzY2VuYXJpbyBpcyBpdCByZWxhcmVkIHRvPw0KDQog
ICA0LiBjb25mdXNpb24gYWJvdXQgdGhlIGRpc2N1c3Npb24gb24gcG50YXc/DQoNCiAgICAgSSB0
aGluayB0aGUgcG50YXcgaXMgZXN0YWJsaXNoZWQgZm9yIHJ0Y3dlYiB0cmFuc3BvcnQgYXJlYXMu
IEhvd2V2ZXIsIEJlY2F1c2Ugb2Ygbm8gY2hhaXJzLCB0aGVyZSB3ZXJlIG1hbnkgZGlzY3Vzc2lv
biBidXQgbm8gZGVjaXNpb24uIEkgZG8gbm90IGtub3cgaWYgcnRjd2ViIGFnZW5kYSBoYXZlIGNv
bnNpZGVyZWQgdGhlIGRpc2N1c3Npb24gaW4gcG50YXcsIGF0IGxlYXN0IEkgZGlkIG5vdCBzZWUg
aXQgaW4gSUVURjg4LiBJIHN0aWxsIHRoaW5rIHRoZXJlIHNob3VsZCBiZSBhIHdheSB0byBjb25j
bHVkZSBhbmQgbWFrZSBkZWNpc2lvbiBvbiByZWxhdGVkIHRvcGljcyBvbiBwbnRhdy4gSSBzdWdn
ZXN0IGNoYWlycyBjb3VsZCBsZWF2ZSBzb21lIHRpbWUgc2xvdCBmb3IgcG50YXcgdG9waWNzIGlu
IElFVEY4OSwgb3Igb3RoZXIgd2F5cy4gQWZ0ZXIgYWxsLCBwbnRhdyBpcyBhIHN1Yi1saXN0IG9m
IHJ0Y3dlYi4gDQoNCg0KQmVzdCBSZWdhcmRzLA0KICAgICBYaW4gDQoNCg0KPi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogcG50YXcgW21haWx0bzpwbnRhdy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgSHV0dG9uLCBBbmRyZXcNCj5TZW50OiBNb25kYXksIEphbnVhcnkg
MjAsIDIwMTQgODoxMCBQTQ0KPlRvOiBwbnRhd0BpZXRmLm9yZw0KPlN1YmplY3Q6IFtwbnRhd10g
Rlc6IEktRCBBY3Rpb246DQo+ZHJhZnQtaHV0dG9uLXJ0Y3dlYi1uYXQtZmlyZXdhbGwtY29uc2lk
ZXJhdGlvbnMtMDMudHh0DQo+DQo+SSB1cGRhdGVkIGRyYWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZp
cmV3YWxsLWNvbnNpZGVyYXRpb24uDQo+DQo+VGhlIG1haW4gY2hhbmdlIGlzIHRoYXQgdGhlIGRy
YWZ0IG5vdyBleHBsb3JlcyB0aGUgZGlmZmVyZW50IG9wdGlvbnMgdGhhdCBhcmUNCj5hdmFpbGFi
bGUgZm9yIGhhbmRsaW5nIHN1Y2ggdGhpbmdzIGFzIEhUVFAgUHJveGllcyBpbiBhIFdlYlJUQyBl
bnZpcm9ubWVudCBhbmQNCj5ubyBsb25nZXIgcmVjb21tZW5kcyBhIHNwZWNpZmljIHNvbHV0aW9u
Lg0KPg0KPldvdWxkIGJlIGdvb2QgdG8gcmVzdGFydCB0aGUgZGlzY3Vzc2lvbiBvbiB0aGVzZSBv
cHRpb25zIGFuZCBkZXRlcm1pbmluZyB0aGUNCj5iZXN0IHdheSBmb3J3YXJkIHRvIGVuc3VyaW5n
IHdlIGdldCBzb21lIGRlZmluZWQgc3RhbmRhcmRpemVkIGJlaGF2aW9yIGZvcg0KPldlYlJUQyBm
b3IgdGhlc2Ugc2NlbmFyaW9zLg0KPg0KPlNvIHBsZWFzZSBnbyBhaGVhZCBhbmQgbWFrZSBjb21t
ZW50cy4NCj4NCj5SZWdhcmRzDQo+QW5keQ0KPg0KPg0KPg0KPi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+RnJvbTogSS1ELUFubm91bmNlIFttYWlsdG86aS1kLWFubm91bmNlLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZg0KPmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPlNlbnQ6
IDIwIEphbnVhcnkgMjAxNCAxMTozNQ0KPlRvOiBpLWQtYW5ub3VuY2VAaWV0Zi5vcmcNCj5TdWJq
ZWN0OiBJLUQgQWN0aW9uOiBkcmFmdC1odXR0b24tcnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRl
cmF0aW9ucy0wMy50eHQNCj4NCj4NCj5BIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUg
ZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuDQo+DQo+DQo+ICAg
ICAgICBUaXRsZSAgICAgICAgICAgOiBSVENXRUIgQ29uc2lkZXJhdGlvbnMgZm9yIE5BVHMsIEZp
cmV3YWxscyBhbmQNCj5IVFRQIHByb3hpZXMNCj4gICAgICAgIEF1dGhvcnMgICAgICAgICA6IFRo
b21hcyBTdGFjaA0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgQW5kcmV3IEh1dHRvbg0KPiAg
ICAgICAgICAgICAgICAgICAgICAgICAgSnVzdGluIFViZXJ0aQ0KPglGaWxlbmFtZSAgICAgICAg
OiBkcmFmdC1odXR0b24tcnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRlcmF0aW9ucy0wMy50eHQN
Cj4JUGFnZXMgICAgICAgICAgIDogMTQNCj4JRGF0ZSAgICAgICAgICAgIDogMjAxNC0wMS0yMA0K
Pg0KPkFic3RyYWN0Og0KPiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIG1lY2hhbmlzbSB0byBl
bmFibGUgbWVkaWEgc3RyZWFtDQo+ICAgZXN0YWJsaXNobWVudCBmb3IgUmVhbC1UaW1lIENvbW11
bmljYXRpb24gaW4gV0VCLWJyb3dzZXJzIChXZWJSVEMpIGluDQo+ICAgdGhlIHByZXNlbmNlIG9m
IG5ldHdvcmsgYWRkcmVzcyB0cmFuc2xhdG9ycywgZmlyZXdhbGxzIGFuZCBIVFRQDQo+ICAgcHJv
eGllcy4gIEhUVFAgcHJveHkgYW5kIGZpcmV3YWxsIGRlcGxveWVkIGluIG1hbnkgcHJpdmF0ZSBu
ZXR3b3JrDQo+ICAgZG9tYWlucyBpbnRyb2R1Y2Ugb2JzdGFjbGVzIHRvIHRoZSBzdWNjZXNzZnVs
IGVzdGFibGlzaG1lbnQgb2YgbWVkaWENCj4gICBzdHJlYW0gdmlhIFdlYlJUQy4gIFRoaXMgZG9j
dW1lbnQgZXhhbWluZXMgc29tZSBvZiB0aGVzZSBkZXBsb3ltZW50DQo+ICAgc2NlbmFyaW9zIGFu
ZCBzcGVjaWZpZXMgcmVxdWlyZW1lbnRzIG9uIFdlYlJUQyBlbmFibGVkIHdlYiBicm93c2Vycw0K
PiAgIGRlc2lnbmVkIHRvIHByb3ZpZGUgdGhlIGJlc3QgcG9zc2libGUgY2hhbmNlIG9mIG1lZGlh
IGNvbm5lY3Rpdml0eQ0KPiAgIGJldHdlZW4gV2ViUlRDIHBlZXJzLg0KPg0KPg0KPlRoZSBJRVRG
IGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPmh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZpcmV3YWxsLWNv
bnNpZGVyYXRpb25zDQo+Lw0KPg0KPlRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZh
aWxhYmxlIGF0Og0KPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWh1dHRvbi1ydGN3
ZWItbmF0LWZpcmV3YWxsLWNvbnNpZGVyYXRpb25zLTAzDQo+DQo+QSBkaWZmIGZyb20gdGhlIHBy
ZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZj
ZGlmZj91cmwyPWRyYWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZpcmV3YWxsLWNvbnNpZGVyYXRpb25z
DQo+LTAzDQo+DQo+DQo+UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPnVudGlsIHRoZSBodG1saXplZCB2
ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+DQo+SW50
ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPmZ0
cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+DQo+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5JLUQtQW5ub3VuY2UgbWFpbGluZyBsaXN0
DQo+SS1ELUFubm91bmNlQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pLWQtYW5ub3VuY2UNCj5JbnRlcm5ldC1EcmFmdCBkaXJlY3RvcmllczogaHR0cDov
L3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPm9yIGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFz
aGFkb3ctc2l0ZXMudHh0DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj5wbnRhdyBtYWlsaW5nIGxpc3QNCj5wbnRhd0BpZXRmLm9yZw0KPmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcG50YXcNCg==

From hangzhou.chenxin@huawei.com  Wed Jan 22 03:56:26 2014
Return-Path: <hangzhou.chenxin@huawei.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202AE1A0444 for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 03:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level: 
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] 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 quyWmfjwERLn for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 03:56:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 975D21A043E for <pntaw@ietf.org>; Wed, 22 Jan 2014 03:56:21 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCU19237; Wed, 22 Jan 2014 11:56:20 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 11:55:16 +0000
Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 11:56:18 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.191]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 19:56:13 +0800
From: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>
To: "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [rtcweb] Query/Comment	on draft-ietf-rtcweb-use-cases-and-requirements-12
Thread-Index: AQHPEdt4BmafjBJA1EK1NoxWhueV6ZqQq+Cw
Date: Wed, 22 Jan 2014 11:56:12 +0000
Message-ID: <9E34D50A21D1D1489134B4D770CE0397680AA8B2@SZXEMA504-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.17.195]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>, "Hutton, Andrew" <andrew.hutton@unify.com>, Parthasarathi R <partha@parthasarathi.co.in>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: [pntaw] FW: [rtcweb] Query/Comment	on	draft-ietf-rtcweb-use-cases-and-requirements-12
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 11:56:26 -0000

 I find it lost in rtcweb mailing list, so I forward it to pntaw list, I th=
ink the guys following this group will be interested in this change proposa=
l. I do not like silence too and I hope the usecase and requirement could b=
e published ASAP.

 The change proposal is related to the discussion on pntaw. Also ,I hope th=
e words could be more accurate and the requirement could be clearer.

 So ,any ideas about it?

 To Magnus:
    What will happen if there is no response?

Best Regards,
     Xin=20


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Wednesday, January 15, 2014 6:20 PM
To: Chenxin (Xin); Hutton, Andrew; Christer Holmberg; Parthasarathi R; rtcw=
eb@ietf.org
Subject: Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requ=
irements-12

WG,

It has been quite some time since the WG last call ended and a new
revision was submitted. As Document Shepherd I want to push this
document to publication request.

Chenxin proposed below three different sets of changes to the document.
Does the WG support making these changes? Please indicate within the
next week if you support or want to reject these changes.

Thanks

Magnus


On 2013-10-17 12:23, Chenxin (Xin) wrote:
> Hi Andy,
>=20
> =20
>=20
>   I think you means F29 not F27:). When I read it , I realize that there
> is cross and ambiguous between 3.3.2 and 3.3.3
>=20
> =20
>=20
>   More details:
>=20
> =20
>=20
>   The topic of 3.3.2 is "Simple Video Communication Service, *NAT/FW*
> that blocks UDP". But in the description and requirement, only *NAT* is
> considered.
>=20
>   The topic of 3.3.3 is "Simple Video Communication Service, FW that
> only allows http", But only *http proxy* deployed scenarios is considered=
.
>=20
> =20
>=20
>   There are other usecases " FW block UDP, incoming TCP, Http allowing
> FW without http proxy deplolyed under the permission of FW policy" ,
> which is lost in the description. If we need consider these usecases , I
> suggest to make some change to the description.
>=20
> =20
>=20
>   Proposal 1 :
>=20
> =20
>=20
>   add FW related words to section 3.3.2
>=20
> -------------------------------------------------
>=20
> 3.3.2.  Simple Video Communication Service, NAT/FW that blocks UDP
>=20
> =20
>=20
> 3.3.2.1.  Description
>=20
> =20
>=20
>    This use-case is almost identical to the Simple Video Communication
>=20
>    Service use-case (Section 3.3.1).  The difference is that one of the
>=20
>    users is behind a NAT*/FW* that blocks UDP traffic.
>=20
> .
>=20
> =20
>=20
> 3.3.2.2.  Additional Requirements
>=20
> =20
>=20
>    F29     The browser must be able to send streams and
>=20
>            data to a peer in the presence of NATs *and FWs* that
>=20
>            block UDP traffic ,* when FW policy allows WebRTC traffic*.
>=20
> -------------------------------------------------------
>=20
>    Proposal 2: If the" Http allowing FW without http proxy deployed"
> case is impliedly included in F29. I suggest to change the topics of
> 3.3.3 to "Simple Video Communication Service, FW that only allows
> traffic via a http proxy". So the 3.3.3 is a specific case.
>=20
> =20
>=20
>     Proposal 3: If " Http allowing FW without http proxy deployed" case
> need to be explicitly mentioned. I suggest to add some descriptions to 3.=
3.3
>=20
> -----------------------------------------------------------------
>=20
> 3.3.3.  Simple Video Communication Service, FW that only allows http
>=20
> =20
>=20
> 3.3.3.1.  Description
>=20
> =20
>=20
>    This use-case is almost identical to the Simple Video Communication
>=20
>    Service use-case (Section 3.3.1).  The difference is that one of the
>=20
>    users is behind a http allowing FW or a FW that only allows traffic
> via a HTTP Proxy.
>=20
> =20
>=20
> 3.3.3.2.  Additional Requirements
>=20
> =20
>=20
>    F37     The browser must be able to send streams and
>=20
>            data to a peer in the presence of http allowing FWs or FWs
> that only
>=20
>            allows traffic via a HTTP Proxy, when FW policy
>=20
>            allows WebRTC traffic.
>=20
> -------------------------------------------------------------------
>=20
> =20
>=20
> =20
>=20
> Best Regards,
>=20
>      Xin
>=20
> =20
>=20


--=20

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
F=E4r=F6gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From hangzhou.chenxin@huawei.com  Wed Jan 22 04:03:36 2014
Return-Path: <hangzhou.chenxin@huawei.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DBD1A043E for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 04:03:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level: 
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] 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 FwKJNfcD6J2O for <pntaw@ietfa.amsl.com>; Wed, 22 Jan 2014 04:03:35 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 992931A043D for <pntaw@ietf.org>; Wed, 22 Jan 2014 04:03:34 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAH50356; Wed, 22 Jan 2014 12:03:33 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 12:03:20 +0000
Received: from SZXEMA402-HUB.china.huawei.com (10.82.72.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 12:03:32 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.191]) by SZXEMA402-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 20:03:25 +0800
From: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhEhAgAMSnnCAABDIoA==
Date: Wed, 22 Jan 2014 12:03:24 +0000
Message-ID: <9E34D50A21D1D1489134B4D770CE0397680AA8CE@SZXEMA504-MBX.china.huawei.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <9E34D50A21D1D1489134B4D770CE0397680AA8A5@SZXEMA504-MBX.china.huawei.com>
In-Reply-To: <9E34D50A21D1D1489134B4D770CE0397680AA8A5@SZXEMA504-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.17.195]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [pntaw] I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 12:03:37 -0000

QmVzaWRlcyAsIEkgc3VwcG9ydCB0aGF0IHRoaXMgZHJhZnQgc2hvdWxkIGJlIGNvbnNpZGVyZWQg
dG8gYmUgYWNjZXB0ZWQgYnkgcnRjd2ViLXRyYW5zcG9ydCBkb2N1bWVudHMgdG9vLg0KDQpCZXN0
IFJlZ2FyZHMsDQogICAgIFhpbiANCg0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5G
cm9tOiBwbnRhdyBbbWFpbHRvOnBudGF3LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBD
aGVueGluIChYaW4pDQo+U2VudDogV2VkbmVzZGF5LCBKYW51YXJ5IDIyLCAyMDE0IDc6NDggUE0N
Cj5UbzogSHV0dG9uLCBBbmRyZXc7IHBudGF3QGlldGYub3JnDQo+U3ViamVjdDogUmU6IFtwbnRh
d10gSS1EIEFjdGlvbjoNCj5kcmFmdC1odXR0b24tcnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRl
cmF0aW9ucy0wMy50eHQNCj4NCj5IaSwNCj4NCj4gICBJIGhhdmUgYSBxdWVzdGlvbiBvbiB0aGUg
dGhpcyBkcmFmdDoNCj4NCj4gIDEuIFNlY3Rpb24gMi4zLiBOQVQvRmlyZXdhbGwgb3BlbiBvbmx5
IGZvciBUQ1Agb24gcmVzdHJpY3RlZCBwb3J0cw0KPg0KPiAgICAgICBJbiB0aGlzIGNhc2UgdGhl
IGZpcmV3YWxsIGJsb2NrcyBhbGwgb3V0Z29pbmcgdHJhZmZpYyBleGNlcHQgZm9yIFRDUA0KPiAg
IHRyYWZmaWMgdG8gc3BlY2lmaWMgcG9ydHMsIGZvciBleGFtcGxlIHBvcnQgODAgKEhUVFApIGZv
ciBIVFRQIG9yIDQ0Mw0KPiAgIGZvciBIVFRQUyhIVFRQUykuICBBIFRVUk4gc2VydmVyIGxpc3Rl
bmluZyB0byBpdHMgZGVmYXVsdCBwb3J0cyAoMzQ3OA0KPiAgIGZvciBUQ1AvVURQLCA1MzQ5IGZv
ciBUTFMpIHdvdWxkIG5vdCBiZSByZWFjaGFibGUgaW4gdGhpcyBjYXNlLg0KPiAgIEhvd2V2ZXIs
IHRoZSBUVVJOIHNlcnZlciBjYW4gc3RpbGwgYmUgcmVhY2hlZCB3aGVuIGl0IGlzIGNvbmZpZ3Vy
ZWQNCj4gICB0byBsaXN0ZW4gdG8gZS5nLiB0aGUgSFRUUChTKSBwb3J0cy4NCj4NCj4gICBJZiBJ
dCBpcyBwb3NzaWJsZSB0aGF0LCBOQVQvRmlyZXdhbGwgZm9yYmlkIG5vbmUtaHR0cCBkYXRhIG9u
IDgwLzQ0Mywgd2hpY2ggd2lsbA0KPm1ha2UgdGhlIGNsaWVudCBmYWlsZWQgdG8gY29ubmVjdCB0
byB0dXJuIHNlcnZlci4NCj4NCj4gICBJIHdhbnQgdGhlcmUgY291bGQgYmUgYSBkaXNjdXNzaW9u
IG9uIHRoYXQgc2NlbmFyaW8gLS0NCj4gICAgICAnIE5BVC9GaXJld2FsbCBvcGVuIG9ubHkgZm9y
IGh0dHAgcGFja2V0IG9uIHJlc3RyaWN0ZWQgcG9ydHMgd2l0aG91dCB0aGUNCj5wcmVzZW5jZSBv
ZiBodHRwIHByb3h5Jw0KPiAgIElzIHN1Y2gga2luZCBvZiBzY2VuZSBjb21tb24gYW5kIHZhbHVh
YmxlIHRvIHdlYnJ0YyBhcHBsaWNhdGlvbj8gIE5lZWQgd2UNCj5jb25zaWRlciBzdWNoIG5hdC9m
dyBjYXNlIGFuZCByZXF1aXJlbWVudD8gc2hvdWxkIHdlIGhhbmRsZSB0aGlzIG5vdyBvcg0KPmNv
bnNpZGVyIGl0IGFzIGEgZnV0dXJlIHJlc2VhcmNoLg0KPqGhIEkgdGhpbmsgdGhpcyBtYWlsaW5n
IGxpc3QgaXMgdGhlIHJpZ2h0IHBsYWNlIHRvIGRpc2N1c3MgaXQuDQo+DQo+DQo+ICAyLiBTZWN0
aW9uIDMuMw0KPiAgICAgQWxsIHNjZW5hcmlvcyBiZXNpZGVzIHRoaXMgaGF2ZSBhIHNvbHV0aW9u
IHRvIG1ha2Ugd2VicnRjIGFwcGxpY2F0aW9uDQo+c3VjY2Vzc2Z1bC4gSSBzdGlsbCB0aGluayBy
ZWNvbW1lbmQgc29sdXRpb24gc2hvdWxkIGJlIGFkZGVkLiBJbiBteSBvcGluaW9uLCBodHRwDQo+
Y29ubmVjdGlvbiwgYWxwbiwgdHVybiBvdmVyIHdlYnNvY2tldCBhcmUgY2FuZGlkYXRlcy4NCj4N
Cj4gIDMuIFJlcXVpcmVtZW50cyBmb3IgUlRDV0VCLWVuYWJsZWQgYnJvd3NlcnMNCj4NCj4gICAg
IiBzdXBwb3J0IGEgbWVjaGFuaXNtIGZvciBjb25uZWN0aW5nIHRvIGEgVFVSTiBzZXJ2ZXIgaW4g
dGhlDQo+ICAgICAgcHJlc2VuY2Ugb2YgYSBmaXJld2FsbCB0aGF0IG9ubHkgcGVybWl0cyBjb25u
ZWN0aW9ucyB0aGF0IG9yZ2luYXRlDQo+ICAgICAgZnJvbSBhIEhUVFAgUHJveHkuICBUaGUgbWVj
aGFuaXNtIGlzIGZvciBmdXJ0aGVyIHN0dWR5LiINCj4NCj4gICAgIFdoeSBhIGZ1dHVyZSBzdHVk
eSBtZWNoYW5pc20gYmVjb21lcyBhIHJlcXVpcmVtZW50PyAgZm9yIHNlY3Rpb24gMy4zPw0KPg0K
PiAgICAidXNlIHRoZSBzYW1lIHByb3h5IHNlbGVjdGlvbiBwcm9jZWR1cmUgZm9yIFRVUk4gYXMg
Y3VycmVudGx5IGRvbmUNCj4gICAgICBmb3IgSFRUUCAoZS5nLiBXZWIgUHJveHkgQXV0b2Rpc2Nv
dmVyeSBQcm90b2NvbCAoV1BBRCkgYW5kIC5wYWMtDQo+ICAgICAgZmlsZXMgZm9yIFByb3h5LUF1
dG8tQ29uZmlnKSINCj4NCj4gICAgICBJIGRvIG5vdCB1bmRlcnN0YW5kICB3aHkgeW91IHB1dCB0
aGlzIHJlcXVpcmVtZW50IGluIHRoZSBkcmFmdC4gV2hpY2gNCj5zY2VuYXJpbyBpcyBpdCByZWxh
cmVkIHRvPw0KPg0KPiAgIDQuIGNvbmZ1c2lvbiBhYm91dCB0aGUgZGlzY3Vzc2lvbiBvbiBwbnRh
dz8NCj4NCj4gICAgIEkgdGhpbmsgdGhlIHBudGF3IGlzIGVzdGFibGlzaGVkIGZvciBydGN3ZWIg
dHJhbnNwb3J0IGFyZWFzLiBIb3dldmVyLA0KPkJlY2F1c2Ugb2Ygbm8gY2hhaXJzLCB0aGVyZSB3
ZXJlIG1hbnkgZGlzY3Vzc2lvbiBidXQgbm8gZGVjaXNpb24uIEkgZG8gbm90IGtub3cNCj5pZiBy
dGN3ZWIgYWdlbmRhIGhhdmUgY29uc2lkZXJlZCB0aGUgZGlzY3Vzc2lvbiBpbiBwbnRhdywgYXQg
bGVhc3QgSSBkaWQgbm90IHNlZSBpdA0KPmluIElFVEY4OC4gSSBzdGlsbCB0aGluayB0aGVyZSBz
aG91bGQgYmUgYSB3YXkgdG8gY29uY2x1ZGUgYW5kIG1ha2UgZGVjaXNpb24gb24NCj5yZWxhdGVk
IHRvcGljcyBvbiBwbnRhdy4gSSBzdWdnZXN0IGNoYWlycyBjb3VsZCBsZWF2ZSBzb21lIHRpbWUg
c2xvdCBmb3IgcG50YXcNCj50b3BpY3MgaW4gSUVURjg5LCBvciBvdGhlciB3YXlzLiBBZnRlciBh
bGwsIHBudGF3IGlzIGEgc3ViLWxpc3Qgb2YgcnRjd2ViLg0KPg0KPg0KPkJlc3QgUmVnYXJkcywN
Cj4gICAgIFhpbg0KPg0KPg0KPj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBw
bnRhdyBbbWFpbHRvOnBudGF3LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBIdXR0b24s
IEFuZHJldw0KPj5TZW50OiBNb25kYXksIEphbnVhcnkgMjAsIDIwMTQgODoxMCBQTQ0KPj5Ubzog
cG50YXdAaWV0Zi5vcmcNCj4+U3ViamVjdDogW3BudGF3XSBGVzogSS1EIEFjdGlvbjoNCj4+ZHJh
ZnQtaHV0dG9uLXJ0Y3dlYi1uYXQtZmlyZXdhbGwtY29uc2lkZXJhdGlvbnMtMDMudHh0DQo+Pg0K
Pj5JIHVwZGF0ZWQgZHJhZnQtaHV0dG9uLXJ0Y3dlYi1uYXQtZmlyZXdhbGwtY29uc2lkZXJhdGlv
bi4NCj4+DQo+PlRoZSBtYWluIGNoYW5nZSBpcyB0aGF0IHRoZSBkcmFmdCBub3cgZXhwbG9yZXMg
dGhlIGRpZmZlcmVudCBvcHRpb25zIHRoYXQgYXJlDQo+PmF2YWlsYWJsZSBmb3IgaGFuZGxpbmcg
c3VjaCB0aGluZ3MgYXMgSFRUUCBQcm94aWVzIGluIGEgV2ViUlRDIGVudmlyb25tZW50DQo+YW5k
DQo+Pm5vIGxvbmdlciByZWNvbW1lbmRzIGEgc3BlY2lmaWMgc29sdXRpb24uDQo+Pg0KPj5Xb3Vs
ZCBiZSBnb29kIHRvIHJlc3RhcnQgdGhlIGRpc2N1c3Npb24gb24gdGhlc2Ugb3B0aW9ucyBhbmQg
ZGV0ZXJtaW5pbmcgdGhlDQo+PmJlc3Qgd2F5IGZvcndhcmQgdG8gZW5zdXJpbmcgd2UgZ2V0IHNv
bWUgZGVmaW5lZCBzdGFuZGFyZGl6ZWQgYmVoYXZpb3IgZm9yDQo+PldlYlJUQyBmb3IgdGhlc2Ug
c2NlbmFyaW9zLg0KPj4NCj4+U28gcGxlYXNlIGdvIGFoZWFkIGFuZCBtYWtlIGNvbW1lbnRzLg0K
Pj4NCj4+UmVnYXJkcw0KPj5BbmR5DQo+Pg0KPj4NCj4+DQo+Pi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+PkZyb206IEktRC1Bbm5vdW5jZSBbbWFpbHRvOmktZC1hbm5vdW5jZS1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4+aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQo+PlNl
bnQ6IDIwIEphbnVhcnkgMjAxNCAxMTozNQ0KPj5UbzogaS1kLWFubm91bmNlQGlldGYub3JnDQo+
PlN1YmplY3Q6IEktRCBBY3Rpb246IGRyYWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZpcmV3YWxsLWNv
bnNpZGVyYXRpb25zLTAzLnR4dA0KPj4NCj4+DQo+PkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2
YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCj4+
DQo+Pg0KPj4gICAgICAgIFRpdGxlICAgICAgICAgICA6IFJUQ1dFQiBDb25zaWRlcmF0aW9ucyBm
b3IgTkFUcywgRmlyZXdhbGxzIGFuZA0KPj5IVFRQIHByb3hpZXMNCj4+ICAgICAgICBBdXRob3Jz
ICAgICAgICAgOiBUaG9tYXMgU3RhY2gNCj4+ICAgICAgICAgICAgICAgICAgICAgICAgICBBbmRy
ZXcgSHV0dG9uDQo+PiAgICAgICAgICAgICAgICAgICAgICAgICAgSnVzdGluIFViZXJ0aQ0KPj4J
RmlsZW5hbWUgICAgICAgIDogZHJhZnQtaHV0dG9uLXJ0Y3dlYi1uYXQtZmlyZXdhbGwtY29uc2lk
ZXJhdGlvbnMtMDMudHh0DQo+PglQYWdlcyAgICAgICAgICAgOiAxNA0KPj4JRGF0ZSAgICAgICAg
ICAgIDogMjAxNC0wMS0yMA0KPj4NCj4+QWJzdHJhY3Q6DQo+PiAgIFRoaXMgZG9jdW1lbnQgZGVz
Y3JpYmVzIG1lY2hhbmlzbSB0byBlbmFibGUgbWVkaWEgc3RyZWFtDQo+PiAgIGVzdGFibGlzaG1l
bnQgZm9yIFJlYWwtVGltZSBDb21tdW5pY2F0aW9uIGluIFdFQi1icm93c2VycyAoV2ViUlRDKSBp
bg0KPj4gICB0aGUgcHJlc2VuY2Ugb2YgbmV0d29yayBhZGRyZXNzIHRyYW5zbGF0b3JzLCBmaXJl
d2FsbHMgYW5kIEhUVFANCj4+ICAgcHJveGllcy4gIEhUVFAgcHJveHkgYW5kIGZpcmV3YWxsIGRl
cGxveWVkIGluIG1hbnkgcHJpdmF0ZSBuZXR3b3JrDQo+PiAgIGRvbWFpbnMgaW50cm9kdWNlIG9i
c3RhY2xlcyB0byB0aGUgc3VjY2Vzc2Z1bCBlc3RhYmxpc2htZW50IG9mIG1lZGlhDQo+PiAgIHN0
cmVhbSB2aWEgV2ViUlRDLiAgVGhpcyBkb2N1bWVudCBleGFtaW5lcyBzb21lIG9mIHRoZXNlIGRl
cGxveW1lbnQNCj4+ICAgc2NlbmFyaW9zIGFuZCBzcGVjaWZpZXMgcmVxdWlyZW1lbnRzIG9uIFdl
YlJUQyBlbmFibGVkIHdlYiBicm93c2Vycw0KPj4gICBkZXNpZ25lZCB0byBwcm92aWRlIHRoZSBi
ZXN0IHBvc3NpYmxlIGNoYW5jZSBvZiBtZWRpYSBjb25uZWN0aXZpdHkNCj4+ICAgYmV0d2VlbiBX
ZWJSVEMgcGVlcnMuDQo+Pg0KPj4NCj4+VGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2Ug
Zm9yIHRoaXMgZHJhZnQgaXM6DQo+Pmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZpcmV3YWxsLWNvbnNpZGVyYXRpbw0KPm5zDQo+Pi8NCj4+
DQo+PlRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZhaWxhYmxlIGF0Og0KPj5odHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1odXR0b24tcnRjd2ViLW5hdC1maXJld2FsbC1j
b25zaWRlcmF0aW9ucy0wMw0KPj4NCj4+QSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24g
aXMgYXZhaWxhYmxlIGF0Og0KPj5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFm
dC1odXR0b24tcnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRlcmF0aW8NCj5ucw0KPj4tMDMNCj4+
DQo+Pg0KPj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMg
ZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+PnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9u
IGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+Pg0KPj5JbnRlcm5l
dC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+PmZ0cDov
L2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+Pg0KPj5fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj5JLUQtQW5ub3VuY2UgbWFpbGluZyBsaXN0
DQo+PkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KPj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPj5JbnRlcm5ldC1EcmFmdCBkaXJlY3RvcmllczogaHR0
cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPj5vciBmdHA6Ly9mdHAuaWV0Zi5vcmcvaWV0
Zi8xc2hhZG93LXNpdGVzLnR4dA0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPj5wbnRhdyBtYWlsaW5nIGxpc3QNCj4+cG50YXdAaWV0Zi5vcmcNCj4+
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wbnRhdw0KPl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cG50YXcgbWFpbGluZyBsaXN0
DQo+cG50YXdAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3BudGF3DQo=
