IETF Logo Mail Archive

Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-plan-00.txt

Iñaki Baz Castillo <ibc@aliax.net> Mon, 08 July 2013 17:32 UTC

Return-Path: <ibc@aliax.net>
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 C6BFC21F9D7C for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 10:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.645
X-Spam-Level:
X-Spam-Status: No, score=-2.645 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 aAph3xUY9hAz for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 10:32:16 -0700 (PDT)
Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177]) by ietfa.amsl.com (Postfix) with ESMTP id A1F3621F9D71 for <rtcweb@ietf.org>; Mon, 8 Jul 2013 10:32:16 -0700 (PDT)
Received: by mail-qc0-f177.google.com with SMTP id n1so2401981qcx.22 for <rtcweb@ietf.org>; Mon, 08 Jul 2013 10:32:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=kgPY455xMm1LwuQI65HK3QMTVnr2ihJBwCn97EMQ32s=; b=Q557x+WLfQn3OzjOIsIp2Yn0to3v8k99d2dJGySAxqQf+C3gWT3x68GcAJSpOCzi0v RqshnWYETSaljtHEWOFvdHxIFguhccj73MqHKoMzqQwqRY7bOTyp2Mvn/JlZRrRJVxg2 uf835EvuHFG33JD91I1tO3wjDE+oO2AcTwGUFrByxi/rJO82Mc76CrimbT/eE32X0FeN 5V4HfnzVTKFhmk0UbQqZyTC2t0c1OaGHQJJPNqXKCvKIOkDLt+cDx4FyaUzVw63zgBVH +g5/BTFZHk/Diogf+m5Q9NLoUq71M4ahMFXP8mP0kcafLf2AltNkOPNkyP9oFfVVZwW6 34NA==
X-Received: by 10.224.90.1 with SMTP id g1mr20283441qam.0.1373304735911; Mon, 08 Jul 2013 10:32:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Mon, 8 Jul 2013 10:31:55 -0700 (PDT)
In-Reply-To: <518BC17C.7030806@alum.mit.edu>
References: <20130503054601.4639.64651.idtracker@ietfa.amsl.com> <CALe60zAi_Lx3QFCbBQ5aPNkgorJAff0E79jkpbQX1Qt3wf2bzg@mail.gmail.com> <CAOJ7v-1Wk6u7XiYrNVmoqr5Jisu2WRvZpte7hQTOiP8YHUc6hg@mail.gmail.com> <008701ce4b21$a0997aa0$e1cc6fe0$@gmail.com> <BLU169-W108D56DF61B85814543873C93BA0@phx.gbl> <518AAAF2.5000207@alum.mit.edu> <CA+9kkMBw4+kXAv6qLCcmGLwMxAqR6P-Tk8dm-ardv_jihHx0Hw@mail.gmail.com> <518BC17C.7030806@alum.mit.edu>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 08 Jul 2013 19:31:55 +0200
Message-ID: <CALiegfk1ZEJfzisDG4fzfBqxObLFsc7C0SpZEkbdxL2ykr+m1Q@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnb0cRHL3ssiHWsFv/wnVAQc2xi+zM6hwacyaGMKhGsVDcfp6lxIfQQ9YY3PO69oPh9ELTk
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-plan-00.txt
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, 08 Jul 2013 17:32:22 -0000

2013/5/9 Paul Kyzivat <pkyzivat@alum.mit.edu>:
> Whatever signaling is used to indicate bundling usage in SDP in RTCWEB
> should be consistent with what is used in clue. It would be unpleasant if we
> had to have a translator in the web server that must translate one SDP
> notation to another.

Hi,

Give a powerfiul real JavaScript Object based API (instead of an
opaque SDP blob) and let the web developer decide whether to construct
**via JavaScript** a CLUE compatible SDP or not (just if he needs
that), and we all will win.

In contrast, by mandating plain SDP (just because SIP uses it) we have
to have a translator in the web server that must translate plain-SDP
to XML-SDP (in Jingle XEP 0167 deployments), or build the best SDP
parser at JS level to parse the SDP blob created by the browser and
convert it into XML, and then convert it back into plain SDP.

Best regards.


--
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email