IETF Logo Mail Archive

Re: [mdnsext] mDNSext features/requirements rollup

vortex <vortex@networkcommons.org> Wed, 30 January 2013 07:11 UTC

Return-Path: <vortex@networkcommons.org>
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 CCA2E21F8AB2 for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 23:11:40 -0800 (PST)
X-Quarantine-ID: <MaQqvc+heVal>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Subject"
X-Spam-Flag: NO
X-Spam-Score: 0.797
X-Spam-Level:
X-Spam-Status: No, score=0.797 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HEADER_COUNT_SUBJECT=3.096]
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 MaQqvc+heVal for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 23:11:39 -0800 (PST)
Received: from abulafia.free2air.net (abulafia.free2air.net [87.106.251.70]) by ietfa.amsl.com (Postfix) with ESMTP id 80AE821F8AAD for <mdnsext@ietf.org>; Tue, 29 Jan 2013 23:11:39 -0800 (PST)
Received: from host86-178-159-153.range86-178.btcentralplus.com ([86.178.159.153] helo=[192.168.1.64]) by abulafia.free2air.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <vortex@networkcommons.org>) id 1U0RpW-0001lX-HG for mdnsext@ietf.org; Wed, 30 Jan 2013 07:11:37 +0000
Message-ID: <5108C79C.7070301@networkcommons.org>
Date: Wed, 30 Jan 2013 07:11:24 +0000
From: vortex <vortex@networkcommons.org>
Organization: free2air
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: mdnsext@ietf.org
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> <20130129200449.GP15365@mx1.yitter.info>
In-Reply-To: <20130129200449.GP15365@mx1.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [mdnsext] mDNSext features/requirements rollup
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: vortex@networkcommons.org
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: Wed, 30 Jan 2013 07:11:40 -0000

On 29/01/2013 20:04, Andrew Sullivan wrote:
> 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.)

AFAIK, close to nothing. But in avahi's case the two issues were bound
together by one or more developers considering them intimately bound,
resulting in Wide Area updates never being implemented, see

http://avahi.org/roadmap

and

http://avahi.org/wiki/GoogleSummerOfCode

Best,

.v

v2.23.0 | Report a Bug | By Email