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

Peter Thatcher <pthatcher@google.com> Thu, 07 March 2013 21:58 UTC

Return-Path: <pthatcher@google.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 6E5DC21F8CA4 for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.771
X-Spam-Level:
X-Spam-Status: No, score=-102.771 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 06J7QP4WyXaN for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:58:54 -0800 (PST)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by ietfa.amsl.com (Postfix) with ESMTP id B11F421F8CC5 for <rtcweb@ietf.org>; Thu, 7 Mar 2013 13:58:53 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id gf7so850857lbb.18 for <rtcweb@ietf.org>; Thu, 07 Mar 2013 13:58:52 -0800 (PST)
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; bh=Rq46FW3oEiGoGji7It+Y/lH44xRYgOxL+3Kq/IsnPzw=; b=HO4nToz6d9V+5lJLhf1wI7yJ1vP86BgblNwCrRy6Uhe/LsXfLcoADlDNursQzR+6Za rW7twe6rYhLPEYyQU8wFUvbnkFR37NythRTZJysvOYaLPD2zUggpLXGDmyXpNFgzAnzL QKmm/koRh8zfxnDTH4r6irYa9Vk0FOOKaBHe30oxYn3Em72u33EruN7lDw51xRYXmpZA hIcKwvMSVRzcCR3Jml7ebm2zz/C9bMwDiYh4nI04aMZqC+sJwRVv1Ql0AObm9FMtR9iN WylqWQrUUKxsCw/OhDNyCImqpmjSAARfTBQA9mpGhBTGgt7J+675tCz/hP6Z63yUSuq4 WLJg==
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=Rq46FW3oEiGoGji7It+Y/lH44xRYgOxL+3Kq/IsnPzw=; b=ZUo1CXfsS5BN04lvaS6z9qEKapMXfHGHY/tfy/jULqlvi1amo9Ihvt3wKJf6OoZf4R ZmRhw4PpiRJczWYWCaDVqCaYRmHi8Yr2DAXGdkww+UBTK0aFOn45FSNK8ASjqUbove11 IKo3RgiDUEbXPcORfMhk2J2oEdO3amf44rOppGY+pK3mYNIO9d7RakoofixW0NH4y/MT jG/f4JZY84t0V2dj7zqC99zGRJqz5ZqItn0IR+lthOJ9fIZ3AypXsAS7kbAoDvCFc3Yw KXmstRCcR4NEe3k0PLmfYETM9EaPsq9xBSoMuTofbvFWKur0TQC3lgXnOB3Bvgs900XF EBVw==
X-Received: by 10.152.109.112 with SMTP id hr16mr30242533lab.38.1362693532547; Thu, 07 Mar 2013 13:58:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.152.6.5 with HTTP; Thu, 7 Mar 2013 13:58:11 -0800 (PST)
In-Reply-To: <CAD5OKxt0DmadedrS1fGT_gnGboxeFx9hhBoTGLkxk0vy01K0Kw@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> <CALiegfmTWZ0dDjfuUixL3nOpZ0LEs30TSOi1iFw7MW94qkD-JQ@mail.gmail.com> <CAJrXDUFy4u5B5AmG8xGN5SfNOe4HduJFunvQC_ht=5NOUYYjLA@mail.gmail.com> <CAD5OKxt0DmadedrS1fGT_gnGboxeFx9hhBoTGLkxk0vy01K0Kw@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Thu, 7 Mar 2013 13:58:11 -0800
Message-ID: <CAJrXDUGat7nwbf6eG7O8v23iwt8sHANzzmduCydZ+fCk7_7eug@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmwlDlw0qjeJ3qy0n4yWTkZYUfcyZQ3Yk4Kv0WTonzPwVul6DKaCAppcTRGHXgFccIOmXM3f2LhvmhilmrB/COBMqQ+IzJSolmnJzeJc0/bAi95jylOvE0du0GGENiLrHpQVUiltfxEaH85BYYNv/5BDmIIGT2xHnex7HSRzDx32cLqagI2nqv7gWxlGlkvI8gSpT17
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:58:55 -0000

To help keep track of all the needs mentioned, I made a Google Doc
that tracks them:

https://docs.google.com/document/d/1hXxZoLFMmypWlkQR8LmbYYD_uZnQS0FWaYItSDB9v-s/edit

If you're interested in a better SessionDescription that offers
low-level control in a readable and programmable way, without quite
"blowing up the world" with major changes to the API, please take a
look and leave comments.  I'll try to keep it up to date with what's
on the mailing list, but it's hard to keep track of everything :).

On Thu, Mar 7, 2013 at 1:46 PM, Roman Shpount <roman@telurix.com> wrote:
> I do not think redefining session description is the best approach. Having
> access to direct API methods that control send codecs, send media types,
> resolution, etc  is easier to understand and to program. I think even simply
> exposing the API from Voice and Video engines in current WebRTC
> implementation would be a more usable API then the current offer/answer SDP
> based one.
> _____________
> Roman Shpount
>
>
> On Thu, Mar 7, 2013 at 4:37 PM, Peter Thatcher <pthatcher@google.com> wrote:
>>
>> Having a minimal SessionDescription command and then a
>> "SessionDescription update message" that says "I'm adding new video
>> now" or "I'm disabling the video
>> right now" absolutely can and should be a part of a better
>> SessionDescription format.  I think that's a good idea and very
>> doable.
>>
>>
>>
>>
>>
>> On Thu, Mar 7, 2013 at 1:33 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>> > 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>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>