South Asia SRF highlights Member priorities on IPv6, routing security, and training

APNIC and SANOG sign an MoU to strengthen collaboration on technical capacity building, community engagement, IPv6 deployment, routing security, and Internet development across South Asia.

More than 100 APNIC Members gathered in Kathmandu, Nepal, for the South Asia APNIC Sub-Regional Forum (SRF), bringing together network operators, policymakers, and Internet stakeholders from across the region.

Held alongside SANOG 44, the forum provided an opportunity for APNIC to hear directly from Members about the challenges shaping South Asia's Internet landscape. Discussions highlighted strong interest in routing security, enterprise IPv6 adoption, practical technical training, and greater community participation in APNIC activities.

APNIC Director General Jia Rong Low opened the forum. APNIC Executive Council members Roopinder Singh Perhar, Yoshinobu Matsuzaki, Vincent 'Achie' Atienza, and Sumon Ahmed Sabir also attended.

APNIC is piloting SRFs to complement APRICOT and APNIC conferences, creating more opportunities for Members to engage through established regional events. The South Asia SRF was the second forum held under the initiative and the first held in South Asia.

Key topics for South Asia

The forum brought together Members, network operators, and Internet stakeholders from across the region to discuss Internet resource management, registry accuracy, IPv6 deployment, routing security, the APNIC Policy Development Process (PDP), and APNIC Foundation initiatives.

Routing security attracted particular interest. Discussions covered Resource Public Key Infrastructure (RPKI), Route Origin Validation (ROV), and Autonomous System Provider Authorization (ASPA). The policy session focused on increasing awareness of the APNIC Policy Development Process and encouraging greater participation from South Asia's Internet community.

A dedicated Community Listening Session gave Members the opportunity to share feedback directly with APNIC on the issues affecting their organizations and networks.

What Members told us

The Community Listening Session was designed to give Members a direct line to APNIC leadership and staff. While discussions covered a broad range of topics, several themes emerged.

Members were interested in improved services and support, particularly regarding Internet resource management, registry processes, automation, and IPv4 availability. They also discussed everyday interactions with APNIC and how services could be made easier to use and more responsive to Member needs.

Practical technical training and implementation guidance were recurring topics. Members expressed interest in operational experience, deployment case studies, and hands-on knowledge that can help organizations address real-world challenges.

IPv6, RPKI, ROV, and ASPA generated strong interest throughout the forum. Members highlighted the need for data on invalid routes and practical testing environments to support ROV implementation. These technologies featured prominently in both technical sessions and Member feedback, reflecting ongoing efforts to improve infrastructure resilience and routing security across the region.

Community participation was another common theme. Members expressed interest in becoming more involved in APNIC activities and the PDP, and in understanding how they can engage more actively between major conferences.

IPv6 beyond the ISP sector

Enterprise IPv6 adoption was a recurring topic during both the Forum and SANOG 44.

While many service providers across the region have made significant progress with IPv6 deployment, discussions highlighted ongoing challenges within enterprise environments.

The issue was particularly evident during a roundtable discussion with representatives from Nepal's banking and fintech sectors. Participants highlighted growing awareness of IPv6 and its importance as a long-term response to IPv4 exhaustion. They also identified barriers to adoption, including legacy systems, skills gaps, limited deployment experience, and the difficulty of building a clear business case.

Similar concerns were raised by Members and operators throughout the week. As IPv6 deployment matures among service providers, helping enterprises navigate their own adoption challenges is becoming an increasingly important area of focus.

Strengthening ties with SANOG

While the Community Listening Session provided dedicated Member feedback, direct engagement continued throughout SANOG 44.

APNIC staff participated in technical sessions, met with Members at the APNIC booth, held meetings with operators and stakeholders, and joined discussions on IPv6 deployment, routing security, technical training, and capacity development.

APNIC representatives also met with government stakeholders during the week to discuss support for IPv6 and RPKI deployment within government infrastructure.

SANOG 44 also marked the signing of a Memorandum of Understanding (MoU) between APNIC and SANOG.

The agreement provides a framework for deeper collaboration on technical capacity development, community engagement, IPv6 deployment, routing security, and future APNIC SRFs. It builds on the long-standing relationship between the two organizations and strengthens cooperation in support of Internet development across South Asia.

APNIC thanks SANOG for hosting the South Asia SRF and helping bring together Members and stakeholders from across the region.

Looking ahead

As APNIC begins work on its next strategic planning cycle, feedback from the South Asia SRF will help inform future priorities and activities.

Discussions at SANOG 44, together with insights from the 2026 APNIC Survey and feedback gathered through other Member engagement activities, provide a valuable view of the issues attracting the greatest attention across the region. These insights will help APNIC focus its efforts where they can best support Members.

View more photos from the recent South Asia SRF:

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.