IETF Logo Mail Archive

Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)

<Markus.Isomaki@nokia.com> Thu, 27 October 2011 10:59 UTC

Return-Path: <Markus.Isomaki@nokia.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 D04F421F8A7B for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 03:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level:
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 pSMuIUHBgFG1 for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 03:59:29 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 0DAD821F86A5 for <rtcweb@ietf.org>; Thu, 27 Oct 2011 03:59:28 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id p9RAxLSr004416; Thu, 27 Oct 2011 13:59:24 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 27 Oct 2011 13:58:58 +0300
Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 27 Oct 2011 12:58:58 +0200
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.190]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0339.002; Thu, 27 Oct 2011 12:58:57 +0200
From: Markus.Isomaki@nokia.com
To: ibc@aliax.net, rtcweb@ietf.org
Thread-Topic: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)
Thread-Index: AQHMkqFmpMtxG3PM+kiX0/xprSe+EZWPxXIAgABBydA=
Date: Thu, 27 Oct 2011 10:58:57 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620EE0D6@008-AM1MPN1-042.mgdnok.nokia.com>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com> <CALiegfmFE0zhBg6aZMtRMO5q-k6_jeHAn9q2XivNw8yjNVqyag@mail.gmail.com>
In-Reply-To: <CALiegfmFE0zhBg6aZMtRMO5q-k6_jeHAn9q2XivNw8yjNVqyag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.21.73.20]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Oct 2011 10:58:58.0666 (UTC) FILETIME=[6D99A4A0:01CC9497]
X-Nokia-AV: Clean
Subject: Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)
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: Thu, 27 Oct 2011 10:59:30 -0000

Hi Iñaki,

Iñaki Baz Castillo wrote:
>
>>
>> http://tools.ietf.org/html/draft-sipdoc-rtcweb-open-wire-protocol-00
>> http://www.ietf.org/id/draft-sipdoc-rtcweb-open-wire-protocol-00.txt
>>
>
>Hi, just wondering if somebody has read this informational draft. I'd would
>really appreciate if folks agree with the conclusiones and requirements
>exposed in the document or want to discuss about them.

Yes, I did. And I do agree with the conclusions and the requirements. There are many different types of web apps and use cases for which real-time communications is useful. For some apps SIP/PSTN interworking is important. Others, like the poker site in your example, just want to integrate something simpler, like a vanilla audio conference, to their existing service. We need to enable all of these and hopefully also some more that we haven't even thought about in the standards groups or the current big corporations.

Markus

v2.23.0 | Report a Bug | By Email