Re: [rtcweb] Draft new version: draft-ietf-rtcweb-use-cases-and-requirements-12 - WGLC comments implemented
Christer Holmberg <christer.holmberg@ericsson.com> Mon, 14 October 2013 12:58 UTC
Return-Path: <christer.holmberg@ericsson.com>
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 C4D3C11E817E for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 05:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.968
X-Spam-Level:
X-Spam-Status: No, score=-3.968 tagged_above=-999 required=5 tests=[AWL=-1.369, BAYES_00=-2.599]
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 DZXOZ-0qdPbN for <rtcweb@ietfa.amsl.com>; Mon, 14 Oct 2013 05:58:47 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id E5CDD21E8093 for <rtcweb@ietf.org>; Mon, 14 Oct 2013 05:58:43 -0700 (PDT)
X-AuditID: c1b4fb38-b7fcf8e0000062b8-b4-525bea8203b0
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 66.C8.25272.28AEB525; Mon, 14 Oct 2013 14:58:42 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0328.009; Mon, 14 Oct 2013 14:58:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Rauschenbach, Uwe (NSN - DE/Munich)" <uwe.rauschenbach@nsn.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Draft new version: draft-ietf-rtcweb-use-cases-and-requirements-12 - WGLC comments implemented
Thread-Index: Ac7IvINFDjps6xe1Q0+JPDy99cM+7AAHt7EAAABqxIA=
Date: Mon, 14 Oct 2013 12:58:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4BE09C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C4BDDF9@ESESSMB209.ericsson.se> <56C2F665D49E0341B9DF5938005ACDF811F599@DEMUMBX005.nsn-intra.net>
In-Reply-To: <56C2F665D49E0341B9DF5938005ACDF811F599@DEMUMBX005.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+JvrW7Tq+ggg59b1C3W/mtnt7h7eA6z A5PHkiU/mTx+rr/KHsAUxWWTkpqTWZZapG+XwJWxqekQa8EE0YrJ31vZGhjX83cxcnJICJhI fH39mxHCFpO4cG89WxcjF4eQwFFGiY0HJjFBOEsYJZqedjF3MXJwsAlYSHT/0wZpEBHIluh/ upAJxBYWKJNY2TyVCaRERKBc4vVbQ4gSK4lJk9tZQGwWAVWJbffuM4PYvAK+Eo9eXmGEGD+R UWJz+zt2kASngJ/E9P99YEWMQAd9P7UGbD6zgLjErSfzmSAOFZBYsuc8M4QtKvHy8T9WkL0S AooSy/vlIMr1JG5MncIGYWtLLFv4GmqvoMTJmU9YJjCKzkIydRaSlllIWmYhaVnAyLKKkaM4 tTgpN93IYBMjMBYObvltsYPx8l+bQ4zSHCxK4rwf3zoHCQmkJ5akZqemFqQWxReV5qQWH2Jk 4uCUamB0+7HiRWj0acb1cyd/btVWsCwS1m2LbdQXFPp87HC017zDjsKiLrv/dvf3v3d/LCO0 Q7x3nsEVtUMH2XJreu5d5VzS/W9m3YROwQ1KfEXfbr5fHmXfvX7Ca5az5ZvP++25rSYof3T5 1sP1HbJVqy5o7G5v+nfmVdP1O4ZxllpRSttrN5cEfWdVYinOSDTUYi4qTgQAcVzxf1MCAAA=
Subject: Re: [rtcweb] Draft new version: draft-ietf-rtcweb-use-cases-and-requirements-12 - WGLC comments implemented
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 12:58:53 -0000
Hi Uwe, I guess you are right. I'll fix that in the next version. Thanks! Regards, Christer -----Original Message----- From: Rauschenbach, Uwe (NSN - DE/Munich) [mailto:uwe.rauschenbach@nsn.com] Sent: 14. lokakuuta 2013 15:53 To: Christer Holmberg; rtcweb@ietf.org Subject: RE: [rtcweb] Draft new version: draft-ietf-rtcweb-use-cases-and-requirements-12 - WGLC comments implemented Hi Christer, A nit: shouldn't the two requirements below mention "receive" as well? Kind regards, Uwe > ---------------------------------------------------------------- > > > > 10. Section 3.2.3.1: > > > > > > 3.2.3.1. Description > > > > This use-case is almost identical to the Simple Video Communication > > Service use-case (Section 3.2.1). The difference is that one of the > > users is behind a FW that only allows http traffic. > > > > If a firewall only allows HTTP traffic, then can we really assume > > that > the firewall administrator per default will accept WebRTC Media and > Data traffic? > > > > I am far from certain of this, and think on a requirement level > > needs > to express a situation where the firewall administrator allows WebRTC > across its FW, or at least can easily configure a rule to block it. > Thus resulting in that any solution for this needs to be easily > identifiable and possible to block. > > > > See also PNTAW@ietf.org mailing list. > > V-12: The sentence starting with "The difference..." is replaced by > "The difference is that one of the users is behind a FW that only > allows traffic via a HTTP Proxy.", as suggested by Andrew H. > > Requirement F37 is modified to: > > "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." [skipping ...] > ---------------------------------------------------------------- > > > > 22. Section 4.2: > > F37 The browser must be able to send streams and > > data to a peer in the presence of FWs that only > > allows http(s) traffic. > > > > I think this requirement should have a caveat along the lines: when > > FW > policy allows WebRTC traffic. > > V-12: Caveat added. > > "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] Draft new version: draft-ietf-rtcweb-use… Christer Holmberg
- Re: [rtcweb] Draft new version: draft-ietf-rtcweb… Rauschenbach, Uwe (NSN - DE/Munich)
- Re: [rtcweb] Draft new version: draft-ietf-rtcweb… Christer Holmberg
- [rtcweb] Query/Comment on draft-ietf-rtcweb-use-c… Parthasarathi R
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Chenxin (Xin)
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Christer Holmberg
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Chenxin (Xin)
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Christer Holmberg
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Hutton, Andrew
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Chenxin (Xin)
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Chenxin (Xin)
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Parthasarathi R
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Magnus Westerlund
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Magnus Westerlund
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Hutton, Andrew
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Parthasarathi R
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Magnus Westerlund
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Hutton, Andrew
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Parthasarathi R
- Re: [rtcweb] Query/Comment on draft-ietf-rtcweb-u… Magnus Westerlund