Romascanu, Dan (Dan) wrote:
-----Original Message-----
From: David Kessens [mailto:david.kessens@xxxxxxx]
Sent: Tuesday, August 05, 2008 2:18 PM
To: Romascanu, Dan (Dan)
Cc: Joel Jaeggli; Henning Schulzrinne; IETF Discussion
Subject: Re: Proposals to improve the scribe situation
Dan,
On Tue, Aug 05, 2008 at 12:43:10PM +0200, Romascanu, Dan (Dan) wrote:
From Joel Jaeggli
[ ... ]
have one. I suspect that if they have anything with an
intel 2100 or
with a prism 2 wireless chipset it's probably time to upgrade
preferably with a fresh os as well...
Many people do not have the liberty of upgrading machines or OSs at
ease.
But is that a problem for you or for the network team ?
There is a point where certain legacy hardware is just not
going to cut it anymore and I don't believe that that is the
fault of the network team.
Basically, whether you like it or not, this is a problem
between you and your IT department (and yes, I do understand
that that is not necessary an issue that you would like to deal with).
David Kessens
---
I respectfully disagree. I would claim that the problem is one of the
network team, as long as the hardware is standards compliant and not
something exotic.
The early ipw2100 driver/firmware combo has some serious quality
(roaming without dissasociating, keying up and transmitting from power
save mode without listening to the air etc) if there still people
running it then they aren't doing themselves or us (the APs) any favors.
That's not something we could do about from the air short of
blacklisting clients that exhibit that behavior.
An IBM ThinkPad acquired three years ago running
Windows XP is still one of the most popular machines, it is carried by
many people and will continue to be carried for another two-three years.
As it is fully IEEE standards compliant and some kind of industry
standard (whatever this means) many people expect to be able to use it
at an IETF standards meeting.
That's fine and we're not going to stop supporting it, but there's a
limit within the engineering constraints we are faced with as to how
well we can make it work. investing in a b/g radio or an a/b/g radio or
an a/b/g/n will result in a more reliable experience in this enivironment.
Telling people that they have 'a problem
between you and your IT department' does not help at all, as most of the
people have no influence on their company's buying or IT policies.
Actually telling this means that we tell them 'you need to buy another
machine in order to efficiently attend an IETF meeting'.
Odds are you'll have a better experience. not doing so won't preclude
access.
Dan
(speaking as an individual)
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf