Re: I-D Action:draft-reid-dnsext-zs-00.txt

[Stephane Bortzmeyer <bortzmeyer@nic.fr>]

On Mon, Nov 12, 2007 at 08:20:01AM -0500,
 Internet-Drafts@ietf.org <Internet-Drafts@ietf.org> wrote 
 a message of 88 lines which said:

> 	Title           : The Zone Status (ZS) DNS Resource Record
> 	Author(s)       : J. Reid
> 	Filename        : draft-reid-dnsext-zs-00.txt

I'm not really convinced of the usefulness of this RR. It is non
structured (so it cannot be automatically parsed) and the only thing
it gives that TXT does not provide is the ability to query only ZS
records, which does not seem a lot. (In the wild, TXT records seem to
be used a lot for this purpose, sometimes with a full CVS $Id$ in a
TXT value.)

If someone wants to work on this topic, I would suggest a more
structured RR. Things like the date of the last update should really
be a parsable type.

But I'm not sure it is worth working on that instead of, for instance,
IRIS for things like "publishing real-time contact data for [ENUM]
zone owners" or the various presence protocols (RFC 3856, or RFC 3921)
for things like "the zone owner is asleep, so don't bother trying
voice-based communication".

The end user considerations section seems to be quite broken, as far
as i18n is concerned. Speaking of "unusual character sets" is
inappropriate, specially when the examples given are Chinese and
Arabic scripts, hardly "unusual". If such records would be used for
messages to the end-user, as suggested in section 3, a real i18n would
be necessary, with language-tagging of the messages.

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