Re: [rtcweb] Review request for RTCWeb standard signaling protocol

"Asveren, Tolga" <tasveren@sonusnet.com> Tue, 18 October 2011 19:45 UTC

Return-Path: <tasveren@sonusnet.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 953E321F8DBA for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 fV+tJPJIzWrB for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:45:29 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id A970B21F8D24 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 12:45:29 -0700 (PDT)
Received: from sonusmail04.sonusnet.com (sonusmail04.sonusnet.com [10.128.32.98]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p9IJk1Bx020564; Tue, 18 Oct 2011 15:46:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Oct 2011 15:45:24 -0400
Message-ID: <033458F56EC2A64E8D2D7B759FA3E7E703DBF6C6@sonusmail04.sonusnet.com>
In-Reply-To: <3BFE6ACE-7429-468A-9248-BAC8118030B4@genband.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Review request for RTCWeb standard signaling protocol
Thread-Index: AQHMjWPJ5Sh3naz7SPaFx9XGCjJhjZWCFU0AgAAGWYCAAE3QgIAACNmAgABHvACAAAOwAIAAAFQAgAACdQD//73TboAAA3Gg
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com><4E8AC222.4050308@alvestrand.no><2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com><CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com><393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com><CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com><CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com><CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com><2E239D6FCD033C4BAF15F386A979BF511598EE@sonusinmail02.sonusnet.com><665A16AB-AAD8-42B3-AC17-7E629EA2DE35@phonefromhere.com><2E239D6FCD033C4BAF15F386A979BF5115992E@sonusinmail02.sonusnet.com><CALiegfmrncjsLVSiWk0tEgzwB00YaBGiqj0SDf9JTm9p1ZNoVA@mail.gmail.com><0950F0E1-6E4B-407F-9563- 654AFE79 F64B@ag-pro jects.com><2E239D6FCD033C4BAF15F386A979BF51159994@sonusinmail02.sonusnet.com><1F2A2C70609D9E41844A2126145FC09804004302@HKGMBOXPRD22.polycom.com><033458F56EC2A64E8D2D7B759FA3E7E703DBF614@sonusmail04.sonusnet.com><8486C8728176924BAF5BDB2F7D7EEDDF3E091D13@ucolhp4d.easf.csd.disa.mil><2E239D6FCD033C4BAF15F386A979BF511599F3@sonusinmail02.sonusnet.com><033458F56EC2A64E8D2D7B759FA3E7E703DBF698@sonusmail04.sonusnet.com><CALiegfkm-=EOiAsFQOwm4cjuW94=Mp8_ndN6L4wdM4BPBwDVww@mail.gmail.com>, <033458F56EC2A64E8D2D7B759FA3E7E703DBF6A5@sonusmail04.sonusnet.com> <3BFE6ACE-7429-468A-9248-BAC8118030B4@genband.com>
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: "Jim McEachern" <jim.mceachern@genband.com>
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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:45:30 -0000

Mea culpa, yes it is more about the nature of relationship between RTCWeb in browser and JS/webserver.

Thanks,
Tolga

> -----Original Message-----
> From: Jim McEachern [mailto:jim.mceachern@genband.com]
> Sent: Tuesday, October 18, 2011 3:32 PM
> To: Asveren, Tolga
> Cc: Iñaki Baz Castillo; rtcweb@ietf.org
> Subject: Re: [rtcweb] Review request for RTCWeb standard signaling
> protocol
> 
> Tolga,
> I'm confused by your statement that "supporting both models would require
> a careful design of RTCWeb stack/JS interface...". Surely the same
> information would have to be supported by the API whether the intelligence
> was in the JS or in the web server. Other than a strong requirement for it
> being asynchronous (which has already been proposed for other reasons) I
> would have thought the API could be the same whether the intelligence is
> in the JS or the web server.
> 
> For the record, I am not arguing either way on where the intelligence
> should be. I'm simply trying to understand the requirements.
> 
> Jim
> 
> 
> On Oct 18, 2011, at 2:28 PM, "Asveren, Tolga" <tasveren@sonusnet.com>;
> wrote:
> 
> > Yes, not required, but possible -if we can achieve that level of
> flexibility-.
> >
> > Overall, there are two models here:
> > i- Webbrowser/JS as signaling/media entity
> > ii- Webbrowser/JS as a media entity controlled by webserver
> >
> > It seems focus is on i- but I heard a few people mentioning about ii-
> and no direct rejection yet. Supporting both models would require a
> careful design of RTCWeb stack/JS interface so that it is flexible enough
> but also can be used easily for simple variations of each model.
> >
> > Thanks,
> > Tolga
> >
> >> -----Original Message-----
> >> From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
> >> Sent: Tuesday, October 18, 2011 2:20 PM
> >> To: Asveren, Tolga
> >> Cc: Ravindran Parthasarathi; Roy, Radhika R USA CIV (US); Avasarala,
> >> Ranjit; Saúl Ibarra Corretgé; rtcweb@ietf.org
> >> Subject: Re: [rtcweb] Review request for RTCWeb standard signaling
> >> protocol
> >>
> >> 2011/10/18 Asveren, Tolga <tasveren@sonusnet.com>;:
> >>> I would think that supporting what Tim Panton describes in another
> >> thread (codec selection done in webserver) could be nice to achieve -
> among
> >> other models- if possible.
> >>
> >> I hope the intelligence is NOT required to be in the web server.
> >>
> >> --
> >> Iñaki Baz Castillo
> >> <ibc@aliax.net>;
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb