Use this to reason about review-stage strategy. Reopen the current CFP and submission page before making process claims; the mechanisms below are the SIGCOMM 2026 rendering and can change per edition.
SIGCOMM layers several author-facing stages, and reading which one you are in drives every subsequent move:
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Contribution | A networking mechanism or architecture that generalizes | A single-site tuning win with no transferable idea |
| Evaluation realism | Testbed, trace, or deployment evidence with reported tails | Simulation-only or mean-only results for a fabric claim |
| Baselines | Comparisons against the strongest deployed alternative | Straw-man baselines the mechanism is built to beat |
| Measurement rigor | Documented workload, topology, run counts, variance | Percentiles with no replication or unstated conditions |
| Clarity | A stated design principle the paper defends | A behavior described but no invariant named |
The PC mixes networking-systems builders, measurement researchers, and theory-leaning networking people; expect at least one reviewer to interrogate the evaluation setup line by line and another to ask whether the mechanism generalizes beyond the tested topology. Because SIGCOMM is the broad flagship, a paper is often read against the strongest prior work in its exact subarea, so a missing state-of-the-art baseline is caught rather than skimmed past.
[Current stage] submitted / reviews / rebuttal / revision / decision / camera-ready
[Outcome class] early reject / rebuttal / one-shot revision / accept-with-shepherd
[Decision actors] <reviewers / discussion / shepherd / chairs>
[Likely leverage] <contribution / evaluation realism / baselines / measurement / clarity>
[Forbidden moves] <identity leak / new unsupported results / dodging the issue list>
[Next response move] <one action>