Slow is not necessarily bad
I've heard a lot of people give IEEE a lot of bad-mouthing because they took so long to certify the 802.11n draft into a standard, but why? If you're looking for someone to blame, blame the vendors involved. THEY are the ones who all have different ideas and likely don't want to agree or compromise. Also, when we're talking about a multi-billion-dollar industry, it's a good idea to take your time and make sure that the standard is properly laid out. Would you really want a rushed (and probably poorly-thought-out) standard simply because vendors didn't want to wait to release their products? Would you prefer that all specifications take the Microsoft OOXML "certification" route?
"This compatibility is achieved thanks to the last details of the specification all being options in the draft, so draft devices should connect seamless with their properly-compliant siblings."
Let me rephrase that for you:
'IEEE and the vendors involved were forced to make the last details of the specifications optional in order to maintain compatibility with pre-standard kit made by jackass vendors who felt they were too important and too greedy to wait for the standard to be certified.'
If you base your product on a draft specification, not a certified standard, you have no right to expect it to inter-operate with a standard-compliant product. If you bought your kit knowing it was based on a draft, pre-standard version of a specification, then you have no right to complain if it doesn't work with standard-compliant kit. There's a reason it's called a draft.