Re: IETF63 wireless

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

 



I think it is also worth pointing out that:

- In certain building enviorments, this technology simply does not
  scale to hundreds of users, unless both the access point and the
  client software cooperate. Given that we have a variety of clients,
  this isn't going to change any time soon. (I'll let the NOC people
  explain this in more detail, but let's give them a few days to rest
  first).

- There were lots of Ethernet drops in the terminal room that could
  be used as a fallback solution. And the hotel's own network and
  even phonelines could have been used. I know it's not ideal or
  convinenient, but sometimes one has to make do.

Simply saying that a network which is built by volunteers (or by anyone
else for that matter) MUST be reliable is just naive. It's a bit like
saying operating systems and other software must be bug free. Keep in
mind that the people who spend their time doing this have lots of
experience, but they, and by extension we the IETF, learn new lessons
every time. That can't be a bad thing.

The hot water did fail in Huston, but that was many IETFs ago :-)

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@xxxxxxxxx  URL: http://www.cisco.com/ipj



_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

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