[rtcweb] #32: Section 3.2.1.1
"rtcweb issue tracker" <trac+rtcweb@trac.tools.ietf.org> Fri, 13 September 2013 00:28 UTC
Return-Path: <trac+rtcweb@trac.tools.ietf.org>
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 2EC6521F9D38 for <rtcweb@ietfa.amsl.com>; Thu, 12 Sep 2013 17:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3RmoaQPe+vwh for <rtcweb@ietfa.amsl.com>; Thu, 12 Sep 2013 17:28:20 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9983A21F9D34 for <rtcweb@ietf.org>; Thu, 12 Sep 2013 17:28:20 -0700 (PDT)
Received: from localhost ([127.0.0.1]:59418 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+rtcweb@trac.tools.ietf.org>) id 1VKHFD-0005Ms-GZ; Fri, 13 Sep 2013 02:28:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org, bernard_aboba@hotmail.com
X-Trac-Project: rtcweb
Date: Fri, 13 Sep 2013 00:28:19 -0000
X-URL: http://tools.ietf.org/rtcweb/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/rtcweb/trac/ticket/32
Message-ID: <066.5fbb20716b37306444e2b32ff3085ce3@trac.tools.ietf.org>
X-Trac-Ticket-ID: 32
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org, bernard_aboba@hotmail.com, rtcweb@ietf.org
X-SA-Exim-Mail-From: trac+rtcweb@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: christer.holmberg@ericsson.com, goran.ap.eriksson@ericsson.com, stefan.lk.hakansson@ericsson.com
Resent-Message-Id: <20130913002820.9983A21F9D34@ietfa.amsl.com>
Resent-Date: Thu, 12 Sep 2013 17:28:20 -0700
Resent-From: trac+rtcweb@trac.tools.ietf.org
Cc: rtcweb@ietf.org
Subject: [rtcweb] #32: Section 3.2.1.1
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 13 Sep 2013 00:28:21 -0000
#32: Section 3.2.1.1 "One user has an unreliable Internet connection. It sometimes loses packets, and sometimes goes down completely." [BA] I assume that this is generating requirement F8 (The browser must detect when a stream from a peer is not received anymore). Since we are using a consent mechanism to send mechanism, you might consider rephrasing F8 to "The browser must detect peer loss of connectivity." However, if we just focus at the packet loss issue, this might suggest a requirement for statistics (F38) or repair of some kind (e.g. either RTX or FEC). -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-rtcweb-use- bernard_aboba@hotmail.com | cases-and- Type: defect | requirements@tools.ietf.org Priority: minor | Status: new Component: use-cases-and- | Milestone: milestone1 requirements | Version: Severity: In WG Last Call | Keywords: -------------------------------------+------------------------------------- Ticket URL: <http://tools.ietf.org/wg/rtcweb/trac/ticket/32> rtcweb <http://tools.ietf.org/rtcweb/>
- [rtcweb] #32: Section 3.2.1.1 rtcweb issue tracker