Home | History | Annotate | Download | only in doc

Lines Matching full:recommended

153    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
316 | : authentication tag (RECOMMENDED) : |
356 The OPTIONAL MKI and the RECOMMENDED authentication tag are the only
371 Authentication tag: configurable length, RECOMMENDED. The
431 since message authentication is RECOMMENDED,
475 master salt is strongly RECOMMENDED, see Section 9.2. A "NULL"
812 is present. It is RECOMMENDED to use replay protection, both for RTP
1208 failures. It is RECOMMENDED that, if a dedicated security module is
1620 than these defaults. For SRTP, smaller values are NOT RECOMMENDED,
1646 size of keys (minimum, maximum, recommended), format of keys,
1647 recommended/required processing of input keying material,
1776 As shown in Figure 1, the authentication tag is RECOMMENDED in SRTP.
1898 The recommended way for a particular key management system to provide
2101 the same RTP session, but it is RECOMMENDED that each SSRC have its
2103 and SSRCs are managed by a key management module as recommended
2104 above, the RECOMMENDED policy for an SSRC collision error is for the
2203 concerns about this are RECOMMENDED to instead use a 192 bit master
2208 160 bit keys it is NOT RECOMMENDED that ad-hoc key-padding schemes
2441 recommended setting of its options.
2476 an issue, we recommended to use low-rate key derivation.
2502 Considering SRTCP and key storage, it is recommended to use low-rate
2521 Use of the MKI for re-keying is RECOMMENDED for most applications
2533 of the streams. Use of the MKI for re-keying is RECOMMENDED.
2603 RECOMMENDED when trying to minimize the number of keys in