<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Volker,</div>
<div><br>
</div>
<div>The idea wasn’t that these meetings would take place in parallel, but rather parts of the day would be allocated to the sessions listed, so for example, WG F2F meetings would be scheduled in the morning (9-12) and afternoon (13.00 – 16.00) with the GNSO
Council meeting being the closing session of the day / meeting (16.00 – 18.00). The DT may want to consider in developing a draft schedule along the same way by building a block schedule that would list proposed meetings that could take place during those
slots?</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Marika</div>
<div><br>
</div>
<div>P.S. And the name is Marika, by the way, my colleague is Mary :-P</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>><br>
<span style="font-weight:bold">Date: </span>Monday 16 March 2015 19:05<br>
<span style="font-weight:bold">To: </span>Marika Konings <<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>>, "<a href="mailto:gnso-newmtgstrat-dt@icann.org">gnso-newmtgstrat-dt@icann.org</a>" <<a href="mailto:gnso-newmtgstrat-dt@icann.org">gnso-newmtgstrat-dt@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [gnso-newmtgstrat-dt] Kickoff?<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">Hi Mary,<br>
<br>
thank you again for the quick preparation. One of my main concerns is the doubling of must-attend sessions and I do not see this new meeting structure helping, but rather compounding the problem.<br>
<br>
Looking at Meeting B, day 4 the WG f2f sessions seem to be in conflict with the council sessions, which fails to take into account that most councillors are also active participants in that work. It may be advisable to cut the f2f sessions entirely from this
meeting which would also fit with the intention of making these meeting "smaller".<br>
<br>
Best,<br>
Volker<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Am 16.03.2015 um 17:17 schrieb Marika Konings:<br>
</div>
<blockquote cite="mid:D12CBD1D.4159D%25marika.konings@icann.org" type="cite">
<div>Hi Volker,</div>
<div><br>
</div>
<div>Thank you for kicking this off - as the deadline for volunteers was last Friday I was planning to send out a note of welcome this week but you beat me to the punch ;-)</div>
<div><br>
</div>
<div>For your information, the following SG/C representatives are subscribed to the mailing list:</div>
<ul>
<li>Bret Fausett (RySG) </li><li>Tony Holmes (ISPCP) </li><li>Rudi Vansnick (NPOC) </li><li>Volker Greimann (RySG) </li><li>James Bladel (RySG) </li><li>Bill Drake (NCUC) </li></ul>
<div>Volunteers from the BC and IPC may still be forthcoming. </div>
<div><br>
</div>
<div>To facilitate the conversation, I have prepared the attached document which outlines the proposed outline for the three yearly meetings by the ICANN Meetings Strategy Working Group to which I have added in yellow the current GNSO meetings and how these
may fit in meetings A and C. As Volker noted, meeting B is a completely different format which will likely require the most consideration. To encourage ideas and suggestions on how this meeting could look from a GNSO perspectives, I’ve added a draft outline.
Of course, this is just to start of the conversation and thinking, taking into the 4-day meeting format. </div>
<div><br>
</div>
<div>The objective for this group is to present the GNSO Council with a proposed format at the latest by the ICANN meeting in Buenos Aires so that there is sufficient time to socialise the proposed GNSO approach for the new ICANN meeting strategy with other
SO/ACs as obviously there will need to be co-ordination between the different groups to minimise conflicts and potential overlap. On that note, do you think it will be helpful to schedule a conference call to discuss next steps and proposed approach for completing
this task, or do you prefer to continue conversations by email for now? </div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Marika</div>
<div><br>
</div>
<div>On 16/03/15 16:57, "Volker Greimann" <<a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>> wrote:</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0
0 5;">
<div>Dear Strategy team,</div>
<div><br>
</div>
<div>as we have not had any feedback on this channel for the past two weeks, </div>
<div>I feel it is appropriate to kick off the discussion to ensure we are </div>
<div>ready with a proposal in time for the first meetings under the new </div>
<div>schedule.</div>
<div><br>
</div>
<div>The one meeting we should probably focus on is the four-day meeting as </div>
<div>it would require the largest re-adjustment, whereas the "normal" and </div>
<div>"long" meetings will probably allow the council to operate with business </div>
<div>as usual.</div>
<div><br>
</div>
<div>Frankly, I currently see no way of how to fit in the current schedules </div>
<div>of the council into the small meeting unless councillors will be in </div>
<div>session for the entirety of the meeting, and therely lose the ability to </div>
<div>communicate effectively outside the council. We will therefore be faced </div>
<div>with limited choices:</div>
<div><br>
</div>
<div>1) Fit the current schedule into the new meeting;</div>
<div>2) Cut down the council meeting to its bare essentials;</div>
<div>3) Add time to the meeting, very much like current practice;</div>
<div>4) Eliminate the council face-to-face meeting at the short meeting.</div>
<div><br>
</div>
<div>Personally, I lean toward support for option 3, as the other options </div>
<div>would result in a loss of effectiveness of the council.</div>
<div><br>
</div>
<div>Anyway, with this, I hope a fruitful discussion kicks off.</div>
<div><br>
</div>
<div>-- </div>
<div>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.</div>
<div><br>
</div>
<div>Mit freundlichen Grüßen,</div>
<div><br>
</div>
<div>Volker A. Greimann</div>
<div>- Rechtsabteilung -</div>
<div><br>
</div>
<div>Key-Systems GmbH</div>
<div>Im Oberen Werk 1</div>
<div>66386 St. Ingbert</div>
<div>Tel.: +49 (0) 6894 - 9396 901</div>
<div>Fax.: +49 (0) 6894 - 9396 851</div>
<div>Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a></div>
<div><br>
</div>
<div>Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> /
<a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a></div>
<div><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> /
<a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a></div>
<div><br>
</div>
<div>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:</div>
<div><a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a></div>
<div><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a></div>
<div><br>
</div>
<div>Geschäftsführer: Alexander Siffrin</div>
<div>Handelsregister Nr.: HR B 18835 - Saarbruecken</div>
<div>Umsatzsteuer ID.: DE211006534</div>
<div><br>
</div>
<div>Member of the KEYDRIVE GROUP</div>
<div><a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a></div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>--------------------------------------------</div>
<div><br>
</div>
<div>Should you have any further questions, please do not hesitate to contact us.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Volker A. Greimann</div>
<div>- legal department -</div>
<div><br>
</div>
<div>Key-Systems GmbH</div>
<div>Im Oberen Werk 1</div>
<div>66386 St. Ingbert</div>
<div>Tel.: +49 (0) 6894 - 9396 901</div>
<div>Fax.: +49 (0) 6894 - 9396 851</div>
<div>Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a></div>
<div><br>
</div>
<div>Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> /
<a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a></div>
<div><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> /
<a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a></div>
<div><br>
</div>
<div>Follow us on Twitter or join our fan community on Facebook and stay updated:</div>
<div><a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a></div>
<div><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a></div>
<div><br>
</div>
<div>CEO: Alexander Siffrin</div>
<div>Registration No.: HR B 18835 - Saarbruecken</div>
<div>V.A.T. ID.: DE211006534</div>
<div><br>
</div>
<div>Member of the KEYDRIVE GROUP</div>
<div><a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a></div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>gnso-newmtgstrat-dt mailing list</div>
<div><a moz-do-not-send="true" href="mailto:gnso-newmtgstrat-dt@icann.org">gnso-newmtgstrat-dt@icann.org</a></div>
<div><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-newmtgstrat-dt">https://mm.icann.org/mailman/listinfo/gnso-newmtgstrat-dt</a></div>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
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: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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.
</pre>
</div>
</div>
</span>
</body>
</html>