Re: [rtcweb] No Plan

Mary Barnes <mary.ietf.barnes@gmail.com> Wed, 29 May 2013 19:23 UTC

Return-Path: <mary.ietf.barnes@gmail.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 4FE4221F9725 for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 12:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 mCoK5DPEPB6X for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 12:23:23 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2D35221F944C for <rtcweb@ietf.org>; Wed, 29 May 2013 12:23:23 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id bv4so567470qab.12 for <rtcweb@ietf.org>; Wed, 29 May 2013 12:23:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rYYH/4tTFFHUrOyWfJ229/Pfbw2EVFUbixprWgOC//M=; b=KXhQ0/Tbnrt7VFelHNydo61/7T3yDwg1XEHTmQvAg8OgHa5rEhv2OWHNiNKSN5TT+o 5w02vEAX07nGLny5+4AVim057Yc7pdo8pyZL+T4ifUG1fvFfwkT6+et/3scPyyMdBqIP ilNTOfBNdTv5pOjjkPO2FEhxdhdT9qCV4nGLxYG7MVhl+VjFt00F5EDr6EeG0s1eY8FN 53pb9Y9AErrFsLm2scafFHmks9iaA2VtrRDzpAnZcBTrAfiYPW+GAJaY1EkG+vgXp9qf +VyeJ1pn13ehXIEmi+DF0R3crJaFW9X8eBAmQMC9NFXBuh0gW63jpkq1Dk3MsA1U7YGu /auA==
MIME-Version: 1.0
X-Received: by 10.224.70.147 with SMTP id d19mr4346725qaj.91.1369855402535; Wed, 29 May 2013 12:23:22 -0700 (PDT)
Received: by 10.49.41.68 with HTTP; Wed, 29 May 2013 12:23:22 -0700 (PDT)
In-Reply-To: <51A65017.4090502@jitsi.org>
References: <51A65017.4090502@jitsi.org>
Date: Wed, 29 May 2013 14:23:22 -0500
Message-ID: <CAHBDyN5Bf+VS=wV+oMRmDF74p7QaTATfzGONDBjeEFNd4cJG9A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: text/plain; charset="ISO-8859-1"
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 19:23:24 -0000

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
>
> 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