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

        RFC 9888

        Title:      Out-of-Band Secure Telephone Identity Revisited (STIR) for 
Service Providers
        Author:     J. Peterson
        Status:     Proposed Standard
        Stream:     IETF
        Date:       June 2026
        Mailbox:    [email protected]
        Pages:      9


        I-D Tag:    draft-ietf-stir-servprovider-oob-08

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

        DOI:        10.17487/RFC9888

The Secure Telephone Identity Revisited (STIR) framework defines means of 
carrying its Personal Assertion Tokens (PASSporTs) either in-band, within the 
headers of a Session Initiation Protocol (SIP) request, or out-of-band, through 
a service that stores PASSporTs for retrieval by relying parties. This 
specification defines a way that the out-of-band conveyance of PASSporTs can be 
used to support large service providers for cases in which in-band STIR 
conveyance is not universally available.

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

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to