Return-Path: 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 90BBC128CE4 for ; Tue, 5 Mar 2019 13:13:43 -0800 (PST) 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=ham 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 qPCgLJUFuRG3 for ; Tue, 5 Mar 2019 13:13:41 -0800 (PST) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 C35811288BD for ; Tue, 5 Mar 2019 13:13:41 -0800 (PST) Received: by mail-io1-xd2b.google.com with SMTP id x4so8317594ion.2 for ; Tue, 05 Mar 2019 13:13:41 -0800 (PST) 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=4FAruVKIi16KvmBGo044T0X2ynmtZvulgDkDBly/xdQ=; b=nfZSPyXJr+aYI+LDhIMiCDfWhIDddffLBq7AieP5NMDCgOJ4je4Lm9tlYvBf/5nxFR PR6n65gbiUGGHAkKlsvsEWh94aV3rf8f0/fC+JqTIzFuv6UL168Dp7nlhs87OMGX6HgE fjo+K0S9BTWueblcXAATczMP7SngY68x380le1MZxcDvJhPZzpRVWhCmdEGxVseZCsCO zYwKuEPegDCDbmUqnK/fMU7XkNe6YjgeyTxcgI4Fk1X4aj9YJlD2Ed2QAoD5vroBqfdY eaz3cLPZlhZnQcJeJ1WKolSJb9UqFZHL0CW512LChwNP4DE7u8LgWE/EWanm3QYmlsHt 3tig== 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=4FAruVKIi16KvmBGo044T0X2ynmtZvulgDkDBly/xdQ=; b=ZTc2C5z8h5BJyIya6SQnwBLKVO19shifjpW2TQTtMy/ekbXSz47TL9jK3KIc/clX8k V1PVrmp6/8Lyx+lIo7aaf7N1aGlGR2fPuqtkon8srayChNGQRyx4wQH9vmXne8W3YHR3 AYVBahrE7poijPsO4TDOmqgA1wB3u4ajwVuR9YVUkPzvEEhIV/AaF2S9lNvr0vBBfqT/ ZlxDXkvWwZseW+qnocwbd0TT06NFKZ7YGxZTg3w0XaGh263hI1ze5YsGbui8Arf+c5vI +Wx073Otx/frWxbqUddChGRYzqnYaYttukynwI0nreDn2swK48eFz0XTTQ7Wl/BKTHcg mAnA== X-Gm-Message-State: APjAAAVHBVTA1ScNT8Dz7txHGKQxZptfYzI72fakW+2ZYY/+e3ywCbPZ f9TBuXxEnwsXROn7TstzDOFiMZfSj9YEIH3mb2EgdgaE X-Google-Smtp-Source: APXvYqx5TLp//FKui4+akmC/PJkDeSFZjinLhdD3aXKT5ElPeBFM9TrWWtfZ0mtvJeuM/V22Rqfl1/tY3d2emtTU+qY= X-Received: by 2002:a5d:9418:: with SMTP id v24mr1189593ion.181.1551820420734; Tue, 05 Mar 2019 13:13:40 -0800 (PST) MIME-Version: 1.0 References: <811b3bb7-8458-4790-b5af-7c4faedc133a@www.fastmail.com> In-Reply-To: <811b3bb7-8458-4790-b5af-7c4faedc133a@www.fastmail.com> From: Justin Uberti Date: Tue, 5 Mar 2019 13:13:29 -0800 Message-ID: To: Martin Thomson Cc: RTCWeb IETF Content-Type: multipart/alternative; boundary="000000000000ef576305835f58e5" Archived-At: Subject: Re: [rtcweb] Call for review X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Mar 2019 21:13:43 -0000 --000000000000ef576305835f58e5 Content-Type: text/plain; charset="UTF-8" Regarding information about implications, we expect to be able to share initial data within the next several weeks. On Tue, Mar 5, 2019 at 1:10 PM Martin Thomson wrote: > How is it that the two drafts this rules on are only informative > references? It probably needs to update IP handling. > > The modes this adds are good, but it specifically states that the > implications aren't known. It even promises to update the draft when that > information is gained. That suggests that this doc might have an uncertain > future. What is the chairs' thinking about the draft? > > On Wed, Mar 6, 2019, at 07:22, Ted Hardie wrote: > > Howdy, > > > > draft-uberti-ip-handling-ex- > > mdns > is a > very short draft describing two new modes related to > draft-ietf-rtcweb-ip-handling < > https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling> using bits of > draft-ietf-rtcweb-mdns-ice-candidates < > https://datatracker.ietf.org/doc/draft-ietf-rtcweb-mdns-ice-candidates/>. > > > > The chairs would like to ask for a couple of reviews; given that it is > > four pages long, we are hopeful that it will not take much time. > > > > Please send your review to the list, > > > > thanks, > > > > Ted > > _______________________________________________ > > rtcweb mailing list > > rtcweb@ietf.org > > https://www.ietf.org/mailman/listinfo/rtcweb > > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > --000000000000ef576305835f58e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Regarding information about implications, we expect to be = able to share initial data within the next several weeks.

On Tue, Mar 5, 201= 9 at 1:10 PM Martin Thomson <mt@low= entropy.net> wrote:
How is it that the two drafts this rules on are only informative= references? It probably needs to update IP handling.

The modes this adds are good, but it specifically states that the implicati= ons aren't known. It even promises to update the draft when that inform= ation is gained.=C2=A0 That suggests that this doc might have an uncertain = future. What is the chairs' thinking about the draft?

On Wed, Mar 6, 2019, at 07:22, Ted Hardie wrote:
> Howdy,
>
> draft-uberti-ip-handling-ex-
> <https://datatracker.ietf.= org/doc/draft-uberti-ip-handling-ex-mdns/>mdns <https://datatracker.ietf.org/doc/draft-uberti-ip-ha= ndling-ex-mdns/> is a very short draft describing two new modes rela= ted to draft-ietf-rtcweb-ip-handling <ht= tps://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling> using bits = of draft-ietf-rtcweb-mdns-ice-candidates <https://datatracker.ietf.org/doc/draft-ietf-rtcweb-mdns-ice= -candidates/>.
>
> The chairs would like to ask for a couple of reviews; given that it is=
> four pages long, we are hopeful that it will not take much time.
>
> Please send your review to the list,
>
> thanks,
>
> Ted
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb >

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
--000000000000ef576305835f58e5--