Re: [rtcweb] No Plan

Richard Barnes <rlb@ipv.sx> Wed, 29 May 2013 21:00 UTC

Return-Path: <rlb@ipv.sx>
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 B468C21F8E6E for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 14:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.146
X-Spam-Level:
X-Spam-Status: No, score=-0.146 tagged_above=-999 required=5 tests=[AWL=-1.387, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1, SARE_HTML_USL_OBFU=1.666]
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 n1cp9bjc7vgl for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 14:00:43 -0700 (PDT)
Received: from mail-ea0-x22f.google.com (mail-ea0-x22f.google.com [IPv6:2a00:1450:4013:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F270721F958B for <rtcweb@ietf.org>; Wed, 29 May 2013 14:00:42 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id h10so5712149eaj.20 for <rtcweb@ietf.org>; Wed, 29 May 2013 14:00:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=e7iYBkDU2XtpXCfYjTDpzzbHSO7CTakX32OT627IcwE=; b=al3VZ9LISaJ1KWZwT/am5Sn8rN0SjHcR4V73G0UZcdxM1IAgvg2QWXxy7c/DZDZ9GP cQIqdw1m6H+ek/OWKRyrYDMfrAHHab5KC4HgR2XHTT2HS6+obHNWtv/xJ8Uc0Ed/5X+h t1gZrwZKrmuqbrtH3xfGxylQrjPbK9AlGD4RYxdKmPkqw3v720hu3b/+BC0XXOy3Uwk2 wG9zAQMeA2MaAEmXzCb9G/85n8Vl1+Pr5z4vyq5Bu74w7A3msYToHnDtnh32hygDz6Q9 3MGRurXkWmqe8oM3ITH5Hsatqb3n1qM5ldG/WTZCw9iYjq13lxzyTrxGdRathE6CXlq8 WoQA==
MIME-Version: 1.0
X-Received: by 10.15.23.4 with SMTP id g4mr6431585eeu.107.1369861241995; Wed, 29 May 2013 14:00:41 -0700 (PDT)
Received: by 10.14.38.199 with HTTP; Wed, 29 May 2013 14:00:41 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <51A66B3B.6070005@gmail.com>
References: <BLU404-EAS183E8C6EC78BF3F108964C793900@phx.gbl> <51A66B3B.6070005@gmail.com>
Date: Wed, 29 May 2013 17:00:41 -0400
Message-ID: <CAL02cgTjJ7RrOZWUUFHCsEGSFSHSkDEt2kEfXB94HV2VzyDPPQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Content-Type: multipart/alternative; boundary=089e01681c86b8c0cb04dde1ac82
X-Gm-Message-State: ALoCoQlBzkuNsdQQQNjvjW7qrcJ8bOSGPba9rfZQ668QviDI9mJjuLidjeCLXUunCJIg3gP7LWKf
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No Plan
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: Wed, 29 May 2013 21:00:47 -0000

Like Paul, I'll reserve a full judgement until I've had a little more time
to digest this.  At first read, though, it seems like there's a lot of
"magic happens here" in the draft.  There's an example of how you establish
a legacy-compatible stream, and an assertion that JS can do the rest.  The
truth of this assertion isn't obvious to me.  It would be helpful if the
document had an example of, say, how one might add a stream.

--Richard


On Wed, May 29, 2013 at 4:55 PM, Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> wrote:

> Hi,
>
> I also think it is the best approach.
>
> Best regards
> Sergio
>
> El 29/05/2013 22:30, Bernard Aboba escribió:
>
>  I also like it quite a bit. In particular I think it is more compatible
>> with simulcast and layered coding than Plan A or Plan B.
>>
>> Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>>
>> Personally, I really like this approach.  I think it will work well
>> for CLUE. You might also want to add a reference to XCON in section 4.
>>    The very reason we chartered XCON was because it seemed much more
>> sensible to include more complex conferencing operations in a separate
>> application layer protocol as opposed to overloading SIP/SDP O/A.
>>
>> Mary.
>>
>> On Wed, May 29, 2013 at 1:59 PM, Emil Ivov <emcho@jitsi.org> wrote:
>>
>>> Hey all,
>>>
>>> Based on many of the discussions that we've had here, as well as many
>>> others
>>> that we've had offlist, it seemed like a good idea to investigate a
>>> negotiation alternative that relies on SDP and Offer/Answer just a little
>>> bit less.
>>>
>>> The following "no plan" draft attempts to present one such approach:
>>>
>>> http://tools.ietf.org/html/**draft-ivov-rtcweb-noplan<http://tools.ietf.org/html/draft-ivov-rtcweb-noplan>
>>>
>>> The draft relies on conventional use of SDP O/A but leaves the
>>> intricacies
>>> of multi-source scenarios to application-specific signalling, with
>>> potentially a little help from RTP.
>>>
>>> Hopefully, proponents of Plans A and B would find that the
>>> interoperability
>>> requirements that concerned them can still be met with "no plan". Of
>>> course
>>> they would have to be addressed by application-specific signalling and/or
>>> signalling gateways.
>>>
>>> Comments are welcome!
>>>
>>> Cheers,
>>> Emil
>>>
>>> --
>>> https://jitsi.org
>>> ______________________________**_________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>>>
>> ______________________________**_________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>> ______________________________**_________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>>
>
> ______________________________**_________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>