[nscp] Updating zone *content* in-scope or not? (Was: Welcome (and proposed charter)

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 16 September 2010 13:06 UTC

Return-Path: <bortzmeyer@nic.fr>
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 77A563A6953 for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 06:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.145
X-Spam-Level:
X-Spam-Status: No, score=-106.145 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, 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 GOkpGj7tliVl for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 06:06:08 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 82F623A6950 for <nscp@ietf.org>; Thu, 16 Sep 2010 06:06:08 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id F3CCD1C013A; Thu, 16 Sep 2010 15:01:31 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id EEE771C009D; Thu, 16 Sep 2010 15:01:31 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id E2F2C7B0037; Thu, 16 Sep 2010 15:01:31 +0200 (CEST)
Date: Thu, 16 Sep 2010 15:01:31 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Message-ID: <20100916130131.GA29091@nic.fr>
References: <4C9091C8.1030702@isc.org> <p062408d6c8b692e2c226@[10.20.30.158]> <A5289BAE-189D-4FF0-8AEC-2CCDC06D3B43@sinodun.com> <p062408dbc8b6aaf55b1a@[10.20.30.158]> <20899_1284570202_o8FH3Loi023191_1F675FEC-C6FE-480D-A598-44BCBFCD46C0@sinodun.com> <F41F5A3D292BA66474A70422@minbar.fac.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F41F5A3D292BA66474A70422@minbar.fac.cs.cmu.edu>
X-Operating-System: Debian GNU/Linux 5.0.5
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: nscp@ietf.org
Subject: [nscp] Updating zone *content* in-scope or not? (Was: Welcome (and proposed charter)
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 13:06:09 -0000

On Wed, Sep 15, 2010 at 02:57:35PM -0400,
 Jeffrey Hutzelman <jhutz@cmu.edu>; wrote 
 a message of 64 lines which said:

> IMHO, zone content management certainly should be in scope.

-1 for a practical reason: we already have several good ways to update
zone content and two are standard and use the DNS (RFC 2136 and
5936).