Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Team:  

Jordyn Buchanan, Kaili Kan, Laureen Kapin, David Taylor, Drew Bagley, Waudo Siganga, Jamie Hedlund, Calvin Browne, Megan Richards, Gaongalelwe Mosweu

Observers:  Zack Coleman

Staff:  Brenda Brewer, Jean-Baptiste Deroulez, Pamela Smith, Margie Milam, Eleeza Agopian, Brian Aitchison, Antonietta Mangiacotti

Apologies:  Jonathan Zuck, Dejan Djukic, Fabro Steibel

Agenda:  

- Welcome, roll-call, SoI - Reach consensus on recommendations for:
     a. Impact of Safeguards – Laureen
     b. Benefits vs. Confusion to End Users – Megan
     c. Registry Policies – Megan

Time permitting, also reach consensus on recommendations:
     d. Preventing Delegations that would be confusing or harmful – Megan
     e. Allowing specific communities to be served by a relevant TLD – Megan
     f. Effectiveness of the Dispute Resolution Process in cases of Formal String Objection – Megan
     g. Simplifying the process – Megan
- A.O.B.

Documents:

Recordings:

Chat Transcript:  EN

Transcript:  EN

Action Items:

  •  Jonathan to provide guidance on the priorities matrix - low, med, high, prerequisite, non-prerequisite

Notes:

VIII. IMPACT OF SAFEGUARDS (Continued) 

Sensitive and Regulated Strings (p. 9) - 

Rec. 1 (p. 9) - High priority, not a prerequisite for subsequent rounds - Consensus approved

Rec. 2 (p. 10) -  add language about directing this to ICANN Board for resolution; add "respectively" after "sensitive health and financial information"  - Consensus approved

Safeguards for Highly-Regulated Strings (p. 10-12)

All high priority, not a prerequisite

Rec. 1 - Consensus approved

Rec. 2 - Consensus approved

Rec. 3 - Consensus approved

Rec. 4 - Consensus approved

Rec. 5 - Consensus approved

Rec. 6 - Consensus approved

Special Safeguards (p. 13ff)

Low priority; not a prerequisite

Rec. - Consensus approved 

Restricted Registration Policies (p. 14ff)

High priority, not a prerequisite for Rec. 1&2

Rec. 1 - Consensus approved

Rec. 2 - Consensus approved; look at subset of TLDs for which registration restrictions could possibly be appropriate

Rec. 3 - Consensus approved

Rec. 4 - Consensus approved (K.Kan conditional)

CONSUMER CHOICE POINT 12. BENEFITS vs. CONFUSION TO END-USERS

Med priority, prerequisite to next round(s)

Rec. -