ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] MOTION - To extend the term of the current GNSO Liaison to the GAC

  • To: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Subject: Re: [council] MOTION - To extend the term of the current GNSO Liaison to the GAC
  • From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
  • Date: Tue, 21 Jun 2016 17:02:52 +0200
  • Cc: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=key-systems.net; h=content-transfer-encoding:content-type:content-type :in-reply-to:mime-version:user-agent:date:date:message-id:from :from:references:to:subject:subject; s=dkim; t=1466521364; x= 1467385365; bh=BpHduxePsUGEObaCN5o81GYuP5B7OJWqac7ar/+f2yc=; b=t PX/Mr1KK4ZuW6nBv83qs15VmNuApLYQBnGVWVXP8T4z6NqovGdeOYQxCjfLymxTz NewlrrxFxzHODLT4e7zGJV3sqOQrhjNrU8psQVRTgwn7bCupyTswDKK/TAQrFWTd f0umRdobMV6uR6+JBLrPJFoU4tId+BWTMjID+/l4IA=
  • In-reply-to: <D38EAB5F.C72EB%jbladel@godaddy.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D38DB801.C6FFA%jbladel@godaddy.com> <00d501d1cb3b$af0d04b0$0d270e10$@paulmcgrady.com> <199E9C8D-0979-4BDC-A156-DD19F0A85BDB@godaddy.com> <EF5FCC7E-33AA-4B6F-9D1F-57C143F3A0FF@paulmcgrady.com> <0E8A13881A6B4301BF7C531B42382858@WUKPC> <17CB771F-B2EA-47A6-896A-AC22C024BF6B@paulmcgrady.com> <D38EAB5F.C72EB%jbladel@godaddy.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1


I would second the amended motion as proposed by Wolf Ulrich.

Volker


Am 21.06.2016 um 15:30 schrieb James M. Bladel:
Thanks all for weighing in.

There currently isn¹t a second to the motion, so I take these changes as
friendly and ask that Marika & team modify the WHEREAS 2 language
accordingly (the most recent version submitted by Wolf-Ulrich, below).


J.



On 6/21/16, 6:50 , "Paul McGrady" <policy@xxxxxxxxxxxxxxx> wrote:

Thanks WU. I think that is fine since it reflects the reality of what
happened and doesn't require any sort of judgment on the quality of the
sole applicant. Thanks!

Best,
Paul


Sent from my iPhone

On Jun 21, 2016, at 6:35 AM, WUKnoben <wolf-ulrich.knoben@xxxxxxxxxxx>
wrote:


Hi Paul,

I'm with you that WHEREAS 2 as originally suggested should be improved.
However expressing or describing hopes in a motion seems to bring in
some subjectivity which is difficult to assess. So I wonder whether this
could be acceptable:

2.    The subsequent call for volunteers resulted in the decision to
extend the selection process.


Best regards

Wolf-Ulrich

-----Ursprüngliche Nachricht----- From: Paul McGrady
Sent: Tuesday, June 21, 2016 4:28 AM
To: James M. Bladel
Cc: GNSO Council List
Subject: Re: [council] MOTION - To extend the term of the current GNSO
Liaison to the GAC


Thanks James. How about we strike it as written, and just say "whereas
the volume of responses to the request for applications for the role was
less robust than hoped for."

Best,
Paul


Sent from my iPhone

On Jun 20, 2016, at 8:50 PM, James M. Bladel <jbladel@xxxxxxxxxxx>
wrote:


Hi Paul -

You are correct, "incomplete" is probably not the best word. The
intention was to leave the door open for the lone application received
to be resubmitted.

I'm fine if we strike "incomplete", or even the entirety of WHEREAS 2.

Thank you,

J.
____________
James Bladel


On Jun 20, 2016, at 16:35, Paul McGrady <policy@xxxxxxxxxxxxxxx>
wrote:

Hi James,

I am Ok with this, except I don't understand WHEREAS 2.  What element
of the
application wasn't completed?  I thought from all that back and forth
that
the reason to not move forward with the one candidate we had was that
there
was only 1 applicant and, in the opinion of some, he didn't fit the
bill.
This motion reads as if there was an application form that didn't
have all
the checkmarks checked.  Can you please elaborate on what is meant by
"incomplete"?  Thanks in advance.

Best,
Paul


-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of James M. Bladel
Sent: Monday, June 20, 2016 3:11 PM
To: GNSO Council List
Subject: [council] MOTION - To extend the term of the current GNSO
Liaison
to the GAC

Councilors -



--
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@xxxxxxxxxxxxxxx

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@xxxxxxxxxxxxxxx

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.






<<< Chronological Index >>>    <<< Thread Index >>>