Seems like a good idea to me. I think the WG should adopt it. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e...@gmail.com
On Mon, Jan 27, 2020 at 10:09 AM Hugo Salgado <hsalg...@nic.cl> wrote: > > Dear DNSOPers, as an operator I tend to have this need to couple > an answer for a query to an auth server, with the actual "SOA zone > version" used. So I think it'll be valuable to have an EDNS option > for it. > > Here I'm proposing it with this new draft. The 'camel index' for > its implementation/hack/proof-of-concept is about 37 lines in > NSD 4.1 (more details in Appendix A). > > I've asked some operators and they see value on it. Is there any > support for adoption in DNSOP? > > ----- > Name: draft-salgado-rrserial > Revision: 01 > Title: The "RRSERIAL" EDNS option for the SOA serial of a RR's zone > Document date: 2020-01-27 > Group: Individual Submission > Pages: 5 > URL: > https://www.ietf.org/internet-drafts/draft-salgado-rrserial-01.txt > Status: https://datatracker.ietf.org/doc/draft-salgado-rrserial/ > Htmlized: https://tools.ietf.org/html/draft-salgado-rrserial-01 > Htmlized: https://datatracker.ietf.org/doc/html/draft-salgado-rrserial > Diff: https://www.ietf.org/rfcdiff?url2=draft-salgado-rrserial-01 > > Abstract: > The "RRSERIAL" EDNS option allows a DNS querier to ask a DNS > authoritative server to add a EDNS option in the answer of such query > with the SOA serial number field of the origin zone which contains > the answered resource record. > > This "RRSERIAL" data allows to debug problems and diagnosis by > helping to recognize the origin of an answer, associating this answer > with a respective zone version. > ----- > > Best, > > Hugo Salgado > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
