Last Call Review of draft-ietf-xrblock-rtcp-xr-synchronization-07
review-ietf-xrblock-rtcp-xr-synchronization-07-secdir-lc-johansson-2014-02-06-00
| Request | Review of | draft-ietf-xrblock-rtcp-xr-synchronization |
|---|---|---|
| Requested revision | No specific revision (document currently at 09) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2014-02-04 | |
| Requested | 2014-01-23 | |
| Authors | Hitoshi Asaeda , Qin Wu , Rachel Huang | |
| I-D last updated | 2014-02-06 | |
| Completed reviews |
Genart Last Call review of -07
by Meral Shirazipour
(diff)
Genart Telechat review of -08 by Meral Shirazipour (diff) Secdir Last Call review of -07 by Leif Johansson (diff) |
|
| Assignment | Reviewer | Leif Johansson |
| State | Completed | |
| Request | Last Call review on draft-ietf-xrblock-rtcp-xr-synchronization by Security Area Directorate Assigned | |
| Reviewed revision | 07 (document currently at 09) | |
| Result | Ready | |
| Completed | 2014-02-06 |
review-ietf-xrblock-rtcp-xr-synchronization-07-secdir-lc-johansson-2014-02-06-00
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. >From the abstract: This document defines two RTP Control Protocol (RTCP) Extended Report (XR) Blocks that allow the reporting of synchronization delay and offset metrics for use in a range of RTP applications. This is outside the area of my expertise but the claim in the Security Considerations section that this I-D doesn't introduce any new security issues beyond those described in RFC3611 seem reasonable. I'd say this goes in the "no problem" bucket.