Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]

Dzonatas Sol <> Tue, 20 September 2011 15:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B3B0E21F8CD4 for <>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.824
X-Spam-Status: No, score=-3.824 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cKIY4S+MC6qq for <>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 18DCE21F8CD0 for <>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
Received: by gxk19 with SMTP id 19so512588gxk.31 for <>; Tue, 20 Sep 2011 08:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bOejBLGIF6aDtSTMDSDrnWPhAn33a5eltzbjWxFspP8=; b=grB5eCE6CuYaNKOx0+TXdzKo0OQuEmir2uAV+q5WWluPwEhBd/NV7HJIqxWnm9fwPZ IUfsbhphKsluEJqAZVroAlRlrHWJz06I+0ky2Uw2RAu1Fj9y+9AYkF7o6Bnw3euJsqUj W6M1omQKKw92LXXrlRliOApGlnVju3xrUAo0c=
Received: by with SMTP id w1mr1710433ict.29.1316531482027; Tue, 20 Sep 2011 08:11:22 -0700 (PDT)
Received: from [] ( []) by with ESMTPS id j2sm2558765ibx.11.2011. (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Sep 2011 08:11:21 -0700 (PDT)
Message-ID: <>
Date: Tue, 20 Sep 2011 08:13:33 -0700
From: Dzonatas Sol <>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110818 Icedove/3.0.11
MIME-Version: 1.0
References: <><><><><><><><><><><> <> <> <> <> <> <4E7844B7.80000> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Sep 2011 15:08:58 -0000

On 09/20/2011 01:56 AM, Hadriel Kaplan wrote:
> On Sep 20, 2011, at 4:48 AM, Olle E. Johansson wrote:
>>> If it could, we'd probably have the siprec/remote-recording requirement accommodated.  :)
>> Well, take a look at the source code for FreeSwitch or Asterisk and you'll see that "setting up a bridge" is not a piece of cake...
>> You are making the assumption that you have no formatting issues and don't need to change framerate for video, orientation or anything else or audio transcoding.
> Nope, I'm not making any such assumption.  I was just pointing out that if the browser did full mixing, then we'd have the remote recording use-case thing done too.

The browser that does "full mixing" is then consider the simulator, so I 
would like to make sure that mix is done in real-time (capable of 
dispersement by solid surfaces rendered, like ray-cast for audio).

I think the question is if there needs to be an API for the mixer (in 
constraint to rtcweb), as I can see that may be harder to interact with 
simulators. Or, do we think of browsers that may have hal mixers (1st 
person spatial only) that don't provide any simulation.

>>>> SIP has been very focused on device<->server interaction, not device<->device.  However:
>>>> note that we have an app that knows why it has these calls in place; we're not defining an
>>>> abstract, portable protocol use here.
>>> Aha!  So it's not "SIP" that you meant... you meant "something that looks like SIP but isn't SIP per the RFCs".  ;)
>> According to RFC 3261 SIP is a peer 2 peer protocol and not a device->server protocol. Just making a point.
> I'm not sure if you meant that in response to my remark or Randell's?  What I meant by saying "it's not really SIP" wasn't because I think SIP is not device<->device (on the contrary, it is)... but rather that if rtcweb uses SIP but then doesn't actually follow the rules of SIP, then it's *not* SIP.
> -hadriel
> _______________________________________________
> rtcweb mailing list


<i>The wheel.</i metro-link=t dzonatasolyndra>