Re: Proposed optimization to multicast DNS

Matt Crawford <crawdad@fnal.gov> Tue, 17 July 2001 15:15 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27642 for <dnsext-archive@lists.ietf.org>; Tue, 17 Jul 2001 11:15:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15MW9q-000Jvg-00 for namedroppers-data@psg.com; Tue, 17 Jul 2001 07:49:06 -0700
Received: from h-135-207-10-122.research.att.com ([135.207.10.122] helo=roam.psg.com) by psg.com with esmtp (Exim 3.31 #1) id 15MW9p-000JvZ-00 for namedroppers@ops.ietf.org; Tue, 17 Jul 2001 07:49:06 -0700
Received: from randy by roam.psg.com with local (Exim 3.30 #1) id 15MW9p-0000Et-00 for namedroppers@ops.ietf.org; Tue, 17 Jul 2001 10:49:05 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Matt Crawford <crawdad@fnal.gov>
To: Brian Zill <bzill@microsoft.com>
Cc: namedroppers@ops.ietf.org, Jun-ichiro itojun Hagino <itojun@iijlab.net>, David Terrell <dbt@meat.net>
Subject: Re: Proposed optimization to multicast DNS
In-reply-to: "17 Jul 2001 00:15:46 PDT." <CB7153628BD3724096258CBFD70AA891015CE012@red-msg-04.redmond.corp.microsoft.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15MW9q-000Jvg-00@psg.com>
Date: Tue, 17 Jul 2001 07:49:06 -0700
Content-Transfer-Encoding: 7bit

    listen on).  Also, Matt's solution addresses the issue raised by David
    Terrell (answer: lowercase the alphabetic characters before hashing).

More precisely, convert to canonical form as defined by DNSSEC ...

    When the Subject is a domain name, either fully-qualified or
    single-component, and the Querier does not have a unicast address
    for the target node, the query MUST be sent to a link-scope
    multicast address formed in the following way.  The Subject Name is
    converted to canonical form, as defined by DNS Security [2535],
    which is uncompressed with all alphabetic characters in lower case.
    (If additional DNS label types for host names are defined, the rules
    for canonicalizing those labels will be found in the defining
    specification.)  Compute the MD5 hash [1321] of the first label of
    the Subject Name -- the portion beginning with the first one-octet
    length field and up to, but excluding, any subsequent length field.
    Append the first 32 bits of that 128-bit hash to the prefix
    FF02:0:0:0:0:2::/96.  The resulting multicast address will be termed
    the "NI Group Address" for the name.


to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.