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

Ted Hardie <ted.ietf@gmail.com> Tue, 12 June 2018 18:56 UTC

Return-Path: <ted.ietf@gmail.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 EB3B1130FAB for <rtcweb@ietfa.amsl.com>; Tue, 12 Jun 2018 11:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 eLIFc47clmn4 for <rtcweb@ietfa.amsl.com>; Tue, 12 Jun 2018 11:56:31 -0700 (PDT)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (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 F0A68130E5A for <rtcweb@ietf.org>; Tue, 12 Jun 2018 11:56:30 -0700 (PDT)
Received: by mail-ot0-x232.google.com with SMTP id i19-v6so9783otk.10 for <rtcweb@ietf.org>; Tue, 12 Jun 2018 11:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+xgtZVjn0BP1L5cVfyOSW9irb1kSU5xaaModoLloHMo=; b=TiLBOKMzYovTl/Opl2UM9JfOkqB+u7nT0b5mHQofHqyUEmWc44IGExRHpSS2Byy3gG VsLviWYKM7AWurbIZgG7Jeq9dj6AnK8DYyHPuq2I5WXtBqVh5hbq5QwZpu3C4dsIJgA0 cT4D7t+lnl2a89FuaBLHenzdzNSmhTTPAqAl8vAZN93d7ojA2E3yMSp+w8/PqXBEYN2G 1tI40LEj4PuY8vv3EwCguGC+qB8COmh/atwvcdUW6vAPM6n/qDE/B3FXWyHbP/J4xSLk ibtYUA6sxvS1MBCYSvVbt0Ai190Zasa2V44BQ6PORGohs0hu4xPUhp1ytPUxYRcEQhb+ /9jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+xgtZVjn0BP1L5cVfyOSW9irb1kSU5xaaModoLloHMo=; b=erpL4Vn4ej1WhHMLDMJUTH++CSWUdN9ZTACxcNYHLCUXLdcqLZ8+d7NHqpQF9yh+Qr LRFN7TmLoYJJ7kKDQ/n1VNc9qJtPCflpsQ9B/KYCc4+11ceH1Ic+6zf8cxzSAiKYJ9G/ OtWp4b7M3MTL4mAPSGIaFJMSxeZjY1GRM/B3RtkjzR+0MGw3D+AZnifuDqEbG20fMRZK RcjQsA0wRza7BZYd/Y3u4erD3LMJpBwfHzYO+9XeLNHVcog9ztoz+kwH1NdDr36E9Bui k1GOisxJAxrVv8i/7Yc7K2JfbhQy+phG5KQy/Ld3zzYOaIfstIFZjU/NMCbDYefLLQVt L49Q==
X-Gm-Message-State: APt69E0wsVg4Jr2weMO2GL38DQigKh9m7lYe1Rd1+oUyBh8tjdLce/+3 ddth8PkAd3tpvaHL4Loj4iGh51I6PJ7U7B1qp4E=
X-Google-Smtp-Source: ADUXVKKUICuH4SYfn2nekETfhPFn0+Xtt0PE7NX+RdiaCrEEsCXucr64T0BzbVXMT+8sOXZXmNUh2LW3U0PsBMf3Qe0=
X-Received: by 2002:a9d:282e:: with SMTP id m43-v6mr1139261otb.393.1528829790178; Tue, 12 Jun 2018 11:56:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66c3:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 11:55:59 -0700 (PDT)
In-Reply-To: <CAOJ7v-2FQ3yfyfmFY8MT17nTFUvsNyixKuXXeT-Rq7zVQKBMnA@mail.gmail.com>
References: <CAOJ7v-2FQ3yfyfmFY8MT17nTFUvsNyixKuXXeT-Rq7zVQKBMnA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 12 Jun 2018 20:55:59 +0200
Message-ID: <CA+9kkMACFhqucwx6pgQS7mqzJBcE09Q6HWFsUq5=BbstAQz+nw@mail.gmail.com>
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
Cc: RTCWeb IETF <rtcweb@ietf.org>, yfablet@apple.com, Sean Turner <sean@sn3rd.com>
Content-Type: multipart/alternative; boundary="00000000000090d1ce056e766cc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/x5RVKlsri-qtTOye-6PDuoJ8P68>
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: Tue, 12 Jun 2018 18:56:36 -0000

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