STIR/SHAKEN protocol
From Just Solve the File Format Problem
(Difference between revisions)
Dan Tobias (Talk | contribs) (Created page with "{{FormatInfo |formattype=electronic |subcat=Telephony }} The '''STIR/SHAKEN protocol''' (Secure Telephone Identity Revisited/Signature-based Handling of Asserted information u...") |
Dan Tobias (Talk | contribs) (→Links) |
||
| Line 18: | Line 18: | ||
* [https://spectrum.ieee.org/telecom/standards/how-your-phone-company-aims-to-stop-robocalls How Your Phone Company Aims to Stop Robocalls] | * [https://spectrum.ieee.org/telecom/standards/how-your-phone-company-aims-to-stop-robocalls How Your Phone Company Aims to Stop Robocalls] | ||
* [https://www.atis.org/sti-ga/ Secure Telephone Identity Governance Authority] | * [https://www.atis.org/sti-ga/ Secure Telephone Identity Governance Authority] | ||
| + | * [https://www.atis.org/sti-ga/resources/docs/shaken-faqs.pdf SHAKEN FAQ] | ||
Latest revision as of 02:16, 4 December 2019
The STIR/SHAKEN protocol (Secure Telephone Identity Revisited/Signature-based Handling of Asserted information using toKENs) is an attempt to reduce robocalls with spoofed Caller ID by providing different levels of authentication of whether the caller has the right to the number they're identifying as, making it easier to block calls that are suspicious.
[edit] Technical documents
- RFC 5280
- RFC 8224
- RFC 8225
- RFC 8226
- RFC 8555
- ACME Challenges Using an Authority Token (draft)
- TNAuthList profile of ACME Authority Token (draft)
- Other resources
