IETF Logo Mail Archive

Re: [rtcweb] Use Case draft

Randell Jesup <randell-ietf@jesup.org> Tue, 01 May 2012 15:57 UTC

Return-Path: <randell-ietf@jesup.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 C8ACA21E813B for <rtcweb@ietfa.amsl.com>; Tue, 1 May 2012 08:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[AWL=0.297, 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 IggxXLy5HJCs for <rtcweb@ietfa.amsl.com>; Tue, 1 May 2012 08:57:10 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 5382021E8134 for <rtcweb@ietf.org>; Tue, 1 May 2012 08:57:10 -0700 (PDT)
Received: from pool-108-16-41-249.phlapa.fios.verizon.net ([108.16.41.249] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1SPFRt-0004ko-Fr for rtcweb@ietf.org; Tue, 01 May 2012 10:57:09 -0500
Message-ID: <4FA0079B.3080609@jesup.org>
Date: Tue, 01 May 2012 11:56:11 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMCYArLPRP3c00UdOja64WRT6ghN0PSy7XvM_wbxBBB+vA@mail.gmail.com> <4F9ACCC9.2040508@mozilla.com> <4F9E7A7E.1020600@ericsson.com> <4F9EFD60.6000809@jesup.org> <4F9F6F4C.5060902@ericsson.com>
In-Reply-To: <4F9F6F4C.5060902@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Use Case draft
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: Tue, 01 May 2012 15:57:10 -0000

On 5/1/2012 1:06 AM, Stefan Hakansson LK wrote:
> On 04/30/2012 11:00 PM, Randell Jesup wrote:
>> The game case can need both reliable and unreliable data at the same
>> time, which gets us reliable, unreliable and multiple streams.
>
> You're right; but currently only game state updates is mentioned.
> Probably that use case should be updated.

Game state updates for a real online game can involve both reliable and 
unreliable data.  Some state can be out-of-date (player positions, 
visual state issues (lighting), etc) and the game will extrapolate 
positions; others (global critical state (live, dead, etc)) must be 
reliable.

-- 
Randell Jesup
randell-ietf@jesup.org

v2.20.0 | Report a Bug | By Email