RFC 4474: Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)

The existing security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the identity of the end users that…

Read RFC 4474 on the RFC Editor

Incoming relationships (35 related RFCs)

Obsoleted by, Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 4975: The Message Session Relay Protocol (MSRP)
Normatively referenced by — RFC 4662: A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
Normatively referenced by — RFC 4916: Connected Identity in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5853: Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
Normatively referenced by — RFC 7345: UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)
Normatively referenced by — RFC 5898: Connectivity Preconditions for Session Description Protocol (SDP) Media Streams
Normatively referenced by — RFC 6910: Completion of Calls for the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5079: Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5370: The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
Normatively referenced by — RFC 5373: Requesting Answering Modes for the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 6216: Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms
Normatively referenced by — RFC 7433: A Mechanism for Transporting User-to-User Call Control Information in SIP
Informatively referenced by — RFC 7201: Options for Securing RTP Sessions
Informatively referenced by — RFC 5922: Domain Certificates in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5630: The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6189: ZRTP: Media Path Key Agreement for Unicast Secure RTP
Informatively referenced by — RFC 5479: Requirements and Analysis of Media Security Management Protocols
Informatively referenced by — RFC 8842: Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
Informatively referenced by — RFC 5025: Presence Authorization Rules
Informatively referenced by — RFC 6714: Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)
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 5567: An Architectural Framework for Media Server Control
Informatively referenced by — RFC 7614: Explicit Subscriptions for the REFER Method
Informatively referenced by — RFC 7879: DTLS-SRTP Handling in SIP Back-to-Back User Agents
Informatively referenced by — RFC 8862: Best Practices for Securing RTP Media Signaled with SIP
Informatively referenced by — RFC 6337: Session Initiation Protocol (SIP) Usage of the Offer/Answer Model
Informatively referenced by — RFC 6404: Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested Countermeasures
Informatively referenced by — RFC 5379: Guidelines for Using the Privacy Mechanism for SIP
Informatively referenced by — RFC 5629: A Framework for Application Interaction in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6917: Media Resource Brokering
Informatively referenced by — RFC 9970: Connected Identity for Secure Telephone Identity Revisited (STIR)