RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
In plain English — editorial summary, not part of the RFC
This document describes private extensions to SIP that enable a network of trusted SIP servers to assert the identity of authenticated users, and the application of existing privacy mechanisms to the identity problem. The use of these extensions is only applicable inside an administrative domain with previously agreed-upon policies for generation, transport and usage of such information. This document does NOT offer a general privacy or identity model suitable for use between different trust domains, or use in the Internet at large.
Document record
- Document ID
- RFC3325
- Published
- December 2002
- Authors
- C. Jennings; J. Peterson; M. Watson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5009Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early MediaCurrent
September 2007
- RFC 6050A Session Initiation Protocol (SIP) Extension for the Identification of ServicesCurrent
November 2010
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- 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 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
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?