The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5

commit 880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5
Author: tbansal <tbansal@chromium.org>
Date: Sat Mar 25 04:44:25 2017

Expose connection subtype from NetworkChangeNotifier

It will be consumed by NQE in the next CL.

BUG= 704998 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

Review-Url: https://codereview.chromium.org/2776523003
Cr-Commit-Position: refs/heads/master@{#459638}

[modify] https://crrev.com/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5/net/android/network_change_notifier_android.cc
[modify] https://crrev.com/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5/net/android/network_change_notifier_android.h
[modify] https://crrev.com/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5/net/base/network_change_notifier.cc
[modify] https://crrev.com/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5/net/base/network_change_notifier.h
[modify] https://crrev.com/880e49e7bf7d6d11f23d7d4dcd8e2e21b9c142b5/net/base/network_change_notifier_unittest.cc

status?

The last CL exposed the subtype information from NCN. Next step is to collect network quality data sliced by subtype. If the analysis shows good correlatio between subtype and network quality, then start the experiment in which NQE actually makes use of the subtype information.

Refreshed during triage.

Refreshed during triage.

Refreshed during triage.

 Issue 696140  has been merged into this issue.

At the minimum, we should use connection subtype information  to establish an upper bound on the network quality.

Refreshed during triage. Any updates? Is there still any plan to do this?

Yes, I still want to do this.