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

Bernard Aboba <bernard.aboba@gmail.com> Tue, 17 July 2018 20:58 UTC

Return-Path: <bernard.aboba@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 7F7E8130DD2 for <rtcweb@ietfa.amsl.com>; Tue, 17 Jul 2018 13:58:49 -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 EtgvFjnRyrgL for <rtcweb@ietfa.amsl.com>; Tue, 17 Jul 2018 13:58:47 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 21638129C6B for <rtcweb@ietf.org>; Tue, 17 Jul 2018 13:58:47 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id y9-v6so1350192vky.3 for <rtcweb@ietf.org>; Tue, 17 Jul 2018 13:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+szVTIgTNSqLyDDYGIkhNiUypa1EsQYfu+8h0KIpz5U=; b=IW/wllrE61PbxD2JnuGMP5b1KCRGZ3oqCQBO8zpMEnocnlbPjKqBlCLDdczApRxdvi 1brF0Q0y0Tt+Oxx8q/MLoWfFHtdd6KEO2uh+eF2yOiP39BA+0p0Y00MVO050uuhBXC6N msQhHhD1nZxzHdUC437Gg7isE+UCjAxk+t1jWJkZdZiu4QlwsaDxHDZMsZNPraWNRCBP yCWU0mGE99bHvOXuk1rCytRy3QPtAZSa6Ym287IaFf0QRf1YXpaTbr/278N+d7q5IHpm 0DOoJ8cw/TAiXMn+y8afdYnVLkfFTo090hOHqUulrgJijj7AWl88D6C6qki9XoqFtujr Ay4Q==
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=+szVTIgTNSqLyDDYGIkhNiUypa1EsQYfu+8h0KIpz5U=; b=DjTBG1DRMG+8FgdrvPHMdd6EVtcyfijESnF2SdyDkil0kIYddujtS1r32KotGqaGUQ jlGhmMs1EBvUz/Zu8qx66uasqyd86wPgGm3Qz/TSqgeFh/fWmSAYuT6eabQfglqy0ja2 qrs8s9M5xz5/C2Vq9F4uKrulhujQAO7V56zBNMy1VyYQDRzC/OXFn7g0wGztPd+/lWpl NRKqgY5hf90FgsLD2bLgI4BCf/FE2hPXFeP/C3PVUterrGz7NqOFgzj7/+atMPF5OAlZ bcZPGzS0IwRFZ5iFLKhiREoY00B6cbb/cMiInfgdjmd+iTcR7MxJTwxaQj0jwQzhreKX mb/Q==
X-Gm-Message-State: AOUpUlHhK2wqxmqjZo//onwfZSanlN++8AaSBjowZoYkHAZvjT7WXEJG i1rbCGQKNr+8hJVmupK9zWCLXou/qCnsnmmuoOk=
X-Google-Smtp-Source: AAOMgpe2RYw8yu9P8Q6EN4Arn243NyhwTGqm2uWKjwZWU2cw3hDr6YBeAprkWLuBFLz54tdh6rx7jXC+gAIbgW/AW/I=
X-Received: by 2002:a1f:dc85:: with SMTP id t127-v6mr1974254vkg.120.1531861125947; Tue, 17 Jul 2018 13:58:45 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <CAJrXDUFzOBL1+8M4JiSaDakJc5VU2SudSD1TbmYGDofysO_K4A@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 17 Jul 2018 16:58:35 -0400
Message-ID: <CAOW+2dukCCyKKwYyvwKuemg-w4VnJr2HTJhX7e=Uq_omf1uawg@mail.gmail.com>
To: Peter Thatcher <pthatcher=40google.com@dmarc.ietf.org>
Cc: Justin Uberti <juberti=40google.com@dmarc.ietf.org>, RTCWeb IETF <rtcweb@ietf.org>, youenn fablet <youennf@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000041e4870571383654"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/DKqW8Dfm1Bb_8VOurLYBtqBqqvw>
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 20:58:50 -0000

Tue, Jul 17, 2018 at 16:46 Peter said:

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?).  I think the only novel thing would be to perhaps make
> it clear that mDNS should be used for the name resolution.
>

[BA] Using mDNS for resolution does introduce potential failure modes. For
example, in a multi-subnet enterprise network using private addresses,
10.1.1.1/24 and 10.2.1.1/24 could connect via a router whereas mDNS
resolution will fail in the absence of proxies. Whether this matters in
practice depends on the topologies where data channel applications are
deployed.

>