RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data
In plain English — editorial summary, not part of the RFC
This document extends Personal Assertion Token (PASSporT), a token for conveying cryptographically signed call information about personal communications, to include rich metadata about a call and caller that can be signed and integrity protected, transmitted, and subsequently rendered to the called party. This framework is intended to include and extend caller- and call-specific information beyond human-readable display name, comparable to the "Caller ID" function common on the telephone network. It is also enhanced with an integrity mechanism that is designed to protect the authoring and transport of this information for different authoritative use cases.
Document record
- Document ID
- RFC9795
- Published
- July 2025
- Authors
- C. Wendt; J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9796SIP Call-Info Parameters for Rich Call DataCurrent
July 2025
- RFC 9410Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)Current
July 2023
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 9967System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)Current
May 2026
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 7643System for Cross-domain Identity Management: Core SchemaUpdated
September 2015
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?