RFC 6503: Centralized Conferencing Manipulation Protocol
In plain English — editorial summary, not part of the RFC
The Centralized Conferencing Manipulation Protocol (CCMP) allows a Centralized Conferencing (XCON) system client to create, retrieve, change, and delete objects that describe a centralized conference. CCMP is a means to control basic and advanced conference features such as conference state and capabilities, participants, relative roles, and details. CCMP is a stateless, XML-based, client server protocol that carries, in its request and response messages, conference information in the form of XML documents and fragments conforming to the centralized conferencing data model schema. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6503
- Published
- March 2012
- Authors
- M. Barnes; C. Boulton; S. Romano; H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 119
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6502Conference Event Package Data Format Extension for Centralized Conferencing (XCON)Current
March 2012
- RFC 6504Centralized Conferencing Manipulation Protocol (CCMP) Call Flow ExamplesCurrent
March 2012
- RFC 6505A Mixer Control Package for the Media Control Channel FrameworkCurrent
March 2012
- RFC 6501Conference Information Data Model for Centralized Conferencing (XCON)Current
March 2012
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6567Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIPCurrent
April 2012
- RFC 6406Session PEERing for Multimedia INTerconnect (SPEERMINT) ArchitectureCurrent
November 2011
- RFC 6405Voice over IP (VoIP) SIP Peering Use CasesCurrent
November 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?