Last Call Review of draft-ietf-payload-rtp-klv-
review-ietf-payload-rtp-klv-secdir-lc-melnikov-2012-02-08-00
Request | Review of | draft-ietf-payload-rtp-klv |
---|---|---|
Requested revision | No specific revision (document currently at 04) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2012-02-14 | |
Requested | 2012-01-23 | |
Authors | Jeff Downs Downs , J. Arbeiter | |
I-D last updated | 2012-02-08 | |
Completed reviews |
Secdir Last Call review of -??
by Alexey Melnikov
|
|
Assignment | Reviewer | Alexey Melnikov |
State | Completed | |
Request | Last Call review on draft-ietf-payload-rtp-klv by Security Area Directorate Assigned | |
Completed | 2012-02-08 |
review-ietf-payload-rtp-klv-secdir-lc-melnikov-2012-02-08-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. This document specifies the payload format (and the corresponding media type) for packetization of KLV (Key-Length-Value) Encoded Data, as defined by the Society of Motion Picture and Television Engineers (SMPTE) in SMPTE 336M, into the Real-time Transport Protocol (RTP). The document is well written. Its Security Considerations section talks about several ways of providing RTP payload confidentiality, integrity and source authenticity. It also talks about causing denial of service in naive decoders by specially crafted packets. I can't think of other things that needs to be covered in this section.