W3C home > Mailing lists > Public > site-comments@w3.org > April 2017

Re: [DRM] On a reasonable implementation

From: Coralie Mercier <coralie@w3.org>
Date: Wed, 5 Apr 2017 14:51:05 +0200
Cc: site-comments@w3.org
Message-Id: <D3D222D9-1A39-43EF-86BB-4E724D7557E2@w3.org>
To: Joshua Hudson <joshudson@gmail.com>
Thank you for your note which I have transferred internally for information.

Kind regards,
Coralie

> On 3 Apr 2017, at 10:03 , Joshua Hudson <joshudson@gmail.com> wrote:
> 
> I saw the news on the call for mass phone calls to oppose DRM. I
> decided it wise to offer a completely different stance.
> 
> What has really enraged people is not the inability to copy media; but
> rather the inability to provide decent cross-platform support. I am on
> a rather strange platform myself due to limiting ADA bugs (in fact
> your regional contact map is not usable here for reasons I don't
> understand).
> 
> I propose the following: define a P-Code VM with a very well-defined
> set of specifications, that leaks only limited information about its
> host platform.
> 
> The VM should have access to the following channels:
> * Video Output
> * Audio Output
> * Video Input
> * Audio Input
> * HTTP
> * HTTPS
> * Web Sockets (there's a javascript standard for this; might as well use it)
> * (if UDP multicast is still a thing might as well find a way to allow it)
> 
> Security: If Video/Audio input is disabled by the host (and this
> should always be possible) present the logical equivalent to unplugged
> hardware.
> 
> The VM should not have access to most of the local filesystem, but
> making HTML local storage work is reasonable. The VM should receive an
> implementation designation string; this does not identify the browser
> but rather the VM library component implementation and version. [This
> makes it possible to work around bugs in a specific version]. Version
> should be a single int64 number where X.Y.Z.P is packed as 4 int16
> numbers to limit the amount of code required to get version range
> checks correct.
> 
> Making CPU speed and presence of certain well-known hardware decoders
> is also reasonable. The hardware list should be kept short but here is
> a reasonable list
> * MP3
> * MP4
> * H.264
> * VP8/WEBM
> * Theora/Vorbis
> 
> (notice this list is drawn from the HTML5 list but MP3/4 is added as
> hardware decoders are already common form these).
> 
> 
> 

--
Coralie Mercier  -  W3C Marketing & Communications -  https://www.w3.org
mailto:coralie@w3.org +336 4322 0001 https://www.w3.org/People/CMercier/
Received on Wednesday, 5 April 2017 12:51:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 April 2017 12:51:18 UTC