RFC 9970: Connected Identity for Secure Telephone Identity Revisited (STIR)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) Identity header field conveys cryptographic identity information about the originators of SIP requests. However, the Secure Telephone Identity Revisited (STIR) framework provides no means for determining the identity of the called party in a conventional telephone-calling scenario. This document updates prior guidance on the "connected identity" problem to reflect the changes to SIP identity that accompanied STIR. It also considers a revised problem space for connected identity as a means of detecting calls that have been retargeted to a party impersonating the intended destination and preventing the spoofing of mid-dialog or dialog-terminating events by intermediaries or third parties.
Document record
- Document ID
- RFC9970
- Published
- June 2026
- Authors
- J. Peterson; C. Wendt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 10006Automatic SIP Trunking and PeeringCurrent
August 2026
- RFC 9888Out-of-Band Secure Telephone Identity Revisited (STIR) for Service ProvidersCurrent
June 2026
- RFC 9475Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR)Current
December 2023
- RFC 9409The 'sip-trunking-capability' Link Relation TypeCurrent
July 2023
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- 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?