EN
Down Arrow
User Icon
Hamburger Icon
SEARCH
X

بحث موقع GAC

بحث

مشورة GAC

تقدم اللجنة الاستشارية الحكومية GAC المشورة الى مجلس إدارة ICANN حول قضايا السياسات التي قد تتداخل مع سياسات ICANN ومختلف القوانين والاتفاقيات الدولية وأهداف المصلحة العامة. ويتم تقديم مشورة اللجنة الاستشارية الحكومية GAC الى مجلس إدارة ICANN من خلال إما البيان الاختتامي للجنة او عبر المراسلات الرسمية.

2013-04-11-IGO

مشورة GAC

الرقم المرجعي:

2013-04-11-IGO

First Delivered via :

N/A

الإجماع:

تحقق الإجماع

2013-04-11-IGO

Communication

a. Protections for Intergovernmental Organisations

The GAC stresses that the IGOs perform an important global public mission with public funds, they are the creations of government under international law, and their names and acronyms warrant special protection in an expanded DNS. Such protection, which the GAC has previously advised, should be a priority.

This recognizes that IGOs are in an objectively different category to other rights holders, warranting special protection by ICANN in the DNS, while also preserving sufficient flexibility for workable implementation.

The GAC is mindful of outstanding implementation issues and commits to actively working with IGOs, the Board, and ICANN Staff to find a workable and timely way forward.

Pending the resolution of these implementation issues, the GAC reiterates its advice to the ICANN Board that:

i. appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch.

GAC Acknowledgement of Register Entry

GAC: 2 May 2013

Board: 9 May 2013

Next Steps/Required Action

Current Status/Communications Log

Board Response (6 June 2013):

2. Protections for Intergovernmental Organizations

In section IV.1.g of the GAC Beijing Communique, the GAC reiterated its advice that 'appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch.' The GAC also noted that it was 'mindful of outstanding implementation issues and commits to actively working with IGOs, the Board, and ICANN Staff to find a workable and timely way forward.' The NGPC appreciates the GAC's willingness to collaborate and address the outstanding implementation issues. So that we may move forward, the NGPC formally requests that the GAC and a small number of NGPC members and ICANN staff begin a dialogue on these issues. The formal request is being sent under a separate cover.

Request for IGO Protections Dialogue.pdf (6 June 2013):

'In the Beijing GAC Communiqué, the GAC reiterated previous advice that 'appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch.' In response to a number of issues raised by the Board, the GAC noted that it is “mindful of outstanding implementation issues” and that it is committed to 'actively working with IGOs, the Board, and ICANN Staff to find a workable and timely way forward.'

The Board thanks the GAC for its willingness to engage on this issue. Toward this end, we would like to propose that the GAC and a small number of Board New gTLD Program Committee members and ICANN staff begin a dialogue on the issues raised by the Board. If the GAC is agreeable to this proposal, ICANN staff would be happy to coordinate logistical details with the GAC Secretariat.

Thank you again for providing advice and input to the Board. We look forward to your response.'

Board Action (Accept/Disagree)

Dialogue to continue:

NGPC Consideration of GAC Beijing Advice 07-03-13[2].docx

  • The New gTLD Registry Agreement will require operators to provide appropriate preventative initial protection for the IGO identifiers. These protections will remain in place while the GAC, NGPC, ICANN Staff and community continue to actively work through outstanding implementation issues.
  • If the NGPC and GAC do not reach an agreement on outstanding implementation issues for protecting IGO names and acronyms by the first meeting of the NGPC following the ICANN 47 meeting in Durban, and subject to any matters that arise during the discussions, registry operators will be required to protect only the IGO names (and not the acronyms) identified on the GAC's IGO List.
  • See http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-02july13-en.htm.

IGO Names Protection .pdf

Previous Advice and Responses:

2012-10-17-IGO (Toronto Communique)

2013-07-18-IGO Acronyms (Durban Communique)

Further Advice and Responses:

2013-11-20-IGO (Buenos Aires Communique)