1 / 5

APNIC rootserver activities 2006/2007

This document provides an overview of APNIC's activities in 2006, highlighting significant achievements such as the consolidation and replacement of routers in Korea, repair works in China, and improvements in connectivity in Australia. It discusses ongoing and upcoming expansion plans in the Philippines and Fiji for 2007, detailing the critical mass necessary for new Internet exchanges. Additionally, it raises questions regarding cTLD support and explores ideas for enhancing services in the region, emphasizing the importance of connectivity improvements and addressing routing policies.

kail
Télécharger la présentation

APNIC rootserver activities 2006/2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. APNIC rootserver activities 2006/2007 February 2007 George Michaelson R&D Officer APNIC

  2. Overvew What happened in 2006? What’s planned for 2007? Any other ideas?

  3. What happened in 2006 Consolidation. Replacement of routers/switches in KR Repair works on routing in CN Many thanks to Juniper/CN and CNNIC for assistance, liaison, remote-hands Improvements in connectivity in AU Adopted the NZ Auckland node Replaced Juniper routers Expansion Planning for PH Planning for FJ

  4. What’s planned for 2007 Expansion PH is in deployment (Iroot) New IX, reaching critical mass (Amante) FJ is shipping, deployment ASAP (Froot) Hosted by USP Delayed by coup (!) Implications for Academic-net preferences AU connectivity improvements being explored to avoid excess traffic to FJ Other nets may want to check if their routing policy will make this node visible at a higher preference

  5. Any other ideas? 'roots are not enough' ccTLD support could make sense TW experience suggests locally significant services are named 'out of ccTLD' as well Probably not gTLD support ... This sector probably self-hosts Limited opportunities for assistance Other services? Ntp stratum-1 time sources? <insert your idea here>

More Related