Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

1. Motion on the Adoption of the IRTP Part B Recommendation #3 (Issue Report on ‘Thick’ WHOIS)

Made by:Tim Ruiz

Seconded by: Stéphane van Gelder

...

a. Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report
http://www.icann.org/announcements/hijacking-report-12jul05.pdf); see also (http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm)

b. Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact (AC). The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar;

...

RESOLVED, the GNSO Council requests an Issue Report on the requirement of ‘thick’ WHOIS for all incumbent gTLDs. Such an Issue Report and possible subsequent Policy Development Process should not only consider a possible requirement of 'thick' WHOIS or all incumbent gTLDs in the context of IRTP, but should also consider any other positive and/or negative effects that are likely to occur outside of IRTP that would need to be taken into account when deciding whether a requirement of 'thick' WHOIS for all incumbent gTLDs would be desirable or not. (IRTP Part B Recommendation #3)

2. Motion to extend the mandate of the Joint ccNSO/GNSO IDN Working Group (JIG)

Made by: Rafik Dammak

Seconded by: Ching Chiao

Whereas

The Joint ccNSO/GNSO IDN Working Group (JIG) was created by mutual charters of the ccNSO (http://ccnso.icann.org/workinggroups/jiwg-charter.pdf) and the GNSO (http://gnso.icann.org/resolutions/#200907); and

Both the IDN ccTLD Fast Track Implementation Plan and the new gTLD process have been approved by the Board of Directors, bringing into effect the JIG charter condition: Upon adoption of either the IDN ccTLD Fast Track Implementation Plan or the new gTLD process by the ICANN Board of Directors, the WG will be closed, unless both the ccNSO and GNSO Council extend the duration of the JIG WG.; and

The JIG identified 3 issues of common interest: 1. Single Character IDN TLDs; 2. IDN Variant TLDs; and, 3. Universal Acceptance of IDN TLDs;  and

The JIG has delivered a first report  on Item 1  “Implementation of Single Character IDN TLD” to the ccNSO council and the GNSO council on 30 March 2011; and

The GNSO Council and the ccNSO Council approved the report on April 7, 2011 and May 10, 2011 respectively; and

The final report  on the first item of interest was delivered to the ICANN Board on May 11, 2011; and

Two issues of common interest remain from the JIG charter; and

The JIG WG has discussed and proposed the following target timeline for completion of the remaining items of common interest:
       • 2011 Jul/Aug: Stocktaking & Development Initial Report for #3 (Public comments Sep 2011)
       • 2011 Sep/Oct: Completion of Initial Report for #2 (Public comments Nov 2011)
       • 2011 Nov/Dec: Completion of Draft Final Report for #2 (Public comments Feb/Mar 2012)
       • 2012 Jan/Feb: Completion of Draft Final Report for #3 (Public comments Feb/Mar 2012)
       • 2012 Mar: Finalization of Final Report for #2
       • 2012 Apr: Finalization of Final Report for #3
       • 2012 May-Oct: Implementation Follow up

Resolved

The JIG Working Group is extended through 2012 to complete work items Two (2.  IDN Variant TLDs) and Three (3. Universal Acceptance of IDN TLDs ) from the original charter.

3. Motion on the Adoption of the PEDNR Final Report and Recommendations

 

Made by: Tim Ruiz

 

Seconded by: Stéphane van Gelder

...

The GNSO Council shall convene a PEDNR Implementation Review Team to assist ICANN Staff in developing the implementation details for the new policy should it be approved by the ICANN Board. The Implementation Review Team will be tasked with evaluating the proposed implementation of the policy recommendations as approved by the Board and is expected to work with ICANN Staff to ensure that the resultant implementation meets the letter and intent of the approved policy. If the PEDNR Implementation Review Team identifies any potential modifications to the policy or new PEDNR policy recommendations, the PEDNR Implementation Review Team shall refer these to the GNSO Council for its consideration and follow-up, as appropriate. Following adoption by the ICANN Board of the recommendations, the GNSO Secretariat is authorized to issue a call for volunteers for a PEDNR Implementation Review Team to the members of the PEDNR Working Group.

4. Motion regarding Public Comments on the Policy Development Process Work Team Final Report

Made by:  Jeff Neuman

Seconded by: Carlos Aguirre

...

RESOLVED, the GNSO Council directs the PDP-WT to review the Summary and Analysis document as well as the comments and make any changes to the PDP-WT Final Report as deemed appropriate. The PDP-WT should submit the updated version of the Final Report to the GNSO Council as soon as possible, preferably in time for consideration at its next meeting on 8 September. 

5. Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations

(For discussion only)

Whereas the Registration Abuse Policies (RAP) Working Group submitted its report to the GNSO Council on 29 May 2010 (see http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf);

...

RESOLVED, in response to Gripe Sites; Deceptive and/or Offensive Domain Names recommendation #1, the GNSO Council acknowledges receipt of this recommendation, and agrees with the RAPWG that no further action is called for at this time.