A Session Initiation Protocol (SIP) Response Code for Rejected Calls
draft-ietf-sipcore-rejected-02

The information below is for an old version of the document
Document Type Active Internet-Draft (sipcore WG)
Last updated 2018-12-28
Replaces draft-burger-sipcore-rejected
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
SIPCORE                                                        E. Burger
Internet-Draft                                     Georgetown University
Intended status: Standards Track                       December 28, 2018
Expires: July 1, 2019

  A Session Initiation Protocol (SIP) Response Code for Rejected Calls
                     draft-ietf-sipcore-rejected-02

Abstract

   This document defines the 608 (Rejected) SIP response code.  This
   response code enables calling parties to learn an intermediary
   rejected their call attempt.  The call will not be answered.  As a
   6xx code, the caller will be aware that future attempts to contact
   the same UAS will likely fail.  The present use case driving the need
   for the 608 response code is when the intermediary is an analytics
   engine.  In this case, the rejection is by a machine or other
   process.  This contrasts with the 607 (Unwanted) SIP response code,
   which a human at the target UAS indicated the call was not wanted.
   In some jurisdictions this distinction is important.  This document
   defines the use of the Call-Info header in 608 responses to enable
   rejected callers to contact entities that blocked their calls in
   error.

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 July 1, 2019.

Copyright Notice

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

Burger                    Expires July 1, 2019                  [Page 1]
Internet-Draft               Status Rejected               December 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Protocol Operation  . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Intermediary Operation  . . . . . . . . . . . . . . . . .   7
     3.2.  jCard Construction  . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  JOSE Header . . . . . . . . . . . . . . . . . . . . .   8
       3.2.2.  JWT Payload . . . . . . . . . . . . . . . . . . . . .   8
       3.2.3.  JWS Signature . . . . . . . . . . . . . . . . . . . .   8
     3.3.  UAC Operation . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Legacy Interoperation . . . . . . . . . . . . . . . . . .   9
     3.5.  Announcement Requirements . . . . . . . . . . . . . . . .  10
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Full Exchange . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Web Site jCard  . . . . . . . . . . . . . . . . . . . . .  14
     4.3.  Multi-modal jCard . . . . . . . . . . . . . . . . . . . .  14
     4.4.  Legacy Interoperability . . . . . . . . . . . . . . . . .  15
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  SIP Response Code . . . . . . . . . . . . . . . . . . . .  16
     5.2.  SIP Feature-Capability Indicator  . . . . . . . . . . . .  16
     5.3.  JSON Web Token Claim  . . . . . . . . . . . . . . . . . .  17
     5.4.  Call-Info Purpose . . . . . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  19
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   The IETF has been addressing numerous issues surrounding how to
   handle unwanted and, depending on the jurisdiction, illegal calls
   [RFC5039].  Technologies such as STIR [RFC7340] and SHAKEN [SHAKEN]
Show full document text