AT-LARGE GATEWAY
At-Large Website
ALAC
RALOs
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Governance
At-Large Reports
Policy Comments & Advice
Working Groups
ICANN Meetings
At-Large Summit (ATLAS III)
At-Large Review Implementation Plan Development
ALAC and RALO Elections, Selections, and Appointments
At-Large Priority Activities - 2021
changes.mady.by.user Matt Ashtiani
保存しました 12 24, 2013
...
The Generic Names Supporting Organization (GNSO) unanimously approved at its meeting on 20 November 2013 the consensus recommendations of the IGO-INGO PDP Working Group, which are now pending Board action. The GNSO Council recommends that a series of identifier protections at the top and second level be granted to International Governmental Organizations (IGO), the Red Cross Red Crescent movement (RCRC), the International Olympic Committee (IOC), and other International Non-Governmental Organizations (INGO). The detailed recommendations can be found in the Final Report [PDF, 645 KB], with a summary provided within the GNSO Council motion. In short, the recommendations cover the following dimensions:
For a detailed background and history of the issue on whether to protect certain IGO and INGO identifiers (including the RCRC and IOC) prior to the initiation of this PDP, please see the Final GNSO Issue Report [PDF, 675 KB] on the Protection of International Organization Names in New gTLDs. The Issue Report was initiated as a result of a recommendation by the GNSO Drafting Team that was formed in October 2011 to provide recommendations to the GNSO Council in response to ICANN Board and Government Advisory Committee (GAC) requests concerning protection of IOC and RCRC names in new gTLDs. After community review, the scope of the Final GNSO Issue Report included a recommendation that the GNSO evaluate whether the names of IGOs and INGOs at both the top level and second levels should be protected in all gTLDs.
At its meeting in October 2012, the GNSO Council considered the Final GNSO Issue Report on the Protection of International Organization Names in New gTLDs, and approved a motion to initiate a Policy Development Process (PDP) for the protection of certain international organization names and acronyms in all gTLDs. The Working Group (WG) was formed on 31 October 2012 and the WG Charter approved by the GNSO Council on 15 November 2012. The GNSO Council also decided to subsume the issue regarding protection for RCRC and IOC identifiers into the new PDP WG discussions.
As part of its deliberations, the PDP WG was required under the WG Charter to consider the following questions:
Whether there is a need for special protections at the top and second level in all existing and new gTLDs for the names and acronyms of the following types of international organizations: International Governmental Organizations (IGOs) protected by international law and multiple domestic statutes, International Non-Governmental Organizations (INGOs) receiving protections under treaties and statutes under multiple jurisdictions, specifically including the Red Cross/Red Crescent Movement (RCRC), and the International Olympic Committee (IOC). In deliberating this issue, the WG should consider the following elements:
If there is a need for special protections at the top and second level in all existing and new gTLDs for certain international organization names and acronyms, the PDP WG is expected to develop policy recommendations for such protections. Specifically, the PDP WG should:
On 14 June 2013 the IGO-INGO PDP Working Group published its Initial Report [PDF, 609 KB] for public comment. On 20 September 2013 the Working Group published its draft Final Report [PDF, 676 KB] for public comment, incorporating feedback received in response to its Initial Report. On 10 November 2013 the Working Group published its Final Report [PDF, 644 KB] and sent it to the GNSO Council, incorporating feedback received in response to its draft Final Report. The Working Group's Final Report includes supplemental documentation in the form of Minority Statements from various Working Group members and their respective constituencies, including IGOs and INGOs who may be affected by the recommendations under consideration.
N/A
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
The final draft version to be voted upon by the ALAC will be placed here before the vote is to beginALAC has made a number of statements on the protection of IGO and INGO names, and has participated actively in all GNSO activities related to this topic. Our views on specific outcomes of this PDP are reflected in the Final Report.
Given the wide range of views expressed in this report, and noting that nothing presented has received the unanimous support of the PDP Working Group, the ALAC would like to take this opportunity to comment on the nature of the Recommendations as well as identify the principles that have guided its positions.
The Draft Final Report includes a wide variety of Recommendations some reflecting a WG Consensus (as defined by the GNSO Working Group Guidelines) some with an even weaker level of support. Not a single one was agreed to by all WG members (Full Consensus), a level of support that is more typical of most GNSO PDPs. For many of the recommendations originally considered by the WG and strongly supported by some, the overall participant views were Divergent. The collection of Recommendations with Consensus level or Strong support, taken as a whole, does not form a cohesive and consistent set of policies. Although each individual Recommendation received sufficient support, the net result is a set of Recommendations that may be incomplete and perhaps even conflicting.0F[1]
The ALAC is particularly concerned that granting blocking-level protections may prohibit other reasonable uses of the same strings, and is not satisfied that the exception procedure options outlined in the report could meet the targets that the ALAC believes are mandatory.
This being the case, it may be important to consider the principles that guided the ALAC in our participation in the activities that led to this report, and that the ALAC believes should guide ICANN in considering any special protections.
[1] As an example, there may be cases where a strong protection is not recommended, but the recommendations may be silent on weaker forms of protection.
[2] Although not a gTLD registration, cern.ca is a good example. The Centre d'exposition de Rouyn-Noranda in northern Quebec has no connection or even a vague relationship with the Conseil Européen pour la Recherche Nucléaire, but they do happen to share an acronym. In the gTLD space, Olympic.diy is a prime example of a new registration that might not be allowed under the proposed rules even though the TLD (diy = Do-it-yourself) is a logical registration for Olympic Paints.
The ALAC has commented on the Protection of IGO and INGO Identifiers in all gTLDs PDP Recommendations in its Statement Ref. AL-ALAC-ST-1113-01-02-EN.
The ALAC raised a number of issues which were in fact changed in the Final Report. The ALAC's final Statement on this Report is therefore contained in the ALAC's minority Statement included in the Report itself.
It should be noted that this minority Statement also serves as formal Advice from the ALAC to the Board.