Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requirements-12

Christer Holmberg <> Wed, 16 October 2013 09:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8B92411E8167 for <>; Wed, 16 Oct 2013 02:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.711
X-Spam-Status: No, score=-5.711 tagged_above=-999 required=5 tests=[AWL=0.538, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2BAFqKXyw1OJ for <>; Wed, 16 Oct 2013 02:32:21 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 44CC011E817C for <>; Wed, 16 Oct 2013 02:32:18 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-67-525e5d21180d
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id BA.D4.03802.12D5E525; Wed, 16 Oct 2013 11:32:17 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Wed, 16 Oct 2013 11:32:17 +0200
From: Christer Holmberg <>
To: "Chenxin (Xin)" <>, Parthasarathi R <>, "" <>
Thread-Topic: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requirements-12
Thread-Index: AQHOyjWVN5kp1LzBPE2VjgDW3Xis9Jn293kg///2p4CAACJ9UA==
Date: Wed, 16 Oct 2013 09:32:16 +0000
Message-ID: <>
References: <> <00d601cec911$b0fd4b60$12f7e220$> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvra5ibFyQwcwFshY3r/QyWkz+1Mdq sfZfO7sDs0fLkbesHkuW/GTy+DD/C3sAcxSXTUpqTmZZapG+XQJXxrojy5gLbktVdC7bxNTA +EC0i5GTQ0LARKJx9kJWCFtM4sK99WxdjFwcQgKHGSVu7HgB5SxhlDgx9wlQFQcHm4CFRPc/ bZC4iEAbo8Txe+8ZQbqFBSIkzsy7CzZJRCBS4mb3NRaQehEBJ4k3+1VBwiwCqhJ//+5iAwnz CvhKTL+ZDzH+MpNE28lp7CA1nAJhEj/ad4LZjEAHfT+1hgnEZhYQl7j1ZD4TxKECEkv2nGeG sEUlXj7+B3aahICixPJ+OYhyHYkFuz+xQdjaEssWvgYr5xUQlDg58wnLBEbRWUimzkLSMgtJ yywkLQsYWVYxsucmZuaklxttYgRGx8Etv1V3MN45J3KIUZqDRUmc98Nb5yAhgfTEktTs1NSC 1KL4otKc1OJDjEwcnFINjGEz//9iF4v8Fr3+eqP8XLbNk//ExjCFZ1qFczi0rrRXFfkzu9LT tmFpoe+vi4xqfossX+ttOezudlNwzZx3l3QTv7Xub1FhO8Gr+YojMmV1ya4N0yKVdypxHT1t UPetcCvX9uoijoLg7dw3L3yR2xpUu1U9+JmpXs4S3hkd68/oSt1Yy62xQomlOCPRUIu5qDgR ACay3rhcAgAA
Subject: Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requirements-12
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 16 Oct 2013 09:32:27 -0000

Hi Xin,

So, you are saying we shouldn't finalize the use-case-requirements document yet?



-----Original Message-----
From: Chenxin (Xin) [] 
Sent: 16. lokakuuta 2013 12:28
To: Christer Holmberg; Parthasarathi R;
Subject: RE: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requirements-12

Hi Christer,

>>  +1. I think we should wait for the result of 
>> discussion
>before modifying the related use case and requirement. there seems no 
>clear consensus by now.
>>  The related use case is 3.3.2 , F29 , 3.3.3 and F37.
>Consensus on what?

Should we just consider the case that " one of the users is behind a FW that only allows traffic via a HTTP Proxy "? what will happen if there is no http proxy deployed? 

There are two options to solve this usecase discussed in PNTAW mailing list. "5)UDP relay candidates via some HTTP/TLS compatible transport (TURN) - MUST/SHOULD (TLS via HTTP CONNET or TURN over WebSockets have been proposed."  List in
Also there is other discussions in 

That all mention that we should consider more than the http proxy scenarios. 

I believe that the PNTAW mailing list is used for discussion of these similar transport problems, including the related use case and requirement. In the end , some consensus should be make to decide what problem we need handle and how to solve it , which will influence the use case and requirement to make it more clear.  Is my thought right? Or miss something...

Best Regards,
>Note that the draft is only talking about requirements.
>>-----Original Message-----
>>From: [] On 
>>Behalf Of Parthasarathi R
>>Sent: Tuesday, October 15, 2013 3:15 AM
>>To: 'Christer Holmberg';
>>Subject: [rtcweb] Query/Comment on
>>Hi Christer & all,
>>In PNTAW mailing list, there is a discussion on firewall blocking 
>>incoming TCP traffic when the firewall blocks UDP or allows only HTTP 
>>traffic. The related link is 
>>Could you please clarify whether F29 & F37 requirement implicitly 
>>indicates that incoming TCP/HTTP traffic is blocked for browser when 
>>these requirements are met. If so, Please update the below requirement 
>>text with those details.
>>   F29     The browser must be able to send streams and
>>           data to a peer in the presence of NATs that
>>           block UDP traffic.
>>  F37     The browser must be able to send streams and
>>           data to a peer in the presence of FWs that only
>>           allows traffic via a HTTP Proxy, when FW policy
>>           allows WebRTC traffic.
>>rtcweb mailing list