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

"Christian Huitema" <huitema@huitema.net> Wed, 18 January 2017 03:59 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 66A86129671 for <dnssd@ietfa.amsl.com>; Tue, 17 Jan 2017 19:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Status: No, score=-1.858 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id s9uP3_rQTOYs for <dnssd@ietfa.amsl.com>; Tue, 17 Jan 2017 19:59:45 -0800 (PST)
Received: from mx36-42.antispamcloud.com (mx36-42.antispamcloud.com []) (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 370041294F9 for <dnssd@ietf.org>; Tue, 17 Jan 2017 19:59:44 -0800 (PST)
Received: from xsmtp03.mail2web.com ([]) by mx36.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1cThPT-00061i-8Y for dnssd@ietf.org; Wed, 18 Jan 2017 04:59:44 +0100
Received: from [] (helo=xmail12.myhosting.com) by xsmtp03.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1cThOm-0006m7-4G for dnssd@ietf.org; Tue, 17 Jan 2017 22:59:42 -0500
Received: (qmail 22191 invoked from network); 18 Jan 2017 03:58:59 -0000
Received: from unknown (HELO icebox) (Authenticated-user:_huitema@huitema.net@[]) (envelope-sender <huitema@huitema.net>) by xmail12.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dnssd@ietf.org>; 18 Jan 2017 03:58:59 -0000
From: "Christian Huitema" <huitema@huitema.net>
To: <dnssd@ietf.org>
Date: Tue, 17 Jan 2017 19:58:57 -0800
Message-ID: <028501d2713f$32d5b3b0$98811b10$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdJxPW9EQEdeAgt2S46ozS0cRy4kMA==
Content-Language: en-us
X-SpamExperts-Domain: xsmtpout.mail2web.com
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.23)
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49KxQtGn3AswOT8Z9YHdvpk1TugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXqWrWBvETTLeCVINQJM30KLRcOb18WfxGyg6Om6u4YYm3eOAcN6NWLzJHjh uAIwNiE5hjoyEb9Oq0NWpyO3vrfYnGR8JorokUtMqNDt1Oktij3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSB8y9Ga5iCmdJFIvDEJb+pKRQRCdMNhge1Unb77YyuZq51KTnsyYNItCsDNnRtPvl+RBdQ80wr wyng3wNtDYr6IWSdEOMftBjsWb6BDQzjSsEw7+KMtoemwN8keIAcPKMBBQ67muZNm3G2c8/Pjjqy k0k0bdVHmDm5y9NcoZdM30MpNkbYYJ8YZ7d5zi74j6F/pxvnk7PJGygctl3LC86in/6DwZpjxPTx I2S/vwoydU3rc+Iv2rc9L0aEB794CHU7QkUmTDfMv/tVj9RPDK26f1ZS3ljmeFVRIgA8pd5GE2NV TgVI3tePcP+0TP9kyYEYMbQXX+yrczlZbif8bnM9QAeYUOp7A73HI6oJg7w/VodqDS3jhFVyYvjB Ar8iUjNZzB9tfY+mOJVw0e2xMRa7D2P5RYOa/miinTReZ5OdasFBlor8ikxQTKPsYxS4ne8toeDw baJnZ2TaZhv/Bk6d8Ds+X00vOaBfD53MN4G7rdk=
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
X-Recommended-Action: accept
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/pYvRu-HMEdnpVeuzFpJ4oy2OsHI>
Subject: [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: Wed, 18 Jan 2017 03:59:46 -0000

I am writing a small implementation of MDNS and DNS-SD to test the privacy
and pairing drafts, and I am puzzled by the IPv4 vs. IPv6 issues. The MDNS
spec mentions that queries can be sent to "multicast address or
its IPv6 equivalent FF02::FB". That's nice, but it is wonderfully
underspecified. Or maybe I am just a bit slow these days, and I just need
help... Given a query for some record type in the ".local" namespace, should
the implementation:

1) Send queries to both and FF02::FB and merge the results?
2) Send queries only to
3) Send queries only to FF02::FB?
4) Send to and then try FF02::FB if no response come after a
5) Or vice versa?
6) Perform some guesswork as to whether the local network prefers IPv4 or
7) Do different things if the query is for an A record versus AAAA?

Also, is there a different recommendation for one-shot queries and
continuous queries? 

And did we decide on purpose to not document that in the RFC?

-- Christian Huitema