RFC 5239: A Framework for Centralized Conferencing
In plain English — editorial summary, not part of the RFC
This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part (ISUP), to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5239
- Published
- June 2008
- Authors
- M. Barnes; C. Boulton; O. Levin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 57
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5244Definition of Events for Channel-Oriented Telephony SignallingCurrent
June 2008
- RFC 5219A More Loss-Tolerant RTP Payload Format for MP3 AudioCurrent
February 2008
- RFC 5261An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) SelectorsCurrent
September 2008
- RFC 5262Presence Information Data Format (PIDF) Extension for Partial PresenceCurrent
September 2008
- RFC 5215RTP Payload Format for Vorbis Encoded AudioCurrent
August 2008
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 5264Publication of Partial Presence InformationCurrent
September 2008
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 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?