RFC 9410: Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)
In plain English — editorial summary, not part of the RFC
This document extends the current error-handling procedures for mapping of verification failure reasons to 4xx codes for Secure Telephone Identity Revisited (STIR) and the Authenticated Identity Management in the Session Initiation Protocol (SIP). It extends the ability to use the Reason header field as an option for conveying an error associated with an Identity header field to the upstream authentication service when local policy dictates that the call should continue in the presence of a verification failure. This document also defines procedures that enable a failure reason to be mapped to a specific Identity header field for scenarios that use multiple Identity header fields, where some may have errors and others may not. The handling of those situations is also defined.
Document record
- Document ID
- RFC9410
- Published
- July 2023
- Authors
- C. Wendt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9027Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services NetworksCurrent
June 2021
- RFC 9795Personal Assertion Token (PASSporT) Extension for Rich Call DataCurrent
July 2025
- RFC 9796SIP Call-Info Parameters for Rich Call DataCurrent
July 2025
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 9967System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)Current
May 2026
- RFC 8417Security Event Token (SET)Current
July 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?