Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For other times: http://tinyurl.com/hduyua6[tinyurl.com]  

 

Proposed Agenda:  

1. Welcome / Roll Call

2. Review of latest version of final status update and recommendations

3. Confirm next steps

 

MP3 recording

Transcript

Adobe Connect Chat

Notes 03 October 2016 meetingAttendance

 Apologies received: Paul McGrady, Ana Neves, Phil Corwin

Attendees:  

Staff:

 

 

 

Documents were circulated prior to the meeting for review. Developed by staff in consultation with the CG leadership.

Consider setting a deadline for input on the three documents that were circulated.

GNSO Liaison to the GAC:

Proposed CG response / recommendation is based on the previous discussion and input provided.

Consider shortening the first recommendation to bring it more in line with the other recommendations in the document. Also consider enumerating the recommendations. Consider adding 'regular' to timely updates to ensure that GNSO policy activities stay at the forefront.

Consider reorganising the structure before it is submitted to the GNSO and GAC so that the individual views are removed and focus is on the actual recommendations. For the background on the recommendations, the GNSO and GAC can be referred to earlier versions of the document and/or CG meetings.

Update 2nd recommendation to include 'and' instead of but.

Change outgoing to former (third skill description)

Update - Liaison to be reviewed on an annual basis (in the form of a conversation between the liaison and the Council) / confirmed on a yearly basis.

Clarify last recommendation that not being considered a non-voting member does not mean the liaison is considered a voting member. Check how other liaisons are referred to. Liaison should be able to participate and attend GNSO Council meetings, but not necessarily considered as a member of the Council.

QLM:

CG to review proposed simplification / modifications proposed

CG to consider whether additional PDPs are needed to 'test' the proposed simplified process before it is recommended that it is included in the PDP manual and how that aligns with the work plan of the CG. Note that at this stage no new PDPs are imminent (as far as staff is aware).

GNSO PDP

Table provides overview of all stages of the PDP, including recommendations already implemented, recommendations being considered and some new ideas for CG review and discussion.

Next steps:

Deadline for review of the GNSO Liaison to the GAC document: Monday 25 January, following which proposed recommendations are shared with the GNSO and GAC for review.  

Deadline for feedback on QLM proposed modifications and questions (see above): 1 February

Deadline for feedback on PDP engagement opportunities: 8 February

Next meeting to be scheduled for Tuesday 16 February at 14.00 UTC.

 

 

Carlos Raul Gutierrez, Mason Cole, Jonathan Robinson, Mark Carvell, Jorge Cancio, Manal Ismail

Staff:Marika Konings, Olof Nordling, Glen de St Gery, Fabien Betremieux, Julia Charvolen, Nathalie Peregrine

Documents:

Draft Final Status Report and Recommendations - ML


Notes 03 October 2016 meeting

Action item #1: CG members to review latest version of Final Status Report by Friday 7 October 23:59 UTC at the latest.

 

1. Welcome / Roll Call

Please state names for transcription purposes

In Helsinki, the leadership team committed to review the survey results, review next steps in light of outstanding items per the charter and develop an approach with the aim to complete CG work by ICANN57

Draft Final Status Report & Recommendations developed as a result and shared with CG for review and input

A number of comments were received and an updated version was developed as a result

Objective is to deliver Final Status Report & Recommendations to the GNSO & GAC in time for ICANN57 to allow for review and consideration during the meeting.

Aim to complete review of final status report on this call or shortly thereafter so that the document can be finalised for submission.

 

2. Review of latest version of final status update and recommendations

Take the document as read - invite CG members to indicate any further comments / questions

Set deadline for final comments / edits following which the document will be submitted to the GNSO & GAC. Consider deadline for comments / edits by Friday 7 October, distribution of Final version to GAC & GNSO on Monday 10 October, which would allow for initial discussion during 13 October GNSO Council meeting and an exchange of views during joint GAC-GNSO session at ICANN57 followed by formal consideration / adoption at ICANN57 by the GNSO and GAC. If there is a need for additional time, CG members are encouraged to communicate this on the mailing list as soon as possible (e.g. additional time until Monday to allow for CG members to review over the weekend).

One of the challenges for the GAC is capacity building to connect with PDPs and GAC leadership oversight.

Need a champion to pass on the baton within the GAC. GNSO Liaison provides all relevant information, but not to do the work for the GAC. Consider adding an additional recommendation to this end. 

Also consider flagging this to the leadership team of both groups and suggest including it as a topic for the joint session.

 

Action item #1: CG members to review latest version of Final Status Report by Friday 7 October 23:59 UTC at the latest.

 

Action item #2: Staff to finalise Final Status Report & Recommendations for submission to GAC & GNSO by 11 October at the latest.

 

Action item #3: Leadership team to consider how to add to the report notion that the work will need to be carried forward within the GAC following the completion of the CG's work.

 

3. Confirm next steps

See action item #1 and #2. Expected to be part of the agenda for the joint GAC-GNSO meeting at ICANN57.

...