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

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 17 September 2010 22:15 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 22D763A697B for <nscp@core3.amsl.com>; Fri, 17 Sep 2010 15:15:09 -0700 (PDT)
X-Quarantine-ID: <YyEhgksprwla>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char DE hex): To: ...lman <jhutz@cmu.edu>, Ond\336ej Sur\230 <ondrej[...]
X-Spam-Flag: NO
X-Spam-Score: -101.135
X-Spam-Level:
X-Spam-Status: No, score=-101.135 tagged_above=-999 required=5 tests=[AWL=0.611, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, 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 YyEhgksprwla for <nscp@core3.amsl.com>; Fri, 17 Sep 2010 15:15:08 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 03D243A692A for <nscp@ietf.org>; Fri, 17 Sep 2010 15:15:07 -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 o8HMFSXM074774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Sep 2010 15:15:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624086fc8b998cb98d6@[10.20.30.158]>
In-Reply-To: <4C6A8B95E7FAF06E143D9425@minbar.fac.cs.cmu.edu>
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> <p0624083ac8b8499641a3@10.20.30.158> <22489_1284679010_o8GNGnKr014689_AANLkTikkgZs3keRo0DcRCx9jSAbrFiHeLsyxE5ss 7hQ7@mail.gmail.com> <4C6A8B95E7FAF06E143D9425@minbar.fac.cs.cmu.edu>
Date: Fri, 17 Sep 2010 15:15:25 -0700
To: Jeffrey Hutzelman <jhutz@cmu.edu>, OndÞej Sur˜ <ondrej@sury.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Cc: nscp@ietf.org, jhutz@cmu.edu
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: Fri, 17 Sep 2010 22:15:09 -0000

At 6:06 PM -0400 9/17/10, Jeffrey Hutzelman wrote:
>--On Friday, September 17, 2010 01:15:13 AM +0200 OndÞej Sur˜ <ondrej@sury.org>; wrote:
>
>>>> > 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?
>>
>>I agree that we should focus on new work first as proposed in previous
>>mails. My understanding of this group is that we basically want start
>>with protocol to add/remove/modify zone configuration remotely.
>
>I don't see managing zone content as necessarily wanting to be a separate protocol from adding zones and setting policy for them.  Let's not paint ourselves into a corner.

I don't see us saying "we'll do that after we have settled on a protocol and specified other management actions first" as "paint ourselves into a corner". It's delaying stuff that can be a distraction.

--Paul Hoffman, Director
--VPN Consortium