The 2012 North American IPv6 Summit has come and gone but requests for my slides from the third day continue to roll in. So I’ve decided, as I often do, to post them up here. My talk “Carrier Grade NAT – Observations and Recommendations” was given as part of the “IPv6 Transition and IPv6 in [...]
This year’s summit is the North American (rather than Rocky Mountain) IPv6 Summit and it will again be the largest IPv6 event in North America, even bigger than last year. There’s a long line up of fantastic speakers and over 500 IPv6 networking professionals expected to be in attendance. Plus, I’m presenting something on all three days!
In this final installment of the don’t panic series “Introducing IPv6,” you will learn about Neighbor Discovery and Stateless Address AutoConfiguration.
The beauty of the IPv6 header is that it has been streamlined and contains only those pieces of information that are necessary on every IPv6 packet. All optional IP information is encoded in extension headers, which are added to packets between the standard IPv6 header and the upper-layer header.
We (the Global Network Engineering Community(GNEC)) have made many mistakes with IPv4 Peering and Transit configurations and operational practices. As operators begin turning up more and more IPv6 E-BGP sessions with peers and transit providers, there is an opportunity to do things right from the beginning.
As with IPv4, an IPv6 address serves as an identifier for an interface or group of interfaces. Also like IPv4, IPv6 addresses come in several types, based on how they represent those interfaces. IPv6 has three types of addresses. This post covers all three, plus some special purpose addresses as well.
The primary difference between IPv4 and IPv6 addresses is length. IPv4 addresses are 32 bits long and IPv6 addresses are 128 bits long. This means that an IPv4 address is made up of 32 1s and 0s while an IPv6 address is made up of 128 of them – 128 binary digits. This massive length forces IPv6 addresses to be written using a different notation than IPv4 addresses and thus makes them very easy to distinguish from IPv4 addresses.
Since I’m starting to speak more publicly and more often, I thought I’d throw out a schedule so that folks will know where I’ll be. So, to kick that off, here is my next 3 months of speaking engagements: LACNIC XVI / LACNOG 2011 / Internet ON 3 to 7 October 2011 Buenos Aires, Argentina [...]
The American Registry for Internet Numbers (ARIN) announced today (27 September 2011) the publication of ARIN Number Resource Policy Manual (NRPM) version 2011.4. As an active member of the ARIN community and an elected member of the ARIN Advisory Council (AC), I am always excited to see new policies implemented (yes, I’m a special breed [...]