Summary

  • SANOG 34 did something operationally difficult: it moved a regional conference from Colombo to Kolkata for what SANOG described as the recent security situation in Sri Lanka, while keeping the dates intact. SANOG's own archive records the move, names the original and replacement hosts, and says the decision followed advice from the local host. What it does not provide is the complete authority chain behind that decision. The gap matters because emergency continuity is also an exercise of institutional power.
  • SANOG's archive documents the relocation of SANOG 34 from Colombo to Kolkata and the continuity of its dates and programme. It does not publish the complete decision and delegation chain. Future emergency moves should pair logistical notices with a compact record of authority, cost allocation and participant remedies.

The archive explains the change

SANOG's official event page says Colombo was the prescheduled venue for SANOG 34. It says the meeting was relocated to Kolkata because of the recent security situation in Sri Lanka, with no change to the 31 July–7 August 2019 dates. The replacement event was hosted by the Internet Society Kolkata Chapter and co-hosted by the Indian Internet Foundation. The final programme lists the conference, tutorial and workshops in Kolkata.

That is a useful public chronology. It tells participants where the meeting moved, why SANOG said it moved, and which organisations stepped into the host roles. It also records that LEARN and LKNOG, the Sri Lankan hosts, remained in contact and offered guidance.

Sources