[Gnso-review-wg] Actions/Discussion Notes for GNSO Review WG Meeting on 28 September

[Julie Hedlund]

Dear GNSO Review Working Group members,

 

Please see below the action items and discussion notes captured by staff from the meeting on 28 September.  These high-level notes are designed to help WG members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at: https://community.icann.org/display/GRWG/2017. 

 

Best regards,

Julie

 

Julie Hedlund, Policy Director

 

 

Action Items/Discussion Notes 28 September

 

Action Items: 

 
OEC/GNSO Council Report: Staff to provide a draft for review at the meeting on 12 October.
Recommendation 6: Combine with charters for recommendations 33 and 36 that also are pending the recommendations from the Work Stream 2 Subgroup on Diversity.  Determine if any aspects of the recommendations can be extracted and marked as completed.
Recommendations 26, 27, 28, & 29: 
Rec 26: Staff (including ICANN Legal) to provide more input on what may be required for disclosure to fulfill the requirement in recommendation 26.
Rec 27: Staff to investigate the feasibility of implementing this recommendation, and report back to the WG.
Rec 28: Staff to review key clauses in section 6.1.2 of the GNSO Operating Procedures that may be necessary to understand changes necessary to implement this recommendation, and provide a draft markup to clarify what changes may be necessary
Rec 29: Staff to provide a proposal on addition of a field in the SOI that lists past and current leadership positions, as well as a draft definition of "leadership position" - both to be reviewed by the WG.
Meeting Schedule: The WG to meet on 12 and 19 October (with 12 October changed to 1400 UTC to avoid a conflict with the GNSO Council), and meeting on 26 October to be cancelled.
 

Notes:

 

1. Update on Consensus Call on Charter for Recommendation 31 – Ended COB 25 September:

 

-- No objections or comments submitted. The Charter is approved by consensus.

 

2. Status of Update to OEC/GNSO Council:

 

-- Presentation to the OEC and the GNSO Council scheduled to take place at ICANN 60.

-- Staff will provide a draft report to the WG within the next week.

 

3. Recommendations 26-29:

 

Recommendation 26:

-- If the questions on this recommendation concern whether or not to include SOIs for exec-com members, need to update this information on a yearly basis to match yearly exec-com elections in GNSO constituencies.

-- Process to review policies under consideration is that they are discussed on GNSO PDP WGs, discussions take place within GNSO SGs/Cs, and the GNSO Council accepts WG recommendations - often, many of the required SOIs are already covered, but concern raised on formalizing a requirement for all the SOIs being updated.

-- Not clear what is meant by a participant's interest or position being required to be disclosed - doesn't this take place anyway during WG deliberations?  If a comment is being submitted on behalf of a client, this might need to be clarified.  Language of the recommendation needs to be clearer on what is required for disclosure.

 

>From the Chat Room:

Marika Konings: Maybe the question is as well what can be disclosed?  Can it be stated that someone is participating on behalf of a client without stating who the client is or what their exact brief was?

 

Recommendation 27:

-- Questions to the GNSO Review WG include where a centralized list of SGs/Cs membership needs to be maintained, and what SOIs are required to be associated with this membership list

Is this recommendation creating additional requirements for SOIs to be posted, or is it only requiring that posted SOIs be linked to the centralized GNSO membership lists also being recommended?

 

Recommendation 28:

-- No comments from WG members on this recommendation

 

Recommendation 29:

>From the Chat Room:

Marika Konings: 

-- Would it be more valuable to list actual leadership positions (with years held) as an accumulation may not be that helpful?

-- Could an interim solution be to add a field asking people to list previous leadership positions held? and what is considered a leadership position, that may also require some definition?

-- Suggestion to add a field that lists current and previous leadership positions, noting that a definition of leadership position needs to be agreed upon

 

4. Meeting Schedule:

 

-- May be of value to hold a meeting on 19 October as well, to review any documents/reports that need to be submitted to the GNSO Council by the 10-day deadline to submit documents ahead of the 1 November public Council meeting.

-- WG agreement: WG to meet on 12 and 19 October (with 12 October changed to 1400 UTC to avoid a conflict with the GNSO Council), and meeting on 26 October to be cancelled.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170928/24d3a764/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4630 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170928/24d3a764/smime-0001.p7s>