HTML DRM specifications are kept secret
The W3C working group continues the discussion of a new extension for the HTMLMediaElement element , which provides an API to control the playback of content in the browser. That is, built-in DRM will appear directly in the browser, so that the right holders will be able to prohibit / restrict the playback of movies and music on users' computers.
Although the new standard has not yet been finally adopted, the right holders have already begun their technical implementation. Interesting details of this process are contained in Mark Watson’s yesterday’s letter from Netflix. This company is one of the main developers of the standard, along with Google and Microsoft .
Mark Watson explained that a number of vendors are currently working on the development of DRM modules for HTML commissioned by copyright holders - media studios. The W3C Consortium does not set out to recognize and publish these specifications, but merely seeks to provide clear APIs for accessing them from the browser. Therefore, the characteristics of specific DRM modules are a trade secret and are kept secret.
DRM modules are designed in accordance with the requirements that the studio imposes. And these requirements are also kept secret. Perhaps they are different from different studios. For an example, you can look at the requirements for products that are compatible with Microsoft PlayReady , says Watson. There, content encryption and key exchange is carried out in approximately the same way SSL is used.
')
“We are not trying to standardize solutions that are developed in accordance with the requirements of the studios. I think it would be quite ambitious, ”added Watson.
However, copyright holders can still announce specifications for DRM. At the very least, the executive director of the W3C consortium, Jeff Jaffe, wants to ask them to do so.
Every year DRM protection becomes more and more difficult. This can be estimated at least by increasing the time of jailbreaking each new version of PS or iOS. Probably the right holders believe that in the end they will be able to create an “unbreakable” DRM protection and permanently eliminate the problem of piracy. It seems to them that even a little bit more and they will be able to return to the blessed times of the end of the 20th century, when it was possible to sell one-song CDs for $ 25.
A sample of the possible extension work for the HTMLMediaElement element is shown in the diagram. DRM in the browser will represent a complex mechanism of cryptographic protection of content, where using JavaScript, the protection mechanism is selected, license acquisition and key exchange is controlled, and proprietary license management methods are implemented.
In the CDM diagram, a content decryption module (Content Decryption Module).
Although the new standard has not yet been finally adopted, the right holders have already begun their technical implementation. Interesting details of this process are contained in Mark Watson’s yesterday’s letter from Netflix. This company is one of the main developers of the standard, along with Google and Microsoft .
Mark Watson explained that a number of vendors are currently working on the development of DRM modules for HTML commissioned by copyright holders - media studios. The W3C Consortium does not set out to recognize and publish these specifications, but merely seeks to provide clear APIs for accessing them from the browser. Therefore, the characteristics of specific DRM modules are a trade secret and are kept secret.
DRM modules are designed in accordance with the requirements that the studio imposes. And these requirements are also kept secret. Perhaps they are different from different studios. For an example, you can look at the requirements for products that are compatible with Microsoft PlayReady , says Watson. There, content encryption and key exchange is carried out in approximately the same way SSL is used.
')
“We are not trying to standardize solutions that are developed in accordance with the requirements of the studios. I think it would be quite ambitious, ”added Watson.
However, copyright holders can still announce specifications for DRM. At the very least, the executive director of the W3C consortium, Jeff Jaffe, wants to ask them to do so.
Every year DRM protection becomes more and more difficult. This can be estimated at least by increasing the time of jailbreaking each new version of PS or iOS. Probably the right holders believe that in the end they will be able to create an “unbreakable” DRM protection and permanently eliminate the problem of piracy. It seems to them that even a little bit more and they will be able to return to the blessed times of the end of the 20th century, when it was possible to sell one-song CDs for $ 25.
A sample of the possible extension work for the HTMLMediaElement element is shown in the diagram. DRM in the browser will represent a complex mechanism of cryptographic protection of content, where using JavaScript, the protection mechanism is selected, license acquisition and key exchange is controlled, and proprietary license management methods are implemented.
In the CDM diagram, a content decryption module (Content Decryption Module).
Source: https://habr.com/ru/post/209016/
All Articles