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

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

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: nscp@core3.amsl.com
Delivered-To: nscp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A55E3A69F3 for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 15:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.263
X-Spam-Level:
X-Spam-Status: No, score=-101.263 tagged_above=-999 required=5 tests=[AWL=0.783, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYDxfyk2E4XU for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 15:25:15 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 42AFC3A69BB for <nscp@ietf.org>; Thu, 16 Sep 2010 15:25:14 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o8GMPZvk074716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Sep 2010 15:25:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
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?
X-BeenThere: nscp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Nameserver control/configuration protocol discussion list <nscp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nscp>, <mailto:nscp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nscp>
List-Post: <mailto:nscp@ietf.org>
List-Help: <mailto:nscp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nscp>, <mailto:nscp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 22:25:16 -0000

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.orgorg:
>> 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