RFC 8871: A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)
In plain English — editorial summary, not part of the RFC
This document describes a solution framework for ensuring that media confidentiality and integrity are maintained end to end within the context of a switched conferencing environment where Media Distributors are not trusted with the end-to-end media encryption keys. The solution builds upon existing security mechanisms defined for the Real-time Transport Protocol (RTP).
Document record
- Document ID
- RFC8871
- Published
- January 2021
- Authors
- P. Jones; D. Benham; C. Groves
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
January 2021
- RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current
April 2020
- RFC 9185DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key ExchangeCurrent
April 2022
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 5850A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP)Current
May 2010
- RFC 2813Internet Relay Chat: Server ProtocolCurrent
April 2000
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?