IETF Logo Mail Archive

Re: Summary: What to do with expired signatures

Paul Vixie <paul@vix.com> Tue, 12 February 2002 14:50 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13720 for <dnsext-archive@lists.ietf.org>; Tue, 12 Feb 2002 09:50:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1) id 16ae6h-0005fW-00 for namedroppers-data@psg.com; Tue, 12 Feb 2002 06:40:31 -0800
Received: from as.vix.com ([204.152.187.70]) by psg.com with esmtp (Exim 3.33 #1) id 16ae6g-0005fQ-00 for namedroppers@ops.ietf.org; Tue, 12 Feb 2002 06:40:30 -0800
Received: from as.vix.com (localhost [127.0.0.1]) by as.vix.com (Postfix) with ESMTP id AC25F28EB3 for <namedroppers@ops.ietf.org>; Tue, 12 Feb 2002 06:40:29 -0800 (PST) (envelope-from vixie@as.vix.com)
From: Paul Vixie <paul@vix.com>
To: namedroppers@ops.ietf.org
Subject: Re: Summary: What to do with expired signatures
In-Reply-To: Message from Edward Lewis <lewis@tislabs.com> of "Tue, 12 Feb 2002 09:19:33 EST." <v03130304b88ed1eb4c99@[192.35.165.115]>
X-Mailer: mh-e 6.0; nmh 1.0.4; Emacs 21.1
Date: Tue, 12 Feb 2002 06:40:29 -0800
Message-Id: <20020212144029.AC25F28EB3@as.vix.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

> I think the issue is a bit more significant than an implementation detail.
> Personally, this thread has convinced me that the servers should not edit
> zones in any way.

I was astounded that anyone here even thought that that was debatable.

> Dynamic delete is an exception.  It is an acceptable exception in that
> dynamic update is sufficiently independent of the action of
> publishing/distributing data.  It is a complication of the zone loading
> process, not the zone serving process.

The zone whatting process?  I have here a server with persistent zone storate.
All zone changes are made by RFC2136 "UPDATE" requests.  There is no "load"
and there is no "zone file" and there is no way to map your "implied delete"
to any process that it has.  Yet this server is entirely protocol compliant.

to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

v2.40.3 | Report a Bug | By Email | System Status