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

["Asveren, Tolga" <[e-mail]>]

Agreed that this is somewhat about "philosophical aspects of priority". Having said that, I really feel not content with a fine-granularity indicator considering how in practice it would/could be generated especially considering all the operator/equipment/call scenario/deployment model combinations. It would be like, actually worse, than how sausages are prepared.

I am not religiously advocating a change toward a binary indicator (i.e. I wouldn't consider the current model as something "wrong") but IMHO that would be a more practical way of getting something useful at the end; just my 2 cents.

Thanks,
Tolga

-----Original Message-----
From: Henning Schulzrinne [mailto:[e-mail]] 
Sent: Wednesday, July 19, 2017 2:33 PM
To: Asveren, Tolga <[e-mail]>; Paul Kyzivat <[e-mail]>; [e-mail]
Subject: RE: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

This type of labeling is very common for email spam filters. It's essentially the same as "There's a 47% chance of rain today." Except that meteorologists are smart enough not to say 47%, but rather 50%.

It is better than the "According to the polls, candidate H has an 89% chance of winning the election." (Any semblance of initials to real persons has a 1-in-26 chance of being made up.)

Theoretically, unlike for elections and somewhat similar to the weather case, this is testable: You could take all the 50% spam or rain predictions, check with some reliable metric (human or rain gauge) whether the spam or rain happened and compare your results, i.e., roughly one in two such predictions should indeed turn out to be spam or rain. (It's more complicated than that, but we're getting pretty close to the philosophical debate of what probabilities mean when making predictions, which is apparently a rather unsettled scientific question.)

To actually answer your question: I don't think this is useful except as a rough way for users to trade false-positive/false-negative penalties. For example, they may discard all 80%+ probability calls, route 30-80% calls to voicemail and ring the below-30% calls. The thresholds are arbitrary, but users may tune them based on experience ("all the calls in voicemail were spam, so I can go lower").

Some people pack an umbrella when there's a 20% chance of rain, others are more willing to risk getting wet. By the way, it is well-known that meteorologists over-predict rain since nobody complains if they did not get soaked.

Henning

-----Original Message-----
From: sipcore [mailto:[e-mail]] On Behalf Of Asveren, Tolga
Sent: Wednesday, July 19, 2017 2:11 PM
To: Paul Kyzivat <[e-mail]>; [e-mail]
Subject: Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

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