Roman Danyliw has entered the following ballot position for draft-ietf-dnsop-serve-stale-09: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-serve-stale/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- * I agree with Mirja, Section 8 is more informative than what is alluded to the paragraph starting with “Several recursive resolvers …” in Section 3, and IMO is worth keeping. I struck me as odd to call out the operation practice of a particular vendor (Akamai). We might want to check if this reference is ok – Ben? * A few reference nits: - Section 6. Per the mention to DNS-OARC, please provide a citation. - Section 6 and 9. The text references “during discussions in the IETF”. What is that specifically – WG deliberation? * Thanks for covering the attacker use cases of stale data in Section 10. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
