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:37 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 00E6E21F8566 for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.784
X-Spam-Level:
X-Spam-Status: No, score=-102.784 tagged_above=-999 required=5 tests=[AWL=-0.107, 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 u098HrV0Wtme for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 13:37:56 -0800 (PST)
Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by ietfa.amsl.com (Postfix) with ESMTP id 6714621F8B16 for <rtcweb@ietf.org>; Thu, 7 Mar 2013 13:37:56 -0800 (PST)
Received: by mail-ve0-f171.google.com with SMTP id b10so789856vea.30 for <rtcweb@ietf.org>; Thu, 07 Mar 2013 13:37:55 -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=8L255dxS10UGOdOxQiEL39dHNbr8jkCoba2Z1dS22q0=; b=J54pc1Yc9OLvtxUKZvGKthyxn4BAR9OHr9k4wKrFm8sTe3vAgwLsPuKfBO+WtJCAAM cQoZ5kT1aod13smDwWBVayULu9k+sjl6K0zbrv69ofnrbvi5Eu72MrR/xJ/mdSmVYV+d iv+x2Yh+DhmbVYqrnMOnIr2hHsAiOPdd/B+UCFDcd9N+lIbL8Kh+eFYDrENnE1oKRhtr 2IdzMEHF7G1EAJ1Ne5XLhjQELSl+LIyl27hdugUqIFhmNUjq0+/CEZ/oZ1sPVrMbUi33 2fAVgfaXhJ+Mhs8uZWj+ad8reeJOjLM3pBvWjBVgdVCY1yy8gyjq/YdObTNByxgJXpcG ef4g==
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=8L255dxS10UGOdOxQiEL39dHNbr8jkCoba2Z1dS22q0=; b=C8710PjXgM+Lc8430UuHagG33eQMdrlwS/U+IYeoCHVJ0A0I3ZGy5BSTzK75h5Uxn6 k+MvrzR7esUdyjf/g0uizDXi84tOnd6cktJ8uAvccA1+FbfHhPSoDn5fSeAIOUOUjOAm CwgHdvlGaojVYdSMaJ1nlHkQzSGsVQYZ9y/ij4pdjgnQm1dPwzNoemAqrXQcI9Ayu0wT 999VE3+E/dYfMgy26+hV0FzF7eng3mUYYe2of4z5TfoIu8JpUHUrRZsk0dkY85b2SEQx BrjhoYdhjBF4ib5CQW67w25xDGNLFDOvbF1dq5m97lTzFeQABOevKwG7KM8OvGJiR4tJ Hz1Q==
X-Received: by 10.220.219.80 with SMTP id ht16mr13296730vcb.30.1362692275805; Thu, 07 Mar 2013 13:37:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.58.49.102 with HTTP; Thu, 7 Mar 2013 13:37:15 -0800 (PST)
In-Reply-To: <CALiegfmTWZ0dDjfuUixL3nOpZ0LEs30TSOi1iFw7MW94qkD-JQ@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>
From: Peter Thatcher <pthatcher@google.com>
Date: Thu, 7 Mar 2013 13:37:15 -0800
Message-ID: <CAJrXDUFy4u5B5AmG8xGN5SfNOe4HduJFunvQC_ht=5NOUYYjLA@mail.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
X-Gm-Message-State: ALoCoQk8GDCyhES6N2ub7vDqEyuqbB00DGPdqa/R7DA7PJoYaKzxEfVBf+e5Q3j5nm2MHm/vIlPiDTjxtTfoIeaNCQdEVuH13k+Sx/00kINhnBa3g8xkiz4pvJQO9M/35SqA/CJHwSnu6Em/XPMEawMxbFCA/v1IauHhsR6TjnUJn3YtdDkFik63a2nsRAvtx++Nprb9CJ1w
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:37:57 -0000

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>