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

Ondřej Surý <ondrej@sury.org> Thu, 16 September 2010 23:16 UTC

Return-Path: <ondrej@sury.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 696363A6807 for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 16:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 alV-3m+CIeuw for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 16:16:19 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id D99FD3A69D6 for <nscp@ietf.org>; Thu, 16 Sep 2010 16:15:27 -0700 (PDT)
Received: by wyi11 with SMTP id 11so2229951wyi.31 for <nscp@ietf.org>; Thu, 16 Sep 2010 16:15:33 -0700 (PDT)
Received: by 10.227.141.138 with SMTP id m10mr3512521wbu.20.1284678933229; Thu, 16 Sep 2010 16:15:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.131.98 with HTTP; Thu, 16 Sep 2010 16:15:13 -0700 (PDT)
In-Reply-To: <p0624083ac8b8499641a3@10.20.30.158>
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>
From: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@sury.org>
Date: Fri, 17 Sep 2010 01:15:13 +0200
Message-ID: <AANLkTikkgZs3keRo0DcRCx9jSAbrFiHeLsyxE5ss7hQ7@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: nscp@ietf.org
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 23:16:21 -0000

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

Ondrej
-- 
Ondřej Surý <ondrej@sury.org>;