Re: [rtcweb] WG adoption call: draft-mdns-ice-candidates

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 01 August 2018 07:52 UTC

Return-Path: <christer.holmberg@ericsson.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 0EB34130FCF for <rtcweb@ietfa.amsl.com>; Wed, 1 Aug 2018 00:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 BOYHepfwdg00 for <rtcweb@ietfa.amsl.com>; Wed, 1 Aug 2018 00:52:14 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B424C130DCC for <rtcweb@ietf.org>; Wed, 1 Aug 2018 00:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1533109931; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=EdiFgzBSJMnMuaIz5lRohymUzsRz1t9nT9NT/PIaX/Y=; b=eWFPIW+S5NDXHro5SU77KIqscYo6zsLTRI/Tn9BjrqX0Q01vDO8jH+/93u7tbfjs jgJe7NlM21nnPEbzzPaqYYrPjagXz23/gJbacR9Cupp4goQriowqhlB7F2Jdc1XH 0rCEE8ZxbIFmkzm+hh+iFWNE95pGH2yfDo70+wpUVpM=;
X-AuditID: c1b4fb3a-a01ff700000079c1-3c-5b6166ab0d56
Received: from ESESBMB505.ericsson.se (Unknown_Domain [153.88.183.118]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 10.2E.31169.BA6616B5; Wed, 1 Aug 2018 09:52:11 +0200 (CEST)
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESBMB505.ericsson.se (153.88.183.172) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 1 Aug 2018 09:52:11 +0200
Received: from ESESBMB503.ericsson.se ([153.88.183.186]) by ESESBMB503.ericsson.se ([153.88.183.186]) with mapi id 15.01.1466.003; Wed, 1 Aug 2018 09:52:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>
CC: Sean Turner <sean@sn3rd.com>, RTCWeb IETF <rtcweb@ietf.org>
Thread-Topic: [rtcweb] WG adoption call: draft-mdns-ice-candidates
Thread-Index: AQHUJgvztDAqqnNgKU61Ukau0VYD2qSkZb7ggAWCyoCAAKPd4A==
Date: Wed, 01 Aug 2018 07:52:11 +0000
Message-ID: <bd36f987512a441f87d3662b316e1512@ericsson.com>
References: <CF938109-02C6-4950-A485-A41D07928B41@sn3rd.com> <11b6f595e3104b8fa70de30a82e09571@ericsson.com> <CAOJ7v-2gp=Eu-q=twCWeueYtW7Vr61r8-=L5O7j4Vn8fkBZcLQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-2gp=Eu-q=twCWeueYtW7Vr61r8-=L5O7j4Vn8fkBZcLQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.153]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZGbG9THd1WmK0wfGrVhZbpwpZrP3Xzm5x ZVUjswOzx4JNpR5Llvxk8jh4kDGAOYrLJiU1J7MstUjfLoErY9WqCUwFv+QqXk6awtLAOEWu i5GDQ0LAROL+9OAuRi4OIYGjjBLTNsxnh3C+MkrcX/CVEcJZyiix88AiRpAONgELie5/2l2M nBwiAmoSD2ftYgWxmQXsJR48+sUIYgsLOEpMeLiXBaLGSeLc/Ztw9sedR9lAbBYBFYnnL78w gdi8AtYSn1ecYIbYtZVRYuu1RWBFnAKBEttu/gErYhQQk/h+ag0TxDJxiVtP5oPZEgICEkv2 nGeGsEUlXj7+xwphK0nsPXadBeRmZgFNifW79CFaFSWmdD9kh9grKHFy5hOWCYxis5BMnYXQ MQtJxywkHQsYWVYxihanFhfnphsZ6aUWZSYXF+fn6eWllmxiBMbSwS2/rXYwHnzueIhRgINR iYfXMCAxWog1say4MvcQowQHs5IIr41MfLQQb0piZVVqUX58UWlOavEhRmkOFiVxXqc0iygh gfTEktTs1NSC1CKYLBMHp1QDo1KI5MF9/JsOTfuV1CU/K6WgzqPjo1GU/Ie2L/0n3G7anK6f afeD5xfnyt8XWnfY+nh4pjB8YtuUrCwYPmuZjNXxjcUnnsw1+SS4Ytsyvpa53Zph/QIurr4a Be3Va+svLeUUqghrUVIsFt47e2ZgXGKXROFhrp4TGYI/rr36WHBk42KhhB+KSizFGYmGWsxF xYkAvQVDY6ECAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/bGnoSCOWXCrV86SMKGbAd9QcEbk>
Subject: Re: [rtcweb] WG adoption call: draft-mdns-ice-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: Wed, 01 Aug 2018 07:52:16 -0000

Hi,

> Regarding DNS resolution and associated complexity, I think we can sidestep most of that here in rtcweb given
> that we will be mandating 1:1 mapping between foo.local names and IP addresses.

If that’s the case, it should be explicitly indicated.

Others (Cullen etc) also raised issues in MMUSIC, but I'll let them speak for themselves whether they think it affects the RTCWEB usage.

Regards,

Christer


On Sat, Jul 28, 2018 at 3:10 AM Christer Holmberg <christer.holmberg@ericsson.com> wrote:
Hi,

In Montreal this was discussed in MMUSIC, and the outcome was that this will require more work, in MMUSIC or ICE.

I have also given some input why I think ICE support of FQDNs in general (not specific to mDNS) requires more work.

For example, as an FQDN can be associated with multiple IP addresses, does that mean that the endpoint providing the FQDN will create separate "sub candidates" for each IP address that the FQND can resolve to (as a candidate per definition is associated with ONE transport (IP address + port + protocol))?. If so, each of those local candidates may end up in different foundations, some may be pruned (or removed because of other reasons). In addition, is the endpoint supposed to send checks on each of these candidates? For how long will it maintain them? Etc etc etc.

The concept of "multi-address candidates" is a new thing, currently not covered by the ICE specifications.

Now, IF we assume a "FQDN candidate" will only resolve to one IP address, the issue is easier to solve, but based on comments from others we cannot make that assumption.

So, while I do not object to working on support of mDNS in ICE, my suggestion would be that the ADs, and the RTCWEB/MMUSIC/ICE chairs, discuss on how to move forward, before we adopt this draft.

Regards,

Christer


-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Sean Turner
Sent: 28 July 2018 03:43
To: RTCWeb IETF <rtcweb@ietf.org>
Subject: [rtcweb] WG adoption call: draft-mdns-ice-candidates

The consensus in the RFCWEB@IETF102 room was that the WG should adopt  https://datatracker.ietf.org/doc/draft-mdns-ice-candidates/ as a WG item. But, we need to confirm this on list.  If you would like for this draft to become a WG document and you are willing to review it as it moves through the process, then please let the list know by 2359UTC 20180810.  If you are opposed to this being a WG document, please say so (and say why).

Note that the draft has been marked as a “Call for Adoption by WG Issued” in the datatracker.

Thanks - spt
_______________________________________________
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