Skip to main content

Last Call Review of draft-ietf-avtext-rtp-grouping-taxonomy-06
review-ietf-avtext-rtp-grouping-taxonomy-06-secdir-lc-hoffman-2015-05-15-00

Request Review of draft-ietf-avtext-rtp-grouping-taxonomy
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2015-05-18
Requested 2015-05-07
Authors Jonathan Lennox , Kevin Gross , Suhas Nandakumar , Gonzalo Salgueiro , Bo Burman
I-D last updated 2015-05-15
Completed reviews Genart Last Call review of -06 by Robert Sparks (diff)
Genart Telechat review of -07 by Robert Sparks (diff)
Secdir Last Call review of -06 by Paul E. Hoffman (diff)
Opsdir Last Call review of -06 by Menachem Dodge (diff)
Assignment Reviewer Paul E. Hoffman
State Completed
Request Last Call review on draft-ietf-avtext-rtp-grouping-taxonomy by Security Area Directorate Assigned
Reviewed revision 06 (document currently at 08)
Result Ready
Completed 2015-05-15
review-ietf-avtext-rtp-grouping-taxonomy-06-secdir-lc-hoffman-2015-05-15-00
Summary: great document, no new security issues introduced.

The title of the document is "A Taxonomy of Grouping Semantics and Mechanisms
for Real-Time Transport Protocol (RTP) Sources", and that covers the content
exactly. The Security Considerations section says:

5.  Security Considerations

   This document simply tries to clarify the confusion prevalent in RTP
   taxonomy because of inconsistent usage by multiple technologies and
   protocols making use of the RTP protocol.  It does not introduce any
   new security considerations beyond those already well documented in
   the RTP protocol [RFC3550] and each of the many respective
   specifications of the various protocols making use of it.

   Hopefully having a well-defined common terminology and understanding
   of the complexities of the RTP architecture will help lead us to
   better standards, avoiding security problems.

That covers it completely.

Unrelated: if you ever wanted a high-level overview of RTP, this document is a
great place to start. Instead of introducing RTP as a technology, it introduces
it in an "who says what to whom" fashion, which is enough to get a pretty clear
picture.

--Paul Hoffman