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

"Roy, Radhika R USA CIV (US)" <radhika.r.roy.civ@mail.mil> Tue, 18 October 2011 13:48 UTC

Return-Path: <radhika.r.roy.civ@mail.mil>
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 DD85621F8B74 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 06:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level:
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 pMd6bPFd9DkI for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 06:48:54 -0700 (PDT)
Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.9]) by ietfa.amsl.com (Postfix) with ESMTP id 47F7921F8B5D for <rtcweb@ietf.org>; Tue, 18 Oct 2011 06:48:54 -0700 (PDT)
Received: from UCOLHP3I.easf.csd.disa.mil (131.64.100.150) by ucolhp2w.easf.csd.disa.mil (131.64.100.9) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Oct 2011 08:48:38 -0500
Received: from UCOLHP4D.easf.csd.disa.mil ([169.254.9.97]) by UCOLHP3I.easf.csd.disa.mil ([169.254.63.236]) with mapi id 14.01.0323.003; Tue, 18 Oct 2011 08:48:38 -0500
From: "Roy, Radhika R USA CIV (US)" <radhika.r.roy.civ@mail.mil>
To: "Asveren, Tolga" <tasveren@sonusnet.com>, "Avasarala, Ranjit" <Ranjit.Avasarala@Polycom.com>, Ravindran Parthasarathi <pravindran@sonusnet.com>, =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
Thread-Topic: [rtcweb] Review request for RTCWeb standard signaling protocol
Thread-Index: AQHMjWPJQsg22CmbRQ+ec/AyTlzr85WCFU0AgAAGWYCAAE3QgP//tE4Q
Date: Tue, 18 Oct 2011 13:48:37 +0000
Message-ID: <8486C8728176924BAF5BDB2F7D7EEDDF3E091D13@ucolhp4d.easf.csd.disa.mil>
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><2E239D6FCD033C4BAF15F3 8 6A979B F 51159950@so nusinmail02.sonusnet.com><0950F0E1-6E4B-407F-9563-654AFE79F64B@ag-projects.com><2E239D6FCD033C4BAF15F386A979BF51159994@sonusinmail02.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804004302@HKGMBOXPRD22.polycom.com> <033458F56EC2A64E8D2D7B759FA3E7E703DBF614@sonusmail04.sonusnet.com>
In-Reply-To: <033458F56EC2A64E8D2D7B759FA3E7E703DBF614@sonusmail04.sonusnet.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [131.64.77.9]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <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 13:48:55 -0000

Folks:

Tolga is right.

We have a very complex problem to solve. It is called negotiations between different types of codecs and between different features of each codec type.

Let us see how simple a protocol can be based on these simple requirements.

BR/Radhika

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Asveren, Tolga
Sent: Tuesday, October 18, 2011 9:17 AM
To: Avasarala, Ranjit; Ravindran Parthasarathi; Saúl Ibarra Corretgé
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol

Yes, something "simple" would be nice but the definition of "simple enough but still allowing me to do what I want to achieve" is very much dependent on the needs of each specific use case/service. There is no universal definition of "simple" here. So, I guess this is yet another argument in favor of not standardizing the protocol between browser and webserver so that everybody can design/use whatever is "simple but good enough" from their perspective.

Thanks,
Tolga