RFC 9475: Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR)
In plain English — editorial summary, not part of the RFC
Secure Telephone Identity Revisited (STIR) provides a means of attesting the identity of a telephone caller via a signed token in order to prevent impersonation of a calling party number, which is a key enabler for illegal robocalling. Similar impersonation is sometimes leveraged by bad actors in the text and multimedia messaging space. This document explores the applicability of STIR's Personal Assertion Token (PASSporT) and certificate issuance framework to text and multimedia messaging use cases, including support for both messages carried as a payload in SIP requests and messages sent in sessions negotiated by SIP.
Document record
- Document ID
- RFC9475
- Published
- December 2023
- Authors
- J. Peterson; C. Wendt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9409The 'sip-trunking-capability' Link Relation TypeCurrent
July 2023
- RFC 9888Out-of-Band Secure Telephone Identity Revisited (STIR) for Service ProvidersCurrent
June 2026
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 9970Connected Identity for Secure Telephone Identity Revisited (STIR)Current
June 2026
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 10006Automatic SIP Trunking and PeeringCurrent
August 2026
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
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?