RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines new functionality for negotiating the security mechanisms used between a Session Initiation Protocol (SIP) user agent and its next-hop SIP entity. This new functionality supplements the existing methods of choosing security mechanisms between SIP entities.
Document record
- Document ID
- RFC3329
- Published
- January 2003
- Authors
- J. Arkko; V. Torvinen; G. Camarillo; A. Niemi; T. Haukka
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 24
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3326The Reason Header Field for the Session Initiation Protocol (SIP)Updated
December 2002
- RFC 3323A Privacy Mechanism for the Session Initiation Protocol (SIP)Current
December 2002
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
- RFC 3312Integration of Resource Management and Session Initiation Protocol (SIP)Updated
October 2002
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?