Re: [rtcweb] IP handling: Using mDNS names for host candidates

Justin Uberti <juberti@google.com> Wed, 13 June 2018 03:20 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 87C97130E72 for <rtcweb@ietfa.amsl.com>; Tue, 12 Jun 2018 20:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.21
X-Spam-Level:
X-Spam-Status: No, score=-18.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 KnTpUV_NUtE6 for <rtcweb@ietfa.amsl.com>; Tue, 12 Jun 2018 20:20:45 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 095A4130DD7 for <rtcweb@ietf.org>; Tue, 12 Jun 2018 20:20:44 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id a195-v6so1968628itd.3 for <rtcweb@ietf.org>; Tue, 12 Jun 2018 20:20:44 -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=3lxzCsrNsCd1mi8g0JE7rOdAZZ60M8IwT12O3/RzuUg=; b=XEGuMemjDz4xis/hf5sITI+vlNhYw5YD+gOuIFW6am4UP4Dik9WgcSEW+pp5B8gfy7 Xlj0j0JuNPpquMOu31k8i9qXx8p/GIhZnGIJUVC2/D55l5unh8031DB9iFMiXSiEtXNV cMR6rdMHPjIzogjdIBHdnByyhgbeMRJnPEz5KoZPNtnFUCC1lhcHObLhfp8022dL6aZ8 NOZM9Ndn1v59pKo2PwDW1mnZjqszENZaMnTn+0pnGdugg/H0sycDgxtE/1Gr+i7+q75H USrkTSzCwnar65cwunswxM3zFpQAjawMu7MZPdyzf8MMAwQToEHrrsdBPMaEk5YbYi4Z 3Y7w==
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=3lxzCsrNsCd1mi8g0JE7rOdAZZ60M8IwT12O3/RzuUg=; b=K1uF23zBI/wi7fgViD9BRreU8SsFMAaLd63PFMoIzkq/+jrTEYleQd/2xZNNb8KPA5 uFv8Uw6tL7j11HwySbwEONx7nYC0UnpFoMZnAo4vqkNTtaZMM5q1zhD+V9MzC6bQxa5J u+FaW+oCdH1VaY1DYNo8tF57EWGNde7LetWoHntgiDJqbgi1ggOSyYNcjrWZKRLQfoWh oglRq8OM+sQahfoo9F2+3cEUbZh7DZkce1C9F6Hb56fZA5bFNf32ivGdlFEZThzzVUPA ZMvHLWU6LysLZM9X+xkLfYSDgHn7BR/1AgMYbMdARN28TdmaccaZ95CKQUQTcviQdZXg 3JNw==
X-Gm-Message-State: APt69E0pjMLlL/7tdyUPunSKpDNzkRjABkKDe8fSnjkHuc3HK5gg4b00 fkH73fphmg9/ffB2d00WanFtzI9PYChUP4dZtKyCkQ==
X-Google-Smtp-Source: ADUXVKJwZ37N+Sjr42+1ntVsLxtxEdIpCre90GTz5RscsW9+F3PNWU5E8puqJa6A2hbcoau++2bph9i7FMIF9sZyqI4=
X-Received: by 2002:a24:2246:: with SMTP id o67-v6mr2961679ito.25.1528860043809; Tue, 12 Jun 2018 20:20:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAOJ7v-2FQ3yfyfmFY8MT17nTFUvsNyixKuXXeT-Rq7zVQKBMnA@mail.gmail.com> <CA+9kkMACFhqucwx6pgQS7mqzJBcE09Q6HWFsUq5=BbstAQz+nw@mail.gmail.com> <14D68A0E-860B-4546-AA68-FD319A2FFAEE@nostrum.com> <CAOJ7v-3SHcmkDQtM8hyGcUg1N6uM1oU_0AOHtM=HERwRj9d4zg@mail.gmail.com> <CAOJ7v-3sJzOLiH_EQc6NQM3NProD+4m=rB23i9Pw=vbLTLm+vw@mail.gmail.com>
In-Reply-To: <CAOJ7v-3sJzOLiH_EQc6NQM3NProD+4m=rB23i9Pw=vbLTLm+vw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 12 Jun 2018 20:20:30 -0700
Message-ID: <CAOJ7v-16TDNvRdsd3gB5v3+2-qOt2D_EvQELKBL1BwB3fZuSZg@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, RTCWeb IETF <rtcweb@ietf.org>, yfablet@apple.com
Content-Type: multipart/alternative; boundary="000000000000d31b37056e7d77e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/luFo8Pjh33NmyUMfU9NKjAI1Nvs>
Subject: Re: [rtcweb] IP handling: Using mDNS names for host candidates
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 13 Jun 2018 03:20:51 -0000

PTAL at https://github.com/juberti/draughts/pull/103.

It would be great to have some time to discuss this in Montreal.

On Tue, Jun 12, 2018 at 4:36 PM Justin Uberti <juberti@google.com> wrote:

> Given the general support here, I'll start writing up a PR to incorporate
> the aforementioned changes, with the goal to avoid emitting private IPv4
> addresses in the default mode.
>
> On Tue, Jun 12, 2018 at 12:14 PM Justin Uberti <juberti@google.com> wrote:
>
>> One option could be that Mode 2 incorporates RFC 4941 stateless IPv6
>> addresses, if supported. Otherwise, mDNS is used. This mode would never
>> include RFC 1918 IPv4 addresses.
>>
>> This would work well in more environments and still provide significant
>> privacy improvements.
>>
>> On Tue, Jun 12, 2018 at 12:08 PM Adam Roach <adam@nostrum.com> wrote:
>>
>>> I’d like to point out that, while this works fine in most residential
>>> settings, it’s pretty broken for multi-segment enterprise deployments.
>>>
>>> /a
>>>
>>> On Jun 12, 2018, at 11:55, Ted Hardie <ted.ietf@gmail.com> wrote:
>>>
>>> On Tue, Jun 12, 2018 at 2:40 AM, Justin Uberti <
>>> juberti=40google.com@dmarc.ietf.org> wrote:
>>>
>>>>
>>>> This is a significant improvement and I think we will want to
>>>> incorporate this suggestion. Is this something we could do as part of this
>>>> WGLC, or should we look for another option?
>>>>
>>>>
>>> Without having cleared this with Cullen or Sean, my personal chair-hat
>>> opinion is that we can do this in WGLC.  If a new technical solution is
>>> found during WG last call, I see no reason not to incorporate it.
>>>
>>> That said, I see two no-hats issues that will want pretty strong text.
>>> The first is that these are really UUIDs, not traditional mDNS names.
>>> We'll need text to strongly discourage the re-use of an existing mDNS name,
>>> since those can leak other information.  Second, we'll need text on what to
>>> do if this name can't be registered or resolved in a particular environment
>>> (not every network supports mDNS, after all).  Does it go back to the
>>> previous Mode 2 behavior, or skip private addresses entirely?  I think the
>>> right idea is "go back to the previous Mode 2 behavior" personally, but
>>> text on it one way or the other is required.
>>>
>>> regards,
>>>
>>> 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
>>>
>>>