RFC 3968: The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document creates an Internet Assigned Number Authority (IANA) registry for the Session Initiation Protocol (SIP) header field parameters and parameter values. It also lists the already existing parameters and parameter values to be used as the initial entries for this registry. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3968
- Published
- December 2004
- Authors
- G. Camarillo
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 8
- Also known as
- BCP98
- Updates:
- RFC 3427
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)Updated
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
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 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?