by Brian Boyko
Editor, Network Performance Daily
The frustrating thing about IPv6 is that as much as we hate to think about it, as much as the transfer might irk and infuriate us – we’ve just about filled up IPv4, and that means that someday soon, we have to move to IPv6.
You can only delay the inevitable, which, right now, looks like it will happen in less than five years.
One of the big selling points of IPv6 was autoconfiguration. Sure, it’s a pain in the but to enter in longer numbers, so the IPv6 standard was designed so that you’d have to enter in those numbers less often. Through “stateless autoconfiguration,” you eliminated the need to set up DHCP.
But there are some advantages to the existing DHCP protocols, especially with visibility into the network, tracking and debugging features, as well as additional manual control – and so many companies, among them Cisco, are pushing for DHCPv6.
In the stateless autoconfiguration, you get true plug and play. The client is assigned an IP when it connects – without the need for a special server. Boom. Done. That’s perfect for portable devices, accessories like printers, and smaller operations in home and small office networks.
But DHCPv6 lets network manajers know what devices are connected to the network, as well as their IP addresses (and if necessary, to reassign them.) This is a major component in troubleshooting and monitoring the network to improve performance.
The downside: In addition to the complexities of changing over from IPv4, network administrators and engineers would have to manage a DHCPv6 network service as well.
Now, as mentioned, small home networks will find stateless autoconfiguration to be a boon, and ISPs will also be happy to avoid using DHCP to assign the addresses of the end-user. But for everyone else, DHCP is no longer a requirement – it’s a choice.
The odd thing about choices in corporate IT environments… it’s usually a short time to solve a problem, but it can take forever to make a decision.
Making a protocol which supports 3.40282367 × 10^38 addresses just that teensy little bit more complicated…
About Brian Boyko
Subscribe
Leave a Reply Click here to cancel reply.
- All Eyes on London’s Docklands January 26, 2012
-
“BYOD” Inspires FUD in IT Managers
January 27, 2012
-
The Illusion of ITIL and the Misunderstanding of IT Tools
January 17, 2012
-
How IT Can Get Control over Mobile Apps
February 1, 2012
-
How to Play a Complete Game when Managing IT
February 2, 2012
-
Balancing Act: A Framework for IT Transformation
February 7, 2012
- Is Your Klout Score Higher Than a 12-Year-Old’s February 6, 2012
-
Service Assurance Daily Weekly Reading List
February 3, 2012
- Super Bowl Ads: A Blast from the Past, a Look Ahead February 3, 2012
-
How to Play a Complete Game when Managing IT
February 2, 2012
-
Mobile Application Development: Gone are those days where mobile phones acted just...
- It’s Monday Morning…. | Meetings Improved.: [...] Mondays always seem to come so fast. Before ...
-
Shafiq Hajee: Remaining competitive in this day and age might no...
-
Melissa: I am totally behind this. Where would we grassroot...
-
Aryne: Hi Jason, I definitely like your idea! Being a new...
APM
Application Management
Application Performance
application performance management
Ask the Service Assurance Expert
Bandwidth Issues
Business Service Management
Capacity Planning
CA World
cloud
Cloud Computing
Commentary
Daily Links
Data Center
Editorial
IT Careers
ITIL
IT Management
IT Management & ITSM
ITSM
IT Spending
Just Too Cool
Miscellany
Mobile
Network Engineering
Networking Tools
Network Management
Network Monitoring
Network Performance
Networks
Network Utilization
Podcasts
Risk Management
Service Assurance
Social Networking
Tech Media Critique
Vidcasts
Video IP
Virtualization
VoIP
WAN Optimization
Web Services
Weekly Reading List
Whiteboard Series
WLAN Performance
Recent Tweets From @CAsvcAssur
Follow @CAsvcAssur on Twitter



No comments yet.