RFC 4313: Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) Resources
In plain English — editorial summary, not part of the RFC
This document outlines the needs and requirements for a protocol to control distributed speech processing of audio streams. By speech processing, this document specifically means automatic speech recognition (ASR), speaker recognition -- which includes both speaker identification (SI) and speaker verification (SV) -- and text-to-speech (TTS). Other IETF protocols, such as SIP and Real Time Streaming Protocol (RTSP), address rendezvous and control for generalized media streams. However, speech processing presents additional requirements that none of the extant IETF protocols address. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4313
- Published
- December 2005
- Authors
- D. Oran
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6787Media Resource Control Protocol Version 2 (MRCPv2)Current
November 2012
- RFC 4320Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
- RFC 4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
- RFC 4298RTP Payload Format for BroadVoice Speech CodecsCurrent
December 2005
- RFC 4348Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio CodecUpdated
January 2006
- RFC 4351Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio StreamCurrent
January 2006
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4353A Framework for Conferencing with the Session Initiation Protocol (SIP)Current
February 2006
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?