Re: [rtcweb] Draft agenda for IETF 87

Iñaki Baz Castillo <ibc@aliax.net> Fri, 12 July 2013 09:11 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 4F66421F9A2A for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 02:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[AWL=0.027, 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 XF+pGxoLy0Pa for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 02:11:30 -0700 (PDT)
Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) by ietfa.amsl.com (Postfix) with ESMTP id A30B821F9C17 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 02:11:23 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s1so4886252qcw.15 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 02:11:23 -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=1WMiL/m7KFC+Yj/NfQktvI25hnKjQcBCo5+/e1QrIpM=; b=SpPP+dKjgxxz0J+ZausXWrSefckcqMYtVKd+IsyqtiDkNqhl3vfO4gLQ07ElS/C83R J7ptgmrYAKpir1l9IffLzhmYmCnlWc9WS4QEa+UBh1yRTtQBlVZj1d7RMzAsZamJ7FJx Lh/NDw34Xj/6GJ0g4HxORMvFdC69WIsa2J0mQB9GCTohXf418k2av/dYdPRMs7R6cB5s d5gcXWzs5dI0dz6juxLMxNKjch7NUS9o5SgJcho4Ew6hX8eIK2509y7dLjXbYGD62Dyz f+mvP5OTCRWu4LRoHe9DikZj+MTS+PPidRHvR8MsuXzJCXAJBU6G3VtrLG2DKylGkZbw WT/A==
X-Received: by 10.49.98.138 with SMTP id ei10mr34092896qeb.3.1373620283061; Fri, 12 Jul 2013 02:11:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Fri, 12 Jul 2013 02:11:02 -0700 (PDT)
In-Reply-To: <1447FA0C20ED5147A1AA0EF02890A64B1C311367@ESESSMB209.ericsson.se>
References: <CA+9kkMBuCTdFsUMtmuBz6BnrSJMpHywEZU+x+m8ARnGprvzDzA@mail.gmail.com> <CAPvvaa+dyYmvsareEy1a9+7ketEFjNarsnRLXkpT_YHPTYni2w@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135D31FD@xmb-aln-x02.cisco.com> <CABkgnnU9r9OT+XW=Ewf=25yBJGCEZxCVnu_r1D=Eu=f9wrV4Kg@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C311367@ESESSMB209.ericsson.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 12 Jul 2013 11:11:02 +0200
Message-ID: <CALiegfm6=dYKubKLkV+pQNY=SOc8WNdoCvA7Es=+N-ouJDbj1g@mail.gmail.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnLwKfhKlSroDevoNiHf89u1e1PyKe9X/j7rkkCeQAAmYMHKJ5/KyI4QVmEP6xBgrqjxysR
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Draft agenda for IETF 87
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: Fri, 12 Jul 2013 09:11:35 -0000

2013/7/12 Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>:
> * JS APIs to:
> ** Apply an SDP (e.g. received on the signaling channel) to the browser
> ** Hand an SDP generated by the browser over to the application (for
> transmission over the signaling wire presumably)
> ** Influencing/modifying the contents of the SDP
> * All belongs to the W3C WebRTC

I've never seen an API in which the application requests some data to
the core, and then mangles such a data before sending it to the peer.
This is like if I ask the browser to send video, the browser gives me
a media description (I will not assume SDP) with ptime=20, and I
mangle the media description to set ptime=50, while at the same time I
have no idea whether my browser can send RTP with ptime=50 or not.
It's just awesome.


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