Fragments - The Internet Protocol Journal, Volume 14, No. 2

RFC Series Editor Search Announcement

The Internet Engineering Task Force (IETF) is seeking an RFC Series Editor (RSE). The RSE has overall responsibility for the quality, continuity, and evolution of the Request for Comments (RFC) [3] Series, the Internet's seminal technical standards and publications series. The position has operational and policy development responsibilities. The overall leadership and supervision of RFC Editor function is the responsibility of the RFC Series Editor. The RSE is a senior professional who must be skilled in leading, managing and enhancing a critical, multi-vendor, global information service. The following qualifications are desired:

  • Leadership and management experience. In particular, demonstrated experience in strategic planning and the management of entire operations. Experience that can be applied to fulfill the tasks and responsibilities described in “"RFC Editor Model (version 2)" [1].
  • Excellent written and verbal communication skills in English and technical terminology related to the Internet a must; additional languages a plus.
  • Experience with editorial processes.
  • Familiar with a wide range of Internet technologies.
  • An ability to develop a solid understanding of the IETF, its culture and RFC process.
  • Ability to work independently, via e-mail and teleconf, with strong time management skills.
  • Willingness and ability to travel as required.
  • Capable of effectively functioning in a multi-actor and matrixed environment with divided authority and responsibility; ability to work with clarity and flexibility with different constituencies.
  • Experience as an RFC author desired.

More information about the position can be found on the RFC Editor Webpage [2]. The RSE reports to the RFC Series Oversight Committee (RSOC). Expressions of interest in the position, Curriculum Vitae (including employment history), compensation requirements, and references should be sent to the RSOC search committee at Questions are to be addressed to the same e-mail address. Applications will be kept confidential. The RSOC will interview interested parties at the IETF meeting in Quebec City that begins July 24, 2011, but the application period is open until the position is filled.

—Fred Baker, Chair, RFC Series Oversight Committee

Remaining IPv4 Address Space Drops Below 5 percent

The Number Resource Organization (NRO) recently announced that less than five percent of the world's IPv4 addresses remain unallocated. APNIC, the Regional Internet Registry for the Asia Pacific region, has been assigned two blocks of IPv4 addresses by the Internet Assigned Numbers Authority (IANA). This latest allocation means that the IPv4 free pool dipped below 10% in January 2010. Since then, over 200 million IPv4 addresses have been allocated from IANA to the Regional Internet Registries (RIRs).



2] Leslie Daigle, "RFC Editor in Transition: Past, Present, and Future," The Internet Protocol Journal, Volume 13, No. 1, March 2010.

Global IPv6 Deployment Monitoring Survey 2011

The Global IPv6 Deployment Monitoring Survey 2011 is now online at:

This survey has been designed by GNKS Consult in collaboration with TNO and the RIPE NCC to further understand where the community stands on IPv6 and what needs be done to ensure that the Internet community is ready for the widespread adoption of IPv6.

Anyone can participate in this survey and we hope that the results will establish a comprehensive view of current IPv6 penetration and future plans for IPv6 deployment. The survey comprises 23 questions and can be completed in about 15 minutes. For those without IPv6 allocations or assignments or who have not yet deployed IPv6, there will be fewer questions.

The survey closes July 31, 2011. We thank you for your time and interest in completing this survey. If you have any questions concerning the survey, please e-mail:

For more information about the survey and links to previous year's survey results, please see:

RFC 6127 Published

The topic of IPv4 depletion and IPv6 deployment is covered in the recently published RFC 6127 entitled "IPv4 Run-Out and IPv4-IPv6 Co-Existence." From the introduction: "When IPv6 was designed, it was expected that the transition from IPv4 to IPv6 would occur more smoothly and expeditiously than experience has revealed. The growth of the IPv4 Internet and predicted depletion of the free pool of IPv4 address blocks on a foreseeable horizon has highlighted an urgent need to revisit IPv6 deployment models. This document provides an overview of deployment scenarios with the goal of helping to understand what types of additional tools the industry needs to assist in IPv4 and IPv6 co-existence and transition." RFCs can be obtained from the RFC Editor web page, see: