Re: [homenet] Mixing DNS in with routing information

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 29 October 2012 15:14 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392D721F8707 for <homenet@ietfa.amsl.com>; Mon, 29 Oct 2012 08:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.908
X-Spam-Level:
X-Spam-Status: No, score=-0.908 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvilprVPQTBO for <homenet@ietfa.amsl.com>; Mon, 29 Oct 2012 08:14:30 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C3F7321F8703 for <homenet@ietf.org>; Mon, 29 Oct 2012 08:14:30 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 13D248A031 for <homenet@ietf.org>; Mon, 29 Oct 2012 15:14:27 +0000 (UTC)
Date: Mon, 29 Oct 2012 11:14:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20121029151427.GC59713@mx1.yitter.info>
References: <55AC86D5-F9A1-43B6-9ECD-1EB7AB8C84C2@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <55AC86D5-F9A1-43B6-9ECD-1EB7AB8C84C2@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [homenet] Mixing DNS in with routing information
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2012 15:14:31 -0000

On Fri, Oct 26, 2012 at 02:12:01PM -0400, RJ Atkinson wrote:
> Earlier, Andrew Sullivan wrote:
> > ...DNSSEC cannot be used for validation with mDNS because 
> > the actual mDNS name is [some string].local., ...
> 
> mDNS can, and regularly is, also used to transport
> DNS information outside the ".local" pseudo-TLD.

Draft-cheshire-dnsext-multicastdns-15 notes that this is a contentious
issue.  (I also think it's a stupid idea, but I don't run the circus,
of course.)  But you're right: in that case, you probably can do
DNSSEC on it.  I'd be delighted to learn that there's a resolver out
there that knows how to do this.  Do you know of one?

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com