Demo Data from EDBT 2026 / reviewers in the wild / expert
Naveenraj Muthuraj
dblp:389/2491
· DBLP profile ↗
2ranked-venue papers
2as first author
2since 2021 · last 2024
0009-0008-0530-6128ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 2 · 2 first-author · 2 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer networks
2 papers |
Transport protocols and congestion control · 61% Network measurement and analytics · 30% Internet architecture and protocols · 9% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Transport protocols and congestion control
QUIC |
1.5 | 2 | 2024 | Poster: How much of the Web Cares about QUIC's Anti-ossification Features? · IMC 2024 Replication: "Taking a long look at QUIC" · IMC 2024 |
Network measurement and analytics › network performance measurement
protocol performance measurement |
0.8 | 1 | 2024 | Replication: "Taking a long look at QUIC" · IMC 2024 |
Methods — techniques the papers use, named apart from their topics
replication study · 0.8measurement · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | Replication: "Taking a long look at QUIC"abstractQUIC, a rapidly evolving protocol, has gained prominence with its standardization and increased adoption as HTTP/3 on the World Wide Web. Originating from Google in 2014, QUIC has seen significant changes in transitioning from Google QUIC (gQUIC) to an IETF standard in 2021. Understanding the performance of the current version of QUIC in comparison to its predecessors is crucial given its evolution and widespread adoption. Naveenraj Muthuraj, Nooshin Eghbal, Paul Lu |
IMC | 1 |
| 2024 | Poster: How much of the Web Cares about QUIC's Anti-ossification Features?abstractQUICv2 and the "Greasing the QUIC Bit'' have features designed to prevent the ossification (aka slowed progress in evolution) of the QUIC protocol. Historically, network middleboxes can become reliant on, for example, specific values or uses of header fields in QUIC packets. When changes are made to the fields, even though allowed by the specifications or for a new version of QUIC, middleboxes can negatively impact valid traffic or force a fallback to an older version of the protocol. Naveenraj Muthuraj, Paul Lu |
IMC | 1 |