Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling: Glare handling

Harald Alvestrand <harald@alvestrand.no> Tue, 18 October 2011 19:33 UTC

Return-Path: <harald@alvestrand.no>
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 993B121F8D82 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ivxRMuv0lZ50 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:33:25 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id D1A5821F8D1B for <rtcweb@ietf.org>; Tue, 18 Oct 2011 12:33:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3070539E151 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 21:33:24 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kope1FThEepm for <rtcweb@ietf.org>; Tue, 18 Oct 2011 21:33:22 +0200 (CEST)
Received: from [172.16.48.71] (unknown [74.125.121.33]) by eikenes.alvestrand.no (Postfix) with ESMTPS id C490C39E082 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 21:33:22 +0200 (CEST)
Message-ID: <4E9DD481.5020700@alvestrand.no>
Date: Tue, 18 Oct 2011 21:33:21 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <4E9D8D82.707@ericsson.com> <CALiegfmuxvwqJMppy4DC7162T4TrCjM3O_FnfpyNujDFuy9o+A@mail.gmail.com> <44B1D328-3875-4E82-9338-AB223E09BB8A@cisco.com>
In-Reply-To: <44B1D328-3875-4E82-9338-AB223E09BB8A@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling: Glare handling
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, 18 Oct 2011 19:33:25 -0000

On 10/18/2011 08:42 PM, Cullen Jennings wrote:
> People mean different things by realtime but when talking about it, I think it is important to keep in mind it is mostly the media that needs to be realtime and perhaps the signaling to set up such media is not as does not have the same level of constraints.
The "overview" draft has the following definition:

    Real-time media:  Media where generation of content and display of
       content are intended to occur closely together in time (on the
       order of no more than hundreds of milliseconds).

The omission of a definition for "real-time" without "media" is not an 
accident; I don't think a consensus definition exists, and I don't think 
we need that term in our work.
>
> On Oct 18, 2011, at 8:40 , Iñaki Baz Castillo wrote:
>
>> 2011/10/18 Magnus Westerlund<magnus.westerlund@ericsson.com>;:
>>> For example an JS application that uses short polling for retrieving any
>>> incomming ROAP messages, as that is timer based and done lets say every
>>> 5 seconds
>> Hi. This is RTC, so *realtime* is required for media sessions. I
>> expect that people should assume WebSocket usage rather than HTTP
>> polling.
>>
>>
>>
>> -- 
>> Iñaki Baz Castillo
>> <ibc@aliax.net>;
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>