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

Hagen Paul Pfeifer <hagen@jauu.net> Fri, 20 January 2017 08:31 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 C4EF7129AAB for <dnssd@ietfa.amsl.com>; Fri, 20 Jan 2017 00:31:15 -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 IjbPdwvWZqoK for <dnssd@ietfa.amsl.com>; Fri, 20 Jan 2017 00:31:14 -0800 (PST)
Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) (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 7814F129AAA for <dnssd@ietf.org>; Fri, 20 Jan 2017 00:31:13 -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 mx2.mailbox.org (Postfix) with ESMTPS id 32B8044DC9; Fri, 20 Jan 2017 09:31:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at heinlein-support.de
Received: from smtp1.mailbox.org ([80.241.60.240]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by spamfilter03.heinlein-hosting.de (spamfilter03.heinlein-hosting.de [80.241.56.117]) (amavisd-new, port 10030) with ESMTPS id MUcofJ6we3sD; Fri, 20 Jan 2017 09:31:09 +0100 (CET)
Date: Fri, 20 Jan 2017 09:31:03 +0100
Message-ID: <bef007b1-5cf7-4deb-a828-e3bd6573fddc@email.android.com>
X-Android-Message-ID: <bef007b1-5cf7-4deb-a828-e3bd6573fddc@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/-_sobz4JjruMsgwq08QOZ1nM5Ps>
Cc: "cheshire@apple com" <cheshire@apple.com>, 'Erik Kline' <ek@google.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: Fri, 20 Jan 2017 08:31:16 -0000


20.01.2017 6:19 wrote  Christian Huitema <huitema@huitema.net>et>:


If we believe that modern platforms all do IPv6 & IPv4, then the optimization for the common case would be something like "try IPv6 first; collect results; after a short timer, repeat query on IPv4, filling the list of known answers with what was learned over IPv6; collect results; on subsequent timers, alternate repeat on IPv6 and IPv4, with the list of known answers collecting everything received so far through either v4 or v6." That would reduce overhead, while still allowing for some IPv6 only or IPv4 only hosts. 


Yes, this sounds reasonable. A good compromise between v4/v6 connectivity, overhead (incl power consumption) and software complexity.

Hagen