feat(quic,h3): DATAGRAM frames and HTTP datagrams (RFC 9221, RFC 9297)

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
networking

Research direction

The issue names the max_datagram_frame_size transport parameter as the starting point, then the QUIC frame handling and the HTTP/3 layer, which needs a capsule protocol for HTTP Datagrams. The payload names no files or tests, so locate the existing frame and transport-parameter code first. Done means DATAGRAM frames can be sent and received, and HTTP Datagrams with capsules are parsed, with tests covering both.

Written by the indexing model from the issue text.

Description

enhancement P2: later

QUIC DATAGRAM frames (the max_datagram_frame_size transport parameter) and HTTP Datagrams with the capsule protocol aren't supported. MASQUE (CONNECT-UDP, RFC 9298) and WebTransport need them.

Dominant language
C
Stars
0
Forks
0
Avg merge
20h 4m
Merged PRs (30d)
25

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/cursed-http

All issues in public/cursed-http

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.