RFC 4245: High-Level Requirements for Tightly Coupled SIP Conferencing
In plain English — editorial summary, not part of the RFC
This document examines a wide range of conferencing requirements for tightly coupled SIP conferences. Separate documents will map the requirements to existing protocol primitives, define new protocol extensions, and introduce new protocols as needed. Together, these documents will provide a guide for building interoperable SIP conferencing applications. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4245
- Published
- November 2005
- Authors
- O. Levin; R. Even
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)Updated
December 2004
- RFC 3968The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3959The Early Session Disposition Type for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3911The Session Initiation Protocol (SIP) "Join" HeaderCurrent
October 2004
- RFC 3903Session Initiation Protocol (SIP) Extension for Event State PublicationUpdated
November 2004
- RFC 3893Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) FormatCurrent
September 2004
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
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?