RFC 6501: Conference Information Data Model for Centralized Conferencing (XCON)
In plain English — editorial summary, not part of the RFC
RFC 5239 defines centralized conferencing (XCON) as an association of participants with a central focus. The state of a conference is represented by a conference object. This document defines an XML- based conference information data model to be used for conference objects. A conference information data model is designed to convey information about the conference and about participation in the conference. The conference information data model defined in this document constitutes an extension of the data format specified in the Session Initiation Protocol (SIP) event package for conference State. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6501
- Published
- March 2012
- Authors
- O. Novo; G. Camarillo; D. Morgan; J. Urpalainen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 94
- Also known as
- —
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 6503Centralized Conferencing Manipulation ProtocolCurrent
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 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?