RFC 8946: Personal Assertion Token (PASSporT) Extension for Diverted Calls
In plain English — editorial summary, not part of the RFC
The Personal Assertion Token (PASSporT) is specified in RFC 8225 to convey cryptographically signed information about the people involved in personal communications. This document extends PASSporT to include an indication that a call has been diverted from its original destination to a new one. This information can greatly improve the decisions made by verification services in call forwarding scenarios. Also specified here is an encapsulation mechanism for nesting a PASSporT within another PASSporT that assists relying parties in some diversion scenarios. This document updates RFC 8224.
Document record
- Document ID
- RFC8946
- Published
- February 2021
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 8224
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8816Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use CasesCurrent
February 2021
- RFC 8688A Session Initiation Protocol (SIP) Response Code for Rejected CallsCurrent
December 2019
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 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?