Re: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




--On Tuesday, January 12, 2016 10:16 -0800 Randall Gellens
<rg+ietf@xxxxxxxxxxxxxxxxx> wrote:

>...
>>  So, would you propose a hard rule of "stop considering any
>>  city unless we could got a room block of at least N rooms",
>>  with N somewhere in the range of 800 or 900?   Unlike the
>>  variety of more subjective rules, it would be very clear and
>>  easy to interpret.    My assumption about IETF 95 is that,
>>  despite understanding and considering the disadvantages of
>>  smaller hotels, the decision-makers believed they had a
>>  sufficient "go to Buenos Aires" mandate to override hotel or
>>  room block size considerations.  I presume that, for the
>>  future, we could change that if we had consensus that, e.g.,
>>  minimum room block size was a firm requirement.
> 
> I'm not fond of hard rules, and would be fine if we had some
> clear information as to why this city was chosen despite the
> room block issue.

I think Ole, Fred, and others have already answered that
question.  The IESG decided that we should go to South America
(whether they or IAOC came up with the idea seems to be in
dispute).  The community was asked if that would be ok (without
mentioning the implications for the hotel situation), came up
with answers the IESG interpreted as "yes', and then the
Meetings Committee moved ahead to make the best arrangements
possible given that the decision to go to Buenos Aires had
already been made.

Now, you probably see some problems with that sequence of events
(and I do too), but it seems to me that, if the Meetings
Committee is given what it reasonably construes as instructions
from the IAOC and/or IESG to hold a meeting in a particular
place at a particular time, then what we ended up with is
exactly what one should expect unless there are definite rules
that say "either these conditions MUST be met or you need to
come back to the community for explicit approval with the rule
for which an exception is proposed explicitly identified".
Noting comments from Ole, Bob Hinden, and others, there also
better be _very_ few such rules because the various systems are
easily overconstrained.

> Which of course is an example of your calls
> for transparency. Maybe a semi-rigid rule that can be
> overridden with good cause (sort of a SHOULD rather than a
> MUST)?

See above.

    john




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]