Robert Wilton has entered the following ballot position for draft-ietf-dnsop-server-cookies-04: 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-server-cookies/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi, Thanks for this document, I found it easy to read. I have a couple of minor questions/comments related to the lifecycles. Section 3: Except for when the Client IP address changes, there is no need to change the Client Cookie often. It is reasonable to change the Client Cookie then only if it has been compromised or after a relatively long period of time such as no longer than a year. Client Cookies are not expected to survive a program restart. It isn't clear to me why it is necessary to put an upper bound a on when a client cookie needs to be changed at all. What is the benefit of changing the client cookie once a year? 5. Updating the Server Secret I think that it would be useful to remind the reader that server secrets are expected to be updated on a semi-regular basis, as described in section 4. Regards, Rob _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
