Re: [rtcweb] New Version Notification for draft-uberti-rtcweb-plan-00.txt

Cullen Jennings <fluffy@iii.ca> Fri, 10 May 2013 18:45 UTC

Return-Path: <fluffy@iii.ca>
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 09D0B21F92B7 for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 11:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.16
X-Spam-Level:
X-Spam-Status: No, score=-3.16 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, 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 QjVTYIAmZlES for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 11:45:15 -0700 (PDT)
Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDD121F910D for <rtcweb@ietf.org>; Fri, 10 May 2013 11:44:52 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by fallback-in1.mxes.net (Postfix) with ESMTP id 6545F2FD7DB for <rtcweb@ietf.org>; Fri, 10 May 2013 14:44:51 -0400 (EDT)
Received: from [192.168.4.101] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D681122E2C3; Fri, 10 May 2013 14:44:48 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <518A1268.8090107@ericsson.com>
Date: Fri, 10 May 2013 11:06:53 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <01AB1BF5-7ABF-4DD3-A831-3A6C96EA680C@iii.ca>
References: <20130503054601.4639.64651.idtracker@ietfa.amsl.com> <CALe60zAi_Lx3QFCbBQ5aPNkgorJAff0E79jkpbQX1Qt3wf2bzg@mail.gmail.com> <CAOJ7v-1Wk6u7XiYrNVmoqr5Jisu2WRvZpte7hQTOiP8YHUc6hg@mail.gmail.com> <518A1268.8090107@ericsson.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
X-Mailer: Apple Mail (2.1503)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] New Version Notification for draft-uberti-rtcweb-plan-00.txt
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: Fri, 10 May 2013 18:45:22 -0000

On May 8, 2013, at 2:52 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:

> * The (3-way) handshake is well aligned with the API (where the sending app initiates the sending of media)

Interesting - I saw it sort of the opposite so perhaps you can you say some more. I saw this as a complete change to everything we had discussed up to this point in how the API would work and how it would interact with Offer/Answer. I figured dealing with this change would set  back the W3C API work over 8 months so this is good news if you see a way that it is the well alighted. Can you explain how it lines up with the current drafts, call flows, existing example applications, and APIs that are all based on a 2 way hand shake?