Following a letter sent by the GAC to the ICANN Board (the NGPC in fact) on 9 September 2013 where no consensus was found on additional specific safeguards (protection of wine GIs), the ICANN Board had to “decide” about what to do regarding .WINE and .VIN new gTLD application: would they allow to proceed or not?
- The ICANN board would have allowed both application to proceed but this would could have caused diplomatic…problems between the EU and ICANN and serious anger from part of the wine Community;
- The ICANN board would have ended all applications. In this case it would have meant that there would not have been any .WINE and .VIN domain names before the second round of applications.
- The ICANN board would have delayed again to give one last chance to applicants. It is precisely what happened: the ICANN Board delayed again to the next ICANN meeting in Buenos Aires in November 2013.
“The ICANN Board New gTLD Program Committee (NGPC) met on 28 September 2013 and, among other things, adopted a scorecard of remaining advice from the Beijing and Durban GACCommuniqués. The scorecard, available here, reflects the following:
.wine and .vin: On 9 September 2013, the NGPC received a letter from Heather Dryden toSteve Crocker re: .wine and .vin. The letter noted that there is no GAC consensus advice onadditional specific safeguards, and that the GAC or its members may communicate furtherdetails to the Board as to the nature of the differences in views.
As such, the NGPC stands ready to hear from GAC members as to the nature of the differences in views expressed in the advice while the NGPC is analyzing the community input received on this advice.
The NGPC directs staff to analyze the GAC advice and other community input received on thisissue, and prepare an analysis and recommendation for decision at the NGPC meeting in Buenos Aires.