ccTLD Briefing Document The ccTLD - ICANN Model CcTLD Relations with ICANN CcTLD organization Mission and size

The ccTLD - ICANN Model “Technically Driven” “THIN” Or “Policy Driven” “THICK”

ccTLD - ICANN “THIN” Model ICANN acts as technical co-ordination body IETF, domain names, root servers, address space No Policy Services: Organization, Publishing, Root Operations Few physical meetings (1 per year)

ccTLD - ICANN “THIN” Model Cost US $ 500,000 per year Root cost estimate US $ 125,000 each 15 Roots = US $ 1,875,000 Total US $ 2,375,000 (US $ 2.5 Million) 25 Countries pay 90% if allocated by name count. About US $ 0.06 to 0.07 per name Calculated at 40 Million names

ccTLD - ICANN “THICK” Model Technical coordination as in “THIN” Policy Development Consensus formation Political System Larger bureaucracy Outreach and Public Relations Campaign to induce compliance

ccTLD - ICANN “THICK” Model If there is “Policy” Requires participation by 200+ countries Requires outreach to achieve this level “Broad-based consensus” claim could be questioned Impact on US-DOC transfer of Root

ccTLD - ICANN “THICK” Model Need to engage another 100+ ccTLD Learn about them Who they are Technical Infrastructure Possibly provide support  Technical Training  Political training  Outsourced DNS or tech services

ccTLD - ICANN “THICK” Model Propose US$ 500,000 / year for 2 years US$ 200,000 Travel grants for meetings US$ 200,000 for outreach trips US$ 100,000 for full time work on IANA database Probably grant funds here, need person to deal with compliance

ccTLD - ICANN “THICK” Model Cost about US$ 7.3 million with root Cost about US$ 5.5 million without root Funding requires $ 0.15 to 0.20 / name Acceptance of grants for ccTLD outreach reduces this by 0.01 / name The fact is, we are here already!!!!

CcTLD Relations with ICANN: Some ccTLDs want the “Thin Model” May not see advantages of “Consensus- based Policy-Making Organization Some ccTLDs want the “Thick Model” But ICANN does not devote sufficient resources to ccTLD issues & Outreach

CcTLD Relations with ICANN: Current Problems 90% of ICANN resources go to gTLD issues. ccTLD is asked for 30% of the ICANN Budget No proportional relationship between domain names and contributions- I.e. NetSol has a “cap” on fees. ccTLD subsidizes US registrars.

CcTLD Relations with ICANN: Current Problems No direct possibility of ccTLD electing member of ICANN Board ccTLDs want a new method of relating. Possible SO or Advisory Council Could still retain DNSO representation for consensus formation between constituencies

CcTLD Mission and size Light Weight ? CENTR suggests using ICANN to co- ordinate regional organizations Requires strong regional organizations CENTR is only really strong one US $ 400,000 budget about 35 members Where does that leave 100+ ccTLDs?

CcTLD Mission and size Substantial ccTLD development ccTLD outreach Political Training Technical Training Possible outsourced DNS Travel assistance and/or Visits to ccTLDs

CcTLD Mission and size Substantial ccTLD Mission Model Strong, World-Wide Organization Administrative support Multi-Language information dissemination Full NGO Status Members pay dues according to their ability to pay. Accept funding from Multi-Nationals

CcTLD Mission and size Substantial ccTLD Organization Peer-to-Peer relationship with ICANN Satisfies Sovereignty issues Guarantees ICANN a fixed income stream to support its work. Reinforce ICANN credibility as a world-wide, consensus based organization. Help USDOC decide root server question.

Conclusion and Call to Action Consider carefully the long-term ramifications of how we guide the Policy and Progress of world-wide Internet development. Be ready to discuss, explain your positions, and help reach agreement on these important matters of mutual interest. Our Mission for the Future.