RFC 8816: Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use Cases
In plain English — editorial summary, not part of the RFC
The Personal Assertion Token (PASSporT) format defines a token that can be carried by signaling protocols, including SIP, to cryptographically attest the identity of callers. However, not all telephone calls use Internet signaling protocols, and some calls use them for only part of their signaling path, while some cannot reliably deliver SIP header fields end-to-end. This document describes use cases that require the delivery of PASSporT objects outside of the signaling path, and defines architectures and semantics to provide this functionality.
Document record
- Document ID
- RFC8816
- Published
- February 2021
- Authors
- E. Rescorla; J. Peterson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
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?