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

Document Type Active Internet-Draft (sipcore WG)
Last updated 2019-02-03
Replaces draft-burger-sipcore-rejected
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
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                                B. Nagda
Expires: August 7, 2019            Massachusetts Institute of Technology
                                                        February 3, 2019

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

Abstract

   This document defines the 608 (Rejected) SIP response code.  This
   response code enables calling parties to learn that 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
   also defines the use of the Call-Info header in 608 responses to
   enable rejected callers to contact entities that blocked their calls
   in error.  This provides a remediation mechanism for legal callers
   that find their calls blocked.

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

Burger & Nagda           Expires August 7, 2019                 [Page 1]
Internet-Draft               Status Rejected               February 2019

Copyright Notice

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