Re: [rtcweb] [MMUSIC] [Ice] [art] [clue] ICE, ICE-bis, and Cluster 238

Heather Flanagan <rse@rfc-editor.org> Tue, 02 October 2018 16:46 UTC

Return-Path: <rse@rfc-editor.org>
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 F1F3912785F; Tue, 2 Oct 2018 09:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 OYNMxXTJmmoE; Tue, 2 Oct 2018 09:46:45 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02A83128D68; Tue, 2 Oct 2018 09:46:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E3BC11D06E0; Tue, 2 Oct 2018 09:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diQf7_ynoKzC; Tue, 2 Oct 2018 09:46:30 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (unknown [108.177.128.150]) by c8a.amsl.com (Postfix) with ESMTPSA id 693D71D06DD; Tue, 2 Oct 2018 09:46:30 -0700 (PDT)
To: Justin Uberti <juberti@google.com>, Adam Roach <adam@nostrum.com>
Cc: Peter Thatcher <pthatcher@google.com>, RTCWeb IETF <rtcweb@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>, ice@ietf.org
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca> <46E40ED2-D289-4C0F-8C0B-82A5980B2692@ericsson.com> <E05D7CB4-832E-4221-ADFE-D8F317EEA8F1@iii.ca> <CAJrXDUGpmZKGQXF0p1hjQv_F=5dQoJLUCT7+6y-=uzwcRv1Ncw@mail.gmail.com> <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com> <2f5dfed4-1f77-51cf-aec8-0d3e8e8edb14@nostrum.com> <CAOJ7v-1bu69yORLo_=bPC_ZuMey5XUrhJ1ZHo+7mzjU4-71n2g@mail.gmail.com> <CAOJ7v-2D+Wptbss1XhEBWbOpUEpOAS8Jb0Hx0rZZk13rAotz-Q@mail.gmail.com>
From: Heather Flanagan <rse@rfc-editor.org>
Message-ID: <35975d78-76b7-b317-c43a-2a57e33198e7@rfc-editor.org>
Date: Tue, 2 Oct 2018 09:47:00 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <CAOJ7v-2D+Wptbss1XhEBWbOpUEpOAS8Jb0Hx0rZZk13rAotz-Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------682A0A1FF2E5BA1B6425480C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/bV59a95ahriv7fMllXMUgZoFnpw>
Subject: Re: [rtcweb] [MMUSIC] [Ice] [art] [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 16:46:55 -0000

Thanks for copying me in, Adam. I definitely agree that this level of 
change is significant enough that it can't be handled in AUTH48. But, 
better it be right than fast!


-Heather

On 10/1/18 1:27 PM, Justin Uberti wrote:
> [dropping some DLs]
>
> I think this is probably a day of work, but will probably take 2 weeks 
> to author and get approval for.
>
> If we go down this path, I would also suggest taking the two pending 
> PRs in JSEP, which will also impact the examples.
> https://github.com/rtcweb-wg/jsep/pull/849
> https://github.com/rtcweb-wg/jsep/pull/850
>
>
> On Mon, Oct 1, 2018 at 1:23 PM Justin Uberti <juberti@google.com 
> <mailto:juberti@google.com>> wrote:
>
>     I think this is probably a day of work, but will probably take 2
>     weeks to author and get approval for.
>
>     If we go down this path, I would also suggest taking the two
>     pending PRs in JSEP, which will also impact the examples.
>     https://github.com/rtcweb-wg/jsep/pull/849
>     https://github.com/rtcweb-wg/jsep/pull/850
>
>     On Mon, Oct 1, 2018 at 12:17 PM Adam Roach <adam@nostrum.com
>     <mailto:adam@nostrum.com>> wrote:
>
>         On 9/27/18 6:20 PM, Justin Uberti wrote:
>         > I agree with Peter. Chrome's implementation is already
>         closer to 8445
>         > than 5245, so I don't see any issues associated with
>         snapping this
>         > cluster to 8445 (aside from the work involved).
>         >
>         > On that topic, note that JSEP will need a few more changes
>         than just
>         > the addition of the 8445 reference and note; the examples
>         will have to
>         > be updated, as will the logic regarding generation of offers
>         and
>         > answers and their parsing (to deal with the new ice-option).
>         These
>         > changes will be modest but probably will need to be done by
>         the authors.
>
>
>         If I read what you're saying correctly, it sounds like you're
>         talking
>         about changes that are significant enough that we'll have to
>         put JSEP
>         through IETF last call and through the IESG again. That being
>         the case,
>         and the rest of the cluster being so close to done, I'd really
>         prefer to
>         see this done very soon, if such changes are required. When do
>         you
>         believe such an update could be available?
>
>         I've copied the RFC Series Editor on this note for her awareness.
>
>         /a
>