[stir] RFC 9410 on Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)

A new Request for Comments is now available in online RFC libraries.

        RFC 9410

        Title:      Handling of Identity Header Errors for
                    Secure Telephone Identity Revisited (STIR) 
        Author:     C. Wendt
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2023
        Mailbox:    chris-ietf@chriswendt.net
        Pages:      7
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-stir-identity-header-errors-handling-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9410

        DOI:        10.17487/RFC9410

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.

This document is a product of the Secure Telephone Identity Revisited Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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
Association Management Solutions, LLC