Source note · Robocall mitigation and RMD obligations
A provider that cannot implement STIR/SHAKEN because it lacks control over the network infrastructure must explain that basis in its filing rather than certify implementation.
Checked 2026-09-16
- Vendor
- Federal Communications Commission
- Product
- Robocall Mitigation Database
- Subsystem
- mitigation plan content
- Deployment
- all-us-voice-service-provider-networks
- Region
- united states
- Release range
- current as of 2026-09-16
- Checked
- 2026-09-16
Sources
- 47 CFR 64.6305 - Robocall mitigation and certification — Legal Information Institute, Cornell Law School · tier 2 current vendor documentation · 47 CFR 64.6305(d)(2)
Cite this note
APA
WarmTransfer. (2026, September 16). Robocall mitigation and RMD obligations: source note robocall-mitigation-mitigation-plan-extension. WarmTransfer. https://warmtransfer.net/knowledge/claims/robocall-mitigation-mitigation-plan-extension
BibTeX
@misc{warmtransfer-claim-robocall-mitigation-mitigation-plan-extension,
title = {Robocall mitigation and RMD obligations: source note robocall-mitigation-mitigation-plan-extension},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/robocall-mitigation-mitigation-plan-extension},
note = {Source note robocall-mitigation-mitigation-plan-extension, checked 2026-09-16}
}