<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC2119 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2397 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2397.xml">
<!ENTITY RFC3261 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3261.xml">
<!ENTITY RFC3326 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3326.xml">
<!ENTITY RFC3968 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3968.xml">
<!ENTITY RFC5039 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5039.xml">
<!ENTITY RFC6809 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6809.xml">
<!ENTITY rfc4474bis PUBLIC '' "http://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.ietf-stir-rfc4474bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="std" docName="draft-schulzrinne-dispatch-status-unwanted-00" ipr="trust200902">
    
    <!-- ***** FRONT MATTER ***** -->
    
    <front>
        <title abbrev="Status Unwanted">A SIP Response Code for Unwanted Calls</title>
        
        <!-- add 'role="editor"' below for the editors if appropriate -->
        
        <!-- Another author who claims to be an editor -->
        
        <author fullname="Henning Schulzrinne" initials="H."
            surname="Schulzrinne">
            <organization>FCC</organization>
            
            <address>
                <postal>
                    <street>450 12th Street SW</street>
                    <city>Washington</city>
                    <region>DC</region>
                    <code>20554</code>
                    <country>US</country>
                </postal>
                
                <phone></phone>
                
                <email>henning.schulzrinne@fcc.gov</email>
                
                <!-- uri and facsimile elements may also be added -->
            </address>
        </author>
        
        <date year="2016" />
        
        <!-- Meta-data Declarations -->
        
        <area>ART</area>
        <workgroup>DISPATCH</workgroup>
        
        <keyword>SIP</keyword>
        <keyword>robocall</keyword>
        <keyword>unwanted</keyword>
        <keyword>response code</keyword>
        
        <abstract>
            <t>
            This document defines the 666 (Unwanted) SIP response code, allowing called parties to indicate that the call was unwanted. The terminating SIP entity may use this information to adjust future call handling behavior for this called party or more broadly.
            </t>
        </abstract>
    </front>
    <!-- *********************************************************************** -->
    <middle>
        <section title="Introduction">

<t>In many countries, an increasing number of calls are unwanted <xref target="RFC5039"/>, as 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 only the last mode, where the called party either rejects the SIP INVITE request as unwanted or terminates the call with a BYE request after answering the call. To allow the called party to express that the call was unwanted, this document defines the 666 (Unwanted) response code.</t>
</section>
        
<section anchor="normative" title="Normative Language">
            
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119
    <xref target="RFC2119"/>.</t>
</section>

<section title="Motivation">
    <t>None of the existing 4xx, 5xx or 6xx response codes allow the called party to convey that they not only reject this call, e.g., using 480 (Temporarily Unavailable), 486 (Busy Here), 600 (Busy Everywhere), 603 (Decline) or 606 (Not Acceptable), but that the caller is unwanted. The particular response code number was chosen to reflect the distaste felt by many upon receiving such calls.</t>
</section>

<section title="Behavior of SIP Entities">

<t>The SIP entities receiving this response code are not obligated to take any particular action. The service provider delivering calls to the user issuing the response MAY, for example, add the calling party to a personal blacklist, or MAY use the information as input when computing the likelihood that the calling party is placing unwanted calls ("crowd sourcing").</t>

<t>The response code MAY also be used in Reason header fields <xref target="RFC3326"/>, typically when the UAS issues a BYE request terminating an incoming call.</t>

</section>

    <section anchor="IANA" title="IANA Considerations">
        <t>This document register a new SIP response code. This response code is defined by the following information, which is to be added to the method and response-code sub-registry under
            http://www.iana.org/assignments/sip-parameters.</t>

        <t><list style="hanging">
            <t hangText="Response Code Number">666</t>
            <t hangText="Default Reason Phrase">Unwanted</t>
            <t hangText="Reference">[this RFC]</t>
            </list>
        </t>
    </section>
    
    <section anchor="security" title="Security Considerations">
        <t>If the calling party number is spoofed, users may report the number as placing unwanted calls, possibly leading to the blocking of calls from the legitimate user of the number in addition to the unwanted caller. Thus, it is RECOMMENDED that the response code is used for creating call filters only if the calling party number has been authenticated using <xref target="I-D.ietf-stir-rfc4474bis"/>.</t>
    </section>
    <section title="Acknowledgements">
        <t>TBD.</t>
    </section>
    
</middle>

<!-- ********************************************************************************* -->

<back>
    <references title="Normative References">
        &RFC2119;
        &RFC3261;
        &RFC3326;
    </references>
    <references title="Informative References">
        &RFC5039;
        &rfc4474bis;
    </references>
</back>
</rfc>
