A new Request for Comments is now available in online RFC libraries.

        RFC 9970

        Title:      Connected Identity for Secure Telephone Identity Revisited 
(STIR)
        Author:     J. Peterson,
                    C. Wendt
        Status:     Proposed Standard
        Stream:     IETF
        Date:       June 2026
        Mailbox:    [email protected],
                    [email protected]
        Pages:      13


        I-D Tag:    draft-ietf-stir-rfc4916-update-07

        URL:        https://www.rfc-editor.org/info/rfc9970

        DOI:        10.17487/RFC9970

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.

This document is a product of the Secure Telephone Identity Revisited Working 
Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to