Source note · Robocall mitigation and RMD obligations
Third-party authentication is authorized only subject to two conditions: the provider with the implementation obligation must make all attestation-level decisions, and all calls must be signed using the certificate of the provider with the implementation obligation.
Checked 2026-09-16
- Vendor
- Federal Communications Commission
- Product
- STIR SHAKEN
- Subsystem
- third-party authentication
- Deployment
- all-us-voice-service-provider-networks
- Region
- united states
- Release range
- compliance from 2025-09-18
- Checked
- 2026-09-16
Sources
- Call Authentication Trust Anchor, Eighth Report and Order (FCC 24-120) — Federal Communications Commission · tier 1 standards and regulators · FCC 24-120 paras 20 and 23
Cite this note
APA
WarmTransfer. (2026, September 16). Robocall mitigation and RMD obligations: source note robocall-mitigation-eight-two-conditions. WarmTransfer. https://warmtransfer.net/knowledge/claims/robocall-mitigation-eight-two-conditions
BibTeX
@misc{warmtransfer-claim-robocall-mitigation-eight-two-conditions,
title = {Robocall mitigation and RMD obligations: source note robocall-mitigation-eight-two-conditions},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/robocall-mitigation-eight-two-conditions},
note = {Source note robocall-mitigation-eight-two-conditions, checked 2026-09-16}
}