Re: [MEDIA_PIPELINE_TF] HTML media errors

On Nov 4, 2011, at 10:05 AM, Vickers, Mark wrote:

This is a great start. The backwards compatibility is good.

Should we reference to the IETF protocol documents which define the errors (DNS, TCP, TLS, HTTP, ...) for the error code list and meanings?

Also, how were these errors chosen out of all errors defined in those specs?

It's not so much a question of referencing the specifications, since the specifications address the protocols and it is implementations that throw errors.

The list comes from considering what are the physical events that can happen that cause failures (what packets could come back, what things could time out etc.) and grouping those in a way that leaves you with a managable number of top-level errors.

We could discuss whether (for example) the various DNS error cases should be bundled or broken out, but since Hixie hinted that 10 new errors might already be too many...

The TLS ones do need review from some security guys.

We should reference HTTP for the HTTP error codes, but for the rest I don't think a reference is necessary (they are well-enough defined by the text).



On Nov 4, 2011, at 9:05 AM, Mark Watson wrote:


I put up a proposal for additional network-related errors at

I would hope these would be uncontroversial and so could be added to one of the existing LC1 bugs as a concrete proposal for discussion.

I suggest we discuss these a little on this list and then link them from the appropriate bug.


Received on Friday, 4 November 2011 17:57:50 UTC