Proposing changes to Navigation Error Logging

Hi,

I'd like to propose a few changes to the Navigation Error Logging draft
spec (
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html
):

1. I'd like to allow more than one error report to be uploaded at once, and
allow the browser to delay that upload to collect multiple reports. When a
page is failing to load, users will often try multiple times, and it would
reduce server load if the error reports could be sent together.

2. Format-wise, to support that, instead of sending a single entry as a
JSON dictionary, I'd like to send a dictionary with a single entry called
"entries", with an array of entries. (I'm suggesting a dictionary so that
future versions of the spec can add additional fields; the server would be
expected to ignore unknown keys in the dictionary.)

3. I'd like to allow the user-agent to retry the uploads if they fail. If
the issue is a transient network issue (i.e. a route is flapping), it's a
waste to throw out the error report just because the network was still
glitched the first time the upload was attempted.

4. I'd like to figure out a way to support logging errors involving
requests that were not top-level navigations. There are plenty of other
things that can fail to load that the site owner might not necessarily have
control over. (For example, Facebook might want to know when parts of their
social plugin fail to load, even if they are not hosted on a site where
Facebook can add an error handler.)

Thoughts?

Thanks,

ttuttle