Hugo Salgado wrote on 2022-04-07 11:02:
On 06:42 07/04, Paul Vixie wrote:
hugo, mauricio,
i hope you will change your nomenclature. a zone serial applies to an rrset
not just to an rr. answers contain rrsets not merely rrs. other than this,
your proposal looks solid to me.
Thank you very much Paul, agree with specifying that it is a set.
However it's not clear to me what you mean by *nomenclature*. Is it
about changing the name of RRSERIAL to RRSETSERIAL? (Or RRS-SERIAL?)
Or will it be enough to clarify it in the introduction and change the
references from "resource record" to "resource record set"?
the semantics of an answer are pretty well understood -- the rrset which
is in the zone containing the qname is easily found. therefore you could
rename the option code to ZONESERIAL or even SERIAL and it would have an
unambiguous meaning.
but it seems to me you'd be better off with a zero-length option called
SERIAL which if set in the query causes the SOA of the answer's zone to
be added to the authority section (similar to an RFC 2308 negative
proof) and which option would only be echoed in the answer's OPT if the
option was supported. you'd want to specify that the SOA in this case is
not optional and that its truncation would cause the TC bit to be set.
--
P Vixie
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
