Skip to main content

Connected Identity for STIR
draft-ietf-stir-rfc4916-update-04

Document Type Expired Internet-Draft (stir WG)
Expired & archived
Authors Jon Peterson , Chris Wendt
Last updated 2024-05-02 (Latest revision 2023-10-23)
Replaces draft-peterson-stir-rfc4916-update
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Russ Housley
IESG IESG state Expired
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to housley@vigilsec.com

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

Abstract

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.

Authors

Jon Peterson
Chris Wendt

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