• IPv6 Materials
  • 2014 Calendar

What do terms like multistakeholderism, Internet governance, and technical community really mean?

Suzanne Woolf

Last year I went to my first Internet Governance Forum in Bali, Indonesia. I was involved in several workshops and discussions about “the role of the technical community in Internet governance,” including the Regional Internet Registries (RIRs) and Internet Engineering Task Force (IETF); the role of governments; questions of increasing access to communications resources for the next billion users; and reactions to “pervasive monitoring” of Internet communications by US and other intelligence agencies. I’ve been involved with “Internet policy” for many years now, as a member of ARIN’s AC, on various ICANN Advisory Committees, and as a liaison to the ICANN Board of Directors…which turned out to be a useful perspective, but by no means complete!

Live Beyond Layer 3

ARIN at CANTO 2014

I’m a layer three guy, which means that I am a network guy, specifically an Internet guy. I work on routers and connect big networks to other big networks to try and make the Internet work better. For a long time, I, and many people like me have tried very hard to ignore what we call layers 8/9/10 (the financial, administrative, and governmental entities involved with the Internet). Or worse, sometimes we have been known to sneer at them as “damage to be routed around”. I know that attitude still persists among some, but it really fails to take in the whole story.

Sign Your DNS Zones


Last month we signed ARIN’s forward DNS zone as part of our commitment to Domain Name System Security (DNSSEC). That means we completed the process that essentially allows resolvers to verify the arin.net information that they receive from ARIN’s nameservers, and it allows users to have a higher degree of confidence that when they go to https://www.arin.net or act on any other information under arin.net that they are communicating with the host they expect. We went through the process of signing ARIN’s forward DNS zones to do our part to contribute to a valuable and trustworthy Internet. The process can be complex, but it’s worth it.

Why Is the Transition To IPv6 Taking So Long?


We stand on the cusp of an explosion in the number of Internet-connected devices. The mobile revolution was just the beginning. Combined, the burgeoning wearables market and the Internet of Things will potentially create billions of new connected devices over the next few years. Every device will need an IP address and there are far too few available addresses within the IPv4 system to handle the sheer quantity of connections. It’s a problem that’s been predicted and solved for many years, in theory at least. But IPv6 is being adopted at a glacially slow pace. The reasons for the gradual adoption are simple to understand. It’s expensive. The Internet is made up of tens of millions of servers, routers, and switches that were designed to work with IPv4. Upgrading that infrastructure entails a significant capital investment.

Caribbean Internet Governance Forum (CIGF) Celebrates 10 Years

Nigel Cassimire

CTU Telecommunications Specialist, Nigel Cassimire, shares what happened at this year’s Caribbean Internet Governance forum. The 10th edition of the Caribbean Internet Governance Forum (CIGF) was held at the Atlantis, Paradise Island Resort in The Bahamas from 6th to 8th August 2014. The CIGF is a regional, multi-stakeholder forum which was initiated by the Caribbean Telecommunications Union (CTU) and the Caribbean Community (CARICOM) Secretariat in 2005 in order to coordinate a regional approach to Internet Governance issues for the final session of the World Summit on the Information Society (WSIS) in Tunis that year. The CIGF has since been convened annually by the CTU and lays claim to being the first such regional forum in the world, all others having been convened after the initial global Internet Governance Forum in 2006.

IETF 90 Part 2: IPv6 reverse DNS

IETF Language Buttons

Some thoughts on IPv6 reverse DNS. Lee Howard was speaking in the Sunset4 working group at IETF 90. He mentioned something that got me thinking. I have often discussed in my talks problems in IPv6 that were unanticipated. A lot of these problems are unintended consequences of very large subnet sizes. Some problems are outlined in RFC 6583. Lee mentioned another interesting problem, reverse DNS. Best practice [RFC1033] says that every Internet-reachable host should have a name (per RFC 1912) that is recorded with a PTR record in the .arpa zone. It also says that the PTR and the A record must match.

From the Twitterverse