Lines Matching refs:MAY

151    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
321    equivalent RTP packet.  The Encrypted Portion MAY be the exact size
322    of the plaintext or MAY be larger.  Figure 1 shows the RTP payload
332    transforms requiring padding.  Transforms MAY specify other padding
360               according to Section 3.2.3.  The MKI MAY be used by key
462    In addition, for each master key, an SRTP stream MAY use the
466       This value, when used, MUST be random, but MAY be public.  Use of
498    Note in particular that the master key(s) MAY be shared between SRTP
757    amount of traffic, and MAY be triggered earlier, e.g., for increased
812    dependent parameter and MUST be at least 64, but which MAY be set to
1092    initial octets of each keystream segment MAY be reserved for use in a
1434    key derivation MAY be performed, according to the
1442    Interoperable SRTP implementations MAY also derive session salting
1483    extensions MAY specify new values in the range 0x06 to 0xff for other
1503    MAY be public.
1593    but MAY be used after careful consideration of the issues in Section
1610    Note however, that it MAY be necessary to extend the SRTP or SRTCP
1703    universal hash functions, MAY be added following the guidelines in
1747    even a zero-length tag (i.e., no message authentication) MAY be used
1815    given the SSRC and MAY be given the initial RTP sequence number for
1838    one RTP session MAY share master keys (as they do by default).
2064    As described, master keys MAY be shared between streams belonging to
2096    of the salting key.  Note that the salting key MUST be random but MAY
2232    SRTP MAY be used with weak authentication (e.g., a 32-bit
2266    Weak or null authentication MAY be acceptable when it is unlikely
2554      master key, also moderate rate re-keying MAY have the same