IETF Logo Mail Archive

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

"Parthasarathi R" <partha@parthasarathi.co.in> Mon, 14 October 2013 19:15 UTC

Return-Path: <partha@parthasarathi.co.in>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 324F921F9FA4 for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 12:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.476
X-Spam-Level:
X-Spam-Status: No, score=-1.476 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6y9mtH8yl4ZF for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 12:15:12 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.235]) by ietfa.amsl.com (Postfix) with ESMTP id B7DA811E8189 for <rtcweb@ietf.org>; Mon, 14 Oct 2013 12:15:07 -0700 (PDT)
Received: from userPC (unknown [122.172.182.21]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 0AC94638178; Mon, 14 Oct 2013 19:15:04 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381778107; bh=q9qxT/gCPk49WSM0xXOPmF2dA9wvDoUc8mWZF3QFQSQ=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=mPUlFLJtjAJg0WwvW/OXF/ilaEQOMrNWAelxzmcFDozzEZuQQighH+KX1vAFy+lxz CHhw5wIqpvJMFgy7CmnsByzBmEY0iyCh87cra/cogyZG1iHc5q7+APcCy11sHU/n1v sonvuBRoJzghCzc7G2rA0hIU//eozxJG70qZH4GA=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, rtcweb@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C4BDDF9@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4BDDF9@ESESSMB209.ericsson.se>
Date: Tue, 15 Oct 2013 00:45:01 +0530
Message-ID: <00d601cec911$b0fd4b60$12f7e220$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7IvINFDjps6xe1Q0+JPDy99cM+7AAUxh6w
Content-Language: en-us
X-CTCH-RefID: str=0001.0A0C0209.525C42BB.005C, 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: 1
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.142
Subject: [rtcweb] Query/Comment on draft-ietf-rtcweb-use-cases-and-requirements-12
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2013 19:15:18 -0000

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
http://www.ietf.org/mail-archive/web/pntaw/current/msg00166.html.

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.

Thanks
Partha

Note:

----------------------------------------------------------------
   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.

v2.23.0 | Report a Bug | By Email