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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 18 October 2011 15:40 UTC

Return-Path: <ibc@aliax.net>
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 61A6A21F8AAF for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 08:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level:
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 pP-HGK+x04k5 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 08:40:49 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id D16E421F8A97 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 08:40:48 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so760507vcb.31 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 08:40:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.117.81 with SMTP id p17mr222627vcq.41.1318952447397; Tue, 18 Oct 2011 08:40:47 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Tue, 18 Oct 2011 08:40:47 -0700 (PDT)
In-Reply-To: <4E9D8D82.707@ericsson.com>
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <4E9D8D82.707@ericsson.com>
Date: Tue, 18 Oct 2011 17:40:47 +0200
Message-ID: <CALiegfmuxvwqJMppy4DC7162T4TrCjM3O_FnfpyNujDFuy9o+A@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>, rtcweb@ietf.org
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 15:40:49 -0000

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>;