envoyproxy/envoy

http2: add per connection(stream 0) HTTP/2 METADATA frames

Open

#15,608 opened on Mar 22, 2021

View on GitHub
 (14 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/httpdesign proposalhelp wanted

Repository metrics

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

Description

Description: Envoy added per stream metadata frame #2394

It's a naive requirement to extend the METADATA frame support to stream 0.

Below metadata fit per connection metadata category.

  1. NodeInfo: the node info is supposed to be stable during the life of the connection.
  2. Connection trace context.

Where to put the new config? A ConnectionMetaData message and field within Http2ProtocolOptions. This option lives in both client and server http/2 connections.

Is anyone feel this useful?

CC @htuch @alyssawilk

Contributor guide

Research direction
Study the existing per stream METADATA frame implementation in Envoy (#2394). Understand the Http2ProtocolOptions and how to add a ConnectionMetaData message. Design the config and code changes for stream 0 metadata.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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/2Envoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20