From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: [WISPAMembers] FCC Order Terminating Certain Form 477 Requirements
Date: Mon, 12 Dec 2022 16:51:43 -0800 [thread overview]
Message-ID: <CAA93jw5MgkshNQigUfByk+9XvSR5-9uO6be58L0A3nwpxHB52w@mail.gmail.com> (raw)
In-Reply-To: <5b9dbe4f30ca40a28a55633a570cbaed@members.wispa.org>
[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]
---------- Forwarded message ---------
From: Louis Peraertz <wispamembers+89724@wispa.org>
Date: Mon, Dec 12, 2022, 2:05 PM
Subject: [WISPAMembers] FCC Order Terminating Certain Form 477 Requirements
To: <dave.taht@gmail.com>
The FCC has taken a step to implement the Broadband Data Collection (BDC)
and modernize the Form 477 data program. It has issued an order that will
terminate the collection of broadband deployment data through Form 477
effective upon publication of this Order in the Federal Register. Instead,
the FCC will require that providers submit broadband deployment data
through the Broadband Data Collection Process for that information. The FCC
will continue to collect broadband and voice subscription data using the
FCC Form 477, but filers will submit their data through the BDC system.
The FCC now has a process in place for collecting more precise
location-specific data than what was used for the Form 477 process.
Going forward, the BDC system, rather than the Form 477 filing platform,
will be used for the submission of both the subscription data collected for
Form 477 and the availability data collected for the BDC. Beginning with
the data as of December 31, 2022, providers are required to submit the
following data using the BDC filing system: fixed and mobile broadband and
voice Form 477 subscription data, fixed and mobile BDC broadband
availability data, BDC mobile voice availability data. The Form 477 filing
system will no longer be used to collect new Form 477 submissions and will
remain open only for filers to make corrections to existing Form 477
filings.
(See paragraphs 12 and 13 of attached order for additional details).
Posted by *Louis Peraertz* to: "Member's Forum board, "FCC Order
Terminating Certain Form 477 Requirements" topic.
*Attachments*
[FCC Order Sunsetting Certain Form 477 Requirements. 12.12.2022. 5 PM.pdf]
<https://members.wispa.org/members/forum/open_attachment.php?att_id=31036035>
*You are opted-in to the [Member's Forum] board. This board is email-list
enabled -- replying to this email will send your message to the entire
message board. For best results if replying, please do so with a clean
message (with no reply or forward history in the message body).*
If you want to stop receiving these emails please click here: opt-out and
unsubscribe
<http://members.wispa.org/members/forum/opt_out.php?fix=X&orgcode=WISP&mid=1959771181>
[-- Attachment #2: Type: text/html, Size: 3271 bytes --]
parent reply other threads:[~2022-12-13 0:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5b9dbe4f30ca40a28a55633a570cbaed@members.wispa.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5MgkshNQigUfByk+9XvSR5-9uO6be58L0A3nwpxHB52w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox