[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dnsext] RRTYPE request: template for ZS record
Jim,
> They don't. They lookup a name (singular) and if they get a ZS record
> back, that's it. If there's nothing there, they give up. No searching
> or tree walking is involved whatsoever.
good. The term "zone", however, implies, that the semantics apply to
more than just the node queried for. So, in your vision, would the "status"
RR for "jim.example" also cover "another.jim.example"?
> gives that misleading impression, please point it out. The proposed
> RRtype is not making any assumptions about DNAME, CNAME, zone cuts,
> wildcards or any of that stuff and doesn't need to. There is
> absolutely no need for any special server or client processing for
> this proposed RRtype. It can be handled according to RFC3597.
This proposed RR type reminds me of HINFO (rather than WKS), recognizing
that HINFO had - at least in the beginning - stricter semantics and indeed
a "registry" for its values. Now, given that the new RR's sematics
aren't at all specified, wouldn't "TXT2" better describe it?
More serious, is the RR definition general enough or is it only useful
in a particular, maybe even highly regulated, namespace? If the resolution
context is provided by the namespace, wouldn't a "Private Use" code do better?
-Peter
--
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/>