The IESG has received a request from the Secure Telephone Identity Revisited WG (stir) to consider the following document: - 'Connected Identity for STIR' <draft-ietf-stir-rfc4916-update-06.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2024-11-19. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-stir-rfc4916-update/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc3375: Generic Registry-Registrar Protocol Requirements (Informational - Internet Engineering Task Force (IETF) stream) _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
