Summary

  • SANOG's official programme records an APNIC-and-SANOG MoU signing ceremony at SANOG 44. APNIC later named SANOG Chair Rupesh Shrestha and APNIC Director General Jia Rong Low as the people who formalized the agreement.
  • APNIC's current partnership page still directs its SANOG Link to MoU to an August 2003 PDF. The operative opening retains xxx for the day, and the APNIC By and Title lines are blank in the public copy.
  • The old text says it becomes effective when signed, requires written bilateral signatures for amendments and continues until terminated after notice. A SANOG brochure from 2004 nevertheless said SANOG already had an MoU with APNIC.
  • None of this establishes invalidity or absence of an executed copy. The missing public object is a lineage record saying whether the 2026 instrument amends, renews, replaces, supersedes or coexists with the earlier one.

One partnership page points to two different moments

The new event is not hidden in inference. The SANOG 44 programme lists an MoU Signing Ceremony: APNIC & SANOG in the opening plenary. APNIC's 25 August retrospective says the agreement was formalized during the event by SANOG Chair Rupesh Shrestha and APNIC Director General Jia Rong Low.

APNIC describes a contemporary field of cooperation: technical capacity development, community engagement, IPv6 deployment, routing security and future APNIC Sub-Regional Forums. It also says the instrument builds on a long-standing relationship. Those statements establish a ceremony, the parties, the named representatives and a public description of purpose. They do not publish the operative text or identify its relationship to any earlier instrument.

That matters because APNIC already maintains a public agreement surface. Its current Memberships & Partnerships table says APNIC has established an MoU with SANOG for meetings, training and educational activities in South Asia. The table's Link to MoU does not open a 2026 file. It opens the APNIC-hosted August 2003 document.

The public user therefore meets two dates without a joining statement: a signing in 2026 and a linked instrument labelled 2003.

The old PDF has a signing-triggered clock but no visible APNIC execution

The 2003 file is more than a historical brochure. It contains five articles covering regional Internet development, exchange of information and assistance, seminars and conferences, training and protection of confidential material. Its final article calls the arrangement nonbinding and says it creates no obligations under law.

The same article gives execution real documentary work. Modifications or amendments are to be made in writing and signed by both parties. The MoU is to become effective on the date of signing. It then remains in force until either party gives written notice, with termination 30 days later unless the parties agree otherwise.

That structure makes the blank fields consequential as evidence, even though it does not make the agreement legally binding. The cover says August 2003, but the operative sentence reads this xxx day of August, 2003. The last page types Gaurab Raj Upadhaya's name and title for SANOG. Under APNIC, the By and Title lines are empty. No handwritten or electronic signature is visible on any of the three public pages.

The bounded conclusion is not that the agreement was never executed. APNIC or SANOG may hold another counterpart, a signed original, a later confirmation or a record that resolves the day. A public PDF with blank execution evidence simply cannot prove those facts by itself. Its own effective-date clause makes the missing join visible: the reader can see the rule, but not the signing event that activates it.

SANOG's 2004 record prevents an easy dismissal

It would be equally careless to call the 2003 file a discarded draft. SANOG's official brochure for SANOG IV, held in Kathmandu in July 2004, told readers that SANOG had MoUs with APIA and APNIC. It described their purpose as exchanging experience, helping each other achieve objectives and supporting each other's work.

That contemporaneous statement does not fill the APNIC signature line or supply the missing day. It is not an execution certificate. It does show that SANOG publicly treated an APNIC MoU as existing within a year of the dated document.

The correct evidence state is therefore neither “obviously unsigned draft” nor “fully proved executed instrument.” The public record contains an incomplete-looking execution page and a contemporaneous institutional statement of existence. Preserving both is more accurate than choosing one and deleting the tension.

The 2026 ceremony needs a relation, not an invented label

Several relations are possible. The 2026 instrument could amend the earlier terms, renew cooperation under a fresh date, restate an existing arrangement, replace or supersede it, or sit beside it as a separate framework for Sub-Regional Forums. The public sources reviewed here do not select among those categories.

APNIC's Sub-Regional Forums page shows why wording matters. For its Pacific partnership, APNIC expressly announced an updated MoU with PITA. The SANOG section describes the forum programme without applying the same adjective. That contrast does not prove that the SANOG document was not updated. It only shows that APNIC can publish a relation label when one is part of the public account.

The July preview of the South Asia forum explains the event's role in bringing policy, technical work and member engagement closer to the region. It does not announce a document transition. The later report confirms a signing and new cooperation fields but still does not state the old instrument's resulting status.

Readers should not have to infer document identity from ceremony photographs or adjacent programme language. A ceremony proves that people signed something. It does not, by itself, identify which earlier text changed or which public link is authoritative afterward.

A small agreement-lineage receipt would close the gap

The public repair does not require disclosing private deliberations or turning a nonbinding MoU into a contract. A compact record can identify the parties, authoritative title, stable agreement ID, document hash, authorized signers, execution date and effective date. One field can classify its relation to the 2003 instrument: amendment, renewal, restatement, replacement, supersession, separate coexistence or correction.

The same record should state what becomes of the older public copy. It might be marked as a public form whose execution is unresolved, a prior effective instrument, a terminated instrument or a superseded version. If the 2026 text contains confidential annexes, APNIC can publish the public portion and describe the bounded omission. The receipt can also preserve duration, review and termination terms and a correction history for the partnership link.

This is not clerical decoration. The two descriptions do not cover identical subjects. The 2003 text emphasizes information exchange, meetings and APNIC training. The 2026 account adds technical capacity development, community engagement, IPv6 deployment, routing security and future APNIC forums. A version relation tells members whether these are new operative fields, a restatement of practice or simply a summary written at a different level.

The gap does not cancel two decades of cooperation

APNIC and SANOG have a long visible operating relationship. SANOG meetings, training, presentations and the 2026 forum supply evidence of cooperation independent of one execution page. The public-record defect should not be inflated into a claim that no collaboration occurred.

Nor does an MoU description delegate control over number-resource policy, APNIC membership, SANOG participants or the networks they operate. Cooperation authority remains bounded by each institution's own role and by the decisions that actually govern registry and network operations.

The conclusion is narrower. APNIC has reported a fresh signing while its current MoU link still exposes an older document whose own activation fields are unresolved on the page. The right correction is additive: retain the 2003 file, retain SANOG's 2004 statement, publish the 2026 public instrument or receipt, and join them with an explicit relation. History remains intact, and the current agreement becomes identifiable.

Sources