RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks

This document describes private extensions to SIP that enable a network of trusted SIP servers to assert the identity of authenticated users, and…

Read RFC 3325 on the RFC Editor

Incoming relationships (30 related RFCs)

Updated by — RFC 8217: Clarifications for When to Use the name-addr Production in SIP Messages
Updated by, Normatively referenced by — RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5009: Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media
Normatively referenced by — RFC 5370: The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
Normatively referenced by — RFC 5379: Guidelines for Using the Privacy Mechanism for SIP
Normatively referenced by — RFC 5502: The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem
Normatively referenced by — RFC 9970: Connected Identity for Secure Telephone Identity Revisited (STIR)
Informatively referenced by — RFC 6973: Privacy Considerations for Internet Protocols
Informatively referenced by — RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)
Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 4412: Communications Resource Priority for the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
Informatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Informatively referenced by — RFC 5025: Presence Authorization Rules
Informatively referenced by — RFC 5039: The Session Initiation Protocol (SIP) and Spam
Informatively referenced by — RFC 5767: User-Agent-Driven Privacy Mechanism for SIP
Informatively referenced by — RFC 7701: Multi-party Chat Using the Message Session Relay Protocol (MSRP)
Informatively referenced by — RFC 7865: Session Initiation Protocol (SIP) Recording Metadata
Informatively referenced by — RFC 7866: Session Recording Protocol
Informatively referenced by — RFC 5947: Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6404: Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested Countermeasures
Informatively referenced by — RFC 6910: Completion of Calls for the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 8876: Non-interactive Emergency Calls
Informatively referenced by — RFC 5079: Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5373: Requesting Answering Modes for the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5629: A Framework for Application Interaction in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 7433: A Mechanism for Transporting User-to-User Call Control Information in SIP
Informatively referenced by — RFC 7549: 3GPP SIP URI Inter-Operator Traffic Leg Parameter
Informatively referenced by — RFC 8496: P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data