A SIP Response Code for Unwanted Calls
draft-ietf-sipcore-status-unwanted-06

Document Type Active Internet-Draft (sipcore WG)
Last updated 2017-06-15 (latest revision 2017-05-10)
Replaces draft-schulzrinne-dispatch-status-unwanted
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jan 2017 - Request publication ... )
Document shepherd Adam Roach
Shepherd write-up Show (last changed 2017-03-02)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to "Adam Roach" <adam@nostrum.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
SIPCORE                                                   H. Schulzrinne
Internet-Draft                                                       FCC
Intended status: Standards Track                             May 8, 2017
Expires: November 9, 2017

                 A SIP Response Code for Unwanted Calls
                 draft-ietf-sipcore-status-unwanted-06

Abstract

   This document defines the 607 (Unwanted) SIP response code, allowing
   called parties to indicate that the call or message was unwanted.
   SIP entities may use this information to adjust how future calls from
   this calling party are handled for the called party or more broadly.

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 http://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 November 9, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Schulzrinne             Expires November 9, 2017                [Page 1]
Internet-Draft               Status Unwanted                    May 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Normative Language  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Behavior of SIP Entities  . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  SIP Response Code . . . . . . . . . . . . . . . . . . . .   5
     5.2.  SIP Global Feature-Capability Indicator . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   In many countries, an increasing number of calls are unwanted
   [RFC5039]: they might be fraudulent, illegal telemarketing or the
   receiving party does not want to be disturbed by, say, surveys or
   solicitation by charities.  Carriers and other service providers may
   want to help their subscribers avoid receiving such calls, using a
   variety of global or user-specific filtering algorithms.  One input
   into such algorithms is user feedback.  User feedback may be offered
   through smartphone apps, APIs or within the context of a SIP-
   initiated call.  This document addresses feedback within the SIP
   call.  Here, the called party either rejects the SIP [RFC3261]
   request as unwanted or terminates the session with a BYE request
   after answering the call.  INVITE and MESSAGE requests are most
   likely to trigger such a response.

   To allow the called party to express that the call was unwanted, this
   document defines the 607 (Unwanted) response code.  The user agent of
   the called party, based on input from the called party or some UA-
   internal logic, uses this to indicate that this call is unwanted and
   that future attempts are likely to be similarly rejected.  While
   factors such as identity spoofing and call forwarding may make
   authoritative identification of the calling party difficult or
   impossible, the network can use such a rejection -- possibly combined
   with a pattern of rejections by other callees and/or other
   information -- as input to a heuristic algorithm for determining
   future call treatment.  The heuristic processing and possible
Show full document text