Como e por que implantar IPv6 no meu provedor de acesso

Summary

The video follows Joel, a network manager at ACME Internet provider, as he navigates the challenges of the depletion of IPv4 addresses. With IPv6 adoption being the future, Joel researches and plans for its implementation at his small but growing company. While dealing with limited IPv4 resources, he learns about IPv6's benefits and the necessity of dual-stack systems. He faces hurdles with hardware compatibility, but the shift to IPv6 becomes crucial for the sustainability and future growth of his provider. The video emphasizes the importance of IPv6 deployment for staying ahead in the evolving internet landscape.

Takeaways

• 😀 IPv4 addresses are running out, but the number of internet-connected devices continues to grow, creating a need for solutions.
• 😀 The exhaustion of IPv4 addresses has led to the implementation of a small reserve of addresses for gradual distribution in Latin America and the Caribbean.
• 😀 The first portion of the IPv4 reserve consists of a /11 block, with a limit of one /22 per provider, and can be requested every six months.
• 😀 The second portion of the reserve is for new entrants, allowing them to request a /22 once, but only if they’ve never requested IPv4 addresses before.
• 😀 NAT (Network Address Translation) was initially considered as a potential solution by Joel, but he realized it creates limitations for users, especially for services like VoIP and gaming.
• 😀 Carrier Grade NAT (CGNAT) would complicate logging requirements, making it a less viable solution for providers in terms of both technical limitations and regulatory concerns.
• 😀 Joel's provider, ACME, could still obtain IPv4 addresses from the reserve for a limited time (likely until 2015 or 2016), but needed to plan for future growth.
• 😀 The recommended solution by NIC.br is to deploy IPv6, which would allow for long-term scalability and alleviate the strain on IPv4 addresses.
• 😀 Many major websites and services, including YouTube, Google, and Facebook, are already IPv6-enabled, making the transition more practical for providers and users alike.
• 😀 Joel planned to implement a dual-stack system (both IPv4 and IPv6) initially, eventually transitioning to IPv6-only in the coming years as IPv4 exhaustion takes effect.

Q & A

What issue is Joel facing at the start of the video?

Joel is dealing with the water rationing in his city, which is affecting his daily routine and causing stress. He also faces the challenge of the depletion of IPv4 addresses.

How does Joel compare the depletion of IPv4 addresses to the water shortage?

Joel compares the IPv4 address shortage to the water shortage in his city. Both issues involve the depletion of a shared resource and require measures like rationing or gradual exhaustion.

What is the role of the NIC.br in the IPv4 address distribution in Brazil?

The NIC.br, through the Registro.br department, is responsible for distributing IPv4 addresses in Brazil. They have a limited reserve of addresses due to the exhaustion of IPv4.

How does the NIC.br handle the exhaustion of IPv4 addresses?

NIC.br has created a small technical reserve of IPv4 addresses, divided into two halves. The first is for gradual exhaustion, while the second is reserved for new entrants. Both allocations are limited to a /22 block, and a new request can be made every six months.

What challenges did Joel consider with using NAT (Network Address Translation) for IPv4?

Joel realized that using NAT would cause issues for users, such as limitations in applications like peer-to-peer file sharing, VoIP, and gaming. Additionally, NAT would complicate logging and IP address allocation, making it difficult to track customers.

Why did Joel ultimately decide against using NAT for his provider?

Joel concluded that using NAT, specifically Carrier Grade NAT (CGNAT), would lead to significant limitations for his users and create additional operational difficulties, such as tracking shared IPs and the cost of additional infrastructure.

What solution did Joel explore to address the depletion of IPv4 addresses?

Joel decided to implement IPv6, as it was a recommended solution by NIC.br. He also considered maintaining IPv4 connectivity through techniques like NAT64, 464XLAT, or NAT444 for compatibility with legacy systems and content.

How did Joel determine that IPv6 adoption was the right path for his provider?

Joel researched and found that major services like YouTube, Google, Netflix, and Facebook already supported IPv6. Additionally, large providers in the U.S. and Europe were ahead in adopting IPv6, which gave him confidence in the transition.

What steps did Joel plan to take in implementing IPv6 at his provider?

Joel planned to secure IPv6 transit with his providers, request an IPv6 block from NIC.br, and implement IPv6 across his network. He also planned to run dual stack (IPv4 and IPv6) operations in the short term, transitioning fully to IPv6 over time.

What challenges did Joel face in deploying IPv6 to his customers?

Joel faced the challenge of his existing customer equipment (CPEs) not supporting IPv6. He would need to work with manufacturers for firmware updates or explore alternative equipment to ensure IPv6 connectivity for his users.