This errata seems correct to me. In addition, Section 6.2 has the following two sentences, just a few lines apart:
CHAIN responses SHOULD include the authoritative NS RRset with its RRSIG records required for validation. ////// CHAIN responses MUST include the NS RRset from the child zone, including the RRSIG records required for validation. ... which is it? Best, Peter (no hats) On 10/12/26 10:03, [email protected] wrote:
The following errata report has been submitted for RFC7901, "CHAIN Query Requests in DNS" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid9214/ -------------------------------------- Type: Technical Reported by: Ensar Sarajčić <[email protected]> Section 8.1 says: Original Text ------------- o The upstream recursive resolver adds the CHAIN option to the DNS response as follows: * Option-code, set to 13 * Option-length, set to 5 * The closest trust point is set to "com." (0x03 0x63 0x6f 0x6d 0x00) Corrected Text -------------- o The upstream recursive resolver adds the CHAIN option to the DNS response as follows: * Option-code, set to 13 * Option-length, set to 13 * The closest trust point is set to "example.com." (0x07 0x65 0x78 0x61 0x6d 0x70 0x6c 0x65 0x03 0x63 0x6f 0x6d 0x00) Notes ----- The provided example seems inconsistent with: https://datatracker.ietf.org/doc/html/rfc7901#section-5.4 Specifically: If a CHAIN answer would be bigger than the recursive resolver is willing to serve, it SHOULD send a partial chain starting with the data closest to the top of the chain. The client MAY resend the query with an updated closest trust point until it has received the full chain. The CHAIN response will contain the lowest closest trust point that was included in the CHAIN answer. I may be confusing the wording here or misunderstanding things, but I understood that the lowest closest trust point in the example response is "example.com." and not "com.". This is especially important to enable clients to use the CHAIN option value instead of checking records in the authority section. Instructions: ------------- This erratum is currently posted as "Reported". Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC7901 (draft-ietf-dnsop-edns-chain-query) -------------------------------------- Title : CHAIN Query Requests in DNS Publication Date : June 2016 Author(s) : P. Wouters Category : Experimental Source : dnsop (ops) Stream : IETF Verifying Party : IESG _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
