RFC 5167: Media Server Control Protocol Requirements
In plain English — editorial summary, not part of the RFC
This document addresses the communication between an application server and media server. The current work in IETF working groups shows these logical entities, but it does not address the physical decomposition and the protocol between the entities. This document presents the requirements for a Media Server Control Protocol (MCP) that enables an application server to use a media server. It will address the aspects of announcements, Interactive Voice Response, and conferencing media services. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5167
- Published
- March 2008
- Authors
- M. Dolly; R. Even
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5188RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B CodecCurrent
February 2008
- RFC 5140A Telephony Gateway REgistration Protocol (TGREP)Current
March 2008
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
- RFC 5196Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)Current
September 2008
- RFC 5133Terminal Endpoint Identifier (TEI) Query Request Number ChangeCurrent
December 2007
- RFC 5124Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)Current
February 2008
- RFC 5215RTP Payload Format for Vorbis Encoded AudioCurrent
August 2008
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?