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

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

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 17 September 2010 22:15 UTC

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?
Precedence: list

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

[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