Re: [Mtgvenue] Comments on draft-baker-mtgvenue-iaoc-venue-selection-process-02

[Ole Jacobsen <[e-mail]>]

Brian,

Keep in mind that when the IETF "takes over" the hotel network it is 
often done after lengthy negotiations and much legwork. There is never 
any guarantee that any given hotel will let us anywhere near their 
network and this situation isn't getting any better. We do of course 
REQUIRE a fully compliant Meeting Network, but that does not mean we 
can always extend it to every sleeping room. And doing it for more 
than one hotel is extremely costly in terms of people resources.

While the "terminal room" no longer has any terminals or computers, 
its history should not be forgotten; it was there as a place where we 
could get our email and get work done. Much as changed since the early 
days, including increasing use of mobile devices that themselves 
function without traditional WiFi connections. As a frequent hotel 
guest I am as frustrated as you are with some of the annoyances of 
in-room WiFi (or Ethernet), but I also have to say that I think we 
have become too demanding when it comes to this topic.

I have this wild idea that the IETF should "leave something good 
behind" in these meeting facilities and I'd like to see that brass 
sign in the lobby that says:

 "The IETF Was Here in 2013. They fixed Our Network and Left Behind 
 Some Great Networking Equipment from the Following Vendors: ...."

:-)

Ole


On Mon, 7 Nov 2016, Brian E Carpenter wrote:

> On 07/11/2016 08:42, Dave Crocker wrote:
> > On 11/6/2016 11:21 AM, Yoav Nir wrote:

> >> I think that by now the network available in average hotels is 
> >> sufficiently non-horrible that we can live with the same kind of 
> >> network as everyone else.
> > 
> > 
> > This is a basic point.  And a specific assessment.  I think I've seen 
> > some disagreement.
> 
> Here's more disagreement. IMHO, some level of problems occur in almost
> any hotel almost any time. Things like broken splash pages*, limited
> addresses per room, broken DNS*, bizarre filters, inadequate capacity
> at busy hours*, and of course complete absence of IPv6*. Not to mention
> paying extra for Internet access, still prevalent in many countries.
> 
> One of the nice things about showing up at the IETF hotel is seeing
> a smooth, efficient dual stack service on the ietf-hotel SSID. But it's
> more than nice: it makes one's personal efficiency much greater, given
> the density of email and of people using *.ietf.org in a small area.
> 
> * all of which I have experienced in the last 3 days at the Copthorne
> Hotel in Wellington, NZ.
> 
>    Brian
> 
> > 
> > It would be helpful to get some discussion that focuses both on the 
> > facts of the assessment and the willingness of the community to live 
> > with existing venue Internet infrastructure, even if that winds up 
> > sometimes being problematic.
> > 
> > d/