Information Collection Being Submitted for Review and Approval to Office of Management and Budget, 54501-54502 [2022-19097]
Download as PDF
Federal Register / Vol. 87, No. 171 / Tuesday, September 6, 2022 / Notices
illegal robocalls from reaching
consumers and to help track these calls
back to the source. Along with further
extension of the Commission’s caller ID
authentication requirements and
Robocall Mitigation Database filing
requirements, the Commission adopted
several robocall mitigation
requirements, including a requirement
for gateway providers to respond to
traceback within 24 hours, mandatory
blocking requirements, a ‘‘know your
upstream provider’’ requirement, and a
general mitigation requirement.
jspears on DSK121TN23PROD with NOTICES
Gateway Provider Report and Order, FCC
22–37, Paras. 65–71, 47 CFR 64.1200(n)(1)
A voice service provider must: . . . Upon
receipt of a traceback request from the
Commission, civil law enforcement, criminal
law enforcement, or the industry traceback
consortium:
(i) If the provider is an originating,
terminating, or non-gateway intermediate
provider for all calls specified in the
traceback request, the provider must respond
fully and in a timely manner;
(ii) If the provider receiving a traceback
request is the gateway provider for any calls
specified in the traceback request, the
provider must fully respond to the traceback
request within 24 hours of receipt of the
request. The 24-hour clock does not start
outside of business hours, and requests
received during that time are deemed
received at 8:00 a.m. on the next business
day. If the 24-hour response period would
end on a non-business day, either a weekend
or a federal legal holiday, the 24-hour clock
does not run for the weekend or holiday in
question, and restarts at 12:01 a.m. on the
next business day following when the request
would otherwise be due. For example, a
request received at 3:00 p.m. on a Friday will
be due at 3:00 p.m. on the following Monday,
assuming that Monday is not a federal legal
holiday. For purposes of this rule, ‘‘business
day’’ is defined as Monday through Friday,
excluding federal legal holidays, and
‘‘business hours’’ is defined as 8:00 a.m. to
5:30 p.m. on a business day. For purposes of
this rule, all times are local time for the office
that is required to respond to the request.
The first portion of the information
collection for which OMB approval is
sought comes from the requirement
adopted in the Gateway Provider Report
and Order that all voice service
providers respond to traceback ‘‘fully
and in in a timely manner’’ and gateway
providers must respond within 24
hours. All voice service providers,
including gateway providers are
required to respond to traceback
requests from the Commission, civil and
criminal law enforcement, and the
Industry Traceback Consortium.
Traceback is a key enforcement tool in
the fight against illegal calls, allowing
the Commission or law enforcement to
identify the caller and bring
enforcement actions or otherwise stop
VerDate Sep<11>2014
20:04 Sep 02, 2022
Jkt 256001
future calls before they reach
consumers. Any unnecessary delay in
the process can increase the risk that
this essential information may become
impossible to obtain. While traceback is
not a new process, some providers have
historically been reluctant to respond,
or have simply ignored requests. This
requirement ensures that all providers
are on notice that a response is required,
and allows real consequences for
refusal.
Federal Communications Commission.
Katura Jackson,
Federal Register Liaison Officer.
[FR Doc. 2022–19096 Filed 9–2–22; 8:45 am]
BILLING CODE 6712–01–P
FEDERAL COMMUNICATIONS
COMMISSION
[OMB 3060–1285; FR ID 102882]
Information Collection Being
Submitted for Review and Approval to
Office of Management and Budget
Federal Communications
Commission.
ACTION: Notice and request for
comments.
AGENCY:
As part of its continuing effort
to reduce paperwork burdens, as
required by the Paperwork Reduction
Act (PRA) of 1995, the Federal
Communications Commission (FCC or
the Commission) invites the general
public and other Federal Agencies to
take this opportunity to comment on the
following information collection.
Pursuant to the Small Business
Paperwork Relief Act of 2002, the FCC
seeks specific comment on how it might
‘‘further reduce the information
collection burden for small business
concerns with fewer than 25
employees.’’ The Commission may not
conduct or sponsor a collection of
information unless it displays a
currently valid Office of Management
and Budget (OMB) control number. No
person shall be subject to any penalty
for failing to comply with a collection
of information subject to the PRA that
does not display a valid OMB control
number.
DATES: Written comments and
recommendations for the proposed
information collection should be
submitted on or before October 6, 2022.
ADDRESSES: Comments should be sent to
www.reginfo.gov/public/do/PRAMain.
Find this particular information
collection by selecting ‘‘Currently under
30-day Review—Open for Public
Comments’’ or by using the search
function. Your comment must be
SUMMARY:
PO 00000
Frm 00053
Fmt 4703
Sfmt 4703
54501
submitted into www.reginfo.gov per the
above instructions for it to be
considered. In addition to submitting in
www.reginfo.gov also send a copy of
your comment on the proposed
information collection to Nicole Ongele,
FCC, via email to PRA@fcc.gov and to
Nicole.Ongele@fcc.gov. Include in the
comments the OMB control number as
shown in the SUPPLEMENTARY
INFORMATION below.
For
additional information or copies of the
information collection, contact Nicole
Ongele at (202) 418–2991. To view a
copy of this information collection
request (ICR) submitted to OMB: (1) go
to the web page https://www.reginfo.gov/
public/do/PRAMain, (2) look for the
section of the web page called
‘‘Currently Under Review,’’ (3) click on
the downward-pointing arrow in the
‘‘Select Agency’’ box below the
‘‘Currently Under Review’’ heading, (4)
select ‘‘Federal Communications
Commission’’ from the list of agencies
presented in the ‘‘Select Agency’’ box,
(5) click the ‘‘Submit’’ button to the
right of the ‘‘Select Agency’’ box, (6)
when the list of FCC ICRs currently
under review appears, look for the Title
of this ICR and then click on the ICR
Reference Number. A copy of the FCC
submission to OMB will be displayed.
FOR FURTHER INFORMATION CONTACT:
As part of
its continuing effort to reduce
paperwork burdens, as required by the
Paperwork Reduction Act (PRA) of 1995
(44 U.S.C. 3501–3520), the FCC invited
the general public and other Federal
Agencies to take this opportunity to
comment on the following information
collection. Comments are requested
concerning: (a) Whether the proposed
collection of information is necessary
for the proper performance of the
functions of the Commission, including
whether the information shall have
practical utility; (b) the accuracy of the
Commission’s burden estimates; (c)
ways to enhance the quality, utility, and
clarity of the information collected; and
(d) ways to minimize the burden of the
collection of information on the
respondents, including the use of
automated collection techniques or
other forms of information technology.
Pursuant to the Small Business
Paperwork Relief Act of 2002, Public
Law 107–198, see 44 U.S.C. 3506(c)(4),
the FCC seeks specific comment on how
it might ‘‘further reduce the information
collection burden for small business
concerns with fewer than 25
employees.’’
OMB Control Number: 3060–1285.
SUPPLEMENTARY INFORMATION:
E:\FR\FM\06SEN1.SGM
06SEN1
jspears on DSK121TN23PROD with NOTICES
54502
Federal Register / Vol. 87, No. 171 / Tuesday, September 6, 2022 / Notices
Title: Compliance with the Non-IP
Call Authentication Solution Rules;
Robocall Mitigation Database (RMD).
Form Number: N/A.
Type of Review: Revision of a
currently approved collection.
Respondents: Business or other for
profit entities.
Number of Respondents and
Responses: 8,970 respondents; 8,970
responses.
Estimated Time per Response: 0.5
hours (30 minutes)–3 hours.
Frequency of Response:
Recordkeeping requirement and on
occasion reporting requirement.
Obligation to Respond: Mandatory
and required to obtain or retain benefits.
Statutory authority for these collections
are contained in 47 U.S.C. 227b, 251(e),
and 227(e) of the Communications Act
of 1934.
Total Annual Burden: 20,503 hours.
Total Annual Cost: No Cost.
Privacy Impact Assessment: No
impact(s).
Nature and Extent of Confidentiality:
The Commission will consider the
potential confidentiality of any
information submitted, particularly
where public release of such
information could raise security
concerns (e.g., granular location
information). Respondents may request
materials or information submitted to
the Commission or to the Administrator
be withheld from public inspection
under 47 CFR 0.459 of the
Commission’s rules.
Needs and Uses: The Pallone-Thune
Telephone Robocall Abuse Criminal
Enforcement and Deterrence (TRACED)
Act directs the Commission to require,
no later than 18 months from
enactment, all voice service providers to
implement STIR/SHAKEN caller ID
authentication technology in the
internet protocol (IP) portions of their
networks and implement an effective
caller ID authentication framework in
the non-IP portions of their networks.
Among other provisions, the TRACED
Act also directs the Commission to
create extension mechanisms for voice
service providers. On September 29,
2020, the Commission adopted its Call
Authentication Trust Anchor Second
Report and Order. See Call
Authentication Trust Anchor, WC
Docket No. 17–97, Second Report and
Order, 36 FCC Rcd 1859 (adopted Sept.
29, 2020). The Second Report and Order
implemented section 4(b)(1)(B) of the
TRACED Act, in part, by requiring a
voice service provider maintain and be
ready to provide the Commission upon
request with documented proof that it is
participating, either on its own or
through a representative, including
VerDate Sep<11>2014
20:04 Sep 02, 2022
Jkt 256001
third party representatives, as a member
of a working group, industry standards
group, or consortium that is working to
develop a non-internet Protocol caller
identification authentication solution,
or actively testing such a solution. The
Second Report and Order also
implemented the extension mechanisms
in section 4(b)(5) by, in part, requiring
voice service providers to certify that
they have either implemented STIR/
SHAKEN or a robocall mitigation
program in the Robocall Mitigation
Database. On May 19, 2022, the
Commission adopted similar obligations
for gateway providers. See Advanced
Methods to Target and Eliminate
Unlawful Robocalls, Call Authentication
Trust Anchor, CG Docket No. 17–59,
WC Docket No. 17–97, Sixth Report and
Order et al., FCC 22–37 (adopted May
19, 2022). Specifically, like voice
service providers, gateway providers
were required to maintain and be ready
to provide the Commission upon
request with documented proof that
they are participating, either on their
own or through a representative,
including third party representatives, as
a member of a working group, industry
standards group, or consortium that is
working to develop a non-internet
Protocol caller identification
authentication solution, or actively
testing such a solution. Gateway
providers were also required to
implement both STIR/SHAKEN on the
IP portions of their networks as well as
a robocall mitigation program. They
must also certify to their
implementation and file a robocall
mitigation plan in the Robocall
Mitigation Database.
Federal Communications Commission.
Katura Jackson,
Federal Register Liaison Officer.
[FR Doc. 2022–19097 Filed 9–2–22; 8:45 am]
BILLING CODE 6712–01–P
FEDERAL COMMUNICATIONS
COMMISSION
[FR ID: 103360]
Privacy Act of 1974; Matching Program
Federal Communications
Commission.
ACTION: Notice of a new matching
program.
AGENCY:
In accordance with the
Privacy Act of 1974, as amended
(‘‘Privacy Act’’), this document
announces a new computer matching
program the Federal Communications
Commission (‘‘FCC’’ or ‘‘Commission’’
or ‘‘Agency’’) and the Universal Service
SUMMARY:
PO 00000
Frm 00054
Fmt 4703
Sfmt 4703
Administrative Company (USAC) will
conduct with the North Carolina
Department of Health and Human
Services. The purpose of this matching
program is to verify the eligibility of
applicants to and subscribers of Lifeline,
and the Affordable Connectivity
Program (ACP), both of which are
administered by USAC under the
direction of the FCC. More information
about these programs is provided in the
SUPPLEMENTARY INFORMATION section
below.
Written comments are due on or
before October 6, 2022. This computer
matching program will commence on
October 6, 2022, and will conclude 18
months after the effective date.
ADDRESSES: Send comments to Elliot S.
Tarloff, FCC, 45 L Street NE,
Washington, DC 20554, or to Privacy@
fcc.gov.
FOR FURTHER INFORMATION CONTACT:
Elliot S. Tarloff at 202–418–0886 or
Privacy@fcc.gov.
SUPPLEMENTARY INFORMATION: The
Lifeline program provides support for
discounted broadband and voice
services to low-income consumers.
Lifeline is administered by the
Universal Service Administrative
Company (USAC) under FCC direction.
Consumers qualify for Lifeline through
proof of income or participation in a
qualifying program, such as Medicaid,
the Supplemental Nutritional
Assistance Program (SNAP), Federal
Public Housing Assistance,
Supplemental Security Income (SSI),
Veterans and Survivors Pension Benefit,
or various Tribal-specific federal
assistance programs.
In the Consolidated Appropriations
Act, 2021, Public Law 116–260, 134
Stat. 1182, 2129–36 (2020), Congress
created the Emergency Broadband
Benefit Program (EBBP), and directed
use of the National Verifier to determine
eligibility based on various criteria,
including the qualifications for Lifeline
(Medicaid, SNAP, etc.). EBBP provided
$3.2 billion in monthly consumer
discounts for broadband service and
one-time provider reimbursement for a
connected device (laptop, desktop
computer, or tablet). In the
Infrastructure Investment and Jobs Act,
Public Law 117–58, 135 Stat. 429, 1238–
44 (2021) (codified at 47 U.S.C. 1751–
52), Congress modified and extended
EBBP, provided an additional $14.2
billion, and renamed it the Affordable
Connectivity Program (ACP). A
household may qualify for the ACP
benefit under various criteria, including
an individual qualifying for the FCC’s
Lifeline program.
DATES:
E:\FR\FM\06SEN1.SGM
06SEN1
Agencies
[Federal Register Volume 87, Number 171 (Tuesday, September 6, 2022)]
[Notices]
[Pages 54501-54502]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2022-19097]
-----------------------------------------------------------------------
FEDERAL COMMUNICATIONS COMMISSION
[OMB 3060-1285; FR ID 102882]
Information Collection Being Submitted for Review and Approval to
Office of Management and Budget
AGENCY: Federal Communications Commission.
ACTION: Notice and request for comments.
-----------------------------------------------------------------------
SUMMARY: As part of its continuing effort to reduce paperwork burdens,
as required by the Paperwork Reduction Act (PRA) of 1995, the Federal
Communications Commission (FCC or the Commission) invites the general
public and other Federal Agencies to take this opportunity to comment
on the following information collection. Pursuant to the Small Business
Paperwork Relief Act of 2002, the FCC seeks specific comment on how it
might ``further reduce the information collection burden for small
business concerns with fewer than 25 employees.'' The Commission may
not conduct or sponsor a collection of information unless it displays a
currently valid Office of Management and Budget (OMB) control number.
No person shall be subject to any penalty for failing to comply with a
collection of information subject to the PRA that does not display a
valid OMB control number.
DATES: Written comments and recommendations for the proposed
information collection should be submitted on or before October 6,
2022.
ADDRESSES: Comments should be sent to www.reginfo.gov/public/do/PRAMain. Find this particular information collection by selecting
``Currently under 30-day Review--Open for Public Comments'' or by using
the search function. Your comment must be submitted into
www.reginfo.gov per the above instructions for it to be considered. In
addition to submitting in www.reginfo.gov also send a copy of your
comment on the proposed information collection to Nicole Ongele, FCC,
via email to [email protected] and to [email protected]. Include in the
comments the OMB control number as shown in the SUPPLEMENTARY
INFORMATION below.
FOR FURTHER INFORMATION CONTACT: For additional information or copies
of the information collection, contact Nicole Ongele at (202) 418-2991.
To view a copy of this information collection request (ICR) submitted
to OMB: (1) go to the web page https://www.reginfo.gov/public/do/PRAMain, (2) look for the section of the web page called ``Currently
Under Review,'' (3) click on the downward-pointing arrow in the
``Select Agency'' box below the ``Currently Under Review'' heading, (4)
select ``Federal Communications Commission'' from the list of agencies
presented in the ``Select Agency'' box, (5) click the ``Submit'' button
to the right of the ``Select Agency'' box, (6) when the list of FCC
ICRs currently under review appears, look for the Title of this ICR and
then click on the ICR Reference Number. A copy of the FCC submission to
OMB will be displayed.
SUPPLEMENTARY INFORMATION: As part of its continuing effort to reduce
paperwork burdens, as required by the Paperwork Reduction Act (PRA) of
1995 (44 U.S.C. 3501-3520), the FCC invited the general public and
other Federal Agencies to take this opportunity to comment on the
following information collection. Comments are requested concerning:
(a) Whether the proposed collection of information is necessary for the
proper performance of the functions of the Commission, including
whether the information shall have practical utility; (b) the accuracy
of the Commission's burden estimates; (c) ways to enhance the quality,
utility, and clarity of the information collected; and (d) ways to
minimize the burden of the collection of information on the
respondents, including the use of automated collection techniques or
other forms of information technology. Pursuant to the Small Business
Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C.
3506(c)(4), the FCC seeks specific comment on how it might ``further
reduce the information collection burden for small business concerns
with fewer than 25 employees.''
OMB Control Number: 3060-1285.
[[Page 54502]]
Title: Compliance with the Non-IP Call Authentication Solution
Rules; Robocall Mitigation Database (RMD).
Form Number: N/A.
Type of Review: Revision of a currently approved collection.
Respondents: Business or other for profit entities.
Number of Respondents and Responses: 8,970 respondents; 8,970
responses.
Estimated Time per Response: 0.5 hours (30 minutes)-3 hours.
Frequency of Response: Recordkeeping requirement and on occasion
reporting requirement.
Obligation to Respond: Mandatory and required to obtain or retain
benefits. Statutory authority for these collections are contained in 47
U.S.C. 227b, 251(e), and 227(e) of the Communications Act of 1934.
Total Annual Burden: 20,503 hours.
Total Annual Cost: No Cost.
Privacy Impact Assessment: No impact(s).
Nature and Extent of Confidentiality: The Commission will consider
the potential confidentiality of any information submitted,
particularly where public release of such information could raise
security concerns (e.g., granular location information). Respondents
may request materials or information submitted to the Commission or to
the Administrator be withheld from public inspection under 47 CFR 0.459
of the Commission's rules.
Needs and Uses: The Pallone-Thune Telephone Robocall Abuse Criminal
Enforcement and Deterrence (TRACED) Act directs the Commission to
require, no later than 18 months from enactment, all voice service
providers to implement STIR/SHAKEN caller ID authentication technology
in the internet protocol (IP) portions of their networks and implement
an effective caller ID authentication framework in the non-IP portions
of their networks. Among other provisions, the TRACED Act also directs
the Commission to create extension mechanisms for voice service
providers. On September 29, 2020, the Commission adopted its Call
Authentication Trust Anchor Second Report and Order. See Call
Authentication Trust Anchor, WC Docket No. 17-97, Second Report and
Order, 36 FCC Rcd 1859 (adopted Sept. 29, 2020). The Second Report and
Order implemented section 4(b)(1)(B) of the TRACED Act, in part, by
requiring a voice service provider maintain and be ready to provide the
Commission upon request with documented proof that it is participating,
either on its own or through a representative, including third party
representatives, as a member of a working group, industry standards
group, or consortium that is working to develop a non-internet Protocol
caller identification authentication solution, or actively testing such
a solution. The Second Report and Order also implemented the extension
mechanisms in section 4(b)(5) by, in part, requiring voice service
providers to certify that they have either implemented STIR/SHAKEN or a
robocall mitigation program in the Robocall Mitigation Database. On May
19, 2022, the Commission adopted similar obligations for gateway
providers. See Advanced Methods to Target and Eliminate Unlawful
Robocalls, Call Authentication Trust Anchor, CG Docket No. 17-59, WC
Docket No. 17-97, Sixth Report and Order et al., FCC 22-37 (adopted May
19, 2022). Specifically, like voice service providers, gateway
providers were required to maintain and be ready to provide the
Commission upon request with documented proof that they are
participating, either on their own or through a representative,
including third party representatives, as a member of a working group,
industry standards group, or consortium that is working to develop a
non-internet Protocol caller identification authentication solution, or
actively testing such a solution. Gateway providers were also required
to implement both STIR/SHAKEN on the IP portions of their networks as
well as a robocall mitigation program. They must also certify to their
implementation and file a robocall mitigation plan in the Robocall
Mitigation Database.
Federal Communications Commission.
Katura Jackson,
Federal Register Liaison Officer.
[FR Doc. 2022-19097 Filed 9-2-22; 8:45 am]
BILLING CODE 6712-01-P