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

Alissa Cooper <alissa@cooperw.in> Thu, 04 August 2016 14:05 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 C8C8412D95C for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2016 07:05:19 -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=4VKJXFLU; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=bRe8y+Jt
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 64ri4W1PhUrM for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2016 07:05:16 -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 83E0012D550 for <rtcweb@ietf.org>; Thu, 4 Aug 2016 07:05:16 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B67C820823; Thu, 4 Aug 2016 10:05:15 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 04 Aug 2016 10:05:15 -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=elxzm swysYpkIx4B/xkm1YondJs=; b=4VKJXFLUx8t6KJto8JnQiZNTCG+hUlaY8L2e5 q2DuaxFYb1sOEb5ZUaqzShXjcc1TniduiTyXAhJYvvihybW616OsIWDUqNmRxnPi 5ZUUCPQ/K73AtFCk0BDSxd9/4UeieiOR0SHOowFGIxWMsYme3BsyYxzKzZXGsqyN Wi+/hg=
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=elxzmswysYpkIx4B/xkm1YondJs=; b=bRe8y +JtRZUSDq4lMTk3EVqWv42BsJNE1dEhd7i5lllgT21ECT+IBzZLROV3DdyoHVBRT 3jZTSbajLi46J3nBCUSWf3gLZebcGR858/zZa1iUpzg5EMlUxOzPBHimfvjO1tRL iQzj9rRYGjUlD4BiGcdZzClopf71RuGv2HLSPQ=
X-Sasl-enc: 55yFLJMe6fjo4l8nRoXW8zdkGPGp2bMx49aDvJw7JCR8 1470319515
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id EAD00F29D9; Thu, 4 Aug 2016 10:05:14 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5C08D9B6-9EB7-4EB8-A13C-31DFE5022C20"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <2076CAA8-A1A0-4FA9-8F20-888BC2FAE36F@cooperw.in>
Date: Thu, 04 Aug 2016 07:05:13 -0700
Message-Id: <A1C30C9C-164A-4EC0-B08C-797DEF68DEC4@cooperw.in>
References: <cf9cb590-1c11-ce0a-07ad-274221db3999@alvestrand.no> <A9BA0203-5A57-4C85-B84F-293B7990BCB3@cooperw.in> <2076CAA8-A1A0-4FA9-8F20-888BC2FAE36F@cooperw.in>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/9mIN67A-Wy1XY-m7hwveWOLFc88>
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 14:05:20 -0000

> On Aug 4, 2016, at 6:46 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
>> 
>> On Aug 4, 2016, at 6:43 AM, Alissa Cooper <alissa@cooperw.in <mailto: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.

… and she has changed ballot positions again back to COMMENT before the telechat, so I will approve this for publication with a point raised to await the resolution of the outstanding issues.

Alissa

> 
> Alissa
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>