Information Collection Being Reviewed by the Federal Communications Commission, 4824-4825 [2023-01436]
Download as PDF
<![CDATA[
lotter on DSK11XQN23PROD with NOTICES1
4824
Federal Register / Vol. 88, No. 16 / Wednesday, January 25, 2023 / Notices
replaced the Interstate Common Line
Support (ICLS) mechanism with the
Connect America Fund—Broadband
Loop Support (CAF–BLS) mechanism.
While ICLS supported only lines used to
provide traditional voice service
(including voice service bundled with
broadband service), CAF–BLS also
supports consumer broadband-only
loops. For the purposes of calculating
and monitoring CAF–BLS, rate-of-return
carriers that receive CAF–BLS must file
common line and consumer broadbandonly loop counts on FCC Form 507,
forecasted common line and consumer
broadband-only loop costs and revenues
on FCC Form 508, and actual common
line and consumer broadband-only loop
costs and revenues on FCC Form 509.
See 47 CFR 54.903(a).
In December 2018, the Commission
adopted the December 2018 Rate-ofReturn Reform Order to require rate-ofreturn carriers that receive Alternative
Connect American Model (A–CAM) or
Alaska Plan support to file line count
data on FCC Form 507 as a condition of
high-cost support. Historically, all rateof-return carriers received CAF BLS or,
prior to that, ICLS, and were required to
file line count data on FCC Form 507 as
a condition of that support. In recent
years, some rate-of-return carriers have
elected to receive A–CAM I, A–CAM II,
or Alaska Plan instead, and those
carriers were not required to file line
count data because the requirement to
file applied only to rate-of-return
carriers receiving CAF BLS. In order to
restore a data set that the Commission
relied on to evaluate the effectiveness of
its high-cost universal service programs,
the Commission revised its rules in that
Order to require all rate-of-return
carriers to file that data. While carriers
receiving CAF–BLS must file the line
count data on March 31 for line counts
as of the prior December 31, the A–CAM
I, A–CAM II, and Alaska Plan carriers
will be required to file on July 1 of each
year to coincide with other existing
requirements in OMB Control No. 3060–
0986. Connect America Fund et al., WC
Docket No. 10–90 Report and Order,
Further Notice of Proposed Rulemaking
and Order on Reconsideration, 33 FCC
Rcd 11893 (2018) (2018 Rate-of-Return
Reform Order). See also 47 CFR
54.313(f)(5).
Federal Communications Commission.
Katura Jackson,
Federal Register Liaison Officer.
[FR Doc. 2023–01462 Filed 1–24–23; 8:45 am]
BILLING CODE 6712–01–P
VerDate Sep<11>2014
16:55 Jan 24, 2023
Jkt 259001
FEDERAL COMMUNICATIONS
COMMISSION
[OMB 3060–1126; FR ID 123425]
Information Collection Being Reviewed
by the Federal Communications
Commission
Federal Communications
Commission.
ACTION: Notice and request for
comments.
AGENCY:
As part of its continuing effort
to reduce paperwork burdens, and 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.
Comments are requested concerning:
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;
the accuracy of the Commission’s
burden estimate; ways to enhance the
quality, utility, and clarity of the
information collected; 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; and ways to
further reduce the information
collection burden on small business
concerns with fewer than 25 employees.
The FCC may not conduct or sponsor a
collection of information unless it
displays a currently valid 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 Office
of Management and Budget (OMB)
control number.
DATES: Written PRA comments should
be submitted on or before March 27,
2023. If you anticipate that you will be
submitting comments, but find it
difficult to do so within the period of
time allowed by this notice, you should
advise the contact listed below as soon
as possible.
ADDRESSES: Direct all PRA comments to
Nicole Ongele, FCC, via email PRA@
fcc.gov and to nicole.ongele@fcc.gov.
FOR FURTHER INFORMATION CONTACT: For
additional information about the
information collection, contact Nicole
Ongele, (202) 418–2991.
SUPPLEMENTARY INFORMATION:
OMB Control Number: 3060–1126.
SUMMARY:
PO 00000
Frm 00026
Fmt 4703
Sfmt 4703
Title: Testing and Logging
Requirements for Wireless Emergency
Alerts (WEA).
Form Number: Not applicable.
Type of Review: Extension of a
currently approved collection.
Respondents: Business or other forprofit entities.
Number of Respondents and
Responses: 76 Participating CMS
Providers; 429,020 Responses.
Estimated Time per Response:
0.000694 hours (2.5 seconds) to generate
each alert log; 2 hours to respond to
each request for alert log data or
information about geo-targeting.
Frequency of Response: Monthly and
on occasion reporting requirements and
recordkeeping requirement.
Obligation to Respond: Required to
obtain or retain benefits. Statutory
authority for this information collection
is contained in 47 U.S.C. 151, 152,
154(i) and (o), 301, 301(r), 303(v), 307,
309, 335, 403, 544(g), 606 and 615 of the
Communications Act of 1934, as
amended, as well as by sections 602(a),
(b), (c), (f), 603, 604 and 606 of the
WARN Act.
Total Annual Burden: 119,021 hours.
Total Annual Cost: No cost.
Privacy Act Impact Assessment: No
impact(s).
Nature and Extent of Confidentiality:
Participating CMS Providers shall make
available upon request to the
Commission and FEMA, and to
emergency management agencies that
offer confidentiality protection at least
equal to that provided in the federal
Freedom of Information Act (FOIA)
their alert logs and information about
their approach to geo-targeting insofar
as the information pertains to alerts
initiated by that emergency management
agency.
Needs and Uses: The Commission
adopted requirements for Participating
CMS Providers to log the basic attributes
of alerts they receive at their Alert
Gateway, to maintain those logs for at
least 12 months, to make those logs
available upon request to the
Commission and FEMA, and to
emergency management agencies that
offer confidentiality protection at least
equal to that provided by federal FOIA.
The Commission also requires
Participating CMS Providers to disclose
information regarding their capabilities
for geo-targeting Alert Messages upon
request to such emergency management
agencies insofar as it would pertain to
Alert Messages initiated by that
emergency management agency. These
recordkeeping and reporting
requirements have potential to increase
emergency managers’ confidence that
WEA will work as intended when
E:\FR\FM\25JAN1.SGM
25JAN1
Federal Register / Vol. 88, No. 16 / Wednesday, January 25, 2023 / Notices
needed. This increased confidence in
system availability encourages
emergency management agencies that
do not currently use WEA to become
authorized. These reporting and
recordkeeping requirements also help to
ensure a fundamental component of
system integrity. Alert logs are
necessary to establish a baseline for
system integrity against which future
iterations of WEA can be evaluated.
Without records that can be used to
describe the quality of system integrity,
and the most common causes of
message transmission failure, it would
be difficult to evaluate how any changes
to WEA may affect system integrity.
Federal Communications Commission.
Marlene Dortch,
Secretary, Office of the Secretary.
[FR Doc. 2023–01436 Filed 1–24–23; 8:45 am]
BILLING CODE 6712–01–P
GENERAL SERVICES
ADMINISTRATION
[Notice–Q–2023–01; Docket No. 2023–0002;
Sequence No. 4]
Request for Nominations; Federal
Secure Cloud Advisory Committee
Federal Acquisition Service
(Q), General Services Administration
(GSA).
ACTION: Notice. The U.S. General
Services Administration (GSA) is
seeking nominations for membership to
the Federal Secure Cloud Advisory
Committee (the Committee).
AGENCY:
GSA is seeking nominations
for membership to the Federal Secure
Cloud Advisory Committee (hereinafter
‘‘the Committee’’ or ‘‘the FSCAC’’), a
Federal advisory committee required by
statute.
DATES: GSA will consider complete
nominations that are received no later
than Thursday, February 9, 2023.
ADDRESSES: Nominations will be
accepted electronically. Please submit
nominations via https://forms.gle/
iuBc67bMYjo1xB5V6, and email
accompanying documents to fscac@
gsa.gov with the subject line: FSCAC
NOMINATION—[Nominee Name].
FOR FURTHER INFORMATION CONTACT:
Zach Baldwin, Federal Risk and
Authorization Management Program,
202–536–8216, fscac@gsa.gov.
SUPPLEMENTARY INFORMATION:
lotter on DSK11XQN23PROD with NOTICES1
SUMMARY:
Background
GSA, in compliance with the
FedRAMP Authorization Act of 2022, is
required to establish the Federal Secure
VerDate Sep<11>2014
16:55 Jan 24, 2023
Jkt 259001
Cloud Advisory Committee (FSCAC), a
statutory advisory committee in
accordance with the provisions of FACA
(5 U.S.C. 10). The Federal Risk and
Authorization Management Program
(FedRAMP) within GSA is responsible
for providing a standardized, reusable
approach to security assessment and
authorization for cloud computing
products and services that process
unclassified information used by
agencies.
The FSCAC will provide advice and
recommendations to the Administrator
of GSA, the FedRAMP Board, and
agencies on technical, financial,
programmatic, and operational matters
regarding the secure adoption of cloud
computing products and services. The
FSCAC will ensure effective and
ongoing coordination of agency
adoption, use, authorization,
monitoring, acquisition, and security of
cloud computing products and services
to enable agency mission and
administrative priorities. The purposes
of the Committee are:
• To examine the operations of
FedRAMP and determine ways that
authorization processes can
continuously be improved, including
the following:
Æ Measures to increase agency reuse
of FedRAMP authorizations.
Æ Proposed actions that can be
adopted to reduce the burden,
confusion, and cost associated with
FedRAMP authorizations for cloud
service providers.
Æ Measures to increase the number of
FedRAMP authorizations for cloud
computing products and services
offered by small businesses concerns (as
defined by section 3(a) of the Small
Business Act (15 U.S.C. 632(a)).
Æ Proposed actions that can be
adopted to reduce the burden and cost
of FedRAMP authorizations for
agencies.
• Collect information and feedback
on agency compliance with and
implementation of FedRAMP
requirements.
• Serve as a forum that facilitates
communication and collaboration
among the FedRAMP stakeholder
community.
The Federal Secure Cloud Advisory
Committee will meet no fewer than
three (3) times a calendar year Meetings
shall occur as frequently as needed,
called, and approved by the DFO.
Meetings will be held virtually or in
person. Members will serve without
compensation and may be allowed
travel expenses, including per diem, in
accordance with 5 U.S.C. 5703.
The Committee shall be comprised of
not more than 15 members who are
PO 00000
Frm 00027
Fmt 4703
Sfmt 4703
4825
qualified representatives from the
public and private sectors, appointed by
the Administrator, in consultation with
the Director of OMB, as follows:
i. The GSA Administrator or the GSA
Administrator’s designee, who shall be
the Chair of the Committee.
ii. At least one representative each
from the Cybersecurity and
Infrastructure Security Agency and the
National Institute of Standards and
Technology.
iii. At least two officials who serve as
the Chief Information Security Officer
within an agency, who shall be required
to maintain such a position throughout
the duration of their service on the
Committee.
iv. At least one official serving as
Chief Procurement Officer (or
equivalent) in an agency, who shall be
required to maintain such a position
throughout the duration of their service
on the Committee.
v. At least one individual representing
an independent assessment
organization.
vi. At least five representatives from
unique businesses that primarily
provide cloud computing services or
products, including at least two
representatives from a small business
(as defined by section 3(a) of the Small
Business Act (15 U.S.C. 632(a))).
vii. At least two other representatives
from the Federal Government as the
Administrator determines to be
necessary to provide sufficient balance,
insights, or expertise to the Committee.
Each member shall be appointed for a
term of three (3) year terms, except the
initial terms, which may be staggered
one (1), two (2) or three (3) year terms
to establish a rotation in which one
third of the members are selected. No
member shall be appointed for more
than two (2) consecutive terms nor shall
any member serve for more than six (6)
consecutive years. GSA values
opportunities to increase diversity,
equity, inclusion and accessibility on its
federal advisory committees.
Members will be designated as
Regular Government Employees (RGEs)
or Representative members as
appropriate and consistent with Section
3616(d) of the FedRAMP Authorization
Act of 2022. GSA’s Office of General
Counsel will assist the Designated
Federal Officer (DFO) to determine the
advisory committee member
designations. Representatives are
members selected to represent a specific
point of view held by a particular group,
organization, or association. Members
who are full time or permanent parttime Federal civilian officers or
employees shall be appointed to serve
as Regular Government Employee (RGE)
E:\FR\FM\25JAN1.SGM
25JAN1
]]>Agencies
[Federal Register Volume 88, Number 16 (Wednesday, January 25, 2023)]
[Notices]
[Pages 4824-4825]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2023-01436]
-----------------------------------------------------------------------
FEDERAL COMMUNICATIONS COMMISSION
[OMB 3060-1126; FR ID 123425]
Information Collection Being Reviewed by the Federal
Communications Commission
AGENCY: Federal Communications Commission.
ACTION: Notice and request for comments.
-----------------------------------------------------------------------
SUMMARY: As part of its continuing effort to reduce paperwork burdens,
and 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. Comments are requested
concerning: 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; the
accuracy of the Commission's burden estimate; ways to enhance the
quality, utility, and clarity of the information collected; 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; and ways to further reduce the
information collection burden on small business concerns with fewer
than 25 employees. The FCC may not conduct or sponsor a collection of
information unless it displays a currently valid 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 Office of Management and Budget (OMB) control number.
DATES: Written PRA comments should be submitted on or before March 27,
2023. If you anticipate that you will be submitting comments, but find
it difficult to do so within the period of time allowed by this notice,
you should advise the contact listed below as soon as possible.
ADDRESSES: Direct all PRA comments to Nicole Ongele, FCC, via email
[email protected] and to [email protected].
FOR FURTHER INFORMATION CONTACT: For additional information about the
information collection, contact Nicole Ongele, (202) 418-2991.
SUPPLEMENTARY INFORMATION:
OMB Control Number: 3060-1126.
Title: Testing and Logging Requirements for Wireless Emergency
Alerts (WEA).
Form Number: Not applicable.
Type of Review: Extension of a currently approved collection.
Respondents: Business or other for-profit entities.
Number of Respondents and Responses: 76 Participating CMS
Providers; 429,020 Responses.
Estimated Time per Response: 0.000694 hours (2.5 seconds) to
generate each alert log; 2 hours to respond to each request for alert
log data or information about geo-targeting.
Frequency of Response: Monthly and on occasion reporting
requirements and recordkeeping requirement.
Obligation to Respond: Required to obtain or retain benefits.
Statutory authority for this information collection is contained in 47
U.S.C. 151, 152, 154(i) and (o), 301, 301(r), 303(v), 307, 309, 335,
403, 544(g), 606 and 615 of the Communications Act of 1934, as amended,
as well as by sections 602(a), (b), (c), (f), 603, 604 and 606 of the
WARN Act.
Total Annual Burden: 119,021 hours.
Total Annual Cost: No cost.
Privacy Act Impact Assessment: No impact(s).
Nature and Extent of Confidentiality: Participating CMS Providers
shall make available upon request to the Commission and FEMA, and to
emergency management agencies that offer confidentiality protection at
least equal to that provided in the federal Freedom of Information Act
(FOIA) their alert logs and information about their approach to geo-
targeting insofar as the information pertains to alerts initiated by
that emergency management agency.
Needs and Uses: The Commission adopted requirements for
Participating CMS Providers to log the basic attributes of alerts they
receive at their Alert Gateway, to maintain those logs for at least 12
months, to make those logs available upon request to the Commission and
FEMA, and to emergency management agencies that offer confidentiality
protection at least equal to that provided by federal FOIA. The
Commission also requires Participating CMS Providers to disclose
information regarding their capabilities for geo-targeting Alert
Messages upon request to such emergency management agencies insofar as
it would pertain to Alert Messages initiated by that emergency
management agency. These recordkeeping and reporting requirements have
potential to increase emergency managers' confidence that WEA will work
as intended when
[[Page 4825]]
needed. This increased confidence in system availability encourages
emergency management agencies that do not currently use WEA to become
authorized. These reporting and recordkeeping requirements also help to
ensure a fundamental component of system integrity. Alert logs are
necessary to establish a baseline for system integrity against which
future iterations of WEA can be evaluated. Without records that can be
used to describe the quality of system integrity, and the most common
causes of message transmission failure, it would be difficult to
evaluate how any changes to WEA may affect system integrity.
Federal Communications Commission.
Marlene Dortch,
Secretary, Office of the Secretary.
[FR Doc. 2023-01436 Filed 1-24-23; 8:45 am]
BILLING CODE 6712-01-P
