And there’s http://www.rfc-editor.org/rfc/rfc5936.txt. It has "Authoritative Transfer (AXFR)” in the abstract.
“Asynchronous" does not appear in that RFC. (In the “not that it matters, but” file: When we had singly threaded name servers, AXFR wasn’t very asynchronous in practice.) (Sorry, I can’t get the message indentation to work in Outlook, so I hacked this up:) On 2/23/15, 17:46: “John Levine” wrote: >>> >>"Authoritative" makes sense. On 2/23/15, 21:09, "Paul Vixie" <p...@redbarn.org> wrote: >> > i think we could pretend that "A" stood for "asynchronous" or anything else >> we wanted, … i think the safest thing is to not invent an acronym, but >> rather, let the QTYPE definition stand as written.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
