James Carlson wrote: > Peter Memishian writes: > >> > For SXCE, that means familiar class action and BFU updates (and a flag >> > day, since you can't go back without misplacing your keys[1]), but >> > most instances of the problem are likely with OpenSolaris (where NWAM >> > is the default), and that has no clear mechanism for dealing with >> > upgrade-related scripting. >> >> Assuming we allow "-" and ".", do we think many users are going to have >> problems with upgrade? I'd expect most are using alphanumerics, and >> spaces already don't really work (hence the bug). >> > > The names that NWAM uses come from the ESSID and BSSID of the AP, and > since the ESSID is a free-form string, and may well be "WEP-$uck$" in > some locations and "%%%yo%%%" in others, I think there's a problem > here, even for those who haven't yet stumbled over the space character > problem. > > I think we've got an obligation to handle this change, or it's going > to result in even _more_ anxiety and dissatisfaction with NWAM and > with OpenSolaris networking in general. We've had our own problems, > but we're also the scapegoat for all the problems elsewhere. >
I agrree, Jim, and I'd like to reiterate that we have an obligation to follow what the IEEE specification says is allowed here. Anything else introduces arbitrary restrictions that may introduce interoperability problems. Darren _______________________________________________ networking-discuss mailing list [email protected]
