Re: limiting our set of cities

[Michael Richardson <[e-mail]>]

Andrew Sullivan <[e-mail]> wrote:
    >> Can you tell the community if the LLC has any plans/thoughts to stop
    >> looking for new places to meet, rather to just establish a list of
    >> 10-15 cities where we have successfully met, and simply repeat?

    > There was a whole WG that went over this ground in detail not very long
    > ago, and it produced a procedure.  I think the procedure is being
    > worked, and in my opinion it would be better to let it run a little
    > while to see whether it produces good results, rather than trying to
    > optimize it right now.

Yes, there was a whole WG, and I think that the WG was encouraged not to
micromanage the IASA/IAOC/IETF-LLC.
{Both draft-ietf-mtgvenue-meeting-policy-07 and draft-ietf-mtgvenue-iaoc-venue-selection-process-16
are surprisingly still in MISREF.. or are they. I guess because of IETF-LLC
stuff. Looks like it might all come out in moment now. meeting-policy-07 does
mention "IASA", btw}

I scanned both documents again to be sure, and indeed, the question of how
the list of venues is to be made is, quite reasonably, not micromanaged in
the documents.

It therefore seems appropriate that I ask the question I did, of the
executive director.   The response, *that this is something the community has
to talk about*, is reasonable, but it was not part of the mtgvenue discussion.

Why is the IETF LLC making lists of cities of places where have never met,
(Ottawa? Seriously?  We established 20years ago it won't work)
and why does it seem like we continue to spend money and time (including
flights to check places out) when we have quite a number of successful
meetings in many places.
Yes, for Europe and North America, many is certainly the case.

I read all about how we have to avoid getting locked in, and we need to
change things periodically to keep the hotels on their toes.  Of course.
I never suggested we meet the same place every year.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [





--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-