IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 16 September 2010 15:35 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 395D63A6B78 for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 08:35:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.243
X-Spam-Level:
X-Spam-Status: No, score=-101.243 tagged_above=-999 required=5 tests=[AWL=0.803, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 rx3T3fcwKEI3 for <nscp@core3.amsl.com>; Thu, 16 Sep 2010 08:35:40 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id DB9CD3A6B68 for <nscp@ietf.org>; Thu, 16 Sep 2010 08:35:36 -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 o8GFZx1D047737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <nscp@ietf.org>; Thu, 16 Sep 2010 08:36:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081fc8b7e8b23cc0@[10.20.30.158]>
In-Reply-To: <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@sino dun.com> <F41F5A3D292BA66474A70422@minbar.fac.cs.cmu.edu> <20100916130131.GA29091@nic.fr>
Date: Thu, 16 Sep 2010 08:35:57 -0700
To: nscp@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [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 15:35:46 -0000

At 3:01 PM +0200 9/16/10, Stephane Bortzmeyer wrote:
>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).

Aren't those only applicable when the zone admin is also running a DNS server, brings it up to date, and then tells the DNS admin to synchronize? And aren't there *many* other deployment scenarios for DNS content?

--Paul Hoffman, Director
--VPN Consortium

v2.23.0 | Report a Bug | By Email