Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 20 July 2017 20:12 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8776131B90 for <sipcore@ietfa.amsl.com>; Thu, 20 Jul 2017 13:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJeBl0vQSDZz for <sipcore@ietfa.amsl.com>; Thu, 20 Jul 2017 13:12:43 -0700 (PDT)
Received: from alum-mailsec-scanner-7.mit.edu (alum-mailsec-scanner-7.mit.edu [18.7.68.19]) by ietfa.amsl.com (Postfix) with ESMTP id C2565131B78 for <sipcore@ietf.org>; Thu, 20 Jul 2017 13:12:43 -0700 (PDT)
X-AuditID: 12074413-281ff70000001b03-c5-59710ebacdbd
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id D7.9C.06915.ABE01795; Thu, 20 Jul 2017 16:12:42 -0400 (EDT)
Received: from [192.168.1.110] (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v6KKCgq0017268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Thu, 20 Jul 2017 16:12:42 -0400
To: sipcore@ietf.org
References: <CY1PR09MB07602078727954F586DCBDD3EAA10@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB235023C01D8658B9B25A3577B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <75f4364f-a10d-18eb-f547-8bdb17acef78@alum.mit.edu> <SN2PR03MB23509530AE70988D06A97191B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <CY1PR09MB07606A3F6AD98F8CB7235FD5EAA60@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB2350B8FDFC86CC4DDA03F013B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <C9588D9A-B3ED-4088-9128-4E4D54FCA06C@shockey.us> <CY1PR09MB0760C398A942BEBB0EAD07D0EAA70@CY1PR09MB0760.namprd09.prod.outlook.com> <8542D641-AE8F-4134-B357-017DC6F73E5F@shockey.us>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <15895f11-85c0-70ab-9cc1-e7b5943e2549@alum.mit.edu>
Date: Thu, 20 Jul 2017 16:12:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <8542D641-AE8F-4134-B357-017DC6F73E5F@shockey.us>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUixO6iqLubrzDSYNMTZouvPzaxOTB6LFny kymAMYrLJiU1J7MstUjfLoEr41j3d6aCq9wVT/9cYWxgnMvZxcjJISFgInHnxn/mLkYuDiGB HUwSR6fdZwdJCAm8YZJom8EKYgsLeEp0rX3KDGKLCIhIPJv+jw2iYSarxOIn3YwgCTYBLYk5 h/6zgNi8AvYSfxecB2tgEVCVmHXwFthQUYE0iRnfrzND1AhKnJz5BKyeU8BO4tPRV2wgNrOA mcS8zQ+ZIWxxiVtP5jNB2PISzVtnM09g5J+FpH0WkpZZSFpmIWlZwMiyilEuMac0Vzc3MTOn ODVZtzg5MS8vtUjXXC83s0QvNaV0EyMkLIV3MO46KXeIUYCDUYmHl2FdQaQQa2JZcWXuIUZJ DiYlUV6WQKAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd7TX4FyvCmJlVWpRfkwKWkOFiVxXrUl 6n5CAumJJanZqakFqUUwWRkODiUJ3v28hZFCgkWp6akVaZk5JQhpJg5OkOE8QMP/gtTwFhck 5hZnpkPkTzHqcvyaufULkxBLXn5eqpQ4734eoCIBkKKM0jy4ObB08opRHOgtYV4JYHIR4gGm IrhJr4CWMAEteeQG8kFxSSJCSqqBUYPn9OPT1psW7Po7W2v35Lknn7w8f/D7nrCjf4WX3xQ1 PrSuVtGxOUPvwifPf9YKG1Vk81LX1bcu/Zdn4/2CdenqnG0T2qIuntuT5r52iZJjyA8hM/cZ ZQzN1w6fqlr/Mbq8W/5izYSSY41yx8M2RS6vMxNSE3NqfnSAZRZXa1VgdNaDvbMNFymxFGck GmoxFxUnAgBh4STmAgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/9fSS3QrDlnrHFxjPM5XRfOqYMwY>
Subject: Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 20:12:45 -0000

On 7/20/17 3:33 PM, Richard Shockey wrote:

>      There are four likely models:
>      
>      * the call type (and spam-quotient) information may be shown to users, but most likely when reviewing voice mail, not a ringing call (where a simple binary indicator is probably more suitable, derived from information in the draft, possibly)
> 
> RS>  That’s what I’ve been thinking.  The binary indicator is most useful during ringing and that is the 2-3 seconds you have when you look at the UA.  Some Data Analytics vendors have indicated there is zero difference in consumer behavior on binary display (good vs bad red vs green) vs granular scoring (0-100) display for instance.  This is really the VERISAT 3GPP parameter for inband SIP usage vs some other out of band transmittal (HTTP) to the UA.

Ring tones could be used to indicate more than a binary choice while 
remaining easy and quick to understand.

> RS> Sure but this is ultimately a consumer / enterprise decision on who does what to analyze the call.  My guess is most consumers (98%) would want the carrier to deal with it.  That’s what we pay them for and life is too complicated as it is.  

Speak for yourself. Admittedly perhaps everyone reading this will fall 
within the 2%. But lots of people are already familiar with configuring 
their ring tones and dialer. It is not at all hard to imagine quite a 
lot of people (at least those < 30 years old) wanting to tweak this stuff.

	Thanks,
	Paul