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

Justin Uberti <juberti@google.com> Mon, 01 October 2018 20:28 UTC

Return-Path: <juberti@google.com>
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 884BF130E0A for <rtcweb@ietfa.amsl.com>; Mon, 1 Oct 2018 13:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 kZRXbGhkZ8S0 for <rtcweb@ietfa.amsl.com>; Mon, 1 Oct 2018 13:28:04 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8658C1252B7 for <rtcweb@ietf.org>; Mon, 1 Oct 2018 13:28:04 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id i76-v6so173281ita.3 for <rtcweb@ietf.org>; Mon, 01 Oct 2018 13:28:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=a12CoQJJgwlBES8h6U10wourkTosGA/q2YOqfyKmOC8=; b=o1HpctyDkRVuWXNt0SdK96+urJfALR45mVsHMYHX92Y8huY2vhL9MYAPRhheWzSCyI 16mEjmqsmr2y9dWzjoMjp9eJnxUGKPPvJx5e9FLjSHUWicVKlqeRARiwFV135yXj4HDh xURxDJq7bUGYRJdjCLHkIK5Kp+fghrwIgvmh8FfR0D8G9r8Dj+wnPXBluA2DV+sEI+FD HSUZAXQP7nQuX0Q6QvMqpga/5VRf9lvdEbQeg4kljH8qxsZ29lpCJGuJnlY99FWM3MGr V7NWj/oZTspthvNe/LRCdYWUoUdULkSPD0NTZRoS1IyjY5urTfvvgA0esHQNgvaw73M9 oJfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=a12CoQJJgwlBES8h6U10wourkTosGA/q2YOqfyKmOC8=; b=pnVsW9h9asf06MUveis1v4Cy46m0RzaKNXNCyD4cMkuGN8pDWtgCAz5AOFeoCfgpsw uMzXli92fZzX0fqS7MQCYkFss0xfiRPmriPCiCPw1Eg/mpv60KWWfq4dBduxOParZrac o3h1kXLxN4vBz0kr2T9YMf/s7phM44/2eu/lHp/U8gfQm6jQY9WK3gcQN4UOT9x/hwud TxNQ/xKF1J9hnWpfdXIyOpDysjOP/rD43X3WGUNuud5TJos3y1+8Ts86NgU5r3cQ0V/6 HvUbpTp0Ckr72ou0+BiU4A29OhtwGqyqxyr/5jNrCdrvDg14NC+ppq9XZ9TmvlDWwine RaxA==
X-Gm-Message-State: ABuFfogC3HAWmK3w81XAhXote6TCm9Mwj/D0z3CTJXkD0vLFKmMlogsr hjQjdUyqfr7N3MOlTkm1IjnPUBTOIvEZ3Mj4UD+wc3U7TQA=
X-Google-Smtp-Source: ACcGV61tZ1EgFuh/Xch5KiOSloGikFrz6e8EeOHXGNpCYJp4F8ziJgd/Azx2CajRenX3oLwWsh3iuHcZ7Wf+OYfDN3Q=
X-Received: by 2002:a24:d1c5:: with SMTP id w188-v6mr10488896itg.99.1538425683533; Mon, 01 Oct 2018 13:28:03 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <CAOJ7v-1bu69yORLo_=bPC_ZuMey5XUrhJ1ZHo+7mzjU4-71n2g@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 1 Oct 2018 13:27:50 -0700
Message-ID: <CAOJ7v-2D+Wptbss1XhEBWbOpUEpOAS8Jb0Hx0rZZk13rAotz-Q@mail.gmail.com>
To: 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>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, ice@ietf.org
Content-Type: multipart/alternative; boundary="00000000000061e47e057730a41d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/lVmjsm1w-THSwsBjnPm3pVgq48k>
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: Mon, 01 Oct 2018 20:28:08 -0000

[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>; 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>; 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
>>
>>