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

Document Type Active Internet-Draft (stir WG)
Last updated 2018-10-22
Replaces draft-peterson-stir-cnam
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Dec 2018 - 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: Informational                                  C. Wendt
Expires: April 25, 2019                                          Comcast
                                                        October 22, 2018

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

Abstract

   This document extends PASSporT, a token for conveying
   cryptographically-signed information about personal communications,
   to include rich data that can be rendered to users, such as a human-
   readable display name comparable to the "Caller ID" function common
   on the telephone network.  The element defined for this purpose is
   extensible to include related information about calls that helps
   people decide whether to pick up the phone.

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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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

Peterson & Wendt         Expires April 25, 2019                 [Page 1]
Internet-Draft              STIR Caller Name                October 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  PASSporT 'rcd' Claim  . . . . . . . . . . . . . . . . . . . .   3
   4.  Further Information Associated with Callers . . . . . . . . .   4
   5.  Third-Party Uses  . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Signing as a Third Party  . . . . . . . . . . . . . . . .   6
   6.  Levels of Assurance . . . . . . . . . . . . . . . . . . . . .   6
   7.  Using 'rcd' in SIP  . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Authentication Service Behavior . . . . . . . . . . . . .   7
     7.2.  Verification Service Behavior . . . . . . . . . . . . . .   7
   8.  Using 'rcd' as additional claims to other PASSporT extensions   8
     8.1.  Procedures for applying 'rcd' as claims only  . . . . . .   9
     8.2.  Example for applying 'rcd' as claims only . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  JSON Web Token Claim . . . . . . . . . . . . . . . . . .  10
     10.2.  PASSporT Types . . . . . . . . . . . . . . . . . . . . .  10
     10.3.  PASSporT RCD Types . . . . . . . . . . . . . . . . . . .  10
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   PASSporT [RFC8225] is a token format based on JWT [RFC7519] for
   conveying cryptographically-signed information about the people
   involved in personal communications; it is used to convey a signed
   assertion of the identity of the participants in real-time
   communications established via a protocol like SIP [RFC8224].  The
   STIR problem statement [RFC7340] declared securing the display name
   of callers outside of STIR's initial scope, so baseline STIR provides
   no features for caller name.  This specification documents an
   optional mechanism for PASSporT and the associated STIR mechanisms
   which extends PASSporT to carry additional elements conveying richer
   information: information that is intended to be rendered to an end
   user to assist a called party in determining whether to accept or
Show full document text