Pam,

 

Regarding the liaison role, I don’t think any of us disagree with your and Maxim’s thought – I certainly don’t.  But the more appropriate place for that requirement is in the Operating Procedures or Description of Council Roles.  The tools we’re building here are simply practical guidance to support the requirements represented there. 

 

Thanks,

Darcy

 

From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org> on behalf of Steve Chan <steve.chan@icann.org>
Date: Wednesday, October 16, 2019 at 4:29 PM
To: Pam Little <pam.little@alibaba-inc.com>, "gnso-pdp3dot0-dt@icann.org" <gnso-pdp3dot0-dt@icann.org>, GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org>
Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements #5 & #13 by Monday 21 October

 

Thanks Pam, typo fixed!

 

Best,

Steve

 

From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org> on behalf of Pam Little <pam.little@alibaba-inc.com>
Reply-To: Pam Little <pam.little@alibaba-inc.com>
Date: Wednesday, October 16, 2019 at 3:59 PM
To: "gnso-pdp3dot0-dt@icann.org" <gnso-pdp3dot0-dt@icann.org>, GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org>
Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements #5 & #13 by Monday 21 October

 

Hi Steve & Team

 

Apologies again for missing our last call but I have now had a chance to listen to the recordings of the meeting. 

 

I note there was quite a bit of discussion around the following in the final version of the GNSO Council liaison supplemental guidance for Improvement 5:

 

The liaison is expected to fulfil his/her role in a neutral manner. Should the liaison wish to intervene / participate in WG deliberations in his/her personal capacity, the liaison is expected to make it explicitly clear when he/she is speaking in liaison capacity and when speaking in personal capacity.

~

- The liaison's primary purpose is to serve as the liaison. The liaison can "take off their liaison hat," which must be done explicitly, but doing so is strongly discouraged. Potential liaisons and the Council should take this into account prior to appointing a Councilor to the position. 
- If the liaison is constantly "taking off his/her hat," this is likely to negatively affect the liaison's ability to serve in the role in the neutral manner and the Council and liaison way may want to consider whether another individual is better able to serve in this role. 
- This particular Job Duty is overarching and affects all other Job Duties.

 

In addition to the typo, I tend to agree with concern and comments from Maxim during the call.

 

I believe there is an inherent conflict between the two different roles: a member of a WG and a GNSO Council Liaison to the WG. To me, a WG member is there to represent himself or herself in an open model or represent his or her SG or C in a representative model (and advocating his/her interests or his or her group's interests as appropriate) while the Liaison is must be a neutral role to have credibility and perform that role well. 

 

My view is that these two roles should be mutually exclusive and, at the outset, the individual needs to choose either be a WG member or be the Council Liaison, not both. 

 

Kind regards,

 

Pam

------------------------------------------------------------------

Sender:Steve Chan <steve.chan@icann.org>

Sent At:2019 Oct. 16 (Wed.) 06:22

Recipient:gnso-pdp3dot0-dt@icann.org <gnso-pdp3dot0-dt@icann.org>

Subject:[GNSO-PDP3Dot0-DT] Final Call: Review Improvements #5 & #13 by Monday 21 October

 

Dear All,  

 

By COB Monday, 21 October, please provide your final input for the Package 3 documents below.

  

Documents for Improvement #5 (Active role for and clear description of Council liaison to PDP WGs):  

    • Including GNSO Council liaisons in WG leadership team activities 
    • Ensuring that there is an on-boarding/handover process for new GNSO Council liaisons

               

Document for Improvement #13 (Review of Working Group Leadership):

 

In absence of concerns/objections, staff will coordinate with the Small Team leads to finalize the Package 3 documents by 23 October, and Improvements #5 and #13 documents will be considered as completed according to the timeline/implementation plan.

 

Thank you for your review. 

 

Best,

Steve

 

 

Steven Chan


Policy Director, GNSO Support

 

Internet Corporation for Assigned Names and Numbers (ICANN) 

12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536


                                                                  

Email: steve.chan@icann.org

Skype: steve.chan55

Mobile: +1.310.339.4410

 

Find out more about the GNSO by visiting: https://learn.icann.org/

Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO

Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar 

See All SO and AC events on the ICANN Global calendar [features.icann.org]

 

 

_______________________________________________ GNSO-PDP3Dot0-DT mailing list GNSO-PDP3Dot0-DT@icann.org https://mm.icann.org/mailman/listinfo/gnso-pdp3dot0-dt _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.