iCANN47 Newcommer session

Get Started. It's Free
or sign up with your email address
Rocket clouds
iCANN47 Newcommer session by Mind Map: iCANN47 Newcommer session

1. Links

2. Suggested sessions

2.1. Current Security updates

2.1.1. Wednesday morning session

2.2. Monday

2.2.1. Welcome Ceremony @ 8:30

2.2.2. New gLTD's Program Status Update @1300

2.2.3. Implemntation of African STrategy @1300

2.2.4. Internet Governance Update @16:30

2.2.5. DNSSEC for Beginners @

2.2.5.1. Recommended Google interactive session

2.3. Tuesday

2.3.1. Consituency Day

2.3.1.1. Supporting Organisations

2.3.1.2. Advisory Committees

2.3.1.3. Stakeholder Groups

2.3.1.4. COnstitinuencies

2.4. Wednesday

2.4.1. Security & stability Update @0900

2.4.2. Latin America and Middle East Regional Strategies @:15

2.4.3. IPv6 Workshop @1500

2.4.4. Africa Untehtered: a digital era of Digital Africa @15:00

2.4.5. Domain name Assoc & CEO Task Force Update @1700

2.4.5.1. Chris Bondini

2.5. Thursday

2.5.1. Meeting Strategy Working Group @900

2.5.1.1. Check who does this?

2.5.1.1.1. Focus on meeting strategy

2.5.2. Interactive COmmunity Outreach Session @11:00

2.5.3. Geographic Regions & review workshop=- fianl report discussion @12:30

2.5.4. Public Forum @13;30

2.5.4.1. 5.5 hours to address the board & executives

2.5.4.1.1. topics publsihed ahead

2.5.4.2. 2 minute time limit comment

2.5.4.3. write out the note for yourself

2.5.5. Board Meeting @18:00

2.6. Networking

2.6.1. Monday

2.6.1.1. At large AFRALO Event

2.6.2. Tuesday

2.6.2.1. Tuesday Music Night

2.6.3. Wed

2.6.3.1. Wed Gala

2.6.4. Thu

2.6.4.1. Thu ICANN47 Warap up cocktail

2.7. Tips & TOols

2.7.1. Newcomer programme sessions

2.7.2. ICANN ACRONYMS download Quizlet

3. Format

3.1. DIscovery

3.2. Engagement

3.3. Pannel session

3.3.1. Pannelists

3.3.1.1. Mouhamet DIOP

3.3.1.2. Pierre

3.3.1.2.1. African Bureau chief

3.3.1.3. Janice

3.4. Janice Douma Lange

3.4.1. [email protected]

4. Goals

4.1. Enable fast & effictive engagement at 1st meeting

4.2. Help to understand iCANN, its structure processes and community

4.3. Provide mentorship, guidance, and networking opportunities

5. Tips

5.1. For transcript and livestream & process

5.1.1. If you represent yourself, say so

5.1.2. Only speak on behalf of a constituencyif you have the mandate to do so

6. iCANN

6.1. iCANN team

6.1.1. 200 staff

6.1.1.1. was 50 pax in 2009

6.1.2. Conference history

6.1.2.1. Toronto

6.1.2.1.1. iCANN45

6.1.2.2. Beijing

6.1.2.2.1. iCANN46

6.1.2.3. Durban

6.1.2.3.1. iCANN47

6.1.3. Email addresses =

6.1.3.1. [email protected]

6.2. Internet Corporation for Assigned Names and Numbers

6.3. 200 locations around the world where have root servers

6.3.1. After a call for the DNS the website is cached on a local server

6.4. Constituencies

6.4.1. At Large

6.4.1.1. All internet Users

6.4.1.1.1. Certified at Large

6.5. Created in 1999

6.6. Regions for ICANN

6.6.1. AF = Africa AP = Asia/Australia/Pacific AQ = Antarctica EUR = Europe LAC = Latin America/Caribbean islands NA = North America

6.7. Functions of ICANN

6.7.1. Domain Name Sustem

6.7.2. gTLD's

6.7.2.1. Generic Top Level Domain (gTLD's)

6.7.3. ccTLD's

6.7.3.1. Country Code Top Level DOmains

6.7.3.1.1. 2 letter ascii code

6.7.4. Root Zone and other infrastrcuture domains

6.7.4.1. Registry of TLD's

6.7.4.1.1. Who thay are allocated to

6.7.5. Internet Protocal (IP) Address Allocation

6.7.5.1. Port numbers assigned to internet protocols

6.7.6. Protocol Paramters Registries

6.7.7. Other Minor Functions (e.g. Time Zone Database)

6.8. How is ICANN funded

6.8.1. Through Generic Top Level Domain registrees

6.8.1.1. .com

6.8.1.2. .net

6.8.1.3. .org

6.8.2. Through country level domains

6.8.2.1. Profit share (not mandatory)

6.8.2.2. use services of ICANN

6.8.3. Registrars

6.8.3.1. provide the service to those who want to have a URL

6.8.4. gTLD's also fund part of the budget

6.8.5. Financing from customers buying domain names

6.8.5.1. you give it to a registrar

6.8.5.1.1. Who gives it to a Registrees

6.9. Shift in ICANN

6.9.1. a shift from implementing the global business plan of ICANN to a regional approach to promote how the region can help make this happen.

6.9.1.1. ICANN is listening to region and setting up structures

7. Topics of dicsussion

7.1. Who runs the Internet

7.1.1. no one person, organzation, or government runs the internet

7.1.2. Who is involved?

7.1.3. Everybody is involved

7.1.4. You have to define your path in co-creating the internet

7.1.5. Components of the Internet

7.1.5.1. Organisations individuals and processes that shape the coordination and mngt of global internet

7.1.5.2. Highly interdependent parts which require significant coordination

7.1.5.3. iCANN is one of the organisations pivotal to naming and addressing

7.2. One world one internet

7.2.1. ideas of multiple people = multi stakeholder approach

7.2.1.1. Internal ICANN Multi Stakeholder structure

7.2.1.1.1. GNSO

7.2.1.1.2. Ombudsman

7.2.1.1.3. Board of Directors

7.2.1.1.4. President & CEO

7.2.1.1.5. Technical communities

7.2.1.1.6. Government advisory committies

7.3. WOrld's Network: the Domain Name System

7.3.1. Internet Protocol numbers are unique addresses that allow computers to find one another

7.3.2. Domain Name System matches IP Numbers with a name

7.3.3. DNS is underpinning the unified internet

7.3.4. ICANN formed in 1998 to coordinate DNS

7.4. How the regiona Staff fit into the model?

7.4.1. Interact w/ regional ICANN community

7.4.2. Make sure our/your voice is heard

7.4.3. Work with partners (ISOC, RIR's) to maintin bottom up approaches on IG

7.4.4. Which leads to the IGO's

7.5. Stakeholder & liaison teams

7.6. Basics; new Generic Top Level Domains (new gTLD's)

7.7. Internationalized domains

7.8. Contractual Relationship Overview

7.8.1. Domain name life cycle iCANN

8. Acronyms & word clarifications

8.1. IGF

8.1.1. Internet Governance Forum

8.2. IDEA

8.2.1. Script available on internet

8.3. iCANN

8.3.1. Internet Corporation for Assigned Names and Numbers

8.3.1.1. ICANN formed in 1998 to coordinate DNS

8.4. DNS

8.4.1. Domain Name System

8.4.1.1. DNS is underpinning the unified internet

8.4.1.2. DOmain Name System matches IP Numbers with a name

8.5. IP

8.5.1. Internet Protocol

8.5.1.1. Internet Protocol numbers are unique addresses that allow computers to find one another

8.6. gTLD's

8.6.1. Generic Top Level Domain (gTLD's)

8.7. ccTLD's

8.7.1. Country Code Top Level DOmains

8.7.1.1. 2 letter ascii code

8.7.1.1.1. SA

8.7.1.1.2. inclduing in cyrillic and arabic for

8.8. Root Zone and other infrastrcuture domains

8.8.1. Registry of TLD's

8.8.1.1. Who thay are allocated to

8.9. ISOC

8.9.1. Internet Society

8.10. RIR

8.10.1. Regional Internet Registry

8.11. IGO's

8.12. GAC

8.12.1. Governments Advisory Committee

8.13. Regions for ICANN

8.13.1. AF = Africa AP = Asia/Australia/Pacific AQ = Antarctica EUR = Europe LAC = Latin America/Caribbean islands NA = North America

8.14. PDP

8.15. DNSSEC

8.15.1. Domain Name System + Security extension

8.15.1.1. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. When typing a name, that name must be first translated into a number by a system before the connection can be established. That system is called the Domain Name System (DNS) and it translates names like www.icann.org into the numbers – called Internet Protocol (IP) addresses. ICANN coordinates the addressing system to ensure all the addresses are unique.

9. Questions

9.1. Fellowship question

9.2. Policy

10. Remarks

11. Suggestions