Eyevinn / moqtransport / 35594611666

77%

main: 77%

Build Type

Pull #26

github

Committed by tobbee

Commit Message

priority: apply Section 7.2 stream tiering over quic-go v0.62.0

quic-go v0.62.0 released RFC 9218-style stream priorities, so the mapping layer carried since f64823d is no longer inert. Forward SetPriority from the quicmoq adapters and give the streams the tiers the draft asks for.

draft-ietf-moq-transport-18 Section 7.2 puts the control streams highest, then the bidi request streams, then Objects. Reserving urgency 0 and 1 for the first two tiers is what makes that hold: spending the whole range on a priority number, as the mappers did, placed Objects from any subscription with subscriber priority below 96 ahead of the control streams.

Objects now map into urgency 2-5 by the top two bits of the priority number, leaving 6 spare and 7 for padding (Section 11.5). Two priorities must differ by at least 64 to be separated, where before it was 32.

The control stream takes its tier in controlStreamPair.open, and request streams in newRequestStream, the one point both the opened and the accepted ones pass through.

quic-go v0.62.0 declares go 1.26.0, so the module minimum moves with it.

Pull Request Pull Request #26: priority: apply Section 7.2 stream tiering over quic-go v0.62.0

Coverage Stats

16 of 16 new or added lines in 5 files covered. (100.0%)

1 existing line in 1 file now uncovered.

4107 of 5352 relevant lines covered (76.74%)

46.43 hits per line