Overall new gTLD program update on program progress, key accomplishments including Auction Implementation, Name Collision, Community Priority Evaluation, and implementation of GAC Advice. Originally presented during the New gTLD Program Update Session at ICANN 49 in Singapore.
5. Text
#ICANN49
144
960
1094
Program Progress – Application Statistics
Objections Completed Contracting
Invitations Issued
Registry
Agreements Signed
Pre-Delegation
Testing Passed
New gTLDs Delegated
CIR Responses
Received
2013 November:
ICANN 48 Buenos Aires
2014 March:
ICANN 49 Singapore
171
249
275
502
358
47
266
24
182
6. Text
#ICANN49
Accomplishments: Buenos Aires to Singapore
o NGPC approved implementation approach for GAC Category 1 Advice
o NGPC approved implementation approach for non-exclusive use
gTLDs subject to GAC Category 2 Advice
o 249 Objections Complete
o 4 Community Priority Evaluation results published
o Auction notifications sent to 306 applicants in 106 contention sets
o Name Collision Framework published for public comment
o Supported delegation of 182 new gTLDs
o Approved 2 additional data escrow agents
o Qualified Launch Program published for public comment
7. Text
#ICANN49
Continuing Work
• Coordinate and manage program processes
o Complete application evaluation
o Monitor objections progress
o Hold first auction
• Support Board and community
o GAC Advice
o Name Collision Framework
o Perceived inconsistencies in String Contention Objection
determinations
• Continue to improve internal processes for reliability
o Contracting
o Community Priority Evaluation
o Pre-Delegation Testing
10. Text
#ICANN49
Application Statuses – Improved Reporting
• 14 March 2014 – ICANN updated application statuses:
https://gtldresult.icann.org/application-result/applicationstatus
o Read announcement (includes link to Advisory):
http://newgtlds.icann.org/en/announcements-and-media/announcement-15mar14-en
• New statuses added
o On Hold
Application has pending activities that may impact the status of the
application
o Will Not Proceed
Application will not continue based on the outcome of a program
process it has completed
11. Text
#ICANN49
Application Statuses Overview
• Final application statuses
o Withdrawn
o Delegated
• Not Approved and Applicant Support statuses
o Not Approved
Application will not continue as a result of a resolution passed by
the ICANN Board
o Applicant Support
Application did not meet the requirements under the Applicant
Support Program
12. Text
#ICANN49
Application Statuses Overview (cont.)
• Status reflects program step application is undergoing
o In Initial Evaluation
o In Extended Evaluation
o Evaluation Complete
o In Community Priority Evaluation
o In Auction
o Contention Resolution Complete
o In Contracting
o In Pre-Delegation Testing
o In Transition to Delegation
16. Text
#ICANN49
14
171
31
47
Determinations Status
In Progress
Applicant Prevailed
Objector Prevailed
Terminated
Objections & Dispute Resolution
• 95% of cases resolved
o Legal Rights, String Confusion Objections complete
• 14 March 2014: Application statuses and contention
sets updated to reflect objection outcomes
17. Text
#ICANN49
Objections – Public Comment
• ICANN published a proposal to address the
perceived inconsistent expert determinations
on String Confusion Objections
• Public Comment Forum
o Comment period: 11 February – 12 March 2014
o Reply period opened: 13 March 2014
o Reply period closes: 3 April 2014
• View or submit comments:
http://www.icann.org/en/news/public-comment/sco-framework-principles-
11feb14-en.htm
18. Text
#ICANN49
GAC Advice – Category 1 Overview
In its Beijing Communiqué, the GAC
proposed specific safeguards that would
apply to a broad category of strings
related to “consumer protection, sensitive
strings, and regulated markets.”
20. Text
#ICANN49
Category 1 Implementation Framework
o 5 February 2014: Implementation Framework adopted
o 10 safeguards:
http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-
annex-2-05feb14-en.pdf
Highly Regulated Sector
Professional Services
Financial
Charity
Corporate Identifiers
Education
Health & Fitness
Gambling
Safeguards
1-8
Regulated Sector
Safeguards 1-
3
Special Safeguards Required
Cyber Bullying/Harassment
Inherently Governmental
Functions
Safeguards 1–9,
or 1-8 & 10
Professional Services
Financial
Charity
Corporate Identifiers
Education
Environmental
Generic Geo Terms
Intellectual Property
Children
Health & Fitness
Gambling
None
21. Text
#ICANN49
GAC Advice – Category 1 Implementation
o Applicants previously subject to GAC Category 1
Advice, who meet eligibility criteria, have been invited
to Contracting
o Safeguards included in Specification 11 – Public
Interest Commitments – of the Registry Agreement
o Public Interest Commitments enforceable via the
PICDRP
o Read Applicant Advisory:
http://newgtlds.icann.org/en/applicants/advisories/gac-cat1-advice-19mar14-en
22. Text
#ICANN49
GAC Advice – Category 2 Overview
In the Beijing Communiqué, Category 2
Safeguard Advice (section 2), the GAC
advised that, "For strings representing
generic terms, exclusive registry access
should serve a public interest goal.”
23. Text
#ICANN49
GAC Advice – Category 2 Responses
Applications subject to
GAC Category 2 Advice
Intend to operate as non-
exclusive access;
applications support
intent
Intend to operate as non-
exclusive access;
applications do not
support intent
Required to submit
statement of public
interest
Proceed to contention
resolution or contracting if all
eligibility criteria are met
Submitted change
request to align
applications with intent
Pending instruction
from NGPC regarding
next steps
Intend to operate as
exclusive access;
applications support
intent
186
139 35 12
34 1
Eligible Pending
24. Text
#ICANN49
GAC Advice – Category 2 Next Steps
• New gTLD Program Committee of ICANN
Board to consider applicant statements on
how exclusive access TLDs will serve the
public interest
• Read Applicant Advisory:
http://newgtlds.icann.org/en/applicants/advisories/gac-cat2-advice-19mar14-en
27. Text
#ICANN49
Community Priority Evaluation
• First 4 results published 18 March 2014
• Expected cycle time for current evaluations ~ 3 months
19
1
8
4
0
5
10
15
20
Pending Eligibility Invited In Evaluation Results Published
Current Status
NumberofApplications
28. Text
#ICANN49
Community Priority Evaluation - Summary
• Independent evaluation applying the criteria of
Applicant Guidebook section 4.2.3
• The CPE Panel developed Evaluation Guidelines
further clarifying the AGB Criteria – Published in
September 2013
• Evaluations performed by Economist Intelligence Unit
o Application Responses
o Publicly Available information
o May request additional information from applicant if required
• High bar to prevail contention via CPE
29. Text
#ICANN49
Auctions
• 6 March 2014: Materials published
o Public Comment Report, Auction Rules, and Bidder
Agreement published:
http://newgtlds.icann.org/en/applicants/auctions#resources
• 19 March 2014: Auction schedule published
o Notifications of Intent to Auction issued
to 106 contention sets – forms due back 17 April
• 4 June 2014: First Auction
• Learn more at our ICANN 49 session:
o Title: New gTLD Program Auctions
o Date/Time: Today, 24 March 2014 – 15:15-16:30 SGT
33. Text
#ICANN49
Contracting Statistics
Applicants Invited to Contracting1094
Applicants Responded to CIR502
Within standard 3-week processing time: 39%
Processing time of apps pending items: 41 Days
Averages
Contracts Sent for Signature427
35. Text
#ICANN49
Registry Operator Code of Conduct
• Set of guidelines for the registry operator relating to certain
and limited operations of a registry
• 18 March 2014: Completed Code of Conduct exemption
requests published for comment
o View requests:
http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting/ccer
o Send comments to exemption-request@icann.org
o View comments:
http://mm.icann.org/pipermail/exemption-request
o Read FAQ:
http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting/ccer/faqs-
18mar14-en.pdf
• ICANN will consider comments prior to determining action
37. Text
#ICANN49
Pre-Delegation Testing
Scheduled Start Date Count
24 Mar 2014 20
31 Mar 2014 10
42 30 20
266
0
100
200
300
Invited Scheduled In Testing Complete
Current Status
• Upcoming PDT Schedule
o Operational capacity of 20 appointments per week
Applications
39. Text
#ICANN49
Name Collision Mitigation
• Public Comment Period
o Comment period opened 26 February 2014
o Reply period closes 21 April 2014
• Name Collision Occurrence Management Framework
o Reserve .corp, .home, & .mail
o Newly delegated TLDs: 120 days from delegation “no
activation” period with wildcard record under TLD
o Already delegated TLDs: 120 days with A and SRV DNS
records for names in SLD block list
• Learn more at our ICANN 49 session:
o Title: Name Collision Mitigation
o Date/Time: Monday, 24 March 2014 – 13:30 to 15:00 SGT
41. Text
#ICANN49
EBERO
• 3rd provider expected to be operational in May 2014
• Exercises
o Held simulations with the two current providers
o SLA Monitoring System used to trigger “event”
o Restored DNS, DNSSEC, RDDS, SRS and Escrow services
efficiently and effectively
o Met SLAs
• Request for Proposals: Additional providers
o Draft under internal review – expected release April 2014
o Expected selection of new providers June 2014
o Bring additional providers online as soon as possible
42. Text
#ICANN49
Trademark Clearinghouse
Statistics (19 March 2014) ICANN 48 ICANN 49
TMCH Records 18,256 27,757
Non-Latin Records 550 1,034
Jurisdictions 99 116
Abused Labels 90 294
UDRP Cases 76 141
Sunrise and Claims 0 21,155
Certified Registrars 4 92
43. Text
#ICANN49
TLD Launch Programs
• Approved Launch Programs
o 19 December 2013: Published Review Guidelines
• Qualified Launch Program
o 13 February 2014: Published Qualified Launch Program
draft for public comment
• Learn more at our ICANN 49 session:
o Title: TLD Launch Process Experiences and Registry Onboarding
o Date/Time: Monday, 24 March 2014 – 17:00-18:30 SGT
45. Text
#ICANN49
Looking Forward to London
• 200th delegation
• 400 Registry Agreements signed
• Finalization of the Name Collision Framework
• First Auction held
• Additional EBERO providers selected
47. Text
#ICANN49
Internationalized Domain Name Variant TLDs
• Many new IDN TLDs introduced into Internet recently
o Some IDN new gTLDs may have variants, alternate labels that are
considered the same or have equivalent meaning
Variant examples: 䲁 and 鳚, Strasse and Straße (hypotheticals, not
suggestions for actual variants)
o There are no rules for IDN labels and associated variants (if any) for
the Root Zone – these Label Generation Rules (LGR) need to exist
• Community work is crucial to creating the LGR
o All scripts should be represented accurately, comprehensively
• Speak Up For Your Language! Learn more at our session:
o Title: IDN Variant TLDs Program Update
o Date/Time: Wednesday, 26 March 2014 – 08:30-10:00 SGT
49. Text
#ICANN49
Related Global Domains Division Sessions
24 March
13:30-15:00
24 March
15:15-16:30
24 March
15:15-16:45
24 March
17:00-18:30
Name Collision Mitigation
New gTLD Program Auctions
TLD Acceptance
TLD Launch Process Experiences and
Registry Onboarding
TLD Registry - Ongoing Operations
26 March
10:30-12:00
IDN Variant TLDs Program Update
26 March
8:30-10:00
Editor's Notes
9 October 2013: 138 applications eligible to proceed to contracting and contention resolution if all eligibility criteria are met
Applicants indicated that the TLD will be operated in a non-exclusive manner and the application supports this intent
28 January 2014: 12 applications submitted statements on public interest
Applications continue to be held pending instructions from NGPC
21 March 2014: Application Update/Explanation Deadline
Applicants who indicated that the TLD will be operated in a non-exclusive manner, but the application does not supports this intent must:
Submit a change request to align the application with the intent
Submit a statement explaining how exclusive access use of the TLD would serve the public interest
Applications continue to be held pending instructions from NGPC
9 October 2013: 138 applications eligible to proceed to contracting and contention resolution if all eligibility criteria are met
Applicants indicated that the TLD will be operated in a non-exclusive manner and the application supports this intent
28 January 2014: 12 applications submitted statements on public interest
Applications continue to be held pending instructions from NGPC
21 March 2014: Application Update/Explanation Deadline
Applicants who indicated that the TLD will be operated in a non-exclusive manner, but the application does not supports this intent must:
Submit a change request to align the application with the intent
Submit a statement explaining how exclusive access use of the TLD would serve the public interest
Applications continue to be held pending instructions from NGPC
The first line there represents the contention sets created by the String Similarity Panel, back about 13 months ago
We had 234 contention sets, and 758 applications in contention
Since then we have seen 47 contention sets resolved, we also had some sets “merge” and 1 set created as a result of objections.
So the new current total is: 233 Contention Sets
164 Active Sets – with 543 applications still in contention
22 Sets on Hold – with 87 applications in contention
Two weeks back we updated application status and contention sets status as Trang described earlier, to reflect results of various processes, most notably objection determinations
This brought us down to 186 Unresolved Contention Sets
Objection determinations changed the structure of several sets
- Some apps were removed from contention
- Some added to contention
- and some sets were joined together
We now have several sets with both direct & indirect contention relationships, ofter referred to as indirect contention sets.
Each Set has assigned one of three statuses:
Active – meaning at least 2 applications remain in direct contention and no applications are on-hold
On Hold –one or more applications has a status of on-hold –thus the set will not move forward until the issue is resolved
Resolved – no direct contention remains, no apps on hold
165 Active
21 On Hold
47 Resolved
To further explain the contention sets we have redesigned the contention set page with improved functionality:
Each Contention Set assigned an identifier number
Contention Set names made up of the String or Strings in the set – eliminates multiple entries for sets with multiple strings (hotels & hoteis)
Visual depiction of each contention set
Lists all contention sets including those resolved
Expanding the details allows users to see the application status of each member of the contention set
We published the first 4 results on 18 March 2014
These results were as recommended by the CPE Panel after careful consideration. The panel concluded that none of the 4 applications met the very high standard to win priority as a community application. The reports reiterate the criteria and explain how the application compared. These contention sets if they remain unresolved will be placed into the queue for Auctions once they are eligible.
These first evaluations did take longer than expected, but we believe this next group should trend back toward the ~ 3 month target duration.
Q & A –
Why were no CQ’s issued to these applicants
CQ’s in CPE are different than Initial Evaluation. The panel defined tight boundaries on what would warrant a clarifying question. There is a fine line where we can not allow applicants to change their applications at this point in the program.
What happened to Osaka?
Osaka had a unique issue as a Geo name string, where both applicants received support from the same government authority as a Geo. Thus we need more information from the government authority before proceeding
CPE Criteria in AGB 4.2.3
Community Establishment
Nexus between Proposed String and Community
Registration Policies
Community Endorsement
Scope of Evaluations
Application Responses – particularly questions 13, 18 -20, 27 & 28
Publicly Available info – Information about the community, Correspondence, Objection Determinations, and Applicant Comments
Because information is reviewed does not necessarily means the panel finds it relevant to the scoring of the application
Auctions are now operational
We published the Summary and Analysis Report of the Public Comment on 6 March 2014
With the publication of the public comment report, we also published the auction rules, and bidder agreement that will be used for operations
Last week we published an updated Auction Schedule – it depicts the 1st Auction being held 4 June 2014
The schedule is a refresh from the one published with the public comment documents in Dec 2013
The document includes those sets already resolved, we thought it made it clearer how the contention set number factored into the schedule
In addition to the schedule, we have notified 106 contention sets that they are being sent to Auction – this represents all of the contention sets currently eligible
This does not mean to imply all 106 are being set to Auction 1. Please consult the Auction Schedule to understand which auction your contention set is schedule to participate.
I am not going to speak much to Auctions as we have a dedicated session later today in this room. I will ask that you hold your questions until that session.
630 In Contention
23 Have GAC Advice
6 Have Objection(s)
46 Pending Change Requests
7 In Re-Evaluation
70 On Hold
UPDATE??
Current statistics as of 16 November 2013:
CIR Notifications sent through Priority Number 1300
960 Applicants invited to contracting
275 Applicants responded to CIR
178 Contracts sent for signature
144 Registry Agreements signed
COI outreach completed
23 incomplete CIR
25 COI
18 negotiate
22 other
-6 ACR
-6BGS
-9ExA
-1 Spec 12
Other
-6 RAs en-route to Akram for signature
-1 on hold (lgbt – pending AM)
As mentioned in the last applicant update, we are pleased to add Nominet to our group of EBERO providers. We expect to be able to declare them operational in May at which point they will join CNNIC and CORE as the third provider.
Over the past quarter we conducted practice simulations with both CNNIC and CORE. These exercises allowed the ICANN and provider teams to gain valuable time and experience working together.
These practice exercises simulated a variety of conditions that are likely to occur in an actual event. The SLA monitoring systems that are in place and already are monitoring the new gTLDs was used to trigger the practice event, just as it would do in an actual event. These practices allowed both teams to work through their processes in a collaborative and productive manner. In both cases, each provider was very effective and efficient at restoring services with both of them easily meeting SLAs.
Looking forward, we also see a need for additional providers to improve geographic distribution and coverage. To support this need, we have developed a draft RFP and expect to release it in the April timeframe. Along with the stringent financial and technical evaluation, location will certainly be considered in the evaluation process. We expect to select the new providers in June with a goal of bringing additional providers online before the end of the year.
The Trademark Clearinghouse has seen significant growth since the last ICANN meeting. The number of trademarks in the database has grown by about 50%. Similarly, non-Latin script records have increased by about 50% as well.
The count of jurisdictions has grown by approximately 15%. The number of abused labels and UDRP cases have also grown significantly.
As of today, there have been over 100 sunrise periods and over 50 claims periods that have been supported by the TMCH. This has resulted in just over 21,000 transactions in Sunrise and Claims. This has been supported by a massive increase in the number of certified registrars.