Network Architect, Author, and Speaker
Joined on June 2, 2012 – United States
Total Post Views: 33,128
Chris Grundemann specializes in the design, implementation, and operation of large IP, Ethernet, and Wireless Ethernet networks and is deeply involved in the policy and politics surrounding internetworking and the Internet. He is JNCIE #449 and is currently engaged with CableLabs as a Network Architect focusing on technical leadership and contributions to standards & specifications within many current Ethernet and IP networking areas, specifically: Carrier Ethernet, VPNs, MPLS, and IPv6.
Chris is the author of Day One: Exploring IPv6 and Day One: Advanced IPv6 Configuration, as well as several IETF Internet Drafts and various industry papers. He is the founding Chair of CO ISOC, the Colorado chapter of the Internet Society, a board member of the Rocky Mountain IPv6 Task Force (RMv6TF), an elected member of the ARIN Advisory Council (AC), a member of the NANOG Program Committee (PC), Co-Chair of the UPnP IPv6 Task Force, and a member of the CEA Pv6 Transition Working Group. Chris also maintains a personal weblog aimed towards Internet related posts typically focusing on network operation and design, tech-policy and the future of the Internet.
Any and all views expressed by Chris are his and his alone. They do not represent the views of any organizations or individuals that he may be associated with in any way.
Except where otherwise noted, all postings by Chris Grundemann on CircleID are licensed under a Creative Commons License.
I recently attended RIPE 66 where Tore Anderson presented his suggested policy change 2013-03, "No Need -- Post-Depletion Reality Adjustment and Cleanup." In his presentation, Tore suggested that this policy proposal was primarily aimed at removing the requirement to complete the form(s) used to document need. There was a significant amount of discussion around bureaucracy, convenience, and "liking" (or not) the process of demonstrating need. Laziness has never been a compelling argument for me and this is no exception. more»
I'm a network engineer, and like many engineers I often gravitate to the big projects; large networks with problems of scale and complexity in my case. However, I also consider myself a student of Occam's razor and often quote Antoine de Saint-Exupéry: "perfection is reached not when there is nothing left to add, but when there is nothing left to take away." In this spirit of "less is more" I have recently become intrigued by the problems appearing in home networking. more»
Almost every conversation I have with folks just learning about IPv6 goes about the same way; once I'm finally able to convince them that IPv6 is not going away and is needed in their network, the questions start. One of the most practical and essential early questions that needs to be asked (but often isn't) is "how do I lay out my IPv6 subnets?" The reason this is such an important question is that it's very easy to get IPv6 subnetting wrong by doing it like you do in IPv4. more»
Declan McCullagh recently opined that the "FBI [and the] DEA warn [that] IPv6 could shield criminals from police." His post was picked-up relatively widely in the past few days, with the headlines adding more hyperbole along the way. So just how real is this threat? Let's take a look. more»
World IPv6 Launch kicked off 6 June 2012 at 00:00 UTC. On this day, multitudes of website operators, network operators and home router vendors from all over the world have joined thousands of companies and millions of websites in permanently enabling the next generation Internet. They have done this by turning IPv6 support on by default in (at least some of) their products and services. This is a major milestone in the history of the Internet. more»