<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
<div><br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<style>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
</style>
<div dir="ltr">
Thanks to Mikey for the resurrection of the ALAC Report, and the [miscommunication] by ICANN staff to the Minister. The letter is not on the ICANN site because it is being 'readdressed'. I spoke to the Chair and Vice Chair last night. A different approach will take place including an apology to the Minister for the letter. ICANN will address the complaints, themselves.<div><br><div>First, I need to hear from the BC folks who did stay at that hotel. </div><div><br></div><div>I know that one member moved, and Chris and I had offered to have another BC member move into one of our rooms, but that didn't happen. </div><div>Can those of you who were at the hotel look at the report from ALAC, and give me [off list] your quick experience?</div><div><br></div><div>Re the letter: </div><div>--the complaint is about the lack of due diligence of ICANN staff, and once it surfaced, how the ICANN staff [meetings staff] handled the complaints/or did not. </div><div><br></div><div>For now, ignore the unfortunate staff letter to the Minister. That will be addressed by the Chair, with an apology.</div><div><br></div><div>However, the responsibility of ICANN to address their decisions and endorsement of the hotel remains. </div><div><br></div><div>Do any of the affected BC members want to share any of your experiences? </div><div><br></div><div>I feel very badly about this for our members. As you all know, originally, Chris, Bene and I were at that hotel. When I moved us due to bad feedback, I had also alerted the members we knew who were there that we were moving ourselves. The cost of moving was rather excessive. But, I didn't realize that ICANN was putting people that they were funding at that hotel. So, our outreach to members was limited accordingly. </div><div><br></div><div>There is a longer term issue in that ICANN continues to accept venue hotels with very limited room availability. We continue to find that the venue hotel is booked out before the host site even goes live, which is a future challenge. On that front, Ayesha and I participated in the Meetings public session and raised several issues. </div><div><br></div><div>And, in that meeting, I did raise the concerns about the experiences of those at that hotel. I cannot tell you that the Board members present demonstrated much awareness of the serious nature of the concerns, not did they ask any questions to learn more. </div><div><br></div><div>BUT, the focus we all take should be the ALAC report and any augmentation, or just general agreement, if that was also your experience. </div><div><br></div><div>As noted, there should not have been an ICANN staff letter to the Minister, and that is separately addressed. I am pleased that the Chair and Vice Chair are both now aware, and addressing that misfortunate misdirected staff communication. We don't need to say more on that front. I was disappointed to hear that they were not briefed on site; but I gather that 'gap' is also now addressed with staff. </div><div><br></div><div>Accepting and endorsing hotels is the responsibility of ICANN staff -- and requires due diligence, and accountability. </div><div><br></div><div>if you were at the hotel and want to share your concerns, please email me and copy Bene, who will compile and help me to generalize the experiences. </div><div><br></div><div>Marilyn Cade,</div><div>BC Chair </div><div><br></div><div>P.S. Mikey, thanks for putting the doc up. </div><div><br></div><div>==================</div><div><br><div>> Subject: Re: [bc-gnso] a pretty scathing report from At Large about Hotel Almendine in Dakar<br>> From: mike@haven2.com<br>> Date: Thu, 1 Dec 2011 11:55:07 -0600<br>> To: bc-gnso@icann.org<br>> <br>> <br>> i threw a copy up on my server -- here's the link;<br>> <br>> http://www.haven2.com/clay-to-guirassy-23nov11-en.pdf<br>> <br>> mikey<br>> <br>> <br>> On Dec 1, 2011, at 10:32 AM, Smith, Bill wrote:<br>> <br>> > <br>> > And now the report is no longer on the ICANN site.<br>> > <br>> > On Nov 30, 2011, at 5:10 AM, Mike O'Connor wrote:<br>> > <br>> > hi all,<br>> > <br>> > i remember several of you mentioning that it was pretty rough going at the Alemendine. i had no idea *how* rough. here's an astonishing report from the At Large documenting the situation with a poll and pictures.<br>> > <br>> > http://www.icann.org/en/correspondence/clay-to-guirassy-23nov11-en.pdf<br>> > <br>> > they raise some pretty interesting points -- and offer suggestions on how to move forward.<br>> > <br>> > m<br>> > <br>> > - - - - - - - - -<br>> > phone 651-647-6109<br>> > fax 866-280-2356<br>> > web http://www.haven2.com<http://www.haven2.com/><br>> > handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)<br>> > <br>> > <br>> > <br>> <br>> - - - - - - - - -<br>> phone 651-647-6109 <br>> fax 866-280-2356 <br>> web http://www.haven2.com<br>> handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)<br>> <br>> <br></div></div></div> </div></div> </div></body>
</html>