ABCDEFGHIJKLMNOPQRSTUVWX
1
SectionTopicAre There New Outcomes Not Previously Seen by the Community?Rationale/Notes
2
Overarching Issues2.2.1 Continuing Subsequent ProceduresNot anticipated
3
Overarching Issues2.2.2 PredictabilityLikely to go out Again for Comment with proposed framework structure.Work remains to be done to at a minimum, refine and clarify the framework. For instance 1) clear boundaries are needed between the framework and any existing GNSO proceses and 2) clear usage guidance is needed for ICANN Org and the community, who will be asked to implement and eventually execute against this framework.
4
Overarching Issues2.2.2.1 Community EngagementNot anticipated
5
Overarching Issues2.2.2.2 Clarity of the Application ProcessNot anticipated
6
Overarching Issues2.2.3 Applications Assessed in RoundsPossible if we suggest a specifc threshold on when to start accepting applications for next subsequent round
7
Overarching Issues2.2.4 Different TLD TypesNot anticipatedWhile work remains to come to agreement on exact types within each of the buckets (e.g., application type, string type, or applicant type), deliberations have not surfaced new types for consideration by the WG.
8
Overarching Issues2.2.5 Application Submission LimitsNot anticipated
9
Overarching Issues2.2.6 Accreditation Programs (RSP Pre-Approval)PossibleThere remain questions about several elements, like re-testing RSPs, differences (if any) between RSP pre-approval and technical requirements.

There are also touchpoints here with the technical evaluation and pre-delegation testing.
10
Foundational Issues2.3.1 Competition, Consumer Trust and Consumer ChoiceNot anticipated
11
Foundational Issues2.3.2 Global Public InterestPossibleThere remains substantial opposition from parts of the community, though some of this resistance may be related to the naming convention (i.e., public interest) and the WG may want to make sure that all have the opportuntity to provide public comment. We may want to test this notion in a public comment period.

There is also the question of whether we should codify the notion of the sensitive / regulatory strings where PICs were added to address initial GAC concerns (Category 1)
12
Foundational Issues2.3.3 Applicant Freedom of ExpressionNot anticipatedIt remains unclear what the additional implementation guidance might look like from a practical perspective.
13
Foundational Issues2.3.4 Universal AcceptanceNot anticipated
14
Pre-Launch Activities2.4.1 Applicant GuidebookNot anticipated
15
Pre-Launch Activities2.4.2 CommunicationsNot anticipated
16
Pre-Launch Activities2.4.3 SystemsNot anticipated
17
Application Submission2.5.1 Application FeesNot anticipated
18
Application Submission2.5.2 Variable FeesNot anticipated
19
Application Submission2.5.3 Application Submission PeriodNot anticipated
20
Application Submission2.5.4 Applicant SupportNot anticipatedSome open questions remain, such as a selection process if there are more qualified applicants than funds,agreeing on a definition for Global South/underserved/underrepresented (potentially reference work ICANN org is doing), metrics for reviewing the program.
21
Application Submission2.5.5 Terms & ConditionsNot anticipatedThis section is dependent on agreement to a limited appeals mechanism.
22
Application Processing2.6.1 Application QueuingNot anticipatedThe WG may make recommendations on prioritizing the processing of applications from previous rounds.
23
Application Processing2.4 Application Change RequestsPossiblePossibly on new processes/procedures discussed if they gain traction.
24
Application Evaluation/Criteria2.7.1 Reserved NamesNot anticipated
25
Application Evaluation/Criteria2.7.1.1 IGO/INGO ProtectionsNot anticipated
26
Application Evaluation/Criteria2.7.1.2 Geographic NamesNot anticipated
27
Application Evaluation/Criteria2.7.2 Registrant ProtectionsNot anticipated
28
Application Evaluation/Criteria2.7.3 Closed GenericsPossibleIf we get a consensus or a good amount of support for something other than 2012 rules.
29
Application Evaluation/Criteria2.7.4 String SimilarityPossibleThere was some discussion that the recommendations could extend beyond singular/plural.
30
Application Evaluation/Criteria2.7.5 IDNsNot anticipatedSome questions remain about the interplay between SubPro's work and future work that is looking at IDNs more holistically.
31
Application Evaluation/Criteria2.7.6 Security and StabilityNot anticipated
32
Application Evaluation/Criteria2.7.7 Applicant Reviews: Technical/Operational, Financial and Registry ServicesNot anticipatedThe WG is awaiting data on EBERO/SLAM data, which could impact the evaluation criteria (as well as the RA and pre-delegation testing).
33
Application Evaluation/Criteria2.3 Role of Application CommentNot anticipated
34
Application Evaluation/Criteria2.7.8 Name CollisionsNot anticipated
35
Dispute Proceedings2.8.1 ObjectionsUndeterminedThere are a number of unresolved elements, but unclear if the outcomes will be something the community has not had the opportunity to comment against.
36
Dispute Proceedings2.8.2 Accountability MechanismsLikelyAdditional detail being formulated here, much of it not in earlier reports.
37
String Contention Resolution2.9.1 Community ApplicationsNot anticipatedThe WG is currently considering whether the implementation guidance provides the needed additional clarity. If something substantially different is agreed upon, that could require additional community review.
38
String Contention Resolution2.1 Auctions: Mechanisms of Last ResortPossibleThe WG is considering changes to the precise type of auction.
39
String Contention Resolution2.2 Private Resolution of Contention Sets (including Private Auctions)UndeterminedThis may be dependent on the outcomes of 2.2 above.
40
Contracting2.10.1 Base Registry AgreementNot anticipated
41
Contracting2.10.2 Registrar Non-Discrimination / Registry/Registrar StandardizationNot anticipated
42
Contracting2.5 Registrar Support for New gTLDsNot anticipated
43
Pre-Delegation2.11.1 Registry System TestingTBD
44
Post-Delegation2.12.1 TLD RolloutTBD
45
Post-Delegation2.12.2 Second-Level Rights Protection MechanismsN/AN/A
46
Post-Delegation2.12.3 Contractual ComplianceTBD
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100