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

Document Type Active Internet-Draft (stir WG)
Authors Chris Wendt  , Jon Peterson 
Last updated 2021-02-22
Replaces draft-peterson-stir-cnam
Stream Internent Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call (wg milestone: Nov 2019 - Submit PASSPorT Exte... )
Revised I-D Needed - Issue raised by WG
On Agenda stir at IETF-110
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           C. Wendt
Internet-Draft                                                   Comcast
Intended status: Standards Track                             J. Peterson
Expires: August 26, 2021                                    Neustar Inc.
                                                       February 22, 2021

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

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
   generating 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 August 26, 2021.

Wendt & Peterson         Expires August 26, 2021                [Page 1]
Internet-Draft                     RCD                     February 2021

Copyright Notice

   Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . . . . . .   7
       5.1.2.  "jcd" key . . . . . . . . . . . . . . . . . . . . . .   7
       5.1.3.  "jcl" key . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  "rcdi" RCD Integrity Claim  . . . . . . . . . . . . . . .   8
       5.2.1.  Creation of the "rcd" element digests . . . . . . . .   9
       5.2.2.  JWT Claim Constraint for "rcd" claims only  . . . . .  12
       5.2.3.  JWT Claim Constraint for "rcd" and "rcdi" claims  . .  12
     5.3.  PASSporT "crn" claim - Call Reason  . . . . . . . . . . .  13
       5.3.1.  JWT Constraint for "crn" claim  . . . . . . . . . . .  13
   6.  "rcd" and "crn" Claims Usage  . . . . . . . . . . . . . . . .  13
     6.1.  Example "rcd" PASSporTs . . . . . . . . . . . . . . . . .  14
   7.  Compact form of "rcd" PASSporT  . . . . . . . . . . . . . . .  15
     7.1.  Compact form of the "rcd" PASSporT claim  . . . . . . . .  15
     7.2.  Compact form of the "rcdi" PASSporT claim . . . . . . . .  16
     7.3.  Compact form of the "crn" PASSporT claim  . . . . . . . .  16
   8.  Further Information Associated with Callers . . . . . . . . .  16
   9.  Third-Party Uses  . . . . . . . . . . . . . . . . . . . . . .  17
     9.1.  Signing as a Third Party  . . . . . . . . . . . . . . . .  18
   10. Levels of Assurance . . . . . . . . . . . . . . . . . . . . .  19
   11. Using "rcd" in SIP  . . . . . . . . . . . . . . . . . . . . .  19
Show full document text