Dear Council colleagues,

FYI below to follow up on the point raised by Rubens yesterday. I raised this with the SO/AC Chairs at last night's dinner and below is the more detailed follow-up. Let's add this to AOB on Wednesday for our own follow up.

Best wishes,

Heather


---------- Forwarded message ----------
From: Heather Forrest <haforrestesq@gmail.com>
Date: Sat, Mar 10, 2018 at 10:39 AM
Subject: Process Mapping documentation
To: SO-AC Chairs List <soac-chairs@icann.org>


Dear all,

I referred briefly at our get-together at last night's SO/AC leaders' dinner to this document ( https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06mar18-en.pdf), which I understand is part of the Process Mapping work, described at https://www.icann.org/processdocumentation). 

I wasn't aware that this had been posted, but it was brought to the GNSO Council's attention by a community member who happened to come across it. What I now understand is that this is not an adopted process, but rather an attempt to describe in plain English the process set out in the diagram, available at https://www.icann.org/en/system/files/files/gac-advice-process-flowchart-31aug17-en.pdf.

One immediate point raised within the GNSO is that this document might usefully address the situation of AC advice that is in conflict with a policy recommendation from an SO (this is not presently addressed in the document). This is something that the GNSO will consider further, but I raise it with you all as it's a matter that concerns all the SOs/ACs and how we all fit together in the ICANN ecosystem. I understand that staff welcomes and is very open to ideas for improving and clarifying these documents.

Best wishes,

Heather Forrest
on behalf of GNSO Council