RFC 9060: Secure Telephone Identity Revisited (STIR) Certificate Delegation
In plain English — editorial summary, not part of the RFC
The Secure Telephone Identity Revisited (STIR) certificate profile provides a way to attest authority over telephone numbers and related identifiers for the purpose of preventing telephone number spoofing. This specification details how that authority can be delegated from a parent certificate to a subordinate certificate. This supports a number of use cases, including those where service providers grant credentials to enterprises or other customers capable of signing calls with STIR.
Document record
- Document ID
- RFC9060
- Published
- September 2021
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8224Authenticated Identity Management in the Session Initiation Protocol (SIP)Updated
February 2018
- RFC 7375Secure Telephone Identity Threat ModelCurrent
October 2014
- RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent
September 2014
- RFC 8396Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and FrameworkCurrent
July 2018
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 3709Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesObsoleted
February 2004
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
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?