RR Text format (was Re: Summary: What to do with expired signatures)

Greg Hudson <ghudson@MIT.EDU> Mon, 18 February 2002 22:03 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20181 for <dnsext-archive@lists.ietf.org>; Mon, 18 Feb 2002 17:03:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1) id 16cvj9-0007dp-00 for namedroppers-data@psg.com; Mon, 18 Feb 2002 13:53:39 -0800
Received: from rip.psg.com ([147.28.0.39]) by psg.com with esmtp (Exim 3.33 #1) id 16cvj8-0007dd-00 for namedroppers@ops.ietf.org; Mon, 18 Feb 2002 13:53:38 -0800
Received: from randy by rip.psg.com with local (Exim 3.33 #1) id 16cvj8-000EyD-00 for namedroppers@ops.ietf.org; Mon, 18 Feb 2002 13:53:38 -0800
In-Reply-To: <3C7133D2.EC81BE86@ehsco.com>
References: <200202181929.g1IJTo160792@nic-naa.net> <3C7133D2.EC81BE86@ehsco.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1014069044.32732.100.camel@error-messages.mit.edu>
Mime-Version: 1.0
Subject: RR Text format (was Re: Summary: What to do with expired signatures)
From: Greg Hudson <ghudson@MIT.EDU>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: namedroppers@ops.ietf.org
Date: Mon, 18 Feb 2002 16:50:44 -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 2002-02-18 at 12:03, Eric A. Hall wrote:
> > the utility of standardizing the text format here escapes me.
> 
> Two reasons: out-of-band zone replication which contributes towards
> overall stability of the Internet's namespace, and zone directives.

(Zone directives?  I don't get it.)

There is certainly utility in being able to replicate zones out of band
between different nameserver implementations, but is the value
compelling?

Should the IETF try to standardize the format of the aliases file used
by MTAs?  The format of access permissions files used by FTP and HTTP
servers?  The format of mailbox files used by an IMAP server?  All of
these standards would facilitate the distribution of services among
heterogeneous server implementations, as well as the gradual migration
of a distributed service from one implementation to another. 
Nonetheless, we don't try to standardize those formats because it would
be a waste of time.  Implementors don't generally see enough value in
this kind of interoperability to prevent them from making little
improvements to or wholesale reinventions of those data formats.  They
write import tools to help people migrate from other implementations to
their own, and usually leave it at that.



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/>