PASSporT Extension for Rich Call Data
draft-ietf-stir-passport-rcd-08

The information below is for an old version of the document
Document Type Active Internet-Draft (stir WG)
Authors Jon Peterson  , Chris Wendt 
Last updated 2020-11-16
Replaces draft-peterson-stir-cnam
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Nov 2019 - Submit PASSPorT Exte... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Peterson
Internet-Draft                                              Neustar Inc.
Intended status: Standards Track                                C. Wendt
Expires: May 20, 2021                                            Comcast
                                                       November 16, 2020

                 PASSporT Extension for Rich Call Data
                    draft-ietf-stir-passport-rcd-08

Abstract

   This document extends PASSporT, a token for conveying
   cryptographically-signed call information about personal
   communications, to include rich meta-data about a call and caller
   that can be signed and integrity protected, transmitted, and
   subsequently rendered to users.  This framework is intended to extend
   caller and call specific information beyond human-readable display
   name comparable to the "Caller ID" function common on the telephone
   network.  The JSON element defined for this purpose, Rich Call Data
   (RCD), is an extensible object defined to either be used as part of
   STIR or with SIP Call-Info to include related information about calls
   that helps people decide whether to pick up the phone.  This signing
   of the RCD information is also enhanced with a integrity mechanism
   that is designed to protect the authoring and transport of this
   information between authoritative and non-authoritative parties
   authoring and signing the Rich Call Data for support of different
   usage and content policies.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 20, 2021.

Peterson & Wendt          Expires May 20, 2021                  [Page 1]
Internet-Draft                     RCD                     November 2020

Copyright Notice

   Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview of the use of the Rich Call Data PASSporT extension    4
   4.  Overview of Rich Call Data integrity  . . . . . . . . . . . .   5
   5.  PASSporT Claims . . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  PASSporT "rcd" Claim  . . . . . . . . . . . . . . . . . .   6
       5.1.1.  "nam" key . . . . . . . . . . . . . . . . . . . . . .   6
       5.1.2.  "jcd" key . . . . . . . . . . . . . . . . . . . . . .   6
       5.1.3.  "jcl" key . . . . . . . . . . . . . . . . . . . . . .   6
       5.1.4.  "rcdi" RCD integrity Claim  . . . . . . . . . . . . .   7
       5.1.5.  Creation of the "rcd" digest  . . . . . . . . . . . .   7
       5.1.6.  JWT Constraint for "rcdi" claim . . . . . . . . . . .   9
     5.2.  PASSporT "crn" claim - Call Reason  . . . . . . . . . . .   9
       5.2.1.  JWT Constraint for "cdn" claim  . . . . . . . . . . .   9
   6.  "rcd" and "crn" Claims Usage  . . . . . . . . . . . . . . . .   9
     6.1.  Example "rcd" PASSporTs . . . . . . . . . . . . . . . . .  10
   7.  Compact form of "rcd" PASSporT  . . . . . . . . . . . . . . .  12
     7.1.  Compact form of the "rcd" PASSporT claim  . . . . . . . .  12
     7.2.  Compact form of the "rcdi" PASSporT claim . . . . . . . .  12
     7.3.  Compact form of the "crn" PASSporT claim  . . . . . . . .  12
   8.  Further Information Associated with Callers . . . . . . . . .  13
   9.  Third-Party Uses  . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Signing as a Third Party  . . . . . . . . . . . . . . . .  15
   10. Levels of Assurance . . . . . . . . . . . . . . . . . . . . .  15
   11. Using "rcd" in SIP  . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Authentication Service Behavior  . . . . . . . . . . . .  16
Show full document text