IETF Logo Mail Archive

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

"Asveren, Tolga" <tasveren@sonusnet.com> Wed, 19 July 2017 18:11 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 2D6CD131B9B for <sipcore@ietfa.amsl.com>; Wed, 19 Jul 2017 11:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level:
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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 (message 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 6Rn3_kfDfbPE for <sipcore@ietfa.amsl.com>; Wed, 19 Jul 2017 11:11:07 -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 12FA9131B88 for <sipcore@ietf.org>; Wed, 19 Jul 2017 11:11:06 -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=jIknou9q2+68/UmHRvddVEEgXIuGFx1Q/gGd9+5PoO0=; b=kdJkCdLRPRQIYl3/8e8NC8qsHmDOk8lmd+9XiDNtOzEZ1CtHh6TC1vKB1Ad84iaSqPK+ErrJ3Z8LLOVUeTaGCy7uX/gdob7bc1DQfEivk0OXNzfrA0bvurqI0LTjGfNTtnQAuC/sd0vGzMcgF/r+d3Oc9u1I9YRko6IwZXy8OLY=
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp0018.outbound.protection.outlook.com [216.32.181.18]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-41-gQ_OiZXrPimpLBNyOIbPkA-1; Wed, 19 Jul 2017 14:11:04 -0400
Received: from SN2PR03MB2350.namprd03.prod.outlook.com (10.166.210.141) by SN2PR03MB2157.namprd03.prod.outlook.com (10.166.209.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Wed, 19 Jul 2017 18:11:02 +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.011; Wed, 19 Jul 2017 18:11:02 +0000
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: 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//8f86lEHhh9VUKR5rSbwxo4z6Ja0ofAgABzoYCAAC1loA==
Date: Wed, 19 Jul 2017 18:11:02 +0000
Message-ID: <SN2PR03MB23509530AE70988D06A97191B2A60@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>
In-Reply-To: <75f4364f-a10d-18eb-f547-8bdb17acef78@alum.mit.edu>
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; SN2PR03MB2157; 20:CQUdz++jldr/8PjuATe97GZIAAX1dfRR9R1YhvpfUS2c1Uw3RbC/A4UeMQM6+9okwSoyaUHmAzLiCTLn+phNCDf8D9Ac8dNJHLgT1mHpU0d0dLzKWvSvBv2AtDCXy0Muez8oZZkWl/quP9BC7uL9KGtu3mAc97MrTZcMbvnqO/8=
x-ms-office365-filtering-correlation-id: 6022b879-4344-4723-305e-08d4ced183e9
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:SN2PR03MB2157;
x-ms-traffictypediagnostic: SN2PR03MB2157:
x-exchange-antispam-report-test: UriScan:(236129657087228)(247924648384137);
x-microsoft-antispam-prvs: <SN2PR03MB21574FFCA2573711088E58E8B2A60@SN2PR03MB2157.namprd03.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(2017060910075)(5005006)(8121501046)(10201501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(20161123560025)(20161123564025)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN2PR03MB2157; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN2PR03MB2157;
x-forefront-prvs: 0373D94D15
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39450400003)(39410400002)(39400400002)(13464003)(377454003)(24454002)(81166006)(2171002)(8936002)(14454004)(7736002)(2900100001)(6436002)(77096006)(3280700002)(2950100002)(7696004)(38730400002)(53546010)(3660700001)(230783001)(5660300001)(55016002)(53936002)(9686003)(8676002)(6506006)(6246003)(6306002)(99286003)(66066001)(478600001)(86362001)(2906002)(3846002)(33656002)(25786009)(229853002)(966005)(189998001)(74316002)(50986999)(102836003)(54356999)(305945005)(76176999)(2501003)(6116002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR03MB2157; H:SN2PR03MB2350.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: sonusnet.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2017 18:11:02.1035 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN2PR03MB2157
X-MC-Unique: gQ_OiZXrPimpLBNyOIbPkA-1
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/WeruQ0Uear4XRaEeBK9j1XoSTdE>
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 18:11:09 -0000

Let me ask this question then:
What would "spam with a likelihood of 47%" mean? Will the specification detail how this percentage need to be calculated? Otherwise how can the end-device take some action based on this value? One could argue that all these are "implementation dependent" but honestly I think this would just create confusion/chaos in practice and likely to be not useful.

Thanks,
Tolga

-----Original Message-----
From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: Wednesday, July 19, 2017 11:24 AM
To: sipcore@ietf.org
Subject: Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

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

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email