IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 19 July 2017 15:24 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 44CF7131C6C for <sipcore@ietfa.amsl.com>; Wed, 19 Jul 2017 08:24:19 -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 WXh8zs9ird-5 for <sipcore@ietfa.amsl.com>; Wed, 19 Jul 2017 08:24:16 -0700 (PDT)
Received: from alum-mailsec-scanner-6.mit.edu (alum-mailsec-scanner-6.mit.edu [18.7.68.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8256F1315FE for <sipcore@ietf.org>; Wed, 19 Jul 2017 08:24:16 -0700 (PDT)
X-AuditID: 12074412-22bff70000003b38-a1-596f799e6ee2
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-6.mit.edu (Symantec Messaging Gateway) with SMTP id B5.7E.15160.E997F695; Wed, 19 Jul 2017 11:24:14 -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 v6JFODis027087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Wed, 19 Jul 2017 11:24:14 -0400
To: sipcore@ietf.org
References: <CY1PR09MB07602078727954F586DCBDD3EAA10@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB235023C01D8658B9B25A3577B2A60@SN2PR03MB2350.namprd03.prod.outlook.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <75f4364f-a10d-18eb-f547-8bdb17acef78@alum.mit.edu>
Date: Wed, 19 Jul 2017 11:24:13 -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: <SN2PR03MB235023C01D8658B9B25A3577B2A60@SN2PR03MB2350.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCIsWRmVeSWpSXmKPExsUixO6iqDu/Mj/SYP8fNouvPzaxOTB6LFny kymAMYrLJiU1J7MstUjfLoErY/rBHSwF99krrr/Pa2CcztbFyMEhIWAi8WdNQhcjF4eQwA4m iQs3prNDOG+YJDpeNLB2MXJyCAt4SnStfcoMYosIiEg8m/6PDaJoPaPE27+tYEVsAloScw79 ZwGxeQXsJa4tXAFmswioShx9/50dxBYVSJOY8f06M0SNoMTJmU/AajgFYiWOTL0DNodZwFbi ztzdzBC2uMStJ/OZIGx5ie1v5zBPYOSfhaR9FpKWWUhaZiFpWcDIsopRLjGnNFc3NzEzpzg1 Wbc4OTEvL7VI10wvN7NELzWldBMjJCiFdjCuPyl3iFGAg1GJh/dBan6kEGtiWXFl7iFGSQ4m JVHeObxAIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8b8qAcrwpiZVVqUX5MClpDhYlcd6fi9X9 hATSE0tSs1NTC1KLYLIyHBxKErxmFUCNgkWp6akVaZk5JQhpJg5OkOE8QMPFQWp4iwsSc4sz 0yHypxiNOZo+bPnCxPFr5tYvTEIsefl5qVLivP3lQKUCIKUZpXlw02CJ5RWjONBzwrw7QAby AJMS3LxXQKuYgFYJ++aArCpJREhJNTAy9vGbfJzwyKx00p9I298zmTP130nWKzak5y3f3bWq +k7fhL/VCxZkfQqwmlFs9uM9+4kfHu4NZVILj88+8rFf/eID1wad4hclhzZVdX9kXOETcSd7 T9kj44OMkfHnKjpaDM2W/Z0snc78YOfWc39Or4pfcLbviZw/x90TCftDvs/d82mi8hVlJZbi jERDLeai4kQAPMZSswcDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/pQ-KncW-Rpt9MBt7HuhePlUlVGE>
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: Wed, 19 Jul 2017 15:24:19 -0000

On 7/19/17 4:34 AM, Asveren, Tolga wrote:

> 2) Communicating spam related information between network and end-user
> 
> I think here what is needed is just a "likely to be spam" indicator as 
> far as network prediction is concerned. End-user would see a visual 
> indicator if the indicator is present. Anything more than that is just 
> "information overdose" IMHO and wouldn't have much practical value for 
> an average user. Another indicator stating "calling identity can't be 
> verified" could be useful but this IMHO is something different.

You seem to be making an assumption about where the intelligence is 
located and policy decisions are made.

What you are saying may be appropriate for a dumb device and/or a dumb 
user. But most phones that will do anything with this information can be 
smart, and so be subject to configuration by the user for preferences. 
I'd rather maximize the amount of information available to the end device.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email