IETF Logo Mail Archive

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

"Asveren, Tolga" <tasveren@sonusnet.com> Fri, 21 July 2017 10:49 UTC

Return-Path: <tasveren@sonusnet.com>
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 13560129B3A for <sipcore@ietfa.amsl.com>; Fri, 21 Jul 2017 03:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level:
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=sonusnetworks.onmicrosoft.com
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 XpUcfO0pgfVx for <sipcore@ietfa.amsl.com>; Fri, 21 Jul 2017 03:49:57 -0700 (PDT)
Received: from us-smtp-delivery-126.mimecast.com (us-smtp-delivery-126.mimecast.com [216.205.24.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF3D6127337 for <sipcore@ietf.org>; Fri, 21 Jul 2017 03:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-sonusnet-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2JCZ2vw+vXjjV4RDWikBL48ephcwCLdCcj5n57NTxWk=; b=h89viYdgCpSoRKUV3+RpX979kkUlgSuV72SM3Jdj7dyZcXcsqfi1ddLAvrYzn0ZxH1Xs4OjLXS9PwIX7BLtxN1CZyiEL2RopnYwD0B857fmHUb9EKVn5vFVtPcJK8pP1RRs946JnSoJlJR/3zg9itCn13JvdMrYyLXQZZASMJ+0=
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0087.outbound.protection.outlook.com [207.46.163.87]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-71-PTu1lIvyM6ajrol47BbdOA-1; Fri, 21 Jul 2017 06:49:53 -0400
Received: from SN2PR03MB2350.namprd03.prod.outlook.com (10.166.210.141) by SN2PR03MB2160.namprd03.prod.outlook.com (10.166.209.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.10; Fri, 21 Jul 2017 10:49:52 +0000
Received: from SN2PR03MB2350.namprd03.prod.outlook.com ([10.166.210.141]) by SN2PR03MB2350.namprd03.prod.outlook.com ([10.166.210.141]) with mapi id 15.01.1282.016; Fri, 21 Jul 2017 10:49:51 +0000
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>, Richard Shockey <richard@shockey.us>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities
Thread-Index: AQHS//8f86lEHhh9VUKR5rSbwxo4z6Ja0ofAgABzoYCAAC1loIAAAo2AgAAGWUCAAWxBgIAADIFAgAAo3ICAAAsFgIAADk8AgAAS8rOAANKUgA==
Date: Fri, 21 Jul 2017 10:49:51 +0000
Message-ID: <SN2PR03MB23509BF513D1D716AFF56D23B2A40@SN2PR03MB2350.namprd03.prod.outlook.com>
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> <15895f11-85c0-70ab-9cc1-e7b5943e2549@alum.mit.edu>, <5D4E83A0-7B5E-4DC9-B8CD-A89B0C7F22B0@shockey.us> <CY1PR09MB076009948A7DC1775E106DEDEAA70@CY1PR09MB0760.namprd09.prod.outlook.com>
In-Reply-To: <CY1PR09MB076009948A7DC1775E106DEDEAA70@CY1PR09MB0760.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [73.29.18.75]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN2PR03MB2160; 20:iT3QL/y5zq7R81LccL9CDcdZybAG6sxgYNHFIDULxHbtUfEPUEeH6n5UYnDtsaE0sWH1yq5zack1R3np2CCKOQtaCr5LKyj5u+gnG6yxWNKRN+dbOUos/JMO3Cq461+bnm+HPoBLUC0gj40UpXaxoVHn4VebI2ZMLgGN/FuQMR0=
x-ms-office365-filtering-correlation-id: 5896a972-ea79-4a9d-d4a6-08d4d02636f8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:SN2PR03MB2160;
x-ms-traffictypediagnostic: SN2PR03MB2160:
x-exchange-antispam-report-test: UriScan:(151999592597050)(26388249023172)(21748063052155);
x-microsoft-antispam-prvs: <SN2PR03MB2160F7726B4F88209280108EB2A40@SN2PR03MB2160.namprd03.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123555025)(20161123562025)(20161123560025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN2PR03MB2160; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN2PR03MB2160;
x-forefront-prvs: 0375972289
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39450400003)(39830400002)(39410400002)(39400400002)(189002)(199003)(377454003)(53936002)(55016002)(99286003)(54896002)(6306002)(9686003)(790700001)(6116002)(102836003)(3846002)(38730400002)(6246003)(2171002)(236005)(8936002)(81166006)(8676002)(81156014)(2501003)(74316002)(2906002)(478600001)(2900100001)(86362001)(3280700002)(68736007)(3660700001)(7696004)(5660300001)(50986999)(189998001)(93886004)(6436002)(54356999)(76176999)(25786009)(101416001)(53546010)(97736004)(229853002)(106356001)(7736002)(33656002)(2950100002)(6506006)(105586002)(77096006)(14454004)(230783001)(66066001); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR03MB2160; H:SN2PR03MB2350.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: sonusnet.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2017 10:49:51.4131 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN2PR03MB2160
X-MC-Unique: PTu1lIvyM6ajrol47BbdOA-1
Content-Type: multipart/alternative; boundary="_000_SN2PR03MB23509BF513D1D716AFF56D23B2A40SN2PR03MB2350namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/qCiL5by7ElPRMRyPoC4vj0REh8o>
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: Fri, 21 Jul 2017 10:49:59 -0000

Would this spam indicator really be useful for anything else during ringing? For post-ringing, the "ultimate decision maker" is already in the loop, the enduser himself. He doesn't need the network to tell him whether the call was spam or not (or a survey or etc...), he can decide himself.

And regarding granularity during ringing, would the UI really display something like "There is a 87% chance that this is a robocall" or "There is a 61% chance that this is a survey". IMHO, we really are already in the "information overdose" area.

Thanks,
Tolga

From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Henning Schulzrinne
Sent: Thursday, July 20, 2017 6:18 PM
To: Richard Shockey <richard@shockey.us>; Paul Kyzivat <pkyzivat@alum.mit.edu>; sipcore@ietf.org
Subject: Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities


From: sipcore <sipcore-bounces@ietf.org<mailto:sipcore-bounces@ietf.org>> on behalf of Richard Shockey <richard@shockey.us<mailto:richard@shockey.us>>

RS> Fair enough.  Choice is fine until someone screws up and you cant find the "reset to default" button.

Consider the Android "Do not disturb" model. It's fairly programmable and you can define time-of-day and event rules and then what are "priority" interrupts that are allowed. Currently, there's "calls from..." starred contacts, from anyone, from contacts, none. You could imagine adding "from non-spam callers" or "personal calls", say, based on the Call-Info header information.

This does not require that users write Javascript code and most users will probably just leave the default behavior, but this offers flexibility to the mobile OS vendors to implement interesting behavior.

Henning

v2.23.0 | Report a Bug | By Email