11

AfTLD 3rd African ccTLD Event, 2009 Tanzania Theme:

“Securing Africa's Internet Infrastructure”

13th - 17th April 2009 , Arusha, Tanzania

Anne-Rachel Inné

Regional Relations Manager, Africa

Overview

– Update ICANN• ICANN-USG Joint Partnership Agreement (JPA) –

where to from here?• Preparing for the new gTLDs• ICANN ccTLD Accountability Framework• GNSO• ASO• ccNSO

– Update IANA

2

ICANN-USG Joint Partnership Agreement (JPA)• Web page: http://www.icann.org/en/jpa/iic/

• The President Strategy Committee posted:– Transition Action Plan

– Improving Institutional Confidence in ICANN

– FAQ

• 27 February 2009, the President's Strategy Committee published its draft Implementation Plan for Improving Institutional Confidence

• Three comment periods and last documents to come out soon

• iic@icann.org open to anyone who has additional questions after reviewing the official documentation

• NTIA will probably soon have a NOIF to ask if termination of JPA is appropriate. Will send information on lists

3

JPA - links

• Related links:• Announcement and links to comments:

http://www.icann.org/en/public-comment/#iic-plan• The March 2009 Board resolution accepting the report and directing

further action is posted at http://www.icann.org/en/minutes/resolutions-06mar09.htm#13

• The draft Implementation Plan on Improving Institutional Confidence is published at: http://www.icann.org/en/jpa/iic/draft-iic-implementation-26feb09-en.pdf

• The President's Strategy Committee homepages: http://www.icann.org/en/psc/

4

Accountability Frameworks with ICANN

• Names: Accountability Framework, Exchange of Letter

• Agreements page: http://www.icann.org/en/cctlds/agreements.html

• Contain clauses stating the obligations of a ccTLD manager and ICANN, but also covers dispute resolution and termination

• ccTLD model MOUs: http://www.icann.org/en/cctlds/agreements.html

5

GNSO update

6

WHOIS

• The GNSO Council has requested Staff to conduct research on feasibility and cost estimates for 6 Whois studies, taking into account ALAC and GAC requests and opinions.

• Details of the studies and the hypothesis can be found in the Council resolution:

• http://gnso.icann.org/resolutions/#200903• Very broadly these studies will examine hypothesis

related to data accuracy, proxy registrations related to abusive or illegal purposes and privacy issues.

7

Inter-Registrar Transfer Policy review process

• GNSO review of inter-registrar transfer policy identified 20+ potential areas for clarification and improvement

• Total of 6 PDPs planned to address specific categories• First PDP – reasons for denial of transfer requests – at Council

approval stage – new text proposed for reasons #8 and #9• Second PDP on “new IRTP issues”

• See Final Report presentation below: http://gnso.icann.org/correspondence/irtp-part-a-report-presentation-16apr09.pdf

• Remaining 4 PDPs will be addressed consecutively with possibility of overlap as resources permit

• Participation sought for PDP B working group to be launched shortly.

• Keep tuned in!8

Inter-Registrar Transfer Policy review process (cntd)

• Working Group, meeting since June 2008 has presented a Final Report Inter-Registrar Transfer Policy (IRTP) Part A Policy Development Process (PDP)

• Presentation:• http://gnso.icann.org/correspondence/irtp-part-a-report-p

resentation-16apr09.pdf• Part A PDP (First in a series of five upcoming PDPs)

addresses the following issues:

9

Inter-Registrar Transfer Policy review process (cntd)

• Issue I –Potential need for exchange of registrant e-mail data between registrars

• in the absence of a simple and secure solution for providing the gaining registrar access to the registrant email address, future IRTP working groups should consider the appropriateness of a policy change that would prevent a registrant from reversing a transfer after it has been completed and authorized by the admin contact

•  • Issue II –Potential need for electronic authentication• Conclusion: “there appears to be broad agreement that there is a

need for other options for electronic authentication.• How? ... GNSO policymaking or should be left to market

solutions

10

Inter-Registrar Transfer Policy review process (cntd)

• Issue III –Potential need for provisions for partial bulk transfers between Registrars

• Conclusion" no need to incorporate provisions for handling partial bulk transfers between How ? ... either through the existing Bulk Transfer provisions, or through existing market solutions.

• Recommend that the current bulk transfer provisions also apply to a bulk transfer of domain names in only one gTLD”

11

Fast Flux• Techniques used by cyber-criminals to evade detection by modifying rapidly

IP addresses and/or name servers

• SSAC advisory issued January 2008

• Staff published Issues Report 26 March, recommended additional fact finding and research to develop best practices and guidelines

• May 2008: GNSO launched PDP and created a chartered working group to answer several questions about scope and impact of fast flux activity and potential solutions

•  Fast Flux Working Group is reviewing the public comments to incorporate into its Final Report.

• Summary of Public Comments:

• (http://forum.icann.org/lists/fast-flux-initial-report/msg00025.html).

• Review the full comments (http://forum.icann.org/lists/fast-flux-initial-report/)

• Wiki Reference:

• https://st.icann.org/pdp-wg-ff/index.cgi?fast_flux_pdp_wg

12

Registration Abuse policy

• Registries and registrars seem to lack uniform approaches to dealing with domain name registration abuse, and questions persist as to what actions constitute “registration abuse.” The GNSO Council has launched a Registration Abuse Policies Working Group to take a closer look at registration abuse policies.

• Registration Abuse Policies Issues Report, 29 October 2008: • http://gnso.icann.org/policies/ • (The report is published in Arabic, French, Spanish and Russian)•  Recent Developments: The Working group meets every two weeks

and if you would like to join please contact the gnso.secretariat@icann.org.

• There will be some reading for you to catch-up, but participation is most welcome.

13

Regitrar Accreditation Agreement• http://gnso.icann.org/resolutions/

• The GNSO Council supports the RAA amendments as documented in

• http://gnso.icann.org/drafts/current-list-proposed-raa-amendments-16dec08.pdf

• and recommends to the Board that they be adopted at its meeting of March 6, 2009;

• http://www.icann.org/en/minutes/resolutions-06mar09.htm#09

•  

• Next Steps:

• representatives from the GNSO community and the ALAC shall be identified to participate in drafting a registrant rights charter

• the GNSO Council will form a Drafting Team to discuss further amendments to the RAA and to identify those on which further action may be desirable.

14

Domain Name tasting• Last year the GNSO Council, and then the Board,

approved policy to curb abuse of the “add grace period” (AGP) for domain tasting

• Board also approved the draft budget for FY 2008-09, included language to curb domain tasting

• Provides transaction fee (currently US$0.20) for AGP deletes that exceed the maximum of:

• (i) 10% of that registrar's net new registrations in that month (defined as total new registrations less domains deleted during AGP) or

• (ii) fifty (50) domain names, whichever is greater.

  15

Domain Name tasting (cntd)

• Prior to AGP Budget/Policy Provision• May 2008: 18.4M• June 2008: 17.6M

•  Since AGP Provision • July 2008: 2.8M• August 2008: 2.1M•  AGP Limits Policy will likely result in few AGP deletes

subject to the excess deletion fee

16

GNSO restructuring

Help build a new GNSO

• The GNSO has created five new Work Teams through which implementation plans for ICANN Board approved GNSO improvement recommendations can be developed and proposed by members of the ICANN community. Each Work Team is made up of community volunteers who have interest in and expertise in one of five main focus areas:

• Constituency/Stakeholder Group Operations • GNSO Operations • New Working Group Model. • New GNSO Policy Development Process (PDP) • Community Communications and Coordination

17

GNSO restructuring (cntd)

• We encourage you to participate in one of the Work Teams.

 • Community Volunteers for the GNSO Improvements

Implementation Work Teams can contact:• gnso.secretariat@gnso.icann.org

• What the New GNSO Council Organisation will look like. When? Aim is for June 2009

18

GNSO new structure

19

New gTLDs• A second draft of an Applicant Guidebook that details the process of

applying for new generic top level domains has been released along with a detailed analysis of comments received so far.

• Comments on the 2nd version close on 13 April• The Implementation Recommendation Team (IRT) has been formed

to provide possible solutions to trademark issues raised in the new Generic Top-Level Domain (New gTLDs) implementation planning. The IRT held an initial administrative teleconference meeting on 25 March, 2009 to, among other things, establish working rules and agendas for future meetings.

• The IRT meeting notes are now available for viewing and comment on the recently established New gTLD Overarching Issues page

• https://st.icann.org/new-gtld-overarching-issues/index.cgi?new_gtld_overarching_issues.

20

New gTLDs (cntd)• As future meeting notes become available they will be posted to the

site.• In response to the Public Comments regarding the draft Applicant

Guidebook posted 24 October, 2008, (http://www.icann.org/en/topics/new-gtlds/comments-2-en.htm), ICANN has created a dedicated WIKI space entitled, "New gTLD Overarching Issues."

• This wiki will enable the community to view and post comments, upload proposals, documents and reports and leave feedback for ongoing dialogue related to the four overarching issues described in earlier postings:

• Trademark Protection • TLD Demand and Economic Analysis • Security and Stability: Root Zone Scaling • Potential for Malicious Conduct

21

GNSO – keep up to date• The WIKI can be accessed at: • https://st.icann.org/new-gtld-overarching-issues/index.cgi?

new_gtld_overarching_issues

• KEEP UP TO DATE WITH THE IMPORTANT WORK GOING ON IN THE GNSO• Sign up for the monthly Policy Update: • http://www.icann.org/en/topics/policy/

• Submit public comments and participate in Working Groups:• http://gnso.icann.org/announcements/

• Check the ICANN and GNSO web sites on a regular basis:• http://www.icann.org• http://gnso.icann.org/

• Check the GNSO Calendar for upcoming meetings: • http://gnso.icann.org/calendar

22

Thank You! Inkosi!

• Questions/Comments Welcome

• policy-staff@icann.org

Glen de Saint Géry

• GNSO Secretariat

• gnso.secretariat@gnso.icann.org

• http://gnso.icann.org

23

2424

ASO Update

2525

ASO update

• The Global Policy Proposal for Allocation of Remaining IPv4 Adress Space was ratified by the ICANN Board on 6 March and has since been embodied in a procedure to be applied when a prescribed threshold in the IPv4 depletion has been reached. Once the IANA free pool of IPv4 address space reaches five /8s, then IANA will allocated one /8 to each RIR.

• A new Global Policy Proposal for handling of recovered IPv4 address space is currently under discussion  in the RIRs. This proposal can be seen as an alternative to inter-RIR transfers - it suggests that IANA act as a repository of the RIRs' recovered IPv4 space and allocates such space to the RIRs according to requests, with smaller minimum allocations than today.

2626

IDNs Update

IDNs - Latest Developments

• Revised IDN ccTLD Draft Implementation PlanRequested finalized for ICANN Board consideration at Seoul

ICANN Meeting, 25-30 October 2009:

• Draft required Documentation of Responsibility

• Financial models for some level of cost-recovery

– will provide financial details to inform process shortly

• Allocation or blocking of variant string (per IDN Tables)

• IDN gTLDs

• Proposal to be released to relax the 3-char restriction for example for ideographs

• IDNA technical standard revision

• must be adhered to, focused session at ICANN Sydney

• IETF, http://www.ietf.org/html.charters/idnabis-charter.html)27

Detailed Agenda• IDNs availability and progress• Revised IDN ccTLD Draft Implementation Plan

• Documentation of Responsibility• Financial Model• IDN Tables and Variants• Contention Prevention and Solutions

• IDN gTLDs• # of characters in a gTLD string

• IDN Technical Focus• Why technical standards are necessary• IDNA protocol revision status

28

• IDNs have existed as second level since 2003• under web protocol standards (revision - IETF)• some email clients (standard underway - IETF)

• We also need IDN TLDs– http:// 例子 . 測試 – IDN .test TLDs since Sept 2005

(http://idn.icann.org)

IDNs so far…

29

Domain Availability

Today

Future Addition

ASCII domain names

(a, b,...,z), (0,1,…,9), (-)

IDN second level

domainname.TLDicann.org

例子 .TLD-under various existing TLDs

IDN TLDs 例子 . 測試

IDN TLD Processes

30

Implementation of Country-code IDN TLDs – Fast Track

- implementation of recommended policy from IDNC WG- to introduce a limited number of IDN ccTLDs- non-Latin scripts only, matching ISO3166 list- meaningful strings in local languages and scriptsCountry-code IDN TLDs – Long Term

- Full policy that caters for all- Follows the full ccNSO Policy Development Process

New Generic TLDs

- New ongoing policy for new gTLDs- Includes internationalized domains- Focus on non-ASCII squatting & confusingly similarity solutions

Revised IDN ccTLD Fast Track Draft Implementation Plan

• Revision 2.0• Released for public comments

– until 6 April 2009

• Specific attention on:– Documentation of Responsibility– Financial Considerations– IDN Tables and Variant Management– Preventing Contention

31

Proposed Details on:Documentation of Responsibility• Standard arrangement (DoR) between prospective IDN

ccTLD operators and ICANN• Draft DoR posted for public comments, based on:

• the existing ccTLD Framework• compliance with provisions for technical aspects

– IDNA protocol– IDN Guidelines

• received comment of previous Draft Plan• Broad variety for and against a required contract

• A separate paper on DoR specifics for public comments

32

Financial Model

• Received comments so far are split between• cost-recovery (like gTLD Program)• no fees or voluntary fees (like existing ccTLDs)

• ICANN standpoint:• new situation different from existing TLDs• requires some cost-recovery from the IDN TLD

managers

• ICANN will release a paper with proposed cost and fee details shortly.

33

Proposed Details on:IDN Tables &Variant Management

• IDN Tables inform users and reduce confusion• based on a language, script, or sets thereof • a registry can use more than one table

• Proposal to urge coordination across language communities when developing tables

• Variant TLD strings: delegated or blocked• Due to linguistic usage of scripts within country/territory• Matching current second level policies and procedures• RFI reply analysis shows @7 variant strings for allocation

34

Preventing Contention• Prevention of contention between

• Fast Track requested IDN ccTLD strings

• Existing TLD strings

• Proposed strings in new gTLD applications

• Proposed rule for “existing TLDs”:• A gTLD application approved by the ICANN Board

• A validated IDN ccTLD string– any other later application for the same string will be denied– Validated = meaningfulness confirmed, technical check passed

• if contention: new gTLD application is placed on hold, the IDN ccTLD request prevails (if passing validation)

• if both parties w/government assent, both applications on hold until contention is resolved

35

Fast Track Process, looking forward• Reaching collaboration on outstanding issues

• DoR• Financial Model• IDN Tables and Variants Management• Contention Solutions

• Enabling finalization of the Implementation Plan• ICANN Board approval

– requested for ICANN Board consideration at Seoul ICANN Meeting, 25-30 October 2009

• Implementation of the process• Launch Fast Track Process• Allocate IDN ccTLDs

• Experience gained is input to the IDN ccTLD PDP

36

IDN gTLDs• Part of ongoing program for new gTLDs• Main changes relating to IDNs in the Guidebook:

– Technical string criteria, which will continue to evolve as the protocol revision in progressing

– # of characters, in particular for CJK community• While it is understood that parts of the community have

expressed a need for 1 and 2-char TLD strings, it was not possible to find a sound way of implementing this need

• Requested feedback from community to set criteria• Much appreciated, ideas have been received that will

continue to be worked upon

37

Why technical standards are necessary• The term "protocol" designates a technical standard

• Core set of protocols determine Internet functionality• The DNS is based on one of the most fundamental protocols

• The IDNA protocol is different, it is• entirely external to DNS, functions at application layer• basic DNS operation not changed by IDN introduction• experience shows multiple application implementations• security problems, warning users => different experience• Different applications different responses

– Blog-post with more details: http://blog.icann.org/2008/11/compliance-with-idn-technical-requirements/#comments

38

IDNA protocol (IETF)• Non-compliance with the IDNA protocol

• Hurts all IDN registries, not just the non-compliant• Applications providers will see further security problems• IDNA protocol exists but is under revision

– Unicode version independent– Fixing right-to-left script problems– Adding characters that previously were not available– Ongoing discussion about mappings

– ICANN standpoint: – the preference is that the protocol revision is completed, however if

indications show that this is not possible then we will proceed with the existing version of the protocol (potentially with additional precautions for the TLD strings to ensure future compatibility).

39

Thank you

http://icann.org/topics/idn

Additional questions, please contact: Tina Dam

Director, IDN

tina.dam@icann.org40

ccNSO Update

What is the ccNSO

• Country Code Names Supporting Organisation– Develop and recommend global policies relating to

ccTLDs to the ICANN Board;– develop voluntary best practices for ccTLD managers,

assisting in skills building within the global community of ccTLD managers, and enhancing operational and technical cooperation among ccTLD managers.

• Secretariat: 1 person, employed by ICANN.• 1 person for policy-support, employed by ICANN.• 18 Councillors, three from each region + 3

NomCom. From African Region: Mohamed El Bashir, .sd; Vika

Mpisane, .za; Paulos Nyirenda, .mw

ccNSO in the ICANN structure

Board of Directors

ASO GNSO CCNSO

President and CEO

ICANN Organisational Chart

ICANN staff

Root Server System Advisory Committee (RSSAC)

Security and Stability Advisory Committee (SSAC)

Governmental Advisory Committee (GAC)

At Large Advisory Committee (ALAC)

Technical Liaison Group (TLG)

Nominating Committee17 voting delegates + 5 non-voting delegates

Regional Internet Registries- ARIN- RIPE NCC- LACNIC- APNIC- AFRINIC

- gTLD Registries & Registrars- Intellectual Property- ISPs- Businesses- Universities- Consumers

ccTLD registries (e.g., .us, .uk, .au, .nl, etc.)

(91) ccNSO Members (April 2009)

Africa

.bi Burundi

.ci Cote d'lvoire

.cm Cameroon

.dz Algeria

.eg Egypt

.et Ethiopia

.ga Gabon

.ke Kenya

.ly Lybia

.ma Morocco

.mg Madagascar

.ml Mali

.mr Mauritania

.mw Malawi

.ng Nigeria

.sd Sudan

.sn Senegal

.tg Togo

.ug Uganda

.za South Africa

Asia-Pacific

.af Afghanistan

.am Armenia

.au Australia

.cn China

.cx Christmas Island

.fj Fiji

.ge Georgia

.hk Hongkong

.il Israel

.jo Jordan

.jp Japan

.kr Korea

.mv Maldives

.nu Niue

.np Nepal

.nz New Zealand

.pw Palau

.sa Saudi Arabia

.sb Solomon Islands

.sg Singapore

.th Thailand

.tr Turkey

.tw Taiwan

.ws Samoa

Europe

.be Belgium

.cz Czech Republic

.de Germany

.fi Finland

.fr France

.gi Gibraltar

.gp Guadeloupe

.hr Croatia

.it Italy

.ky Cayman Islands

.lt Lithuania

.ms Montserrat

.nl Netherlands

.no Norway

.pt Portugal

.rs Serbia

.ru Russia

.se Sweden

.si Slovenia

.sk Slovakia

.uk United Kingdom

Latin America and

Caribbean.ar Argentina

.bo Bolivia

.br Brazil

.cl Chile

.cr Costa Rica

.cu Cuba

.do Dominican Republic

.ec Ecuador

.gt Guatemala

.gy Guyana

.hn Honduras

.ht Haiti

.jm Jamaica

.lc Saint Lucia

.mx Mexico

.ni Nicaragua

.pa Panama

.pe Peru

.sv El Salvador

.tt Trinidad and Tobago

.uy Uruguay

.ve Venezuela

North America

.ca Canada

.pr Puerto Rico

.us United States

.vi US Virgin Islands

(According to ICANN Regions)

ccNSO Travel fund

• ccNSO can sponsor a limited number of travellers to the ICANN meetings

• Funding is made available for those who “actively contribute to the work of the ccNSO in particular to its projects and meetings.”

• More information on ccnso.icann.org, or contact ccnsosecretariat@icann.org

Current ccNSO topics- IDNs:

• IDN Fast Track: Implementation plan anticipated to be finalised by ICANN Meeting Seoul (Oct -09).

• IDN ccPDP: Issues report was initiated by ccNSO Council 7th April 2009. Means that PDP has “kicked off”, expected to finish in 2011 (not including implementation)

• ccNSO submitted input to new gTLD Applicant Guidebook – on issues covering geographic names

Current ccNSO Topics –Working Groups:• Strategic and Operational Planning (SOP) WG: To

coordinate and organise participation of ccTLD managers in ICANN's Strategic and Operational planning processes. Will include session strategic issues for ccTLD at Sydney meeting.

• http://www.icann.org/en/public-comment/public-comment-200904.html#op-budget-fy2010 comments open until April 30, 2009

• Meetings Programme WG: To help shaping the ccNSO meeting agendas, ensuring all regions can be involved (participants from African Region: Eric Akumiah, AfTLD; Vika Mpisane, .za)

• Delegation and Redelegation WG: To explore delegation and redelegation issues (this group is yet being formed)

Upcoming topics

• Conficker and establishing structure for mutual warning;

• Registry/Registrar session

• Strategic Issues

• Delegation/redelegation discussions

• Focus on Administrative issues (such as advertising, registration methods)

ccnso.icann.org

ccnsosecretariat@icann.org

5050

IANA Update

5151

IANA update

• Improved technical conformance testing. (Tests for root zone changes will be improved. IANA will shortly start emailing TLD operators on a regular basis to inform them of any technical issues, including an explanation of how to fix them.)

• Work is ongoing on new IDN ccTLDs (IANA will be adding new staff and procedures to deal with both IDN ccTLDs and new gTLDs)

• Interim Trust Anchor Repository (IANA has deployed a new service that allows TLDs that use DNSSEC to list their trust anchors. This is a precursor to signing the DNS root zone. Available at itar.iana.org)

• Root Zone Automation (Hoping to shortly receive US Government signoff to allow us to start public usage of the system. It will run in parallel with existing manual processes to ensure it is stable)

ICANN Fellowship Programme

• http://www.icann.org/en/fellowships/• Upcoming Meetings:• The 35th International Public ICANN meeting in Sydney, Australia

21-26 June 2009 Main Venue: HILTON Sydney 488 George Street | Sydney, NSW 2000 | Australia

• More information about this meeting can be found at http://syd.icann.org/

• The 36th International Public ICANN meeting in Seoul, Korea 25-30 October 2009Main Venue: TBD

• Application Round opens: 18 May 2009 • Application Round closes: 30 June 2009

52

53

http://syd.icann.org/

5454

Questions?

Thank You