envoyproxy/envoy

Feature request: network quality estimator support

Open

#8,425 opened on Sep 29, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
design proposalhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: Feature request: Network quality estimator support

Description:

For many applications, it is important to know the network quality of each client. eg, when you watch a video on youtube, it displays different quality (1080p, 720p, 360p...), if your network quality is good, then 1080p, if weak, then 360p. This feature depends on network quality estimator. Now on client side, there are some implementations, see https://chromium.googlesource.com/chromium/src/+/master/net/nqe.

I'd like to see network quality estimator support in envoy, then, the application server side can get network quality of each client and decides which quality of the resources(videos, images) to dispatch for the given request, It will be great for the developers of the applications.

Thanks for your time to take a consideration!

[optional Relevant Links:]

Any extra documentation required to understand the issue. Please open this URL by Chrome: https://googlechrome.github.io/samples/network-information/index.html Example output:

         type: undefined
     downlink: 2.3Mb/s
          rtt: 100ms
  downlinkMax: undefinedMb/s
effectiveType: 4g
     saveData: false

Contributor guide

Research direction
Investigate the Chromium NQE implementation and propose a design for integrating network quality estimation into Envoy's filter chain. Focus on the client side metrics (RTT, downlink) and how to expose them to server side filters.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++HTTP proxy concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40