[Anima-bootstrap] some info about multicast DNS

Sheng Jiang <jiangsheng@huawei.com> Thu, 12 May 2016 01:38 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1550412D0A5 for <anima-bootstrap@ietfa.amsl.com>; Wed, 11 May 2016 18:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.216
X-Spam-Status: No, score=-5.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 K__783cJFK7R for <anima-bootstrap@ietfa.amsl.com>; Wed, 11 May 2016 18:38:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3382B12D1A5 for <anima-bootstrap@ietf.org>; Wed, 11 May 2016 18:38:26 -0700 (PDT)
Received: from (EHLO lhreml705-cah.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id COM42773; Thu, 12 May 2016 01:38:18 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com ( by lhreml705-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Thu, 12 May 2016 02:38:16 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([]) with mapi id 14.03.0235.001; Thu, 12 May 2016 09:38:12 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
Thread-Topic: some info about multicast DNS
Thread-Index: AdGr7t4zxuzWit0FRQGs8w+DFLA56A==
Date: Thu, 12 May 2016 01:38:11 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927C6637C7@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B927C6637C7NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.5733DE8A.005F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ea604523585bbce1f15ec231a18349ea
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/YKEM_yQsQm_RhrrzXTXu_KTJ70A>
Cc: peter van der Stok <stokcons@xs4all.nl>
Subject: [Anima-bootstrap] some info about multicast DNS
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 01:38:29 -0000

Resend this email on behalf of Peter van der Stok. This email was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it.

Peter, if it is your intension to participant ANIMA bootstrap mail list discussion, please subscribe.


Dear all,

I have looked at RFC6762 and selected some phrases that may help in the


The text below addresses most of the questions raised yesterday.

The most basic kind of Multicast DNS client may simply send standard

DNS queries blindly to, without necessarily even

being aware of what a multicast address is.

IANA has allocated the IPv6 multicast address set FF0X::FB (where "X"

indicates any hexadecimal digit from ’1’ to ’F’) for the use

described in this document [MC6]. Only address FF02::FB (link-local

scope) is currently in use by deployed software, but it is possible

that in the future implementers may experiment with Multicast DNS

using larger-scoped addresses, such as FF05::FB (site-local scope)


Sending Multicast DNS responses via multicast has the benefit that

all the other hosts on the network get to see those responses,

enabling them to keep their caches up to date and detect conflicting


However, there are situations where all the other hosts on the

network don’t need to see every response.

To avoid large floods of potentially unnecessary responses in these

cases, Multicast DNS defines the top bit in the class field of a DNS

question as the unicast-response bit. When this bit is set in a

question, it indicates that the querier is willing to accept unicast

replies in response to this specific query, as well as the usual

multicast responses.

There is much additional text about responders, and how they announce





Peter van der Stok

vanderstok consultancy

mailto: consultancy@vanderstok.org<mailto:consultancy@vanderstok.org>

www: www.vanderstok.org<http://www.vanderstok.org>

tel NL: +31(0)492474673     F: +33(0)966015248