On Nov 21, 2008, at 19:46, Ted Hardie wrote:
I don't see how the proposed ZS RRTYPE solves this problem. It seemslike it has exactly the same problem as TXT does: it will be completelyunstructured data. It also seems likely that different zones might diverge on how they present zone status information.
Well, I suppose the I-D could say something like "don't put more than one ZS RR at any node/zone". An unstructured (human readable) text string is all that's needed here: anything fancier is overkill IMO. A TXT record can't easily provide that info because these are already used for too many ad-hoc purposes.
Is there a draft that describes the standard for zone status information?
No. Though there's an I-D for the template explaining how the RR could be used. There is a demonstrated need for this and applications in .tel that will use the proposed RRtype. Provided a type code gets issued.
All the proposed RRtype tries to achieve is provide a simple, lightweight method to get an unstructured string from the DNS that presents hopefully informative information about the zone. If a more structured record is needed for something more elaborate perhaps that could be given yet another RRtype?
-- 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/>