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

Ted Hardie <ted.ietf@gmail.com> Tue, 17 July 2018 22:11 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 7D74C13104D for <rtcweb@ietfa.amsl.com>; Tue, 17 Jul 2018 15:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] autolearn=ham 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 kzWly-4soTcJ for <rtcweb@ietfa.amsl.com>; Tue, 17 Jul 2018 15:11:04 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 EA907131031 for <rtcweb@ietf.org>; Tue, 17 Jul 2018 15:11:03 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id k81-v6so5005179oib.4 for <rtcweb@ietf.org>; Tue, 17 Jul 2018 15:11:03 -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=gI4wEbzVxquz1JmiYulgSV2uqzefLjsdZfGpeoXfXxA=; b=RJN6FmBwLbeZdOdscVCaFYhuWFSH8NPYI8yXXaEUgjSSj5tuq+YCuayLuQfKUMN1ma k6eRBxb1W8udAm9C5I5c8eOp+3IP9mQsR+1uhgf5qZyibvmyeM3a8wU44H8VfTWQKdsp u8ay/+FE4qD/D/ELnjgUXp84P0vIxrLAXtSYUlghrUy9jVVB4XaPNdKyfQ7fX7yuBkva CS/IZsJpDEtG4PQItSDPRmebkA5kxBpV49qs92GzQ0KRmPOxwg96n8sB+PDNLIvGeyhF VQ7pFKeDumD2glhr1ya0U4fT07FiOUEf6R66lx99YZN4BwvQJ+hL8RH0o5DmugzNco7d hX+Q==
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=gI4wEbzVxquz1JmiYulgSV2uqzefLjsdZfGpeoXfXxA=; b=kAETmHKb02mPtlAP3Yh+zqgQNUfHNtZGkBWL/6oXuRgDVwpJH4G0G8GUssIORixMtW b3a3qmjYRI/7XLfKosBHGEnSAr2MIjdzRc7YMPq1n/Pvm8amvbYqLHpJ+pUw/GmZ4qXQ z3BI7CHdLv+VOgddTFM/tupnidoJTA/Dgrf6wpdYlD3Vn2uugWjjp0U+he8+5fRfd+8b KLFOp20SM7rxvZkIAzT0d4MMKQjQhuIi8y3KDCoUKCyDWZpK6PH5be62iMWWtLjEdVTS yNLxpfKbozREyX/PnX4VjnekA92hE21OOKOuRulA/MkfIsh099DgCMDslR84rWHYv2+t JdUQ==
X-Gm-Message-State: AOUpUlGrsy4vwPrLtwpvFN4O62slyhTF6SD6KcB3+q48YOiZUcWo1Uhs Y9PSN7Zjz6oXenzWYW15iU17LxLSErSbU78tFqA=
X-Google-Smtp-Source: AAOMgpc9tHtOYRVM6GyQf5I8pVNT53c7ehPl6lHgQqk5kokf3NrDgA24iEApL39D3qJMfxnhoP+mFKVKkjtAevNVtwU=
X-Received: by 2002:aca:4782:: with SMTP id u124-v6mr3855122oia.45.1531865463081; Tue, 17 Jul 2018 15:11:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 15:10:32 -0700 (PDT)
In-Reply-To: <CAJrXDUFzOBL1+8M4JiSaDakJc5VU2SudSD1TbmYGDofysO_K4A@mail.gmail.com>
References: <CAOJ7v-2FQ3yfyfmFY8MT17nTFUvsNyixKuXXeT-Rq7zVQKBMnA@mail.gmail.com> <092e15c3-3ae8-5b18-1195-498f9cef1488@alvestrand.no> <CAOJ7v-3e8ytXd5NQLYdPyVdiSYDy4kGxQvbEh=_D9Mm0eSLmVg@mail.gmail.com> <CAPcE_Lf5kVoMzid1+Vc=mhGuH9v7nqoSq=TYJE8W9FMfcggKJA@mail.gmail.com> <CABcZeBOSyuOP6E4dreJc_OoxMTqZg-N5J9Gkbp7ygrXQbFd-XQ@mail.gmail.com> <CAOJ7v-3vZH81m9DK9CNmEH3UKTBZT+0f1=uuQdz7ou2JXxeMsA@mail.gmail.com> <CANN+akbH54-05VceqL-rfq+ZURB85LxXFb4_B5KV_6KaLaC=+g@mail.gmail.com> <CAJrXDUFzOBL1+8M4JiSaDakJc5VU2SudSD1TbmYGDofysO_K4A@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 17 Jul 2018 18:10:32 -0400
Message-ID: <CA+9kkMA41=kWQJLj8x=3D8OpbouqfvMUkVgPb=+cboXco3Sxrg@mail.gmail.com>
To: Peter Thatcher <pthatcher=40google.com@dmarc.ietf.org>
Cc: youenn fablet <youennf@gmail.com>, RTCWeb IETF <rtcweb@ietf.org>, Justin Uberti <juberti=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c5514a0571393843"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/vF2-GNYVOavO3L8yiRIy5IRkBvw>
Subject: Re: [rtcweb] IP handling: Using mDNS names for host candidates
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.27
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, 17 Jul 2018 22:11:19 -0000

On Tue, Jul 17, 2018 at 4:46 PM, Peter Thatcher <
pthatcher=40google.com@dmarc.ietf.org> wrote:

> Where is the right place to comment on draft-mdns-ice-candidates?
>


> I looked at it from an ICE WG perspective, and it seems to be that since
> (in RFC 5245), the candidate address can be a FQDN (section 15.1) you don't
> need the special steps you have in section 3.2, because a .local address is
> a FQDN (isn't it?).
>

The use of a .local signals that this is a special use name within the
context of multicast DNS (RFC 6762).  One key difference there is that the
uniqueness of a standard DNS name is derived from the hierarchical
delegation of the DNS.  Uniqueness in MDNS is achieved using a local probe
and announce method.  As Harald pointed out in the room, there are some
latency consequences to that; those might be avoided by generating probable
uniqueness in names via the UUID mechanism, but that still need to be
worked out.  That, I think means the work in 3.1 is definitely needed.


> I think the only novel thing would be to perhaps make it clear that mDNS
> should be used for the name resolution.
>
>
You might treat the special steps as redundant (since .local should signal
mDNS), but I personally think it is helpful, because it discourages
coalescing with standard DNS responses (which is permitted by 6762).

Just my personal opinion.

Ted





> On Fri, Jun 29, 2018 at 6:07 PM youenn fablet <youennf@gmail.com> wrote:
>
>> A draft describing the Safari/WebKit approach is available at
>> https://www.ietf.org/id/draft-mdns-ice-candidates-00.txt
>>
>> Eric, can you precise the kind of information you would like to have?
>> Some testing has been done to validate the approach but I do not think
>> this is representative of the actual state of the affair. Safari/WebKit is
>> not gathering any related statistic..
>>
>>    Y
>>
>> Le ven. 29 juin 2018 à 11:10, Justin Uberti <juberti=40google.com@dmarc.
>> ietf.org> a écrit :
>>
>>> I believe such data will be forthcoming from the Safari team. We are
>>> also working on this.
>>>
>>> On Fri, Jun 29, 2018 at 7:03 AM Eric Rescorla <ekr@rtfm..com
>>> <ekr@rtfm.com>> wrote:
>>>
>>>> It seems like this is something one could A/B test and measure
>>>> connection rates. Has someone done so?
>>>>
>>>> -Ekr
>>>>
>>> _______________________________________________
>> 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
>
>