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

Edward Lewis <Ed.Lewis@neustar.biz> Mon, 20 September 2010 18:24 UTC

Return-Path: <Ed.Lewis@neustar.biz>
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 B13393A67B1 for <nscp@core3.amsl.com>; Mon, 20 Sep 2010 11:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.341
X-Spam-Level:
X-Spam-Status: No, score=-101.341 tagged_above=-999 required=5 tests=[AWL=1.258, BAYES_00=-2.599, 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 fhibZ9yWyDZO for <nscp@core3.amsl.com>; Mon, 20 Sep 2010 11:24:20 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id B4D1E3A659A for <nscp@ietf.org>; Mon, 20 Sep 2010 11:24:19 -0700 (PDT)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id o8KIOWG1049433; Mon, 20 Sep 2010 14:24:33 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.147] by Work-Laptop-2.local (PGP Universal service); Mon, 20 Sep 2010 14:24:39 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Mon, 20 Sep 2010 14:24:39 -0400
Mime-Version: 1.0
Message-Id: <a06240800c8bd5615cdee@[10.31.200.147]>
In-Reply-To: <076D7E021C1972DBD3D412B8@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> <p0624086fc8b998cb98d6@[10.20.30.158]> <076D7E021C1972DBD3D412B8@minbar.fac.cs.cmu.edu>
Date: Mon, 20 Sep 2010 14:24:30 -0400
To: Jeffrey Hutzelman <jhutz@cmu.edu>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: nscp@ietf.org, ed.lewis@neustar.biz
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: Mon, 20 Sep 2010 18:24:20 -0000

At 18:27 -0400 9/17/10, Jeffrey Hutzelman wrote:
>As I see it, zone content management should be in scope for the
>to-be-developed protocol, and needs to be one of the things we consider as
>we design that protocol, even if actually defining how it works is not one
>of the first things we work on.

Have you read RFCs 1995, 1996 and 5936 for inter-authority server 
coordination of zone content and RFCs 2136 and 3007 for altering the 
content?

Certainly the specified mechanism(s) have their limitations, but 
that's not what I think is needed to be discussed now.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Spouses, like Internet protocols, lack necessary troubleshooting tools. Sigh.