RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec
RFC 9607
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed author "K. Maver": changed name from "Keith Maver" to "K. Maver", cleared country (was "United States of America") |
|
2026-05-20
|
(System) | Changed author "M. Faller": changed name from "MikeFaller" to "M. Faller", cleared country (was "United States of America") |
|
2026-05-20
|
(System) | Changed author "D. Hanson": changed name from "Dan Hanson" to "D. Hanson", cleared country (was "United States of America") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-07-24
|
(System) | Received changes through RFC Editor sync (created document RFC 9607, created became rfc relationship between draft-ietf-avtcore-rtp-scip and RFC 9607, set abstract to 'This … Received changes through RFC Editor sync (created document RFC 9607, created became rfc relationship between draft-ietf-avtcore-rtp-scip and RFC 9607, set abstract to '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.', set pages to 15, set standardization level to Proposed Standard, added RFC published event at 2024-07-24) |
|
2024-07-24
|
(System) | RFC published |