IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 28 July 2018 10:10 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 B1EA9130E21 for <rtcweb@ietfa.amsl.com>; Sat, 28 Jul 2018 03:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 QU5b8v-JH6hK for <rtcweb@ietfa.amsl.com>; Sat, 28 Jul 2018 03:10:09 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 1B555130E14 for <rtcweb@ietf.org>; Sat, 28 Jul 2018 03:10:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1532772606; 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=FO2wOuxtFEjpFr2j65EokU9sGelUHF2w3J5VYDBgDwE=; b=am9q9pp1pB75LlqX2yULJXUr3w8+4wEIcxc44AZ62FoqJho5AB52mWEBSH/kWlEC aGap5LmJqqVsBq4wkT1KBtRCR3DwIIsyP/xO6Z5OOyuGNUdcxXVm4AajJPC85w1Y M+jNvtWripM7KMJE4DwRbuJCcEcJA9xcXZP3aj5G6l4=;
X-AuditID: c1b4fb25-b05ff70000006cb9-98-5b5c40fe7d8f
Received: from ESESBMB501.ericsson.se (Unknown_Domain [153.88.183.114]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id CC.7C.27833.EF04C5B5; Sat, 28 Jul 2018 12:10:06 +0200 (CEST)
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESBMB501.ericsson.se (153.88.183.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Sat, 28 Jul 2018 12:10:05 +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; Sat, 28 Jul 2018 12:10:05 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Sean Turner <sean@sn3rd.com>, RTCWeb IETF <rtcweb@ietf.org>
Thread-Topic: [rtcweb] WG adoption call: draft-mdns-ice-candidates
Thread-Index: AQHUJgvztDAqqnNgKU61Ukau0VYD2qSkZb7g
Date: Sat, 28 Jul 2018 10:10:05 +0000
Message-ID: <11b6f595e3104b8fa70de30a82e09571@ericsson.com>
References: <CF938109-02C6-4950-A485-A41D07928B41@sn3rd.com>
In-Reply-To: <CF938109-02C6-4950-A485-A41D07928B41@sn3rd.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+NgFvrOLMWRmVeSWpSXmKPExsUyM2J7ke4/h5hog/OXxCzW/mtnt7iyqpHZ gcljyZKfTB4HDzIGMEVx2aSk5mSWpRbp2yVwZTy5MYG94Id4xav9/1kaGFeIdzFycEgImEgc OM/RxcjFISRwlFHiSutOli5GTiDnG6PEw3YmiMQyRomGfctZQRrYBCwkuv9pg9SICNhL3Nzd wgpiCws4Skx4uJcFIu4kce7+TSjbSOLcil5GEJtFQFXix7R/YDavgLXE0yebmSB22UhMPz6b DWQ8p4CtxNHdnCBhRgExie+n1oCVMAuIS9x6Mh/MlhAQkFiy5zwzhC0q8fLxP1YIW0li77Hr LCBjmAU0Jdbv0odoVZSY0v2QHWKroMTJmU9YJjCKzkIydRZCxywkHbOQdCxgZFnFKFqcWpyU m25krJdalJlcXJyfp5eXWrKJERgdB7f8Vt3BePmN4yFGAQ5GJR5eU2DUCLEmlhVX5h5ilOBg VhLh1fofHS3Em5JYWZValB9fVJqTWnyIUZqDRUmc96H55ighgfTEktTs1NSC1CKYLBMHp1QD o7xUdbKKaar8LO9An12FH5jmNmQWCiw/9OHoD/+HV1oLFjJYcRgZv965/uHDkvMuf2ddnvvn lHNWS4j/jTsP189wLPS5WfFgFu/mgr7GMz+1kgyt+Tge3Al6Wvl0H/cDx1N64ZsL7IWmOq04 b/kha66nYOb33uQ9/Yv6T/3qFdzE/evzjxN/8pVYijMSDbWYi4oTARIgY/OKAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/dIzePElM87OZrvU60nsYg7BF5GI>
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: Sat, 28 Jul 2018 10:10:13 -0000

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

v2.23.0 | Report a Bug | By Email