RFC 3840: Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This specification defines mechanisms by which a Session Initiation Protocol (SIP) user agent can convey its capabilities and characteristics to other user agents and to the registrar for its domain. This information is conveyed as parameters of the Contact header field. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3840
- Published
- August 2004
- Authors
- J. Rosenberg; H. Schulzrinne; P. Kyzivat
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3842A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
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?