I remain disappointed that the concepts of Minneapolis, and MPLS, have not been extended to calling them 'mipples.' Are we going to Mipples? again? Is our network infrastructure mipples-enabled? Should we implement a bogop mipples vippen? L. sometimes a metaphor is just a metaphor. ________________________________________ From: ietf <ietf-bounces@xxxxxxxx> on behalf of Jari Arkko <jari.arkko@xxxxxxxxx> Sent: Tuesday, 5 January 2016 10:53:51 PM To: Stewart Bryant Cc: IETF Discussion Subject: Re: Hotel situation > Minneapolis is really a metaphor for functional, works well for most > people, easy to get flights and hotels, flight times not too bad, not regarded > as a holiday trip at work, everyone is there to work. Yes. And I think we have several conceptual Minneapolises :-) some of which we are returning to. > It does not have to be Minneapolis, but the utilitarian properties above, > are in my view far more relevant than the IETF World Tour model we > seem to have in place. Our main criteria is 1-1-1*, and I agree that we can get some further efficiencies by focusing more on repeat locations with good experience. But we will still need to meet in different parts of the world. Granted, two out of the last 15 meetings were in touristy locations - that’s still probably less than, say corresponding fraction in some other organisations such as the IEEE. In any case, for me the main criteria is ease of travel (flights), availability of a range of hotels (and the hotel block in main ones), and ability to put the IETF network in and other practical issues. Jari