2 ms·
I find it weird that it's STIR/SHAKEN that's constantly being mentioned. It won't actually change anything apart from people getting a more accurate source disp
by viraptor 5y ago
I find it weird that it's STIR/SHAKEN that's constantly being mentioned. It won't actually change anything apart from people getting a more accurate source displayed.
The part that actually changes something is this:
> When the FCC notifies a gateway provider about an ongoing robocall campaign, the provider would have to [...] and "promptly block all traffic associated with the traffic pattern identified in that notice."
That's all that was needed for years. Make it the telco's problem to either point the finger at the next peer responsible, or block their customer. We didn't actually need the caller authentication for this - you can identify and flag calls without it. I'm happy this rule is coming, but I wish that was done earlier before the effort of fixing the callerid.
- yellow_lead 5y agoWhy won't it change things? My team was responsible for implementing STIR/SHAKEN at a large Telco. Customers could, in the future, block calls for which the number is inaccurate (B/C attestation). If you get a call from a number, you should be able to know the number owner actually made the call. Then, robocall laws could be enforced, since you can actually find the responsible party from the number that dialed you.
- viraptor 5y ago> block calls for which the number is inaccurate Numbers are relatively cheap. The scams will just get a bit more expensive to run, but getting a block of thousands of provably-correct numbers is trivial. Especially if you're going to return them in a month after they're burned for spam purposes.