IETF Logo Mail Archive

Re: [mdnsext] mDNSext features/requirements rollup

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 29 January 2013 20:04 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2077521F88EA for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 12:04:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level:
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[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 Ri-lXubZkPVf for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 12:04:49 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id AC7C821F88B5 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 12:04:49 -0800 (PST)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B98E48A031 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 20:04:47 +0000 (UTC)
Date: Tue, 29 Jan 2013 15:04:49 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: mdnsext@ietf.org
Message-ID: <20130129200449.GP15365@mx1.yitter.info>
References: <mailman.97.1359403423.10833.mdnsext@ietf.org> <D99048ACAF96354EBFD6A811E3C65ACD10977A7C@CH1PRD0811MB407.namprd08.prod.outlook.com> <1359484752.31527.140661184088257.2DD91FC3@webmail.messagingengine.com> <51082424.9090404@networkcommons.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <51082424.9090404@networkcommons.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [mdnsext] mDNSext features/requirements rollup
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 20:04:50 -0000

On Tue, Jan 29, 2013 at 07:33:56PM +0000, vortex wrote:
> Alternate stacks such as avahi (non-cross platform) have waited for
> "vital" security implementations for DNSSEC before implementing write
> enabled DNS-SD (a big mistake IMHO!), and because DNSSEC is so hairy
> this has not happened either (on their roadmap unimplemented/delayed for
> years).

This is probably a clue-stick that should be applied off-list, but
what does DNSSEC have to do with writing records into the DNS?
(Unless by "DNSSEC" you mean SIG(0) or TSIG or something like that.)

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email