RFC 8225: PASSporT: Personal Assertion Token
In plain English — editorial summary, not part of the RFC
This document defines a method for creating and validating a token that cryptographically verifies an originating identity or, more generally, a URI or telephone number representing the originator of personal communications. The Personal Assertion Token, PASSporT, is cryptographically signed to protect the integrity of the identity of the originator and to verify the assertion of the identity information at the destination. The cryptographic signature is defined with the intention that it can confidently verify the originating persona even when the signature is sent to the destination party over an insecure channel. PASSporT is particularly useful for many personal-communications applications over IP networks and other multi-hop interconnection scenarios where the originating and destination parties may not have a direct trusted relationship.
Document record
- Document ID
- RFC8225
- Published
- February 2018
- Authors
- C. Wendt; J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 25
- Also known as
- —
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 8226Secure Telephone Identity Credentials: CertificatesUpdated
February 2018
- RFC 8217Clarifications for When to Use the name-addr Production in SIP MessagesCurrent
August 2017
- RFC 8251Updates to the Opus Audio CodecCurrent
October 2017
- RFC 8197A SIP Response Code for Unwanted CallsCurrent
July 2017
- RFC 8254Uniform Resource Name (URN) Namespace Registration TransitionCurrent
October 2017
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 8259The JavaScript Object Notation (JSON) Data Interchange FormatCurrent
December 2017
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?