Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)
RFC 8588

Document Type RFC - Proposed Standard (May 2019; No errata)
Last updated 2019-05-14
Replaces draft-wendt-stir-passport-shaken
Stream IETF
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Robert Sparks
Shepherd write-up Show (last changed 2018-10-18)
IESG IESG state RFC 8588 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to Robert Sparks <rjsparks@nostrum.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          C. Wendt
Request for Comments: 8588                                       Comcast
Category: Standards Track                                      M. Barnes
ISSN: 2070-1721                                                iconectiv
                                                                May 2019

   Personal Assertion Token (PaSSporT) Extension for Signature-based
         Handling of Asserted information using toKENs (SHAKEN)

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8588.

Wendt & Barnes               Standards Track                    [Page 1]
RFC 8588                         SHAKEN                         May 2019

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview of   "shaken" PASSporT Extension . . . . . . . . . .   4
   4.  PASSporT "attest" Claim . . . . . . . . . . . . . . . . . . .   4
   5.  PASSporT "origid" Claim . . . . . . . . . . . . . . . . . . .   4
   6.  Example "shaken" PASSporT . . . . . . . . . . . . . . . . . .   5
   7.  Using "shaken" in SIP . . . . . . . . . . . . . . . . . . . .   5
   8.  Order of Claim Keys . . . . . . . . . . . . . . . . . . . . .   5
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. Privacy Considerations  . . . . . . . . . . . . . . . . . . .   6
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  JSON Web Token claims  . . . . . . . . . . . . . . . . .   7
     11.2.  PASSporT Types . . . . . . . . . . . . . . . . . . . . .   7
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     12.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

Wendt & Barnes               Standards Track                    [Page 2]
RFC 8588                         SHAKEN                         May 2019

1.  Introduction

   The Signature-based Handling of Asserted information using toKENs
   (SHAKEN) [ATIS-1000074] specification defines a framework for using
   Secure Telephone Identity Revisited (STIR) protocols including the
   Personal Assertion Token (PASSporT) [RFC8225], SIP Authenticated
   Identity Management [RFC8224], and the STIR certificate framework
   [RFC8226] for implementing the cryptographic validation of an
   authorized originator of telephone calls using SIP.  Because the
   current telephone network contains traffic originated from both VoIP
   and TDM/SS7 (Time Division Multiplexing / Signaling System 7), there
   are many scenarios that need to be accounted for where PASSporT
   signatures may represent either direct or indirect call origination
   scenarios.  The SHAKEN [ATIS-1000074] specification defines levels of
   attestation of the origination of the call as well as an origination
Show full document text