RFC 4485: Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) is a flexible yet simple tool for establishing interactive communications sessions across the Internet. Part of this flexibility is the ease with which it can be extended. In order to facilitate effective and interoperable extensions to SIP, some guidelines need to be followed when developing SIP extensions. This document outlines a set of such guidelines for authors of SIP extensions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4485
- Published
- May 2006
- Authors
- J. Rosenberg; H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4484Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)Current
August 2006
- RFC 4483A Mechanism for Content Indirection in Session Initiation Protocol (SIP) MessagesCurrent
May 2006
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 4488Suppression of Session Initiation Protocol (SIP) REFER Method Implicit SubscriptionCurrent
May 2006
- RFC 4481Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time IntervalsCurrent
July 2006
- RFC 4480RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)Current
July 2006
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 4475Session Initiation Protocol (SIP) Torture Test MessagesCurrent
May 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?