To tell the truth, I've never read the FCC sales pitch for STIR/SHAKEN. When I originally read about STIR/SHAKEN, articles had terms like authentication, verification, digital signature, cryptography, etc so I assumed this protocol to be a "certification authority" like other network validation processes. Meaning, only a completed validation process would allow a 2-way communications session.
However, the FCC sales pitch doesn't mention anything about stopping spoofs, blocking spoofs or preventing spoofs from ringing my phone. There isn't a hint of Access Denied. The key phrase is as follows:
"...it will give Americans more confidence that the caller ID information they receive is accurate and will allow voice service providers to provide helpful information to their consumers about which calls to answer."
More specifically "...the caller ID information they receive..." & "...which calls to answer."
This means spoofs will still happen and spoofs will still ring our phones. All Cox is doing is "stamping" the Caller ID info with their seal of approval. If you don't see the seal, be cautious.
My point is if had to look at the Caller ID in the first place, why do I need a seal? If I don't recognize the number...or think the number is fake...or just feel something is off with the Caller ID, I'm already not answering the call. Moreover, with or without STIR/SHAKEN, why is Cox allowing (000) 000-0000 to ring my phone?
The problem with spoofs is scammers are creative to lure you. For example, these are real spoofs: Untd St Govt, Police, Rebate, CoxComm. With STIR/SHAKEN, couldn't a scammer just spoof a seal of authentication and verification? Couldn't a scammer just prefix the spoof with , [AUTH], , [CERT], , [VAL], etc? I mean, Cox is already allowing the spoofs. Will Cox edit the spoofs to remove the spoofed seal? Did Cox ever train us to verify if a seal is their seal?
Bottom line: Nonsense will still ring your phone and Cox will still gladly take your "extra for my 30 blocked number feature."