Session Initiation Protocol (SIP) Call Flow Examples with PASSporT Diversion and History-Info
draft-barnes-stir-passport-div-hi-callflows-02

Document Type Active Internet-Draft (individual)
Last updated 2018-10-23
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
STIR                                                           M. Barnes
Internet-Draft                                                 iconectiv
Intended status: Informational                          October 22, 2018
Expires: April 25, 2019

   Session Initiation Protocol (SIP) Call Flow Examples with PASSporT
                       Diversion and History-Info
             draft-barnes-stir-passport-div-hi-callflows-02

Abstract

   This document focuses on use cases and call flows which include the
   History-Info header field and a SIP Identity header field with a
   PASSport with a "div" claim in cases of retargeting.  These use cases
   are derived from those provided in the SIP History-Info call flows
   document.  The objective is to describe the optimal way to correlate
   the History-Info header fields with a PASSporT with diversion
   information to increase the level of confidence in the History-Info
   header field by the terminating entity making use of the information.

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

Barnes                   Expires April 25, 2019                 [Page 1]
Internet-Draft  PASSporT Div and History-Info Call Flows    October 2018

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   2
   3.  Detailed call flows . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  PBX Voicemail Example . . . . . . . . . . . . . . . . . .   3
     3.2.  Consumer Voicemail Example  . . . . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  Acknowledgements  . . . . . . . . . . . . . . . . . . . .  16
   6.  Informative References  . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Overview

   Many services that use SIP require the ability to determine why and
   how the call arrived at a specific application.  The use cases
   provided in [RFC7131] illustrate the use of the History-Info header
   field [RFC7044] for example applications and common scenarios.  The
   document [I-D.ietf-stir-passport-divert] extends the PASSporT,
   defined in [RFC8225] to cryptographically-sign the calling party
   information, to include an indication that a call has been diverted
   from its original destination to a new one.  This document discusses
   the applicability and use of this PASSporT extension for diverted
   calls in the context of scenarios for which use of the History-Info
   header field is essential for processing by the terminating entity.
   Descriptions of the example use cases, call flow diagrams and
   messaging details including both History-Info header field and a SIP
   Identity header field with a PASSport capturing the retargeted
   identity are provided.

2.  Conventions and Terminology

   The term "retarget" is used as defined in [RFC7044].  The term
   "divert" refers to a specific type of retargeting and is used per the
   context in [I-D.ietf-stir-passport-divert].  The terms "location
   service", "redirect" and "address-of-record (AOR)" are used
   consistent with the terminology in [RFC3261].

Barnes                   Expires April 25, 2019                 [Page 2]
Internet-Draft  PASSporT Div and History-Info Call Flows    October 2018

3.  Detailed call flows

   The scenarios in this section provide sample use cases for the
   History-Info header along with a PASSporT(s) containing the
   retargeted identity for informational purposes only.  They are not
Show full document text