Skip to main content

Participation and network issues for Delhi meeting

As many of the remote participants have noticed, we have been having network problems at the ICANN meeting in Delhi, which is impacting remote participation.

As soon as the technicians have sorted out the problem, we will come back with an explanation and update this post with details.


[This has come from the technical staff to explain the issues there have been over the past few days]

We have been faced with many challenges here.

The week before the meeting there were a total of five undersea fibre cuts in the Asia Pacific region. Because of this, a lot of the traffic of the region has been aggregated and is all traveling through the remaining fibre paths (all at capacity at the moment). As the fibres are replaced, it will certainly impact the region (in a positive way!) but unlike when your computer crashes at home, deploying the “tech support” to a cut undersea fibre can take up to a week to arrive at the destination.

We’ve run into some hurdles with the local transit as well in the way of trying to get them to sort out our AS number and properly announce (and transit) our traffic.

We have also had a challenge with stable power in the hotel. There have been a number of power outages (either partial or full) and blown circuits. Some of these have directly impacted the ability to feed power to the routers we are using to egress the hotel. Though we have UPS (uninterruptible power supplies), we’ve found a number of them have been mis-wired ore plugged into the hotel UPS, which can cause a “blowback” and cut the power.

Although service has not been stable, the team that is here locally has done an amazing job of adapting to each new challenge and providing a solution in the most timely fashion that they were able to.

We apologize for any inconvenience and assure you we are doing everything within our power to try to keep the services running so that the meetings can be effective. It should also be noted that the local staff have provided incredible support dealing with multiple challenges.


    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."