Volker, Please can you help me (us?) understand the thinking behind the following: 1. The ICANN board informs the GNSO council about the Communique 2. The GNSO council deliberates input and drafts a letter to the ICANN board including a proposed response to the GAC In 1 above, I realise that you said this could be optional. I am not sure it is necessary. In 2 above, I wonder if it should be along the following lines: The GNSO council deliberates input and drafts a proposed response to the GAC including preparing a copy of the proposed response to be sent to the ICANN board. Thank-you Jonathan From: David Cake [mailto:dave@difference.com.au] Sent: 05 December 2014 00:19 To: Volker Greimann Cc: Council Subject: Re: [council] Moving ahead on the GAC communique On 4 Dec 2014, at 8:32 pm, Volker Greimann <vgreimann@key-Systems.net> wrote: Hi David, I agree that any and all affected WGs [should/need to] be the first stop on our path to determining policy impact, however in some scenarios this may prove impractical: - the advice does not touch upon existing policy, i.e. would require a new policy making process; or - the advice touches upon existing policy that was created in the dawn of times (so to speak), so the original WG members are no longer available in sufficient numbers to advise the council. Absolutely. Existing WGs should be consulted on matters that concern them, but that will not cover all issues. Of course, there will also be elements of the GAC Communique which do not concern the GNSO directly, and that we do not need to comment on at all. Regards David Our process should have a clear path for all situations to ensure a quick turnaround. We may also want to reach out to the Policy and Implementation WG as they may have discussed elements of the puzzle we may find useful for this endeavor as well. Best, Volker Am 04.12.2014 03:01, schrieb David Cake: Thank you Volker for kicking this process along. I very much agree that input from Constituencies is valuable, but should be with reference to the existing policy process. I do think we should have a step in the process where we directly ask for input from all working groups that are referenced (directly or indirectly) by GAC advice. While we are working on more direct interaction between the GAC and WGs, when they are discussed in the GAC Communique we should respond on behalf of the GNSO, and of course such response should be in full consultation with the WG concerned. David On 4 Dec 2014, at 5:15 am, Volker Greimann <vgreimann@key-Systems.net> wrote: As discussed during the last council meeting, one of our action items is for the Council to examine ways in which the GAC communiqués can be channeled through the ICANN Board to the GNSO Council where they can be analyzed for possible policy implications arising from the recommendations, and where the GNSO Council can report back to the ICANN Board with a proposed method of responding to the communiqué and initiating policy work if there be a need. In the discussion, a lightweight and informal process was proposed where a call for topics would be put out to the various GNSO constituencies and stakeholder groups and these would be sent in the form a letter by the Council, within 30 to 60 days upon receipt of a GAC communiqué, to the Board responding to that communiqué. As a framework for discussion, the following steps are suggested: 1) GAC publishes its communique 1b) optional: The ICANN board informs the GNSO council about the Communique and requests an analysis of the communique for issues that touch upon ongoing or new policy work 2) 1st post-meeting council session: The Council deliberates the GAC communique and instructs councillors take the communique to their stakeholder groups and constituencies for analysis of whether and if so how the communique touches upon, complements or contradicts existing policy, whether it impacts ongoing policy work or whether it suggests the initiation of new policy work. This review should exclude any opinion on such policy and be limited to the analysis whether policy would be affected and therefore should be obtainable within a turn-around time of 2 weeks. 3) 2nd post-meeting council session: The GNSO council deliberates input and drafts a letter to the ICANN board including a proposed response to the GAC Potential responses could be: - Council recommends initiation of new policy work based on GAC advice - Council recommends informing the GAC that [suggestion] has been deliberated during previous or ongoing policy work and has been [accepted/rejected/partially accepted] by the community - Council recommends revisiting prior PDP to analyse and deliberate the impact of suggested advice on existing policy. - Council advises Board that existing policy already covers [suggestion] and [suggestion] is a mere question of implementation of said policy I am shooting from the hip here to put up a straw man, so if anyone would like to add to these suggestions or suggest a different approach, the floor is yours. -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net <http://www.key-systems.net/> / www.RRPproxy.net <http://www.rrpproxy.net/> www.domaindiscount24.com <http://www.domaindiscount24.com/> / www.BrandShelter.com <http://www.brandshelter.com/> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu <http://www.keydrive.lu/> Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net <http://www.key-systems.net/> / www.RRPproxy.net <http://www.rrpproxy.net/> www.domaindiscount24.com <http://www.domaindiscount24.com/> / www.BrandShelter.com <http://www.brandshelter.com/> Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu <http://www.keydrive.lu/> This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone. -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net <http://www.key-systems.net/> / www.RRPproxy.net <http://www.rrpproxy.net/> www.domaindiscount24.com <http://www.domaindiscount24.com/> / www.BrandShelter.com <http://www.brandshelter.com/> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu <http://www.keydrive.lu/> Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net <http://www.key-systems.net/> / www.RRPproxy.net <http://www.rrpproxy.net/> www.domaindiscount24.com <http://www.domaindiscount24.com/> / www.BrandShelter.com <http://www.brandshelter.com/> Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu <http://www.keydrive.lu/> This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.