RFC 8588: Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)
In plain English — editorial summary, not part of the RFC
This document extends the Personal Assertion Token (PASSporT), which is a token object that conveys cryptographically signed information about the participants involved in communications. The extension is defined based on the "Signature-based Handling of Asserted information using toKENs (SHAKEN)" specification by the ATIS/SIP Forum IP-NNI Task Group. It provides both (1) a specific set of levels of confidence in the correctness of the originating identity of a call originated in a SIP-based telephone network as well as (2) an identifier that allows the Service Provider (SP) to uniquely identify the origin of the call within its network.
Document record
- Document ID
- RFC8588
- Published
- May 2019
- Authors
- C. Wendt; M. Barnes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8580Sieve Extension: File Carbon Copy (FCC)Current
May 2019
- RFC 8579Sieve Email Filtering: Delivering to Special-Use MailboxesCurrent
May 2019
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- RFC 8606ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header FieldCurrent
June 2019
- RFC 8607Calendaring Extensions to WebDAV (CalDAV): Managed AttachmentsCurrent
June 2019
- RFC 8610Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data StructuresUpdated
June 2019
- RFC 8616Email Authentication for Internationalized MailCurrent
June 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?