On 10/08/2019 06:26, Wes Hardaker wrote:
8.2.2 DONE The biggest issue is of course to find out what to put in the extended --------------------------------------------------------------------------------- error code. On some resolvers (at least on Knot), the place where the error is noticed can be quite far from the place where the answer is built, with its EDNS options. In practice, we had to add data to the request object, for the extended error information to be carried to the module that emits the extended error code EDNS option. So, the real difficulty is not in the draft, but in knowing and understanding your resolver. + Response: As agreed to in IETF105, we've removed the RCODE binding.
Consensus calls for WG documents are supposed to be made on the list. I *like* the RCODE binding. Ray _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
