RFC 4353: A Framework for Conferencing with the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) supports the initiation, modification, and termination of media sessions between user agents. These sessions are managed by SIP dialogs, which represent a SIP relationship between a pair of user agents. Because dialogs are between pairs of user agents, SIP's usage for two-party communications (such as a phone call), is obvious. Communications sessions with multiple participants, generally known as conferencing, are more complicated. This document defines a framework for how such conferencing can occur. This framework describes the overall architecture, terminology, and protocol components needed for multi-party conferencing. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4353
- Published
- February 2006
- Authors
- J. Rosenberg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 29
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4351Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio StreamCurrent
January 2006
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
- RFC 4348Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio CodecUpdated
January 2006
- RFC 4375Emergency Telecommunications Services (ETS) Requirements for a Single Administrative DomainCurrent
January 2006
- RFC 4376Requirements for Floor Control ProtocolsCurrent
February 2006
- RFC 4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
- RFC 4320Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
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?