Re: [rtcweb] Summary of Signaling Components in RTCweb (clarifications)

Wolfgang Beck <wolfgang.beck01@googlemail.com> Mon, 24 October 2011 07:28 UTC

Return-Path: <wolfgang.beck01@googlemail.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 166AE21F8B88 for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 00:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 0jPOTleKwvIf for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 00:28:41 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 35F9A21F8B83 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 00:28:38 -0700 (PDT)
Received: by yxi11 with SMTP id 11so1268460yxi.31 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 00:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+9C7XmxN0oZefE9l0Fwv0TLKp4xXVsMkilLGoI8ZtGY=; b=NGVcKw6m5hhQAdDj6NAc3P2n7n7JD6ykXE9cYLc0MlDwT8jsfTp2ujsohm+DXiRP2/ ZFrHR3WoHQ3Dq+VX7rVfR/QxPLuwBkqxCxSc+n5MXdN7lGi3RQfz9QY1Sh4PgLf1gX+z 8fkq1k0eEAP4Rvi0D2FDG0w6rkFfhXRl7BVs8=
MIME-Version: 1.0
Received: by 10.68.16.69 with SMTP id e5mr13459359pbd.67.1319441317297; Mon, 24 Oct 2011 00:28:37 -0700 (PDT)
Received: by 10.68.55.230 with HTTP; Mon, 24 Oct 2011 00:28:37 -0700 (PDT)
In-Reply-To: <4EA1558F.4030203@alvestrand.no>
References: <CALiegfmQBEEX+6FuA3tujePh3HUyfCU5Wy3N_=cn_K_GXZ267g@mail.gmail.com> <CALiegf=2Kv1CpS+EONbKZ01R8vvX2g1ofQ+Wgj5EEETr0vQK_g@mail.gmail.com> <931AFC17-0745-439C-ADB4-6E4581855645@phonefromhere.com> <4EA1558F.4030203@alvestrand.no>
Date: Mon, 24 Oct 2011 09:28:37 +0200
Message-ID: <CAAJUQMi=ZUTCmFkVMqj2UORDKCzgNckK0NMVej70wsXNd3LEPA@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of Signaling Components in RTCweb (clarifications)
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: Mon, 24 Oct 2011 07:28:42 -0000

On Fri, Oct 21, 2011 at 1:20 PM, Harald Alvestrand <harald@alvestrand.no> wrote:
> Tim Panton wrote:
>> So in short, I think that treating the SDP-like as a blob has significant
>> disadvantages.
>
> A point on which we agree .... Yes, I also think we need to have the ability
> to open the blob at the point that makes sense for the application - whether
> that's in the browser, the JS, the server, or somewhere else.
> _______________________________________________

ROAP only makes sense if the JS application has no full understanding
of the blob. If it can understand everything that's in the blob,
it could just use the ROAP API as a low-level API. Maybe that's the
way forward..


Wolfgang