Re: [rtcweb] A compromise for SDES

Hrishikesh Kulkarni <rishi@turtleyogi.com> Sun, 14 July 2013 17:03 UTC

Return-Path: <rishi@turtleyogi.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 38C7821F9B0D for <rtcweb@ietfa.amsl.com>; Sun, 14 Jul 2013 10:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.357
X-Spam-Level:
X-Spam-Status: No, score=-2.357 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 QcueHW2IpBo7 for <rtcweb@ietfa.amsl.com>; Sun, 14 Jul 2013 10:03:30 -0700 (PDT)
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by ietfa.amsl.com (Postfix) with ESMTP id BBE1121F9ADE for <rtcweb@ietf.org>; Sun, 14 Jul 2013 10:03:30 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id ar20so23854720iec.21 for <rtcweb@ietf.org>; Sun, 14 Jul 2013 10:03:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=wGPYPD7mudvDTip9e43jaqVYePdmg7BHLEX+cF9Dy5g=; b=BgfOZeIWWqUcgGQgUtkWK76b64sl3I6jO/7zI7mHtDnujgnLtfxuum7RpCdMTzFHQD 1O9NzeNpQxncqpVxeO5RMEKjGuqmHgdS19bxIDtK7oJRoVVw9ye8gmrDLTgpfCGd69Eg jXozKbDOTd847ux79gNaJwwddpH+7CBO+UBIuOeSk2yyA4PkXtXmfuugtNtOro2ddkVQ 7RCzaUeUbLkDOSk56sacuZaVhns9BEqHDwzXbNSK2vU6fddy1bkM+TOjQSh50r2XgAhY yuV23qlrAP6EELhQ+Tcw7vXbxUt5p9wYbo71kd0H4TYVTIj4K5eUCK/cyyjeaGyGW6au uTRA==
MIME-Version: 1.0
X-Received: by 10.42.79.142 with SMTP id r14mr16829041ick.51.1373821409869; Sun, 14 Jul 2013 10:03:29 -0700 (PDT)
Received: by 10.64.231.36 with HTTP; Sun, 14 Jul 2013 10:03:29 -0700 (PDT)
X-Originating-IP: [122.167.74.243]
In-Reply-To: <BLU169-W1221AE43EFBADA8B862E43993650@phx.gbl>
References: <CA+9kkMBuCTdFsUMtmuBz6BnrSJMpHywEZU+x+m8ARnGprvzDzA@mail.gmail.com> <CABkgnnXOa44ZkZj-g6r7Qdk8dwm6m81yT4U=Q23-hE1Q7Hn22w@mail.gmail.com> <F9556428-B6B8-407D-9D62-9A1CC04D4253@oracle.com> <B2DF729D-B313-4D3E-9C06-DA00AF7A14FF@oracle.com> <BLU169-W1221AE43EFBADA8B862E43993650@phx.gbl>
Date: Sun, 14 Jul 2013 22:33:29 +0530
Message-ID: <CALFWOz4dY8gQANnq1o5rxuJibbrn0=DKy77ju8xayyUO6gpNZA@mail.gmail.com>
From: Hrishikesh Kulkarni <rishi@turtleyogi.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary=20cf3010ea091ee74604e17bb964
X-Gm-Message-State: ALoCoQlUsfDoE5emUKBCE3xlOdY9QvkXpLwDCmQX3EV39laB1S4qtTLCfLE4bMLfOKQen6qTfgcN
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] A compromise for SDES
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: Sun, 14 Jul 2013 17:03:35 -0000

Very interesting discussion and important thread. I have a comment on JS
API's.

On Sun, Jul 14, 2013 at 2:32 AM, Bernard Aboba <bernard_aboba@hotmail.com>wrote;wrote:

> Hadriel --
>
> .....
>
> As you state, the vast majority of customers I talk to are interested
> primarily in the "RAI 2.0" aspects of WebRTC, and only secondarily, if at
> all, in the W3C JS APIs.  Given the displacement of feature phones by
> smartphones, the growth in availability of wireless data as well as the
> increasing availability of connectivity that can support interactive video
> (all areas of very rapid growth over the next few years), the focus of
> realtime communications app developers I talk to is not on browser, but on
> the development of native applications.  And unless HTML5-based approaches
> such as Firefox OS gain traction, that focus is likely to remain.
>
>
WebRTC JS API's has the potential to make video/audio based web apps the
first class citizens of internet. Focus on interop at the media plane and
signaling plane is important. But it is critical to focus and bring better
JS API's to browser and browser frameworks. I am startup and many customers
I talk to are asking for video web apps on Internet explorer which
unfortunately is lacking as compared to Chrome and Firefox (both of which
are available on mobile too).

regards,
Rishi
OneKlikStreet.com




>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>