Re: [rtcweb] Transport -15 submitted, still some issues

Alissa Cooper <alissa@cooperw.in> Thu, 04 August 2016 13:46 UTC

Return-Path: <alissa@cooperw.in>
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 41C2F12D54C for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2016 06:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=xqfdu9EK; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=HZggB6R/
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBAXBU7LvNWi for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2016 06:46:28 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FD9E12B025 for <rtcweb@ietf.org>; Thu, 4 Aug 2016 06:46:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A15ED207CD; Thu, 4 Aug 2016 09:46:27 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 04 Aug 2016 09:46:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=TNAWk sL8LRT6IR/XeIabW/+f0TM=; b=xqfdu9EKoDiWCMJidqpfwKJBd9ziEfqn/rGeG kGOEgqXq7B2XyEbm33x5Qrimo/eQXbzeFbsyFmBrTiwOMrustQyBg6UX37vM6MzV J6DRDnFu3cYpfw6mux9HXkiA2o5yaTEwYF9eJIETLCODn+k2OkhvYVjdzEkjmAg4 zCgbGQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=TNAWksL8LRT6IR/XeIabW/+f0TM=; b=HZggB 6R/OuEYJiXZBc1ITgalMfqP0gyokNoNvqQNk2UYqwsahj1Yfox/7WaGtcpyL3w9d km96Y9AWzh5NJJx2KP/YhT6d81/ouv/xsE2E3XkAjRCPFipd7VyNADbaT1C5k9Fc YT3Iz7iKk3knGqoA+B9C6aHUw0q92720R5aAK8=
X-Sasl-enc: yIEAow9GJYOCT9oKeyUjUIf9TFwY3yG6TKDj4lqTUIkz 1470318387
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 03733F2D2B; Thu, 4 Aug 2016 09:46:26 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C31FDAC4-575B-487E-BA93-6D9E92DA108F"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <A9BA0203-5A57-4C85-B84F-293B7990BCB3@cooperw.in>
Date: Thu, 04 Aug 2016 06:46:25 -0700
Message-Id: <2076CAA8-A1A0-4FA9-8F20-888BC2FAE36F@cooperw.in>
References: <cf9cb590-1c11-ce0a-07ad-274221db3999@alvestrand.no> <A9BA0203-5A57-4C85-B84F-293B7990BCB3@cooperw.in>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/yy7d_SpNQG_fRrwa4rT0r3YepGI>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Transport -15 submitted, still some issues
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: <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, 04 Aug 2016 13:46:30 -0000

> On Aug 4, 2016, at 6:43 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> Thank you, Harald, for processing all the comments so efficiently.
> 
>> On Aug 4, 2016, at 3:45 AM, Harald Alvestrand <harald@alvestrand.no <mailto:harald@alvestrand.no>> wrote:
>> 
>> I have submitted -15 and closed those issues that I believe it resolves.
>> There are six left in the tracker: One I forgot (#40), one raised today
>> in the IESG (#41), and Andy's "RETURN reference" issue (#42), as well as
>> 3 issues where I suggested "no change" as a resolution.
>> 
>> Comments welcome!
>> 
>> Note - I believe #41 and #42 are technical changes, so should formally
>> require IESG re-processing. I believe the others are editorial in
>> nature, so can be done without a new IESG pass.
> 
> For #41, Mirja has suggested the following text:
> 
> "For transport of media, secure RTP is used.  The details of the profile of RTP used are described in "RTP Usage“ [I-D.ietf-rtcweb-rtp-usage], which mandates the use of a circuit breaker [draft-ietf-avtcore-rtp-circuit-breakers-17] and congestion control (see [draft-ietf-rmcat-cc-requirements-09] for further guidance).“
> 
> This is non-normative text suggested in a non-blocking comment, and it’s up to the WG to decide whether to include it. But whether or not it gets included, if the text is along the lines that she suggests then the document will not have to be re-processed by the IESG.

Apologies, before I sent this I failed to see that Mirja changed her ballot position from COMMENT to DISCUSS. So this issue requires a resolution before the document can be approved for publication.

Alissa