Re: [rtcweb] Proposed Plan for Usage of SDP and RTP - Lower level API minus SDP

Iñaki Baz Castillo <ibc@aliax.net> Thu, 07 March 2013 21:33 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 193A221F8ABC for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level:
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=0.050, 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 ChwjZSNBlcFF for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:33:39 -0800 (PST)
Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) by ietfa.amsl.com (Postfix) with ESMTP id 62DEA21F852B for <rtcweb@ietf.org>; Thu, 7 Mar 2013 13:33:39 -0800 (PST)
Received: by mail-qe0-f43.google.com with SMTP id 1so602957qee.30 for <rtcweb@ietf.org>; Thu, 07 Mar 2013 13:33:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=IIUJd1yjBjYFnaF81MOT17xMUSts5OfGnxuH45mYppg=; b=HQyE+nredEG+2pNHjvSK7cZ5IxQeLpW+VjVZheKjv7ydej4zA30hTgR6MoNhG1T2rS VqCm1+VuX4ZHMMblU6RhKgkCuRFIVDdt0iQFqECQ6TjFBM0YokOMMRZBhaYF8R9Tgilp m0ERjF05CIBhHmQn/nNECWBc7gqdKo0Ickfdw/MJYzFLoQ+qAP6njdNAWUA7dZ4YgOPr Xf/H2j5ieJMBLpvHYsNWbDAc24IyS7NhLLlXXi+/ZrYm1CgyZan5VeCEPOcz+/tMvAhs OZ9HKy4Q0OcVFn7+pDVadEMNNBpKuFqFdG/faaPf4GKd5IgizFCFfbXjGBrUJpfzBYkR B//g==
X-Received: by 10.49.133.195 with SMTP id pe3mr56719174qeb.58.1362692018850; Thu, 07 Mar 2013 13:33:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.49.12.233 with HTTP; Thu, 7 Mar 2013 13:33:18 -0800 (PST)
In-Reply-To: <CAJrXDUEK9DCMfxOoq-8HPQwjTZrVvW-CEZJzte_gzyUs16hJuw@mail.gmail.com>
References: <CD5D3F35.B22B%robin@hookflash.com> <B9549E2E-6E68-4F34-A9C0-1F050285A70A@acmepacket.com> <CAJrXDUGSMfQ=SNrSxKVvay=4JUXHULy0cO2pRN9+iFJ23doWZQ@mail.gmail.com> <CAJrXDUHvcsuN6vXs8wku_aUrs-siHdn2wBDOJBgpgDPJySgdSg@mail.gmail.com> <CABcZeBMt7vaMnhcDD0-U7n6Hn-T=sHcGUGEV4=vAs8DVcoi-CQ@mail.gmail.com> <CAJrXDUGqxDxS5=_YnLOWVT6xOgXYuspGS5U2gXevc+PP2vLdHw@mail.gmail.com> <CALiegfnZKVOgmh_5Qb2HeXuAL1BdxDc=U-=t1NfEEMC4DHMUew@mail.gmail.com> <CAJrXDUEK9DCMfxOoq-8HPQwjTZrVvW-CEZJzte_gzyUs16hJuw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Thu, 7 Mar 2013 22:33:18 +0100
Message-ID: <CALiegfmTWZ0dDjfuUixL3nOpZ0LEs30TSOi1iFw7MW94qkD-JQ@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmJKHzVIy1ONvUjvQj3/EgYybOAlyscb4ZLPL0ut0fQ1ZyefzR49un1dvUHFy6a81cqYFV5
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposed Plan for Usage of SDP and RTP - Lower level API minus SDP
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, 07 Mar 2013 21:33:40 -0000

2013/3/7 Peter Thatcher <pthatcher@google.com>:
> So, would you like a SessionDescription to send to the other side that
> is flexible and manageable, such as a JSON object?

If I have to receive the *entire* JSON / rawSDP /
whateverSessionDescription again with minimal changes just for
enabling/disabling video, I don't like it since it means that I must
"compare" the current SD with the new one.

I don't care whether the format is raw SDP, JSON or whatever. What I
would like is that I can establish an audio/video session with a peer
and, at some time, I can send a *minimal* SD "command" / "RPC" to say
the remote "Hi I am dissabling the video right now".


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