Compliance with the Non-IP Call Authentication Solution Rules; Robocall Mitigation Database (RMD)

ICR 202311-3060-021

OMB: 3060-1285

Federal Form Document

Forms and Documents
Document
Name
Status
Justification for No Material/Nonsubstantive Change
2023-11-24
Justification for No Material/Nonsubstantive Change
2023-11-24
Supporting Statement A
2023-09-01
Supporting Statement A
2023-09-01
IC Document Collections
IC ID
Document
Title
Status
245947
Modified
ICR Details
3060-1285 202311-3060-021
Active 202308-3060-015
FCC WCB
Compliance with the Non-IP Call Authentication Solution Rules; Robocall Mitigation Database (RMD)
No material or nonsubstantive change to a currently approved collection   No
Regular
Approved without change 12/05/2023
Retrieve Notice of Action (NOA) 11/24/2023
  Inventory as of this Action Requested Previously Approved
11/30/2026 11/30/2026 11/30/2026
12,800 0 12,800
39,663 0 39,663
0 0 0

The Federal Communications Commission (FCC) is submitting this non-substantive change request to the Office of Management and Budget (OMB) for approval due to the omission of 47 CFR § 64.6305(f) in the CFR Citation Section of ROCIS. The Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act and subsequent Commission orders require voice service providers, gateway providers and certain non-gateway intermediate providers to implement STIR/SHAKEN on their networks unless they are subject to an extension or exemption and, and maintain and be ready to provide the Commission upon request with documented proof that it working to develop a non-internet Protocol caller identification authentication solution, or actively testing such a solution. These providers are also required to submit identifying information as well as information regarding their efforts to mitigate illegal robocalls to the FCC’s Robocall Mitigation Database. The Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act obligates the Commission to require voice service providers (i) take reasonable steps to find a non-IP call authentication solution and (ii) if receiving an extension to the STIR/SHAKEN implementation deadline, create a robocall mitigation program. The Commission also required gateway providers to take reasonable steps to find a non-IP call authentication solution and (ii) create a robocall mitigation program.

US Code: 47 USC 227b, 227(e), 251(e) Name of Law: Communications Act of 1934 of 1934
  
None

3060-AL00 Final or interim final rulemaking 88 FR 40096 06/21/2023

  88 FR 42069 06/29/2023
88 FR 60679 09/05/2023
No

1
IC Title Form No. Form Name
Business or other-for profit

  Total Approved Previously Approved Change Due to New Statute Change Due to Agency Discretion Change Due to Adjustment in Estimate Change Due to Potential Violation of the PRA
Annual Number of Responses 12,800 12,800 0 0 0 0
Annual Time Burden (Hours) 39,663 39,663 0 0 0 0
Annual Cost Burden (Dollars) 0 0 0 0 0 0
No
No

$164,392
No
    No
    No
No
No
No
No
Jonathan Lechter 202 418-1500 jonathan.lechter@fcc.gov

  No

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).
The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:
 
 
 
 
 
 
 
    (i) Why the information is being collected;
    (ii) Use of information;
    (iii) Burden estimate;
    (iv) Nature of response (voluntary, required for a benefit, or mandatory);
    (v) Nature and extent of confidentiality; and
    (vi) Need to display currently valid OMB control number;
 
 
 
If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.
11/24/2023


© 2024 OMB.report | Privacy Policy