IETF Last Call Review of draft-ietf-avtcore-rtcp-green-metadata-08
review-ietf-avtcore-rtcp-green-metadata-08-secdir-lc-roca-2026-06-17-00
| Request | Review of | draft-ietf-avtcore-rtcp-green-metadata |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2026-06-19 | |
| Requested | 2026-06-05 | |
| Authors | Yong He , Christian Herglotz , Edouard Francois | |
| I-D last updated | 2026-07-09 (Latest revision 2026-07-02) | |
| Completed reviews |
Secdir IETF Last Call review of -08
by Vincent Roca
(diff)
Genart IETF Last Call review of -09 by Paul Kyzivat (diff) Genart Telechat review of -10 by Paul Kyzivat (diff) |
|
| Assignment | Reviewer | Vincent Roca |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-avtcore-rtcp-green-metadata by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/k4RxKmoM0CCzYCiQBVHeVQgA3oM | |
| Reviewed revision | 08 (document currently at 13) | |
| Result | Ready | |
| Completed | 2026-06-17 |
review-ietf-avtcore-rtcp-green-metadata-08-secdir-lc-roca-2026-06-17-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. Summary: ready Globally, this ID looks ready to me. I only have a small comment: an ID introducing a extension of a given protocol usually starts its "Security Considerations" section with a link to the "Security Consideration" section of base RFC it depends on, since what applies there also applies in general. For instance, RFC 4585 on extended RFC profiles discusses timing attacks that IMHO also apply here (eg. what happens if a malicious entity does not follow timing rules of section 4.2.3). Also, RFC 4585 recommends in its "Security Consideration" section that "Senders as well as receivers SHOULD behave conservatively when observing strange reporting behavior", whereas no such recommendation is done here. Regards, Vincent