Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 23 September 2013 09:13 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 4B87E11E8175 for <rtcweb@ietfa.amsl.com>; Mon, 23 Sep 2013 02:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level:
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 ZmvPpDc4XKtQ for <rtcweb@ietfa.amsl.com>; Mon, 23 Sep 2013 02:13:42 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC0D11E8174 for <rtcweb@ietf.org>; Mon, 23 Sep 2013 02:13:41 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hm2so1953860wib.10 for <rtcweb@ietf.org>; Mon, 23 Sep 2013 02:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ROLq+B6cxT//D99LIEPTcDowvIrG2g2/brIQPq6yaGg=; b=ftJYz9Uro+/KZk3Z3LDcFqfgCMETmIic23f+MuZ6EvM7Iec1no3TkBvh5kMS8aBllc OtuamDlZuKSWCsTdw+A5oXci1GBLuVrPZ4/wWej/nMkUEMsrfT9d/KhPIkDOSurCm9AV +4PqdrUyCiinicgU/gzHkoXuOF6H34oOPsQsAGRJ8Pg8HDyhpmuyZABKCPlUYVkuimPi p/XDfvNenNsLKH3Z9+mWmdXDGFM2ROiPgwxNZYhe5W/CdQXpGc6lXVDztQgEADuShnp+ 9st7sZN7grh07NWoqJiwfvaxLuJvhNDcmcAhguPmmbucTbCsYkxA9LlG9azFmyX4eYnl 6t7g==
X-Received: by 10.194.60.73 with SMTP id f9mr29348wjr.65.1379927621247; Mon, 23 Sep 2013 02:13:41 -0700 (PDT)
Received: from [192.168.1.45] (54.Red-83-61-124.dynamicIP.rima-tde.net. [83.61.124.54]) by mx.google.com with ESMTPSA id i8sm24165047wib.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Sep 2013 02:13:40 -0700 (PDT)
Message-ID: <52400640.4010606@gmail.com>
Date: Mon, 23 Sep 2013 11:13:36 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <C5E08FE080ACFD4DAE31E4BDBF944EB11667BBA0@xmb-aln-x02.cisco.com> <5238446D.8050700@ericsson.com>
In-Reply-To: <5238446D.8050700@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
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, 23 Sep 2013 09:13:43 -0000

+1

Shouldn't we add it as a requirement also?

Best regards
Sergio
El 17/09/2013 14:00, Magnus Westerlund escribió:
> 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.