[rtcweb] Spencer Dawkins' Yes on draft-ietf-rtcweb-jsep-24: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Thu, 14 December 2017 05:42 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A03B71200F3; Wed, 13 Dec 2017 21:42:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-rtcweb-jsep@ietf.org, Ted Hardie <ted.ietf@gmail.com>, rtcweb-chairs@ietf.org, ted.ietf@gmail.com, rtcweb@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151323013465.6079.10099272164953886555.idtracker@ietfa.amsl.com>
Date: Wed, 13 Dec 2017 21:42:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/4X5U8QSIUGba_l6VT5jGB3hyUwY>
Subject: [rtcweb] Spencer Dawkins' Yes on draft-ietf-rtcweb-jsep-24: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Dec 2017 05:42:14 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-rtcweb-jsep-24: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I found myself wishing that Section 3.8 was a bit clearer about the advantages
of sequential versus parallel forking. I can imagine some of the advantages
because I have a SIP background, and I can dig some of what I was expecting to
see in 3.8.2, but I'm imagining and digging, and I'm betting that the document
could be more explicit about the tradeoffs - just saying "if you're
communicating with a SIP endpoint, most of them can only exchange media with
one endpoint at a time" is already helping.