IPv6 Center of Excellence
Welcome to the Infoblox IPv6 CoE blog!
Paul, Tom and I share this blog, though we each publish under our own bylines. While we’ve usually got IPv6 topics on our minds, we’re also interested in hearing what’s on yours. If you have questions or suggestions, please feel free to get in touch with us at ipv6coe@infoblox.com.
Last month, Infoblox began deployment of IPv6 on our internal networks. We've supported IPv6 on our web server and name servers since World IPv6 Day in 2011, but we'd held off on the implementation of IPv6 on internal networks until now. I thought those of you considering an internal IPv6 deployment might appreciate a few of our war stories, while the rest of you might get a chuckle or two from our mishaps. Here's our first story - a cliffhanger!
Last month, Infoblox began deployment of IPv6 on our internal networks. We've supported IPv6 on our web server and name servers since World IPv6 Day in 2011, but we'd held off on the implementation of IPv6 on internal networks until now. I thought those of you considering an internal IPv6 deployment might appreciate a few of our war stories, while the rest of you might get a chuckle or two from our mishaps. Here's our first story - a cliffhanger!
And now, part three of a four-part blog on creating an IPv6 addressing plan.
A Sample Plan
Let’s say you’re creating an address plan for a campus LAN that has groups of network segments supporting particular functions (i.e., voice, wired and wireless data, etc.). In addition to the addressing required for these functions, you’ll also need addresses for infrastructure. Finally, additional subnets for future use should also be included: