The Federal Communications Commission hit a U.S. communications with penalties totalling almost $3 million last week following a preventable service outage that affected a communications service utilised by Americans with disabilities, and all because the company failed to renew their domain name in 2016.
The FCC reached a settlement with Sorenson Communications following the outage with the company agreeing to provide enhanced notices to consumers during outages, and pay $2.7 million to reimburse the Telecommunications Relay Services Fund and a $252,000 penalty.
Video relay service, a form of telecommunications relay service, enables people who are deaf, hard-of-hearing or speech disabled to make calls over broadband through intermediaries using American Sign Language and video equipment. VRS is funded through the Telecommunications Relay Service Fund.
To qualify for reimbursement, VRS providers must comply with the Communications Act and FCC rules, which require that services be able at all times to handle any type of call normally provided by carriers, including 911 calls.
In 2016, Sorenson failed to renew its domain name, and on 6 June, Sorensonâs websiteâs domain registration was deactivated. As a result, consumersâ calls made through this domain failed to connect, resulting in a service outage.
Service was not fully restored until 8 June. The Commissionâs investigation found the outage was preventable. The FCCâs Enforcement Bureau investigated this incident and reached todayâs settlement with the company.
Abstract: The Internet is in transition. The original address space, IPv4, is nearly exhausted; the Internet is in the progress of migrating to the new IPv6 address space. Continue reading Potential Impacts on Communications from IPv4 Exhaustion & IPv6 Transition by Robert Cannon, Federal Communications Commission; Cybertelecom
Abstract: The Internet is in transition. The original address space, IPv4, is nearly exhausted; the Internet is in the progress of migrating to the new IPv6 address space.The Internet Protocol version 4 (IPv4) developed in the late 1970s has the capacity for about 4 billion unique addresses. It would have been hard to imagine in the 1970s that 4 billion addresses were not going to be enough. But by the early 1990s, Internet engineers recognized that the supply of addresses was relatively limited compared to likely demand, and they set to work designing a successor to IPv4. They developed a new Internet Protocol, IPv6, with a vastly increased address space: 340 trillion trillion trillion addresses.Broadband Internet access has become essential to the United States and the rest of the world. The exhaustion of IPv4 addresses and the transition to IPv6 could result in significant, but not insurmountable, problems for broadband Internet services. In the short term, to permit the network to continue to grow, engineers have developed a series of kludges. These kludges include more efficient use of the IPv4 address resource, conservation, and the sharing of IPv4 addresses through the use of Network Address Translation (NAT). While these provide partial mitigation for IPv4 exhaustion, they are not a long-term solution, increase network costs, and merely postpone some of the consequences of address exhaustion without solving the underlying problem. Some of these fixes break end-to-end connectivity, impairing innovation and hampering applications, degrading network performance, and resulting in an inferior version of the Internet. These kludges require capital investment and ongoing operational costs by network service providers, diverting investment from other business objectives. Network operators will be confronted with increased costs to offer potentially inferior service.The short term solutions are necessary because there is not enough time to completely migrate the entire public Internet to “native IPv6” where end users can communicate entirely via IPv6. Network protocol transitions require significant work and investment, and with the exhaustion of IPv4 addresses looming, there is insufficient time to complete the full IPv6 transition.But the short-term solutions are problematic. The “solution to the solution” is to complete the transition to a native IPv6 network. A native IPv6 network will restore end-to-end connectivity with a vastly expanded address space, will improve network performance, and should decrease costs. Completing the transition of the public Internet to IPv6 will take time.To read this FCC article in full, see: