Re: [rtcweb] Relaxing SDP O/A (was RE: Agenda requests for Atlanta meeting)

Martin Thomson <martin.thomson@gmail.com> Thu, 18 October 2012 16:36 UTC

Return-Path: <martin.thomson@gmail.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 D762421F86EF for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 09:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.719
X-Spam-Level:
X-Spam-Status: No, score=-3.719 tagged_above=-999 required=5 tests=[AWL=-0.420, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 326eBxBhgQcG for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 09:36:02 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE3B21F86EC for <rtcweb@ietf.org>; Thu, 18 Oct 2012 09:36:01 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so6729669lam.31 for <rtcweb@ietf.org>; Thu, 18 Oct 2012 09:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=IY7dbnpMiAWSh//zMnHBYOHKeb5Mn0K7EagnWh2NfWY=; b=DtWfBBtT+HlzRkEwfP0KyhgyM7H5V6KlKhoHQsWwpKyzdF3Y076r11PRlCHjgLK93o T3O/hU82KAnUIMY3WpnTsT4HOYTKwvuFuBZ+kJsQw7sKwNVWmgrHv/ARtMXldd6cWuvp Ec7n1yATBWMwX/2h4aS0PpU2bKFDSffePQPXaw3nIMQDijStuGL+JtZ5OS5y1OJ399I1 Sc7YJ1ryHk5YrUxHrfX2Xyd9PaLvgKQwmGKfVVEdbTePgDhbuh2acIbVJnz90FdEBfLy ixgRXb2Qu/E3yS84Ut6ol/s2wYBG/2egmDxIiWUrrU9TyMfdShQqwhG08LmxUPulZDeB mZzg==
MIME-Version: 1.0
Received: by 10.112.43.34 with SMTP id t2mr8073385lbl.109.1350578161094; Thu, 18 Oct 2012 09:36:01 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Thu, 18 Oct 2012 09:36:00 -0700 (PDT)
In-Reply-To: <CALiegfmJQa2SZXqrL-cAV21O1k79gC+KVWxwF1peJPjZ1nkTsw@mail.gmail.com>
References: <AE1A6B5FD507DC4FB3C5166F3A05A484160ED478@tk5ex14mbxc272.redmond.corp.microsoft.com> <507F3680.4060200@alum.mit.edu> <CALiegfmJQa2SZXqrL-cAV21O1k79gC+KVWxwF1peJPjZ1nkTsw@mail.gmail.com>
Date: Thu, 18 Oct 2012 09:36:00 -0700
Message-ID: <CABkgnnVPHdB_PrNDbq_RiZ=RPfQgUv7aV1u3cqQLvAS5Mx5STg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Relaxing SDP O/A (was RE: Agenda requests for Atlanta meeting)
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, 18 Oct 2012 16:36:02 -0000

On 18 October 2012 09:19, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> 2012/10/18 Paul Kyzivat <pkyzivat@alum.mit.edu>du>:
>> I have been assuming that this is to be accomplished by the server pushing
>> javascript that is aware it is/may be interworking with sip, and which then
>> constrains itself to the subset of JSEP that compatible with 3264. And then
>> it is of course limited to those behaviors on the sip side that fall within
>> the subset of 3264 that JSEP supports.
>>
>> Is that the right way to view it?
>
> Hi Paul, what about is the JavaScript app directly speaks SIP? please
> let's also consider this case. Current web apps based on HTML5 and
> modern JavaScript are powerful like any other desktop application. No
> need to consider them limited and rely all the logic in the web server
> (like 5 years ago).
Iñaki,

I think that is *exactly* what Paul said.  After all, the Javascript
has to come from somewhere.  That's usually a server.  The alternative
is that there is a server somewhere that does this work.

I find the distinction uninteresting.  Server or Javascript are both
"application" and where this code is executed matters very little.

--Martin