3 ms·
The eventual fix will be adopting ATIS SHAKEN and STIR protocols, which is, very roughly, signed caller ID. The FCC is now demanding it of carriers: https://do
by troydavis 8y ago
The eventual fix will be adopting ATIS SHAKEN and STIR protocols, which is, very roughly, signed caller ID. The FCC is now demanding it of carriers:
https://docs.fcc.gov/public/attachments/DOC-354933A1.pdf https://docs.fcc.gov/public/attachments/DOC-354933A1.pdf (Background and open letters to carriers: https://www.fcc.gov/document/chairman-pai-demands-industry-adopt-protocols-end-illegal-spoofing https://www.fcc.gov/document/chairman-pai-demands-industry-a...)
How it works, short version: https://transnexus.com/blog/2017/stop-spoofed-robocalls-with-stir-and-shaken/ https://transnexus.com/blog/2017/stop-spoofed-robocalls-with...
How it works, long version: http://www.atis.org/01_resources/whitepapers/#shaken-studies http://www.atis.org/01_resources/whitepapers/#shaken-studies (find in page for “SHAKEN” and “Caller ID”)
- sofaofthedamned 8y agoApologies for not reading through these links, but does this fix just the caller-id issue, or the routing issue - i.e. routing an SMS to a bad actor?
- Rjevski 8y agoJust caller ID, and even then it seems like it’s between service providers only - you have to trust your carrier to validate signatures and reject bad/missing ones.