RFC 9970 on Connected Identity for Secure Telephone Identity Revisited (STIR)
rfc-editor@rfc-editor.org Mon, 29 June 2026 21:25 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from celery-6fb6b66788-xmtjs (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 607D410A3053E; Mon, 29 Jun 2026 14:25:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782768342; bh=r//rarAqn9eCImNzd0TGzRPabFqiYE7e1N++cBvAJok=; h=Subject:From:To:Cc:Date; b=mjpDLXimIfzIkUrOaSIcRHAClAuIbnpqEID2YwfEp3a008PHZmPLYEKls/HYUyFRj BqEomTx5ubX+NOBtoa5pMTK1nVOk4Td08k2ahsTkfKF3fp4DkHs37xowTXbfbP2FQt qhdFgLCo0PuaiO5b+pt9LRPuNnUEgfqObX4meaAA=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9970 on Connected Identity for Secure Telephone Identity Revisited (STIR)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Mon, 29 Jun 2026 21:25:42 -0000
message-id: <178276834228.15.16692154926595669906@rfc-editor.org>
Message-ID-Hash: 4PJBDT5VRJLQFK3VTHCABE2TXR6HTYPY
X-Message-ID-Hash: 4PJBDT5VRJLQFK3VTHCABE2TXR6HTYPY
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: stir@ietf.org, rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/_OOLDRtFjxdFmb2aNFF9UTGXwko>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
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: jon.peterson@transunion.com,
chris@appliedbits.com
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team