Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requirements - HTTP Only Firewall.
Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Thu, 11 July 2013 06:43 UTC
Return-Path: <stefan.lk.hakansson@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 B0A8521F9C88 for <rtcweb@ietfa.amsl.com>; Wed, 10 Jul 2013 23:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.479
X-Spam-Level:
X-Spam-Status: No, score=-3.479 tagged_above=-999 required=5 tests=[AWL=-1.180, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 6URriWCx-DUS for <rtcweb@ietfa.amsl.com>; Wed, 10 Jul 2013 23:43:53 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 095F221F9BF1 for <rtcweb@ietf.org>; Wed, 10 Jul 2013 23:43:52 -0700 (PDT)
X-AuditID: c1b4fb38-b7f456d000002e83-6f-51de5426e834
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id D8.E8.11907.6245ED15; Thu, 11 Jul 2013 08:43:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0328.009; Thu, 11 Jul 2013 08:43:50 +0200
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Thread-Topic: draft-ietf-rtcweb-use-cases-and-requirements - HTTP Only Firewall.
Thread-Index: AQHOfXXNrAsp212+jEyOU4O3Fl3TyA==
Date: Thu, 11 Jul 2013 06:43:49 +0000
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1C3104E7@ESESSMB209.ericsson.se>
References: <20130627084022.19251.22430.idtracker@ietfa.amsl.com> <1447FA0C20ED5147A1AA0EF02890A64B1C306ECD@ESESSMB209.ericsson.se> <9F33F40F6F2CD847824537F3C4E37DDF1163B018@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvra5ayL1Agw/HdC3O9nWxW6z9187u wOSxZMlPJo8bt98zBzBFcdmkpOZklqUW6dslcGXcPbqTveCwScWCH0uZGxhvancxcnJICJhI /J9/mxHCFpO4cG89WxcjF4eQwFFGiZ5jW6GcRYwSR759ZAapYhMIlNi6bwEbiC0iYC3xYX4L WJxZwFBi8eztTCC2MFDNikUvmCFqgiTu3V7HBGHrSexf1wvWyyKgKvHj0CGwOK+Ar0Tj1+Us EMtOMUqsenEWrJkR6KTvp9YwQSwQl7j1ZD4TxKkCEkv2nGeGsEUlXj7+xwphK0k0LnnCClGv J3Fj6hQ2CFtbYtnC18wQywQlTs58wjKBUXQWkrGzkLTMQtIyC0nLAkaWVYwcxanFSbnpRgab GIERcXDLb4sdjJf/2hxilOZgURLn3aJ3JlBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY6oK Q6DjucRHetOK2pasbCv7evzK0mJ/nfRzCVc+rpPWzjl+VrRqyc+P/KItua7sx78t1hG5KZv5 s+QdR6vDl1LrHlsOLreo7t+bHddKaqbO6BKUvXvmrmPz/P7uDY9SfnY4fuvTrxCe1fHWXzcr zu74SZmWnSXzgvf/7PdN/Wm4hDP6ksRiJZbijERDLeai4kQAuqfbNFYCAAA=
Cc: "rt >> \"rtcweb@ietf.org\"" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requirements - HTTP Only Firewall.
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: Thu, 11 Jul 2013 06:43:58 -0000
Hi Andrew, thanks for catching this! F37 currently reads: "The browser must be able to send streams and data to a peer in the presence of FWs that only allows http(s) traffic." Would a change 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." be correct? Br, Stefan On 7/10/13 4:00 PM, Hutton, Andrew wrote: > Hi, > > Regarding the use case in 3.2.3 covering a HTTP only FW the text > states: > > "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". > > This needs to be changed to allow for the common case when a HTTP > Proxy is deployed so I suggest changing the last sentence to > > "The difference is that one of the users is behind a FW that only > allows traffic via a HTTP Proxy". > > There also needs to be a corresponding change to requirement F37. > > I believe we have previously discussed changing this but have to > admit I could not fine the e-mail chain so maybe it was during a > meeting. > > Regards Andy > > > > >> -----Original Message----- From: rtcweb-bounces@ietf.org >> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Stefan Håkansson LK >> Sent: 27 June 2013 09:50 To: rt >> "rtcweb@ietf.org" Subject: >> [rtcweb] Fwd: New Version Notification for draft-ietf-rtcweb- >> use-cases-and-requirements-11.txt >> >> From the change log: >> >> o Described that the API requirements are really from a W3C >> perspective and are supplied as an appendix in the introduction. >> Moved API requirements to an Appendix. >> >> o Removed the "Conventions" section with the key-words and >> reference to RFC2119. Also changed uppercase MUST's/SHOULD's to >> lowercase. >> >> o Added a note on the proposed use of the document to the >> introduction. >> >> o Removed the note talking about WS from the "FW that only allows >> http" use-case. >> >> o Removed the word "Skype" that was used as example in one of the >> use-cases. >> >> o Clarified F3 (the req saying the everything the browser sends >> must be rate controlled). >> >> o Removed the TBD saying we need to define reasonable levels from >> the requirement saying that quality must be good even in presence >> of packet losses (F5), and changed "must" to "should" (Based on a >> list discussion involving Bernard). >> >> o Removed F6 ("The browser must be able to handle high loss and >> jitter levels in a graceful way."), also after a list discussion. >> >> o Clarified F7 (used to say that the browser must support fast >> stream switches, now says that reference frames must be inserted >> when requested). o Removed the questions from F9 (echo >> cancellation), F10 (syncronization), F21 (telephony codec). >> >> o Exchanged "restrictive firewalls" for "limited middleboxes" in >> F19 (as proposed by Martin). >> >> o Expanded DTMF and IVR in F22 (proposed by Martin) >> >> o Added ref to RFC5405 in F23 (proposed by Lars Eggert). >> >> o Exchanged "service provided" for "web application" in F32. >> >> o Changed the text in 3.2.1 that motivates F36 (new text "It is >> essential that media and data be encrypted, authenticated ... bound >> to the user identity."); and rewrote F36, included a ref to >> RFC5479. >> >> o Changed "quality of service" to "quality of experience" in F38. >> >> o Added F39. >> >> o Used new formulation of A17 (proposed by Martin). >> >> o Updated A20. >> >> o Updated A25. >> >> Things that have not been done: >> >> - No use-case on emergency services added (as said already in >> http://www.ietf.org/mail-archive/web/rtcweb/current/msg07253.html) >> >> - No use-case on real-time text added (as said already in >> http://www.ietf.org/mail-archive/web/rtcweb/current/msg07254.html) >> >> - No clarification on what solution(s) related to multiple >> resolutions of the same content added (discussed in >> http://www.ietf.org/mail-archive/web/rtcweb/current/msg07256.html >> but no input received). >> >> - The order of the requirements (Fn) is still a mess - but I kept >> it as is for this version to make diffing simpler. To be fixed in >> an upcoming version. >> >> Stefan >> >> >> -------- Original Message -------- Subject: New Version >> Notification for >> draft-ietf-rtcweb-use-cases-and-requirements-11.txt Date: 10:40 >> From: internet-drafts@ietf.org <internet-drafts@ietf.org> To: >> Christer Holmberg <christer.holmberg@ericsson.com>, Göran >> Eriksson AP <goran.ap.eriksson@ericsson.com>, Stefan Håkansson >> LK <stefan.lk.hakansson@ericsson.com>, Göran Eriksson AP >> <goran.ap.eriksson@ericsson.com> >> >> >> A new version of I-D, >> draft-ietf-rtcweb-use-cases-and-requirements- 11.txt has been >> successfully submitted by Christer Holmberg and posted to the IETF >> repository. >> >> Filename: draft-ietf-rtcweb-use-cases-and-requirements Revision: >> 11 Title: Web Real-Time Communication Use-cases and Requirements >> Creation date: 2013-06-27 Group: rtcweb Number of pages: 30 >> URL: >> http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-use-cases-and- >> >> requirements-11.txt >> Status: >> http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and- >> requirements Htmlized: >> http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and- >> requirements-11 Diff: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-use-cases-and- >> requirements-11 >> >> Abstract: This document describes web based real-time communication >> use- cases. Requirements on the browser functionality are derived >> from use- cases. >> >> >> >> >> >> The IETF Secretariat >> >> >> >> >> _______________________________________________ rtcweb mailing >> list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb >
- [rtcweb] Fwd: New Version Notification for draft-… Stefan Håkansson LK
- Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requ… Hutton, Andrew
- [rtcweb] draft-ietf-rtcweb-use-cases-and-requirem… Hutton, Andrew
- Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requ… Stefan Håkansson LK