Re: Summary: What to do with expired signatures

["Eric A. Hall" <[e-mail]>]

Eric Brunner-Williams in Portland Maine 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. The
latter will have to be replaced with something else before the file can be
deprecated, but moreover, I can't think of a good reason to deprecate it
in the first place. Clearly it is useful. I would like to hear arguments
that it is unuseful and an interoperability hazard of such magnitude that
the loss of stability afforded by a common import/export format (at least)
is worthwhile. Anybody?

Okay then, well, if we aren't going to deprecate it, would a clarification
of the spec that redefined the purpose (import/export, not the backend DB)
and the structural format of the file be such a resource drain that the
effort should not be undertaken? What is the limiting resource here?
Wouldn't such an effort strengthen the benefits?

I'm certainly comfortable with a MAY clause so that implementors don't
have to mess with it if they don't have the resources. But otherwise it
offers some pretty important features. Best for the Internet community to
spend a few cycles cleaning it up, I would think.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

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