[RDS-WHOIS2-RT] Next Monday's meeting

[Volker Greimann]

I would like to send my apologies for the upcoming Friday meeting as I 
will be at a conference from today until Friday evening.

For the Monday meeting, the usual conflict applies and it would be 
really beneficial if that meeting slot could somehow be moved to a later 
time as the conflict will continue to exist.

Best,

Volker


Am 15.02.2018 um 06:22 schrieb Alan Greenberg:
> We have 3 more meetings prior to the ICANN61 meeting, and 3 or 4 after 
> ICANN61 and before we meeting in Brussels.
>
> According to the workplan we approved, the period from mid-next week 
> until the end of the ICANN meeting we would assembling our findings 
> and beginning to draft recommendations. As I read things, we are now 
> WAY behind on most topics.
>
> Prior to and at our last Brussels meeting, we made a conscious choice 
> to tackle most of the parts of the review described in the Bylaws, and 
> we also added a number of other areas. We are now going to have to 
> commit to actually deliver this work.
>
> There is no doubt that all of us are busy and no doubt over-committed, 
> but we all applied to work on this Review and now have to carve out 
> the time to do it, or accept that we cannot and resign.
>
> A quick check of the subgroup mailing lists shows that for February, 
> we have had a total of 25 messages posted by RT Members to all 13 
> lists. If that is an indication of the work going on, then we seem to 
> have a problem. If work is preceding off-list, please move it to the 
> list so that everyone can follow it.
>
> If will be on the call, please be prepared to discuss all of your 
> subgroups, and particularly the one(s) you are leading. If you cannot 
> make one or both of the calls next week, PLEASE send your apologies 
> ahead of time so we know who will be on the call, and please make sure 
> that someone on your subgroup(s) will be there do discuss the issues.
>
> Alan
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt

-- 
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 at key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / 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

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 at key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / 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

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.