Re: [dnssd] When does MDNS/DNS-SD use IPv6?

Hagen Paul Pfeifer <hagen@jauu.net> Thu, 19 January 2017 08:16 UTC

Return-Path: <hagen@jauu.net>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 216BC12940F for <dnssd@ietfa.amsl.com>; Thu, 19 Jan 2017 00:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level:
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no autolearn_force=no
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 RJ30AyZB1cRV for <dnssd@ietfa.amsl.com>; Thu, 19 Jan 2017 00:16:47 -0800 (PST)
Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (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 7A43E128B37 for <dnssd@ietf.org>; Thu, 19 Jan 2017 00:16:47 -0800 (PST)
Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 3FE6944E30; Thu, 19 Jan 2017 09:16:45 +0100 (CET)
X-Virus-Scanned: amavisd-new at heinlein-support.de
Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id JHhIJlJY6CmO; Thu, 19 Jan 2017 09:16:37 +0100 (CET)
Date: Thu, 19 Jan 2017 09:16:35 +0100
Message-ID: <4bbb6dce-3f89-40a6-9028-15d723391da0@email.android.com>
X-Android-Message-ID: <4bbb6dce-3f89-40a6-9028-15d723391da0@email.android.com>
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Christian Huitema <huitema@huitema.net>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/OK8DdpU8PhXfSSSopH7VY5euqOE>
Cc: "cheshire@apple com" <cheshire@apple.com>, dnssd@ietf.org
Subject: Re: [dnssd] When does MDNS/DNS-SD use IPv6?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2017 08:16:49 -0000



Am 19.01.2017 02:13 schrieb Christian Huitema <huitema@huitema.net>et>:


> The Apple open source mDNSResponder implementation sends both queries in parallel.

OK. But if we all nodes do that and if all nodes publish their records on both IPv4 and IPv6, there is going to be a fair amount of duplicate traffic. More on potential fixes later in this message.


Fair amount of what? DNS, OK, but considering all traffic it is probably neglicable. As always: it is a compromise between implementation complexity, already deployed software, new extensions, new bugs and other factors. And hoping that in a not so far future IPv6 only networks exists.

Hagen