The ICANN Board New gTLD Program Committee (NGPC) wishes to share with the ICANN community its progress in consideration of the GAC advice and what steps are still to be taken. The NGPC met on 8 May to consider a Plan for responding to the Governmental Advisory Committee’s advice on New gTLDs, transmitted to the Board through its 11 April Beijing Communiqué. The Plan is in two parts: Part 1 shown below consists of actions for soliciting input from Applicants and from the Community.
|Item||Resp.||Start Date||Compl. Date||Status|
|1||Publish GAC Communiqué and notify applicants of 21-day GAC Advice Response Period||Staff||18 April||Complete|
|2||Applicants 21-day response period to GAC Advice||Applicants||19 April||10 May||In progress|
|3||Publish GAC Communiqué to solicit input on how the New gTLD Board Committee should address GAC advice regarding safeguards applicable to broad categories of New gTLD strings||Staff||23 April||Complete|
|4||Public comment period on how Board should address GAC Advice re: Safeguards||Public||23 April||Comment:
|5||Collect and summarize applicant responses to GAC Advice||Staff||11 May||31 May||Not Started|
|6||Summarize and analyze public comments on how Board should address GAC Advice re: Safeguards||Staff||5 June||12 June||Not Started|
|7||Review and consider Applicant responses to GAC Advice and Public Comments on how Board should respond to GAC Advice re: Safeguards||New gTLD Program Committee||13 June||20 June||Not Started|
Part 2 consists of actions for responding to each advice given by the GAC. In so doing, the NGPC is developing a GAC scorecard similar to the one used during the GAC and the Board meetings in Brussels on 28 February and 1 March 2011.
Each GAC scorecard item will be noted with a “1A”, “1B”, or “2″:
Part 2 of the Plan is not yet finalized and, with respect to some of the advice, cannot be finalized until after the review of the Public Comments due to be completed on 20 June.
The NGPC will next meet in Amsterdam on 18 May and will provide a further update following that meeting.
This ICANN announcement was sourced from: