Skip to main content

Connected Identity for STIR

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Jon Peterson , Chris Wendt
Last updated 2022-01-13 (Latest revision 2021-07-12)
Replaced by draft-ietf-stir-rfc4916-update
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-stir-rfc4916-update
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The SIP Identity header conveys cryptographic identity information about the originators of SIP requests. The Secure Telephone Identity Revisited (STIR) framework however provides no means for determining the identity of the called party in a traditional telephone calling scenario. This document updates prior guidance on the "connected identity" problem to reflect the changes to SIP Identity that accompanied STIR, and 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, as well as the spoofing of mid-dialog or dialog-terminating events by intermediaries or third parties.


Jon Peterson
Chris Wendt

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)