Call for public comment: IGF 2016 IPv6 Best Practices document

By on 29 Nov 2016

Categories: Community Tech matters

Tags: , ,

Blog home

Calling all network operators: we need your feedback on the IGF 2016 – Best Practice Forum on  ‘Understanding the commercial and economic incentives behind a successful IPv6 deployment’ document before it is presented at the upcoming Internet Governance Forum (IGF) in Guadalajara, Mexico, from 6 to 9 December 2016.

It’s not just operational communities who are encouraging IPv6 deployment. At the IGF, IPv6 is discussed as a way to accommodate access/connectivity and to prepare for the future growth of the Internet, in particular, connecting the next billion people.

These discussions, centered around the Best Practices Forum (BPF) on IPv6, give us the opportunity to reach groups beyond the technical community and understand their views and needs, including business decision makers and policy makers.

This year’s BPF on IPv6 will focus on the economic incentives and commercial drivers behind the decision to adopt IPv6.

To discuss these issues from a regional perspective, I organized a session—IPv6 deployment in the Asia Pacific region— at the Asia Pacific Internet Governance Forum (APrIGF) held in Taipei, Taiwan, in July this year. We continued these discussions at the Cooperation SIG at APNIC 42.

We have also had mailing list discussions, a call for case studies and regular teleconferences where anyone is able to participate. Several colleagues from the RIR community have already provided great input, and we appreciate their efforts and expertise.

These discussions have been captured in the document mentioned above: IGF 2016 – Best Practice Forum on IPv6 ‘Understanding the commercial and economic incentives behind a successful IPv6 deployment’.

Before the document is presented at the upcoming IGF in December, we are seeking public feedback and comments.

Want to get involved?

  • Join the mailing list
  • Provide your comments on our document online
  • Join us at the IGF 2016
    • In person: the IPv6 BPF will take place on 7 December from 15:00 to 16:30 (UTC -6)
    • Remotely: remote participation is open to anyone

Areas needing your feedback

We welcome your feedback, especially on:

  1. Cost Simulation (Section 4.1.5)
    • Considerations made in cost of deployment
  2. Sectoral Observations on the state of IPv6 deployment for ISPs, IXPs, Data centers, Cloud Service providers, Content Providers, Vendors, Mobile networks (Section 4.2)
    • There is still a limited description for Cloud Service providers
  3. Remaining challenges (Section 5)
    • For ‘Further encourage deployment’
    • Issues raised such as cost of debugging, training staff
  4. For ‘Countries where IPv6 deployment is not taking place’
    • Feedback welcome from developing countries
  5. Conclusions / next steps (Section 6)
    • Key messages
    • What can be the takeaways/key messages to policy makers and business decision makers? For example, some inputs request governments to play a stronger role in requiring vendor support for IPv6.

About the IPv6 BPF activity

Sumon A. Sabir and I are the coordinators of this group – you may recognize both of us as active participants in the APNIC community. Please feel free to reach out to us directly or on our mailing list for any questions about the IPv6 IGF BPF in 2016.

Next steps

After the IPv6 BPF session on 7 December, we will incorporate both online and ‘in the room’ feedback in the document.

The finalized document will be published on the IGF website in late December 2016/January 2017 and we will undertake broad outreach with key stakeholders, including those outside the technical communities.

More information is available at: BPF IPv6 – Understanding the commercial and economic incentives behind a successful IPv6 deployment.

Rate this article

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

Leave a Reply

Your email address will not be published. Required fields are marked *