RFC 6230: Media Control Channel Framework
In plain English — editorial summary, not part of the RFC
This document describes a framework and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The framework uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between application servers and associated external servers such as media servers. The motivation for the creation of this framework is to provide an interface suitable to meet the requirements of a centralized conference system, where the conference system can be distributed, as defined by the XCON working group in the IETF. It is not, however, limited to this scope. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6230
- Published
- May 2011
- Authors
- C. Boulton; T. Melanchuk; S. McGlashan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 49
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6231An Interactive Voice Response (IVR) Control Package for the Media Control Channel FrameworkUpdated
May 2011
- RFC 6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration InformationCurrent
July 2011
- RFC 6222Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)Obsoleted
April 2011
- RFC 6271Requirements for SIP-Based Session PeeringCurrent
June 2011
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 6184RTP Payload Format for H.264 VideoCurrent
May 2011
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 2011
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?