Lines Matching refs:encrypted

93    an authentication header.  The session description MAY be encrypted
262    encrypted).  The session itself, as distinct from the session
354       the SAP packet is encrypted.  If this bit is 0 the packet is not
355       encrypted.  See section 7 for details of the encryption process.
359       payload is to be compressed and encrypted, the compression MUST be
412    the payload type and payload are encrypted and/or compressed.
463    is sent.  If an announcement is encrypted, and many of the receivers
466    received.  For this reason, the use of encrypted SAP announcements is
471    The opinion of the authors is that encrypted SAP is useful in special
472    cases only, and that the vast majority of scenarios where encrypted
475    scenarios where encrypted announcements may be useful.  For this
477    experimentation with encrypted announcements.
482    encrypted SAP.
484    Note that if an encrypted announcement is being announced via a
488    no mechanism to chain modified encrypted announcements, so it is
492    encrypted sessions should be prepared to discard old versions of
498    Session announcements that are encrypted with a symmetric algorithm
513    In addition the recipients of such encrypted announcements cannot be
514    assumed to only be authorized key holders.  Such encrypted
524    encrypted with an asymmetric algorithm, but then it is possible to
602    If a SAP packet is to be compressed or encrypted, this MUST be done
777       bit in the SAP header to indicate that the payload is encrypted,
800     o SAPv1 included a timeout field for encrypted announcement, SAPv2