<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think that Wolf-Ulrich is right on both points; however, I think it would be most efficient for the Secretariat to coordinate meeting venues with ICANN and then let ICANN handle the travel management directly.<div><br></div><div>Russ</div><div><br></div><div><br><div><div><div>On Jul 31, 2014, at 3:46 PM, WUKnoben wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<div style="WORD-WRAP: break-word; FONT-SIZE: 14px; FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(0,0,0); -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" dir="ltr">
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<div>Thanks Adiel for the draft which I’m mostly in line with,</div>
<div> </div>
<div>Additional comments:</div>
<div> </div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">1.
Secretary should be fluent in English speaking and writing; good knowledge of
one or more additional (ICANN) languages would be of advantage</div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">2. Travel
management should comply with ICANN rules. It seems that the secretariat’s task
here is just an interface<br><br>Best
regards<br><br>Wolf-Ulrich<br></div></div></div></div>
_______________________________________________<br>Internal-cg mailing list<br><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><br></blockquote></div><br></div></div></body></html>