A new Request for Comments is now available in online RFC libraries.
RFC 9607
Title: RTP Payload Format for the
Secure Communication Interoperability Protocol (SCIP)
Codec
Author: D. Hanson,
M. Faller,
K. Maver
Status: Standards Track
Stream: IETF
Date: July 2024
Mailbox: [email protected],
[email protected],
[email protected]
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtcore-rtp-scip-09.txt
URL: https://www.rfc-editor.org/info/rfc9607
DOI: 10.17487/RFC9607
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.
This document is a product of the Audio/Video Transport Core Maintenance
Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
