Re: Proposed optimization to multicast DNS
Jun-ichiro itojun Hagino <itojun@iijlab.net> Thu, 12 July 2001 13:21 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA18812 for <dnsext-archive@lists.ietf.org>; Thu, 12 Jul 2001 09:21:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15KfKp-0008Et-00 for namedroppers-data@psg.com; Thu, 12 Jul 2001 05:12:47 -0700
Received: from rip.psg.com ([147.28.0.39] ident=exim) by psg.com with esmtp (Exim 3.31 #1) id 15KfKo-0008En-00 for namedroppers@ops.ietf.org; Thu, 12 Jul 2001 05:12:46 -0700
Received: from randy by rip.psg.com with local (Exim 3.30 #1) id 15KfKo-0006Hc-00 for namedroppers@ops.ietf.org; Thu, 12 Jul 2001 05:12:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
To: Brian Zill <bzill@microsoft.com>
Cc: namedroppers@ops.ietf.org
Subject: Re: Proposed optimization to multicast DNS
In-reply-to: bzill's message of Wed, 11 Jul 2001 22:54:04 MST. <E15KZQK-0000DD-00@psg.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15KfKp-0008Et-00@psg.com>
Date: Thu, 12 Jul 2001 05:12:47 -0700
Content-Transfer-Encoding: 7bit
>I propose something similar for multicast DNS. All IPv6 responders >should listen to multicast queries on a "solicited name multicast >address" instead of a single well-known multicast address. They derive >their solicited name multicast address(es) by combining a 104-bit >well-known link-local multicast prefix with the 24-bit result of a hash >over the first portion of the name of the record(s) for which they are >authoritative. Senders wishing to issue a query for a given record >would first generate the solicited name multicast address corresponding >to the record they wish to lookup. Then they would send the query to >that address. Only those nodes listening to that particular multicast >address would receive the packet, thus reducing significantly the amount >of packet processing required by nodes participating in multicast DNS. I guess we'd better reuse NI group address defined in draft-ietf-ipngwg-icmp-name-lookups-07.txt, page 4. it is formatted as 96bit wellknown + 32bit hash, and will be like ff02::2:xxxx:yyyy (it is not officially assigned yet on IANA table). itojun to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body.
- Proposed optimization to multicast DNS Brian Zill
- Re: Proposed optimization to multicast DNS Jun-ichiro itojun Hagino
- Re: Proposed optimization to multicast DNS David Terrell