RFC 9607: RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec
In plain English — editorial summary, not part of the RFC
This document describes the RTP payload format of the Secure Communication Interoperability Protocol (SCIP). SCIP is an application-layer protocol that provides end-to-end session establishment, payload encryption, packetization and de-packetization of media, and reliable transport. This document provides a globally available reference that can be used for the development of network equipment and procurement of services that support SCIP traffic. The intended audience is network security policymakers; network administrators, architects, and original equipment manufacturers (OEMs); procurement personnel; and government agency and commercial industry representatives.
Document record
- Document ID
- RFC9607
- Published
- July 2024
- Authors
- D. Hanson; M. Faller; K. Maver
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9601Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a ShimCurrent
August 2024
- RFC 9599Guidelines for Adding Congestion Notification to Protocols that Encapsulate IPCurrent
August 2024
- RFC 9595YANG Schema Item iDentifier (YANG SID)Current
July 2024
- RFC 9621Architecture and Requirements for Transport ServicesCurrent
January 2025
- RFC 9622An Abstract Application Programming Interface (API) for Transport ServicesCurrent
January 2025
- RFC 9623Implementing Interfaces to Transport ServicesCurrent
January 2025
- RFC 9626Video Frame Marking RTP Header ExtensionCurrent
March 2025
- RFC 9628RTP Payload Format for VP9 VideoCurrent
March 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?