Last Call Review of draft-ietf-jmap-calendars-18
review-ietf-jmap-calendars-18-secdir-lc-nir-2024-06-20-00
Request | Review of | draft-ietf-jmap-calendars |
---|---|---|
Requested revision | No specific revision (document currently at 22) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2024-06-27 | |
Requested | 2024-06-13 | |
Authors | Neil Jenkins , Michael Douglass | |
I-D last updated | 2024-06-20 | |
Completed reviews |
Genart Last Call review of -18
by Roni Even
(diff)
Artart Last Call review of -19 by Jean Mahoney (diff) Secdir Last Call review of -18 by Yoav Nir (diff) |
|
Assignment | Reviewer | Yoav Nir |
State | Completed | |
Request | Last Call review on draft-ietf-jmap-calendars by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/ukJbCyIaJkTbfTwsBXEfvz4wnHs | |
Reviewed revision | 18 (document currently at 22) | |
Result | Has nits | |
Completed | 2024-06-20 |
review-ietf-jmap-calendars-18-secdir-lc-nir-2024-06-20-00
Hello, I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. The document is clear and understandable, and the Security Considerations section is very good. I liked section 9.1 which highlights privacy concerns specific to calendars, although I believe that all of these concerns also apply to email. Yes, pretty much any event in my calendar says what I'm going to be doing at a certain time, and very often where I'm going to be; contacts include phone numbers and addresses, but things like that are discussed over email all the time. Section 9.3 of calendar-specific DoS was educational for me. NITS: - in section 9.3.2 s/pused/pushed/