Skip to main content

PASSporT: Personal Assertion Token
RFC 8225

Revision differences

Document history

Date By Action
2018-06-15
(System) Received changes through RFC Editor sync (added Errata tag)
2018-02-16
(System) IANA registries were updated to include RFC8225
2018-02-14
(System)
Received changes through RFC Editor sync (created alias RFC 8225, changed title to 'PASSporT: Personal Assertion Token', changed abstract to 'This document defines a …
Received changes through RFC Editor sync (created alias RFC 8225, changed title to 'PASSporT: Personal Assertion Token', changed abstract to '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.', changed pages to 25, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-02-14, changed IESG state to RFC Published)
2018-02-14
(System) RFC published