Re: [nscp] Updating zone *content* in-scope or not?

Re: [nscp] Updating zone content in-scope or not?

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 16 September 2010 22:25 UTC

Mime-Version: 1.0
Message-Id: <p0624083ac8b8499641a3@[10.20.30.158]>
In-Reply-To: <22k4mlbb6k.fsf@ziptop.autonomica.net>
References: <4C9091C8.1030702@isc.org> <p062408d6c8b692e2c226@[10.20.30.158]> <A5289BAE-189D-4FF0-8AEC-2CCDC06D3B43@sinodun.com> <p062408dbc8b6aaf55b1a@[10.20.30.158]> <F41F5A3D292BA66474A70422@minbar.fac.cs.cmu.edu> <20100916130131.GA29091@nic.fr> <p0624081fc8b7e8b23cc0@[10.20.30.158]> <22r5gtcwtj.fsf@ziptop.autonomica.net> <p06240837c8b839e8f192@[10.20.30.158]> <22k4mlbb6k.fsf@ziptop.autonomica.net>
Date: Thu, 16 Sep 2010 15:25:34 -0700
To: Lars-Johan Liman <liman@autonomica.se>, nscp@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [nscp] Updating zone *content* in-scope or not?
Precedence: list

At 12:01 AM +0200 9/17/10, Lars-Johan Liman wrote:
>At 9:28 PM +0200 9/16/10, Lars-Johan Liman wrote:
>>> I agree with Stéphane that there are already standardized mechanisms to
>>> handle zone content updates. I may well be that they require the zone
>>> admin to run a DNS server, but you _can_ (and that's an obvious future
>>> to me) send dynamic updates from an application that doesn't work as a
>>> DNS server _to_ the master server, so _some_ of your cases can probably
>>> be dealt with, but not all. *)
>
>paul.hoffman@vpnc.org:
>> I was not aware of those applications. Can you point to some examples?
>
>Well, "nsupdate" is the most obvious one. "dhclient" and "dhcpd" are two
>more.

Wow, my memory for programs I don't like is bad. Good call on all of them.

> > That works for me, although it should probably be written into the charter.
>
>It should, definitely.

If others agree that we want to possibly do this, but only after we have done the "new" work first, I'll write up proposed words. What do folks think?

--Paul Hoffman, Director
--VPN Consortium

[nscp] Welcome (and proposed charter) Jelte Jansen
Re: [nscp] Welcome (and proposed charter) Paul Hoffman
Re: [nscp] Welcome (and proposed charter) jad
Re: [nscp] Welcome (and proposed charter) Paul Hoffman
Re: [nscp] Welcome (and proposed charter) jad
Re: [nscp] Welcome (and proposed charter) Jeffrey Hutzelman
[nscp] Updating zone *content* in-scope or not? (… Stephane Bortzmeyer
Re: [nscp] Updating zone *content* in-scope or no… Paul Hoffman
Re: [nscp] Updating zone *content* in-scope or no… Lars-Johan Liman
Re: [nscp] Updating zone *content* in-scope or no… Paul Hoffman
Re: [nscp] Updating zone *content* in-scope or no… Lars-Johan Liman
Re: [nscp] Updating zone *content* in-scope or no… Paul Hoffman
Re: [nscp] Updating zone *content* in-scope or no… Ondřej Surý
Re: [nscp] Updating zone *content* in-scope or no… Jeffrey Hutzelman
Re: [nscp] Updating zone *content* in-scope or no… Paul Hoffman
Re: [nscp] Updating zone *content* in-scope or no… Jeffrey Hutzelman
Re: [nscp] Updating zone *content* in-scope or no… Ondřej Surý
Re: [nscp] Updating zone *content* in-scope or no… Tony Finch
Re: [nscp] Updating zone *content* in-scope or no… Edward Lewis
Re: [nscp] Updating zone *content* in-scope or no… Wes Hardaker
Re: [nscp] Updating zone *content* in-scope or no… Tony Finch
[nscp] Proposed wording for the charter Paul Hoffman
Re: [nscp] Updating zone *content* in-scope or no… Jeffrey Hutzelman