RFC 8817: RTP Payload Format for Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Codec
In plain English — editorial summary, not part of the RFC
This document describes the RTP payload format for the Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) speech coder. TSVCIS is a scalable narrowband voice coder supporting varying encoder data rates and fallbacks. It is implemented as an augmentation to the Mixed Excitation Linear Prediction Enhanced (MELPe) speech coder by conveying additional speech coder parameters to enhance voice quality. TSVCIS augmented speech data is processed in conjunction with its temporally matched Mixed Excitation Linear Prediction (MELP) 2400 speech data. The RTP packetization of TSVCIS and MELPe speech coder data is described in detail.
Document record
- Document ID
- RFC8817
- Published
- August 2020
- Authors
- V. Demjanenko; J. Punaro; D. Satterlee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8130RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) CodecCurrent
March 2017
- RFC 8423Reclassification of Suite B Documents to Historic StatusCurrent
July 2018
- RFC 5008Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME)Obsoleted
September 2007
- RFC 8825Overview: Real-Time Protocols for Browser-Based ApplicationsCurrent
January 2021
- RFC 8826Security Considerations for WebRTCCurrent
January 2021
- RFC 8827WebRTC Security ArchitectureCurrent
January 2021
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
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?