[VoiceOps] Robocall Mitigation in lieu of STIR/SHAKEN

[Alex Balashov]

Well, a number of bright-eyed, bushy-tailed, enterprising eager beavers have ploughed full-on into the dubious business — more superstition than science — of proprietary reputation-scoring / spam risk-scoring for numbers. Nothing more exciting to the entrepreneurial element than an opportunity to provide a knock-off of a regulatory requirement that falls just a millimetre shy of overt intellectually fraud.

I imagine querying one of those services’ database of numbers scraped from the National Association of Ignoble Car Warranty Merchants or Ashley Madison or whatever ... could be construed to the gullible as a “good”-faith effort at robocall mitigation. It’s an A-for-effort kind of cultural moment anyhow.

—
Sent from mobile, with due apologies for brevity and errors.

> On Mar 9, 2021, at 7:32 PM, Zilk, David <David.Zilk at cdk.com> wrote:
> 
> 
>  
> The FCC is mandating that service providers must fully implement STIR/SHAKEN or certify that they are taking reasonable steps to avoid originating illegal robocall traffic in the portions of their network where STIR/SHAKEN can’t be implemented. They have also declined to specify what those steps might be, though there may be more information available when they clarify the certification process by March 30th.
>  
> What steps are people taking to meet this robocall mitigation requirement when STIR/SHAKEN is not able to be implemented?
>  
> David
>  
>  
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210309/bf67d434/attachment-0001.htm>