Lines Matching full:protection
36 protection to the RTP traffic and to the control traffic for RTP, the
53 3.3.2. Replay Protection. . . . . . . . . . . . . . . . 15
131 protection to the RTP traffic and to the control traffic for RTP,
142 proves to be a suitable protection for heterogeneous environments
184 provided is actually only integrity protection and not data origin
194 protection against replayed packets.
197 except that SRTCP integrity protection is mandatory (malicious or
222 These properties ensure that SRTP is a suitable protection scheme for
242 confidentiality and integrity protection, both for the SRTP stream
380 indirectly provides replay protection by authenticating
382 protected as this does not provide any extra protection.
439 authentication and replay protection are provided), containing
498 * a separate replay list is maintained (when replay protection is
662 5. For message authentication and replay protection, first check if
693 index estimated in Step 2. If replay protection is provided, also
704 protection (Section 3.3.2), encryption (Section 4.1), message
809 3.3.2. Replay Protection
811 Secure replay protection is only possible when integrity protection
812 is present. It is RECOMMENDED to use replay protection, both for RTP
813 and RTCP, as integrity protection alone cannot assure security
823 protection. Packet indices which lag behind the packet index in the
964 selected for the protection of the associated SRTP stream(s),
988 * SRTCP replay protection is as defined in Section 3.3.2, but using
996 SHALL by default be the same as selected for the protection of the
2131 Protection against such attacks can be provided simply by increasing
2412 proper integrity protection.
2420 random plaintext values. While this protection is not equivalent to
2472 protection can be applied smoothly. Under these assumptions, use of
