Request for Security Review of draft-ietf-avtcore-rtp-scip

The AVTCORE WG would like to solicit a Security review of "RTP payload
format for the SCIP codec" (draft-ietf-avtcore-rpt-scip).  The document is
available for inspection here:
draft-ietf-avtcore-rtp-scip-01 - RTP Payload Format for the SCIP Codec
<https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/>

When submitting a review, please CC the AVTCORE WG ([email protected]).

As noted in the introduction, SCIP is a "pseudo-codec" that provides secure
session establishment and transport over RTP.  One of the goals of the
document is to improve interop between SCIP endpoints and intermediaries
such as SBCs and RTP relays.  For example, SBCs have been  observed to
reject SDP Offers including SCIP, and some RTP relays have attempted to
interpret or transcode SCIP RTP payloads, which is not helpful because they
are encrypted and integrity protected.

While SCIP is primarily used for secure audio communications, there is some
experience with video (H.264) as well. In conferencing use cases, SCIP
should be considered a "hop by hop" security service, in contrast to an
"end to end" service such as SFrame. That is, SCIP is compatible with audio
mixing or video MCU services, with the central conferencing server having
access to cleartext media, thereby being considered "trusted".

Note that the document has informative references to the following
documents which can be made available upon request:

         [SCIP210]   SCIP-210, "SCIP Signaling Plan", Revision 3.10, 26
                     October 2017, request access via email
                     <[email protected]>.

         [SCIP214]   SCIP-214.2, "Secure Communication Interoperability
                     Protocol (SCIP) over Real-time Transport Protocol
                     (RTP)", Revision 1.1, 18 April 2014, request access
                     via email <[email protected]>.


Bernard Aboba

For the AVTCORE WG Chairs