RFC 5567: An Architectural Framework for Media Server Control
In plain English — editorial summary, not part of the RFC
This document describes an architectural framework for Media Server control. The primary focus will be to define logical entities that exist within the context of Media Server control, and define the appropriate naming conventions and interactions between them. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5567
- Published
- June 2009
- Authors
- T. Melanchuk
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 25
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5574RTP Payload Format for the Speex CodecCurrent
June 2009
- RFC 5577RTP Payload Format for ITU-T Recommendation G.722.1Current
July 2009
- RFC 5580Carrying Location Objects in RADIUS and DiameterUpdated
August 2009
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5589Session Initiation Protocol (SIP) Call Control - TransferCurrent
June 2009
- RFC 5606Implications of 'retransmission-allowed' for SIP Location ConveyanceCurrent
August 2009
- RFC 5527Combined User and Infrastructure ENUM in the e164.arpa TreeCurrent
May 2009
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?