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

Dzonatas Sol <dzonatas@gmail.com> Tue, 20 September 2011 15:08 UTC

Return-Path: <dzonatas@gmail.com>
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 B3B0E21F8CD4 for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.824
X-Spam-Level:
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 mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKIY4S+MC6qq for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 18DCE21F8CD0 for <rtcweb@ietf.org>; Tue, 20 Sep 2011 08:08:58 -0700 (PDT)
Received: by gxk19 with SMTP id 19so512588gxk.31 for <rtcweb@ietf.org>; Tue, 20 Sep 2011 08:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; 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 10.42.137.1 with SMTP id w1mr1710433ict.29.1316531482027; Tue, 20 Sep 2011 08:11:22 -0700 (PDT)
Received: from [192.168.0.50] (adsl-70-133-70-225.dsl.scrm01.sbcglobal.net. [70.133.70.225]) by mx.google.com with ESMTPS id j2sm2558765ibx.11.2011.09.20.08.11.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Sep 2011 08:11:21 -0700 (PDT)
Message-ID: <4E78AD9D.8010408@gmail.com>
Date: Tue, 20 Sep 2011 08:13:33 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110818 Icedove/3.0.11
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com><CA+9kkMAwnnKKO5+q6ey4Z0QNxax1QF21vVtw8FNsHy_rmfenjQ@mail.gmail.com><4E76E078.5020708@jesup.org><8548CBBD-4E12-48F3-BC59-341FF45EF22F@acmepacket.com><4E77495E.4000409@jesup.org><CALiegfkTdCAeEdZbXP1Y9L6i4Anjrgf1CG6ZNj35WGoHL3p_Ew@mail.gmail.com><4E774F92.4040405@jesup.org><8ECCEE59-E855-4EA9-92B9-543D1585B1F0@ag-projects.com><4E778F1F.9090105@jesup.org><CEA0AC9E-6387-4066-95DC-0D70302E80A7@ag-projects.com><4E77C3EC.9060801@jesup.org> <CAD5OKxtciYxaVpb7b3G9yMg1A97b9dkjkOpppZcSRzS5SAO3+A@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0DD8@sonusinmail02.sonusnet.com> <C55E752E-18FD-402C-A7DE-1627813B3F6D@acmepacket.com> <4E78351C.20103@jesup.org> <E4C646E9-44E5-4EBE-9AA1-D97500FAEE66@acmepacket.com> <4E7844B7.80000 05@jesup.org> <BB52C621-1D9E-41DD-B36B-28404740A1FE@acmepacket.com> <DA32EB0C-EDBF-45DE-A654-6CDF772DC4DC@edvina.net> <D56D6784-1700-4777-98F4-CAF9BEAF7751@acmepacket.com>
In-Reply-To: <D56D6784-1700-4777-98F4-CAF9BEAF7751@acmepacket.com>
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-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, 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
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>    


-- 

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