Re: [mdnsext] mDNSext features/requirements rollup

nudge <nudgemac@fastmail.fm> Tue, 29 January 2013 18:39 UTC

Return-Path: <nudgemac@fastmail.fm>
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 D7CF421F886D for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 10:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 o08oEJlGKpHH for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 10:39:13 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6F121F8858 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 10:39:13 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 78A2820E99 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 13:39:12 -0500 (EST)
Received: from web6.nyi.mail.srv.osa ([10.202.2.216]) by compute3.internal (MEProxy); Tue, 29 Jan 2013 13:39:12 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date:in-reply-to:references; s=mesmtp; bh= jua9DlXy/cZFfhBNeK93jRt4JE4=; b=JshqOwnmsnaDPDoj30Kh0+SxhD7VVCpe SpQTB/+oKZJuyrZJVQ+aPxw9Mi8TdBvzEguTJkAPwlpM++RxjxjePS/8o6RF83h4 X/btthghbt91dIonXSM4WqjroRb2DL4gl0HwXF/5B9kf603iRXIrKM4OoPR754ux LVuoVraLYsM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=jua9DlXy/cZFfhBNeK93jRt4JE4=; b=gnbAQ yRSnWDpfCqledMVd3RG3i5lv5wa18y1lOHWr/5w5g9dqzhsfqGinyQM0QR/vGyJM 46jtApFNv7X9vMngBc0380cMeQwhmkHVwcc4n9vHT1N2CpjaW7eWKYGEa7OdbxsF bZnQ5yqmNlFfGeMkeYUS+RF0FlQB93kOTZHeQ8=
Received: by web6.nyi.mail.srv.osa (Postfix, from userid 99) id 3EC5921AE4; Tue, 29 Jan 2013 13:39:12 -0500 (EST)
Message-Id: <1359484752.31527.140661184088257.2DD91FC3@webmail.messagingengine.com>
X-Sasl-Enc: ljLn4ZW6atp1sI23+LdgpOKIpqY9SYhcHFukRztix14q 1359484752
From: nudge <nudgemac@fastmail.fm>
To: "<mdnsext@ietf.org>" <mdnsext@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - html
Date: Tue, 29 Jan 2013 19:39:12 +0100
In-Reply-To: <D99048ACAF96354EBFD6A811E3C65ACD10977A7C@CH1PRD0811MB407.namprd08.prod.outlook.com>
References: <mailman.97.1359403423.10833.mdnsext@ietf.org> <D99048ACAF96354EBFD6A811E3C65ACD10977A7C@CH1PRD0811MB407.namprd08.prod.outlook.com>
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 18:39:14 -0000

On Tue, Jan 29, 2013, at 07:07 PM, Alf Watt wrote:
> 
> I think Andrew's point is worth taking the time to seriously consider. We
> already have dynamic DNS update but as previously mentioned configuration
> of the DNS server and it's clients out has proven to be either too
> difficult or not of interest to various OS vendors.
> 
> It's worth mentioning that Apple has all the parts in place to pull this
> off:
> 
> - A Server OS with an embedded DNS server which they provide a UI to
> manage
> - Traditional and Mobile Clients with mDNSResolvers running on them
> - A profile distribution system which make pushing configuration options
> including keys easy
> 
> Given the will to get the features implemented Apple could solve part of
> the problem this without any changes to mdns.
> 
> There are still things that fall outside of that scope which we should
> consider, but ignoring the opportunity to uses the existing protocols
> seems like a lot of effort to reproduce work that already exists.
> 
> Best,
> Alf
> 

As someone who successfully tested and implemented WAB with TSIG
protected updates[1] in an Apple environment about a year or so ago, I
would tend to agree. It wasn't as difficult as I imagined partly because
of a lack of documentation. Of course, things have changed since and I
need to test again soon. But back then you had to front-end named with
dnsextd if you needed llq (obviously you do). If that's still true it
blocks other useful stuff such as rpz and rrl and needs fixing IMO.

[1]I also tested TSIG protected reads DNSprivate, where's that going ?