Description
Secure Telephone Identity Revisited (STIR) is a comprehensive 3GPP and IETF standards framework designed to restore trust in caller identification by preventing the spoofing of calling line identification (CLI). At its core, STIR provides a mechanism for originating networks to cryptographically sign the identity of the caller (the telephone number) and for terminating networks to verify that signature before presenting the call to the called party. The architecture is based on a decentralized trust model where Authentication Services (ATS) in the originating network and Verification Services (VS) in the terminating network perform the key operations.
The technical workflow begins when a call is initiated. In the originating network, a STIR-enabled entity (like an S-CSCF or a dedicated STIR Authentication Service) creates a digital identity token called a PASSporT (Personal Assertion Token). This token contains critical claims: the calling party's number (orig), the called party's number (dest), the time of issuance (iat), and a unique call identifier. This token is then signed using a private key associated with the originating service provider's domain. The signed PASSporT is inserted into the SIP INVITE request, typically within the Identity header as defined in RFC 8224.
As the SIP INVITE traverses networks towards the destination, the terminating network's STIR Verification Service extracts the PASSporT. To verify the signature, the VS performs a series of steps. It first determines the appropriate public key required for verification. This is done by querying a public key infrastructure, specifically using the Telephone Identity (TEL) URI of the caller to discover a corresponding Secure Telephone Identity Governance Authority (STI-GA) and then a Certificate Repository Service (CRS) to retrieve the public key certificate of the originating provider. Upon successful signature verification, the VS confirms that the caller ID has not been altered in transit and that it was attested by a trusted originating network. The verification result (e.g., "verstat: TN-Validation-Passed") is then added to the SIP signaling, allowing the terminating UE or network to apply appropriate handling, such as displaying a verified checkmark or prioritizing the call.
Purpose & Motivation
STIR was created to combat the escalating global problem of caller ID spoofing, which fuels spam, fraud (like vishing and Wangiri fraud), and robocalls. The traditional SS7 and SIP signaling systems used in telephony networks had no inherent security mechanism to validate the source of caller ID information. Malicious actors could easily inject false numbers into the "From" header, leading to widespread consumer distrust in the telephone network. This eroded the utility of voice services and caused significant financial and privacy harms.
The framework, initially developed by the IETF and later adopted and profiled by 3GPP starting in Release 17, was motivated by regulatory pressure and industry need for a technical solution. It addresses the limitations of previous, often proprietary, call-filtering solutions by providing an end-to-end cryptographic verification standard that works across administrative and technological boundaries (e.g., between different carriers, between IP and TDM networks). STIR establishes a chain of trust where service providers vouch for the numbers they assign to their subscribers. Its "Revisited" designation distinguishes it from earlier, less comprehensive attempts at secure caller ID. By enabling verified caller ID, STIR aims to restore confidence in voice communications, empower users to make informed answering decisions, and provide a foundation for richer, trusted communication services.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the STIR function was integrated within a broader framework for caller identity analytics, which now formally encompasses STIR/SHAKEN verification results. This integration was detailed through stage 2 work items that provided clarifications and specifications for IMS due to the introduction of STIR/SHAKEN alongside related services like RCD and eCNAM.
In Release 18, the STIR/SHAKEN updates focused on corrections and alignment, including diagram fixes and resolving a non-occurring scenario. The enhancements also addressed the handling of intra-CSP sessions and the CSP's selection of a Telephony Application Server. These changes ensured better specification consistency and operational clarity for the STIR verification function within Caller Identity Analytics.
In Release 19, the update to the STIR function was an editorial update specifically for its application to messaging, as detailed by incorporating the latest RFC 9475 within the STIR/SHAKEN framework. This change refined the normative references and descriptive text for the STIR/SHAKEN procedures used for verifying caller identity in messaging contexts. The update ensures the specification aligns with the current IETF standards for signature-based handling of asserted identity information.
- Editorial update of RFC 9475 in clause E.2.3 STIR/SHAKEN for messaging TS 33.127CR0254
Explore further
Broader topics and technologies where STIR plays a role.
Defining Specifications
3GPP specifications that define or reference STIR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.173 vk00 | IMS Multimedia Telephony Service Definition | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |