grafana/k6

Support for QUIC protocol

Open

#238 opened on Jun 6, 2017

View on GitHub
 (6 comments) (3 reactions) (0 assignees)Go (30,564 stars) (1,537 forks)batch import
featuregood first issue

Description

Hi

As discussed briefly in Slack, it'd be great to get support for the QUIC transport protocol (currently an IETF draft though has a dedicated working group and very wide support so is extremely likely to be ratified before too long):

There's a potentially helpful QUIC lib for Go which is used by Caddy - quic-go (MIT license).

QUIC is UDP-based so this might cause some issues/complexity and is worth calling out in docs as folks will need to ensure they allow udp:443 from load gen(s) to server(s)/LBs.

Please let me know if you need any more info from me.

Cheers

Contributor guide

Tech stack
go
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.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programmingNetwork protocols
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Research the QUIC protocol and the quic go library (MIT license). Investigate how k6's current architecture handles HTTP/1.1 and HTTP/2, and determine the changes needed to support QUIC as a transport. Key areas: replacing TCP with UDP for QUIC, integrating quic go into the existing connection management, and updating the documentation to note UDP port requirements. Look at the existing codebase structure, particularly the net/ and lib/ directories, to identify integration points.