Last Call Review of draft-ietf-payload-rtp-vc2hq-05
review-ietf-payload-rtp-vc2hq-05-secdir-lc-salowey-2018-05-13-00
Request | Review of | draft-ietf-payload-rtp-vc2hq |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2018-05-16 | |
Requested | 2018-05-02 | |
Authors | James P. Weaver | |
I-D last updated | 2018-05-13 | |
Completed reviews |
Genart Last Call review of -05
by Elwyn B. Davies
(diff)
Secdir Last Call review of -05 by Joseph A. Salowey (diff) |
|
Assignment | Reviewer | Joseph A. Salowey |
State | Completed | |
Request | Last Call review on draft-ietf-payload-rtp-vc2hq by Security Area Directorate Assigned | |
Reviewed revision | 05 (document currently at 08) | |
Result | Ready | |
Completed | 2018-05-13 |
review-ietf-payload-rtp-vc2hq-05-secdir-lc-salowey-2018-05-13-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. The summary of the review is the document is ready. The security considerations seem well thought out and are follow the guidelines of RFC7202 for RTP payload definitions. I like the fact that it includes some information on possible implementation pitfalls. Cheers, Joe