Overview of Domain Name System

1. Overview of Domain Name System

2. Agenda Key Definitions Of the Dots and Names Key Internet Organizations

3. Key Definitions

4. Definitions .ZA DNA: .ZA Domain Name Authority DNS: Domain Name System ccTLD: country code Top Level Domain • .za .uk .ke gTLD: generic Top Level Domain • .com .org .net ICANN: Internet Corporation for Assigned Names & Numbers

5. Definitions Registry: entity licensed to operate a domain • Current: no entity formally licensed yet • Co.za, org.za, gov.za operate like a registry Registrar: entity licensed to liaise between registrant & registry • grows the domain name industry by selling names • Example could be ISP’s and Telcos • Current: no entity formally licenced yet Registrant: applicant for/holder of domain name • You, me, sabc, woolworths, sita, etc

6. Of the Dots & Names

7. How did the DNS come alive? The .ARPA (advanced research projects agency) post Cold War • Primarily for US Defense but later expanded • American origin & ownership of the DNS Internationalisation of DNS • DNS made available beyond the US • Ad-hoc delegation of country domains What were the first dots? • .com, .mil, .gov, .net….and later .za!

8. How did the DNS come alive? ICANN enters the fray in the 90s • Unilaterally established & appointed by US govt to manage DNS & IP address allocation on a contract • Had a Joint Partnership Agreement with US government • JPA succeeded by Affirmation of Commitments (2009!) • Global community-driven policy & standards development model (multi-stakeholder consultations) • Outsourced DNS technical operations to IANA • ICANN has authority over gTLDs but not over ccTLDs

9. What’s the DNS exactly? The Domain Name System (DNS) helps users find their way around the Internet. Every computer on the Internet has a unique address called its "IP address" (Internet Protocol address). Because IP addresses (which are strings of numbers) are hard to remember, the DNS allows a familiar string of letters (the "domain name") to be used instead. So rather than typing "192.0.34.163," you can type "www.yourname.org."

10. DNS structure

12. Key gTLD characteristics • gTLDs used not to have geographic limitations, until the 2013 launch of new gTLDs where geoTLDs (.africa, .joburg, etc) have become common • gTLDs account to ICANN, not to national governments, even if they are geographic. They are subject to Californian law & courts. • They are wholly bound by ICANN policy & whatever specific policies geoTLDs may develop, they must comply with ICANN policy. • Typically, gTLDs use 2nd level registration model • yourname.com, yourname.org, yourname.cat

13. Key gTLD characteristics • gTLDs are required to accept ICANN-accredited registrars. (There are only 7 ICANN-accredited registrars in Africa). • gTLDs pay per domain name fees to ICANN (ranging between US$0.18 and US$0.25). There may be additional annual fees to be paid to ICANN. • gTLD registry operators are subject to ICANN technical & operational standards. For example, they have no choice but to use EPP registry systems and deploy DNSSec as these are ICANN standards. • Domain name disputes resolved through ICANN UDRP using ICANN-accredited adjudicators.

14. ccTLDs

15. ccTLD characteristics • A ccTLD serves a specific country. There can only be one ccTLD for each country. • ccTLDs are usually operated by local entities. Most ccTLD registries are operated by for profit or not-for-profit entities • Their policy development processes are locally driven & subject to national laws & courts. They are not subject to ICANN policies and standards. • All ccTLDs were delegated using the ISO country code list. That’s we have .ZA & not .SA

16. ccTLD characteristics • Domain name registration models are normally split between 2nd and 3rd level registrations • yourname.za vs yourname.co.za • Registry models are normally split between self-operation & outsourced registry operation. For example, auDA (Australia), like ZADNA, outsources registry operations, whereas Nominet (UK) & CNNIC (China) are “ZADNAs” that operate registries on their own & only accredit/license registrars. • ccTLDs typically generate their revenue from domain name registration & renewal fees. .ZA is one of most price-competitive ccTLDs well ahead of .uk, .cn, .de, etc.

17. What are the key principles? • Holding a domain name is a license not a right, but recent foreign courts’ decisions are starting to challenge this position. • Registration is on first-come first-served basis,unless registrations are moderated. Registry operators have no one making calls on applicants’ rights to apply for names. That’s why we have alternative dispute resolution (ADR) mechanisms for complaints. • Registration & renewal process is usually automated (except in some moderated SLDs e.g. ac.za & gov.za) & is done through accredited registrars.

18. What are the key principles? • It is typical practice for registrars to bundle domain name registration with hosting, web design & ecommerce services, hence domain name pricing differs from one registrar to another. • A contractual relationship exists between Registrar & Registrant. Neither the registry operator nor ZADNA are parties. • Registrants have rights to transfer to their domain names from one registrar to another. • Domain name disputes are usually resolved through Dispute Resolution Process • .ZA has Alternate Dispute Resolution Process

19. Why register a domain name? In this game, a name means a lot more than you may think! • 360.com (sold for $17,000,000 in 2015) • Insure.com(sold for $16,000,000 in 2009) • Sex.com($14,000,000 in 2006) • Fund.com($10,000,000 in 2008) • Porn.com($9,500,000 in 2007) • Fb.com ($8,500,000 in 2010) • Business.com($7,500,000 in 1999) • Diamond.com($7,500,000 in 2006) • Beer.com($7,000,000 in 2004)

20. Why register a domain name? • A name online gives you unique identity • Email, web ID • The world reaches you easily online • Participation in e-commerce is enhanced • Easy to attract potential customers online • Search engine optimisation, online advertisin • A name gives you exclusive online real estate

21. Why register .ZA? .ZA is South Africa’s internet top level domain (TLD). It identifies all domain names (including email & web addresses) that are registered in South Africa internet space. Simply put, .ZA is South Africa’s online real estate.

22. Why register .ZA? • .ZA gives you a clear online ID • Everybody recognizes you’re South African (while .com & .net say you’re somebody somewhere in the globe) • Registration is automated & therefore fast • We have an EPP central registry (ZACR) • Our registration fees are very competitive • Coza, Net.za, Org.za & Web.za wholesale fee = R45 • Ac.za, Gov.za, Nom.za fee = free!

23. Why register .ZA? • We have a robust & secure world-class EPP system • Even .africa, .durban, .joburg & .capetown are on board! • We have a proven dispute resolution system against cybersquatting & intellectual property abuse • You join the biggest & fastest growing namespace in Africa with more than a million registrations! • You invest in the local ICT industry (because your fees are used in South Africa)

24. Why register .ZA? • You choose where to register!

25. .ZA 2nd level domains Dormant domains • Alt.za* • Ngo.za • Tm.za Active domains • Ac.za • Co.za* • Edu.za • Gov.za • Law.za • Mil.za • Net.za • Nom.za • Org.za • School.za • Web.za* Private domains • Agric.za • Grondar.za • Nis.za * Impose no eligibility requirements

26. How do I register .ZA? • Choose your name • Choose your .ZA 2nd level domain • Check if the name is available • See “Whois Services of .ZA domains” at ZADNA.org.za • Choose your registrar/ISP to register the name for you • ZACR has +400 accredited ISPs/regsitrars • Registrars charge you bundled fees

27. ZADNA Policy & Regulation Co.za Registrants Registrars Registry Operator Net.za Org.za Web.za Law.za ZADNA Policy & Regulation In the EPP system, registrars register names across multiple SLDs using the same registration interface, dealing with a single registry operator. This reduces systems configuration costs, while speeding up registration of domain names.

28. Key Internet Organizations

30. ICANN structure

31. ICANN ccNSO • The Country Code Names Supporting Organisation (ccNSO) is a body within the ICANN structure created for and by ccTLD managers. • Since its creation in 2003, the ccNSO has provided a forum for country code Top Level Domain (ccTLD) managers to meet and discuss topical issues of concern to ccTLDs from a global perspective. • The ccNSO provides a platform to nurture consensus, technical cooperation and skill building among ccTLDs and facilitates the development of voluntary best practices for ccTLD managers. • It is also responsible for developing and recommending global policies to the ICANN Board for a limited set of issues relating to ccTLDs, such as the introduction of Internationalized Domain Name ccTLDs (IDN ccTLDs).

32. ICANN gNSO • The Generic Names Supporting Organization (gNSO) fashions (and over time, recommends changes to) policies for generic Top-Level Domains (e.g., .com, .org, .biz). • The GNSO strives to keep gTLDs operating in a fair, orderly fashion across one global Internet, while promoting innovation and competition. • Sample GNSO issues: • When you register a domain name, what services must the registrar provide? • If you forget to renew your domain name, and it expires, can you get it back? • What happens if someone registers a domain name that is confusingly similar to yours?

33. ICANN ALAC • At-Large is the name for the community of individual Internet users who participate in the policy development work of ICANN. More than 140 At-Large Structures representing the views of individual Internet users are active throughout the world. • ICANN At-Large provides essential policy advice to ICANN, including guidance on how to ensure changes to the Internet’s addressing system can help ensure the Internet becomes a more trusted and safe place, how Internationalized Domain Names (“local language” domain names) are implemented, and how additional new top-level domains (.info, .name, .museum, etc.) are introduced.

34. ICANN GAC • The GAC is an advisory committee to ICANN, created under the ICANN Bylaws. It provides advice to ICANN on public policy aspects of ICANN’s responsibilities with regard to the Internet Domain Name System (DNS). • The GAC is not a decision-making body. It advises ICANN on issues that are within ICANN’s scope. • GAC advice has a particular status under the ICANN Bylaws. Its advice must be duly taken into account by the ICANN Board, and where the Board proposes actions inconsistent with GAC advice it must give reasons for doing so and attempt to reach a mutually acceptable solution. • The GAC appoints a non-voting liaison to the ICANN Board. This is normally the GAC Chair.

35. ICANN ASO • The purpose of the Address Supporting Organization (ASO) is to review and develop recommendations on Internet Protocol (IP) address policy and to advise the ICANN Board. Fifteen volunteers, three from each of the five RIR communities, serve on the ASO Address Council (AC). • Under the ICANN ASO Memorandum of Understanding, the ASO AC’s responsibilities include: • Undertaking a role in the global policy development process. • Defining procedures for the selection of individuals to serve on other ICANN bodies, in particular on the ICANN Board, and implementing any roles assigned to the AC in such procedures. • Providing advice to the ICANN Board on number resource allocation policy, in conjunction with the RIRs.

36. ICANN ASO • The purpose of the Address Supporting Organization (ASO) is to review and develop recommendations on Internet Protocol (IP) address policy and to advise the ICANN Board. Fifteen volunteers, three from each of the five RIR communities, serve on the ASO Address Council (AC). • Under the ICANN ASO Memorandum of Understanding, the ASO AC’s responsibilities include: • Undertaking a role in the global policy development process. • Defining procedures for the selection of individuals to serve on other ICANN bodies, in particular on the ICANN Board, and implementing any roles assigned to the AC in such procedures. • Providing advice to the ICANN Board on number resource allocation policy, in conjunction with the RIRs.

37. IETF • The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. • The IETF will pursue this mission in adherence to the following cardinal principles: • Open process - any interested person can participate in the work, know what is being decided, and make his or her voice heard on the issue. Part of this principle is our commitment to making our documents, our WG mailing lists, our attendance lists, and our meeting minutes publicly available on the Internet. • Technical competence - the issues on which the IETF produces its documents are issues where the IETF has the competence needed to speak to them, and that the IETF is willing to listen to technically competent input from any source. Technical competence also means that we expect IETF output to be designed to sound network engineering principles - this is also often referred to as "engineering quality". • Volunteer Core - our participants and our leadership are people who come to the IETF because they want to do work that furthers the IETF's mission of "making the Internet work better". • Rough consensus and running code - We make standards based on the combined engineering judgment of our participants and our real-world experience in implementing and deploying our specifications. • Protocol ownership - when the IETF takes ownership of a protocol or function, it accepts the responsibility for all aspects of the protocol, even though some aspects may rarely or never be seen on the Internet. Conversely, when the IETF is not responsible for a protocol or function, it does not attempt to exert control over it, even though it may at times touch or affect the Internet.

38. Internet Governance Forum • The mandate of the Forum is to: • Discuss public policy issues related to key elements of Internet governance in order to foster the sustainability, robustness, security, stability and development of the Internet; • Facilitate discourse between bodies dealing with different cross-cutting international public policies regarding the Internet and discuss issues that do not fall within the scope of any existing body; • Interface with appropriate inter-governmental organizations and other institutions on matters under their purview; • Facilitate the exchange of information and best practices, and in this regard make full use of the expertise of the academic, scientific and technical communities; • Advise all stakeholders in proposing ways and means to accelerate the availability and affordability of the Internet in the developing world; • Strengthen and enhance the engagement of stakeholders in existing and/or future Internet governance mechanisms, particularly those from developing countries; • Identify emerging issues, bring them to the attention of the relevant bodies and the general public, and, where appropriate, make recommendations; • Contribute to capacity building for Internet governance in developing countries, drawing fully on local sources of knowledge and expertise; • Promote and assess, on an ongoing basis, the embodiment of WSIS principles in Internet governance processes; • Discuss, inter alia, issues relating to critical Internet resources; • Help to find solutions to the issues arising from the use and misuse of the Internet, of particular concern to everyday users; • Publish its proceedings

39. Thank you