Telechat Review of draft-ietf-avtext-rams-scenarios-
review-ietf-avtext-rams-scenarios-secdir-telechat-melnikov-2012-05-04-00

Request Review of draft-ietf-avtext-rams-scenarios
Requested rev. no specific revision (document currently at 05)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2012-05-08
Requested 2012-04-26
Authors Ali Begen
Draft last updated 2012-05-04
Completed reviews Genart Last Call review of -?? by Vijay Gurbani
Secdir Telechat review of -?? by Alexey Melnikov
Assignment Reviewer Alexey Melnikov
State Completed
Review review-ietf-avtext-rams-scenarios-secdir-telechat-melnikov-2012-05-04
Review result Ready
Review completed: 2012-05-04

Review
review-ietf-avtext-rams-scenarios-secdir-telechat-melnikov-2012-05-04

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 Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a 


method based on RTP and RTP Control Protocol (RTCP) that enables an RTP 


receiver to rapidly acquire and start consuming the RTP multicast data. 


Upon a request from the RTP receiver, an auxiliary unicast RTP 


retransmission session is set up between a retransmission server and the 


RTP receiver, over which the reference information about the new 


multicast stream the RTP receiver is about to join is transmitted at an 


accelerated rate. This document provides example scenarios and discusses 


how the RAMS solution could be used when there are two or more multicast 


streams to be acquired from the same or different multicast RTP sessions.






The document says that it has no security considerations. While I would 


agree that it doesn't add new security considerations to the one defined 


in RFC 6285, I am a bit puzzled why it doesn't say exactly that. RFC 


6285 has very extensive Security Considerations.