Re: dynamic update zone
Edward Lewis <edlewis@arin.net> Mon, 16 September 2002 13:01 UTC
Received: from psg.com (smmsp@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03260 for <dnsext-archive@lists.ietf.org>; Mon, 16 Sep 2002 09:01:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 17qvF5-0008ZR-00 for namedroppers-data@psg.com; Mon, 16 Sep 2002 05:44:43 -0700
Received: from smtp1.arin.net ([192.149.252.33]) by psg.com with esmtp (Exim 3.36 #1) id 17qvEy-0008Yk-00 for namedroppers@ops.ietf.org; Mon, 16 Sep 2002 05:44:36 -0700
Received: from ops.arin.net (ops.arin.net [192.149.252.141]) by smtp1.arin.net (8.12.4/8.12.4) with ESMTP id g8GCidRF036054; Mon, 16 Sep 2002 08:44:39 -0400 (EDT)
Received: from [192.149.252.231] (localhost [127.0.0.1]) by ops.arin.net (8.9.0/8.9.0) with ESMTP id IAA15693; Mon, 16 Sep 2002 08:44:33 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1 (Unverified)
Message-Id: <a05111b02b9a8c9f944e1@[193.0.9.238]>
In-Reply-To: <007c01c25b1f$4ac2cf30$b9370681@BARNACLE>
References: <a05111b19b9a649f294c9@[193.0.9.238]> <00cd01c25a91$e5f917e0$b9370681@BARNACLE> <a05111b03b9a7377eabc4@[193.0.9.238]> <007c01c25b1f$4ac2cf30$b9370681@BARNACLE>
Date: Sat, 14 Sep 2002 07:14:49 -0400
To: Scott Rose <scottr@antd.nist.gov>, namedroppers@ops.ietf.org, Edward Lewis <edlewis@arin.net>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: dynamic update zone
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Status: No, hits=-0.9 required=5.0 tests=IN_REP_TO,DATE_IN_PAST_48_96 version=2.31
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
At 8:15AM -0400 9/13/02, Scott Rose wrote: >If I'm thinking correctly about this, the new interpretation of the rcodes >would be: >refused - means that the server will never accept an update from the sender >until some misconfiguration is correct, or policy stuff. > >frozen(whatever) - means that the sender could normally make the update, but >the server has been frozen by an admin for some time period. Try again >later and it might suceed. > >correct? That sounds like what I had in mind. For a manual (interactive) client, I think that the difference between the two would be to print "permanent error" for a REFUSED, and "temporary error" for a FROZEN (or SUSPENDED). For an automated client, I probably wouldn't recommend different treatments - so as to prevent overly persistent broken implementations. (Perhaps the log message is different in the two cases, as suggested for the manual client.) -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-703-227-9854 ARIN Research Engineer -- 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/>
- dynamic update zone Edward Lewis
- Re: dynamic update zone Bill Sommerfeld
- Re: dynamic update zone Rob Austein
- Re: dynamic update zone Edward Lewis