I don't know about quagga mussels, but last week I dove in a quarry where the zebra mussels easily colonized everything down to the bottom at 80 feet or so. Being filter feeders, I can't imagine the depth bothers them much.
It's actually eastern Pennsylvania, the helicopter has a Pennsylvania Power and Light (PPL) logo on it. If you look carefully in the background you can see the Delaware Water Gap in the mountains.
Nevertheless, it's the same for the weather, Fall/Winter is gonna be windy enough you can't wait around for it.
Apple Kremlinology suggests they'd be hesitant to provide that information with a paper trail. There would be a lot less mysteries in the Apple world if they did.
That said, you could probably get an answer at WWDC, if you find one of the code signing guys at the lab and corner them.
Ten seconds of running WireShark and watching iTunes talk to an AppleTV running v6 will give you something like that, where iTunes and the AppleTV do much talking about 'fp-setup' and FPLY and handshake together.
Apple's AirPlay (AirTunes) devices have actually been doing these FPLY verifications for years now, but they were optional and talking to the devices with the older non-FPLY protocol worked. It's just as of Apple TV 6.0 that they appear to be dropping the old connection exchange and requiring the FPLY one to talk to the device.
I'm not quite sure what you think we have to gain by claiming we think FairPlay is required now, when it really wasn't? This weblog post was to inform our customers about an issue with our software and ATV 6. We'd all dearly love a solution.
...perhaps Apple's intent was simply to drop support for the extremely old clients that Airfoil was emulating? That seems like a much simpler explanation to me than some sort of nefarious plan to break Airfoil.
My suspicion would be that feature was added in response to external demands (e.g, movie/TV studios required it for remote playback), and making it mandatory was a later simplification.
