draft-sip-identity-confusion-bcp
Mitigating SIP Identity Spoofing Caused by Semantic Ambiguities
The Session Initiation Protocol (SIP) carries originator identity
through multiple header fields --- From, P-Asserted-Identity, P-
Preferred-Identity, Remote-Party-ID, Identity and so on --- whose
processing is spread across several specifications. Because these
mechanisms leave significant room for implementation choice, SIP
servers and user agents frequently disagree on which identity signal
to trust and how to parse it. Recent research has demonstrated that
these semantic ambiguities enable caller-ID and message-origin
spoofing in the majority of tested server-client combinations, even
when TLS and authentication are correctly deployed.
This document provides best current practices for mitigating identity
spoofing caused by such ambiguities. It defines identity-validation
rules at each stage of the SIP signaling path, from the originating
server through trust boundaries and transit proxies to the receiving
user agent, and includes guidance on deployment, migration, and
interoperability with legacy systems.