"A DRM plugin framework is by definition a plugin framework. I relly don't want DRM in html either, but I have a hard time finding logical arguments against it"

I'm Australian so this probably won't translate, but if I go into someone's house, and they have a brand new gun rack on the wall, with no gun in it, a few thoughts go through my head:

1. They have a gun but have secreted it somewhere while I'm around. 2. They are going to get a gun. 3. They bought the house with a new gun rack, and don't object enough to guns to remove it immediately.

Now, as was stated earlier, DRM (like a lot of guns) was invented with only one purpose. If I see the governing body of an open web standard starting to stick in frameworks for DRM, I think 3 very similar thoughts to those above.

In short, not being able to find an argument against something, doesn't mean it won't leave you wondering what the actual use case of this will be, and start thinking if it really needs an argument against it. I personally think it needs a whole bunch of better arguments for the proposal than those that have been raised til now.