Page History

...

The Policy Development Process Manual makes clear that “Approved GNSO Council policies that have been adopted by the ICANN Board and have been implemented by ICANN Staff may only be amended by the initiation of a new PDP on the issue.” It can therefore be concluded that where there is a conflict between an existing consensus policy and subsequent policy recommendation(s) on the same subject matter, the newer policy recommendation prevails. While the EPDP was scoped differently and under different circumstances than the Thick Whois PDP, it is undeniable that the two policy development processes overlapped in covering the same issue of transfer of Registration Data from registrar to registry, and therefore, the IRT should implement Recommendation #7 as written and intended.

Motion -  Appointment of a GNSO Non-Registry Liaison to the Customer Standing Committee

Submitted by: Carlton Samuels

Seconded by:  

Whereas,

1. The existing GNSO Non-Registry Liaison to the Customer Standing Committee James Gannon was nominated to serve a two-year term beginning 1 October 2019.
2. The Liaison stepped down from the role as of ICANN69 due to his appointment to the PTI Board.
3. On 9 November 2020, the GNSO launched an Expression of Interest (EOI) process via email to the GNSO Stakeholder Groups and Constituencies to solicit volunteers to serve in the Liaison role for the remainder of the current term.
4. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to appoint.
5. The SSC reviewed the one application received, taking into account the criteria outlined in the EOI announcement.
6. The SSC submitted its full consensus recommendation to the GNSO Council on 11 January 2021, by way of submission of the relevant motion.
7. The GNSO Council considered the recommendations of the SSC.

Resolved,

1. The GNSO appoints Milton Mueller to serve as GNSO Non-Registry Liaison to the Customer Standing Committee.
2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the Customer Standing Committee.
3. The GNSO Council instructs the GNSO Secretariat to inform the appointed candidate that he has been selected.

Motion -  Nomination of a Mentor for the ICANN Fellowship Program

Submitted by: Carlton Samuels

Seconded by:  

Whereas,

1. The SO/AC Chairs have agreed to the formation of a Community Representatives Group to select nominees for the Bylaws-mandated Independent Review Process (IRP) Standing Panel.
2. On 18 November 2020, ICANN, in consultation with the SO/ACs, opened an Expression of Interest process to solicit volunteers for the Community Representatives Group (https://www.icann.org/news/announcement-2020-11-18-en) with the understanding that Expressions of Interest would be reviewed by the specific SO/ACwhose endorsement was requested by the applicant.
3. The GNSO SG/C Chairs and GNSO Council Leadership agreed that the SSC should be deployed to select the GNSO’s Representative(s) to the Community Representatives Group.
4. The SG/C Chairs provided written guidance for the SSC to support the selection process.
5. The SSC reviewed the application received, taking into account the guidance provided by the SG/C Chairs.
6. The SSC submitted its full consensus recommendation to the GNSO Council on 11 January 2021, by way of submission of the relevant motion.
7. The GNSO Council considered the recommendations of the SSC.

Resolved,

1. The GNSO appoints [name] to serve as a GNSO Representative to the Community Representatives Group that will nominate the Independent Review Process (IRP) Standing Panel.
2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to the SO/AC Chairs and ICANN.
3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate of the Council’s decision.

Motion -  Appointment of a GNSO Representative to the Community Representatives Group that will nominate the Independent Review Process (IRP) Standing Panel.

Submitted by: Carlton Samuels

Seconded by: 

Whereas,

1. On 16 November 2020, the ICANN Fellowship Program invited ICANN's Supporting Organizations and Advisory Committees to nominate one individual each (total of 7) to serve in the capacity of Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN72 (see https://www.icann.org/news/announcement-2020-11-16-en)
2. On 3 December 2020, the GNSO launched an Expression of Interest (EOI) process to solicit volunteers for the GNSO-nominated mentor position (seehttps://gnso.icann.org/en/announcements/announcement-03dec20-en.htm).
3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to nominate.
4. The SSC reviewed the applications received, taking into account the criteria outlined in the EOI announcement.
5. The SSC submitted its full consensus recommendation to the GNSO Council on 11 January 2021, by way of submission of the relevant motion.
6. The GNSO Council considered the recommendations of the SSC.

Resolved,

1. The GNSO nominates [name] to serve as a ICANN Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN72.
2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program.
3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate that he or she has been selected.
4. The GNSO Council requests the GNSO Secretariat to send a response to those applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise.