Domain Reliability status

[Alexey Baranov]

Hi chromium-dev, net-dev,

 

Quite a long time ago I saw google doc on one of these mailing lists, describing Domain Reliability feature. We (yandex) find this feature really fascinating. AFAIU it is now enabled in chromium by default, but only for pre-defined (mostly google) list of sites (so-called baked-in configs). The original document mentioned (can't find a link:( ) that there should be a way for site to announce it has domain reliability config. What are the plans about it? And while it is not ready, is it possible to include some third-party hosts (in our case, yandex-related) into chromium baked in config list? Will chromium team accept such CL?

 

Thanks in advance!

[Siddharth Vijayakrishnan]

Alexey, 

We've been iterating on the W3C spec for this : http://www.w3.org/TR/navigation-error-logging/ and I think we have enough consensus to get this to an Intent to Implement right now.  Stay tuned ..

--
You received this message because you are subscribed to the Google Groups "net-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.
To post to this group, send email to net...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/161931426030640%40webcorp01g.yandex-team.ru.

[Ryan Sleevi]

+ttuttle and igrigorik

> --
> You received this message because you are subscribed to the Google Groups "net-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.
> To post to this group, send email to net...@chromium.org.
> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/161931426030640%40webcorp01g.yandex-team.ru.

There is still active concern on security, privacy, maturity, and stability of the APIs in question, which is why we have been recalcitrant to expose it beyond a small subset, so that we can better refine the spec.

That is, the compatibility risk (as described on http://www.chromium.org/blink#TOC-Policy-for-shipping-and-removing-web-platform-API-features ) is still fairly high, but we're working to reduce that.

https://w3c.github.io/network-error-logging/ is the spec in question. It would be great to get more feedback from other UAs to work through these risks.

[Ilya Grigorik]

We've just published the FPWD of "Network Error Logging": 

- http://www.w3.org/TR/2015/WD-network-error-logging-20150305/

- https://github.com/w3c/network-error-logging/

Re, maturity/compatibility: we've been iterating on the spec on public-webperf and above draft is the result of feedback from UA's (IE is "positive"; FF has been quiet so far), monitoring vendors, large sites, etc. That said, more feedback is always welcome! Alexey: please take a look at above link and let us know (public-web-perf@, or open an issue on GH repo) if you have any questions, suggestions, etc.

ig

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/CACvaWvZCccjyMvcGS2p2ChLEg%2BeJ3hOXb9C5xB%3DXNc6vJZxK3w%40mail.gmail.com.

[Alexey Baranov]

+ igrigorik@

Thanks everyone for the answers and links to the draft! This is great that this feature is on the way to become web standard. We'll definitely look at it.

 

The last thing to ask is whether it is possible to add some (yandex) hosts to current domain reliability baked-in configs for experiments. Received data would help us to understand better what we may want from that API (as a site owner).

 

11.03.2015, 18:34, "'Ilya Grigorik' via net-dev" <net...@chromium.org>:

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/CADXXVKqdzjAqZXyOuGn3SRuVZCTUD8atjECS4NEMgbTyELBuaw%40mail.gmail.com.

[Chris Bentzel]

re: baked in configs

I think there's a couple options:

  a) Putting configs inside of Yandex browser, but not upstreaming to Chromium repo.

  b) Putting configs inside of Chromium but not necessarily be used by any Chromium-based browser.

  c) Putting configs inside of Chromium and also in Chrome by default.

a) is definitely your call.

b) and c) seem OK up front, but we don't have a clear acceptance policy right now. If you're interested in that (sounds like you are) I'll try to loop in appropriate folks about making the call there.

-------

Also: would you be providing your own collection service or do you expect to use the Google ones that can be seen in the existing baked-in configs?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/24011426116561%40webcorp01g.yandex-team.ru.

[Alexey Baranov]

 

 

14.03.2015, 16:04, "Chris Bentzel" <cben...@chromium.org>:

re: baked in configs

 

I think there's a couple options:

 

  a) Putting configs inside of Yandex browser, but not upstreaming to Chromium repo.

  b) Putting configs inside of Chromium but not necessarily be used by any Chromium-based browser.

  c) Putting configs inside of Chromium and also in Chrome by default.

 

a) is definitely your call.

we'll doing that also.

 

 

b) and c) seem OK up front, but we don't have a clear acceptance policy right now. If you're interested in that (sounds like you are) I'll try to loop in appropriate folks about making the call there.

Sure, we are interested:)

 

 

-------

 

Also: would you be providing your own collection service or do you expect to use the Google ones that can be seen in the existing baked-in configs?

Yes, we're building our own service and would like to use it if that will be acceptable in chrome. We'll also appreciate any tips and/or caveats you'll find appropriate to share about building such service. Optimal number of different collectors and their locations, for instance... why not just use anycast and so on.

[Chris Bentzel]

After further thought, we'd like to avoid adding additional baked-in configs into Chromium. 

We plan to be moving towards a standards-based solution soon - Network Error Logging, mentioned earlier in the thread by Ilya. Ideally we'll be able to deprecate Domain Reliability soon in Chromium in favor of that approach. Adding additional baked-in configs, particularly from more organizations, will make that deprecation harder.

It sounds like you'll still be adding baked-ins to Yandex browser for the time being. Would definitely appreciate any feedback on the Network Error Logging spec based on your experience using it.  

[faste...@gmail.com]

Is there a bug already filed for the progress on implementing Network Error Logging? Will it show up on chromestatus.com?

Thanks!

[Alexey Baranov]

Sounds totally reasonable, thanks anyway!

 

16.03.2015, 13:00, "Chris Bentzel" <cben...@chromium.org>: