RFC 3711:The Secure Real-time Transport Protocol (...
RFC-Ref

traffic


Click on the red underlined text to get to the source

... message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, ...
... replay protection to the RTP traffic and to the control traffic for RTP, RTCP ...


... limitation enforces a security benefit by providing an upper bound on the amount of traffic that can pass before cryptographic keys are changed. Re-keying ...
... changed. Re-keying (see Section 8.1) MUST be triggered, before this amount of traffic, and MAY be triggered earlier, e.g., for increased security and access control ...
... bandwidth. The effect of the size of the added fields on the SRTCP traffic will be that messages will be sent with longer packet intervals. The increase in the intervals will be directly proportional to size of the added fields. For the pre- ...


... RFC2675], which are not likely to be used for RTP-based multimedia traffic). This restriction on the maximum bit-size of the packet that can be encrypted ...


... senders SHALL count the amount of SRTP and SRTCP traffic being used for a master key and invoke key management to re-key if needed ...


... attacks and their applicability to the encryption of Internet traffic is provided in [MF00]. In summary, the effective key size ...


... security protocol for the RTP/RTCP traffic in many different scenarios. SRTP has a number of configuration ...
... share the same master key as per Section 9.1 to secure all their respective RTCP traffic. This shared master key could then be the same one used by the sender to protect its outbound SRTP ...
... same one used by the sender to protect its outbound SRTP traffic. Alternatively, it could be a master key shared only among the receivers ...
... receivers and used solely for their SRTCP traffic. Both alternatives require the receivers to trust ...



Google
Web
RFC-Ref