SIGCOMM Related Work
Use this to audit novelty and placement. SIGCOMM is the broad networking flagship, so a paper
is read against the strongest prior work in its exact subarea — and against results scattered
across sibling venues. Reopen the current CFP for concurrent-submission and anonymity rules
before advising.
Positioning checks
- Separate the mechanism you contribute from engineering polish: a new protocol, transport
signal, forwarding architecture, measurement-driven design, or programmable-data-plane
technique.
- Sweep the whole networking literature, not just SIGCOMM: the nearest prior work may sit in
NSDI, MobiCom, CoNEXT, IMC, SIGMETRICS, INFOCOM, or a journal like IEEE/ACM Transactions on
Networking. A bibliography that cites only SIGCOMM signals a narrow read.
- Prove each placement. Verify the venue and year on dblp and the ACM DL before you assert
it; do not rely on memory for where a famous result appeared.
- Distinguish main-track proceedings from CCR editorial notes — OpenFlow's famous CCR
note is not a SIGCOMM conference paper, and citing it as one is a checkable error.
- Handle concurrent and prior versions honestly, and keep every self-citation phrased so
double-blind review survives.
Venue-coverage table
| Literature lane |
Typical venues |
What SIGCOMM reviewers check |
| Networking design flagships |
SIGCOMM, NSDI, CoNEXT |
Whether the nearest deployed mechanism is compared or distinguished |
| Wireless / mobile |
MobiCom, SIGMOBILE venues |
Whether relevant PHY/mobility work is acknowledged when adjacent |
| Measurement |
IMC |
Whether the motivating measurement rests on the right prior characterizations |
| Performance analysis |
SIGMETRICS |
Whether known models/bounds are credited |
| Archival journals |
IEEE/ACM ToN, JSAC |
Whether classical results are not being rediscovered |
A missing state-of-the-art comparison from the right venue is a recognizable SIGCOMM reject
pattern that benchmark strength alone does not repair.
The misattribution guard
Before citing "X appeared at SIGCOMM YYYY":
1. Find it on dblp.org/db/conf/sigcomm/ -> confirm the edition and page range
2. Confirm ACM DL lists it in the SIGCOMM conference proceedings, not CCR editorial
3. Rule out the sibling: Hedera is NSDI, RED is ToN, BBR is CACM
4. If unresolved -> mark 待核实 and do not assert the venue
Positioning vignette
A paper proposes a data-center transport that schedules flows in the fabric. Its nearest
neighbors: an earlier SIGCOMM congestion-signal paper (DCTCP), a fabric-scheduling paper in the
same lineage (pFabric), and an NSDI flow-scheduling system that is often confused with it. The
novelty sentence should name all three contrasts — a different signal than the first, a
different scheduling granularity than the second, and a design rather than the deployed-system
framing of the NSDI neighbor — with each venue verified.
Concurrent-work judgment calls
- Independently concurrent work at another venue: cite neutrally, state the technical
difference, and avoid priority claims reviewers cannot verify under blinding.
- Your own prior workshop or preprint version: cite in a blind-safe third person and confirm
the current CFP's stance on overlap before relying on it.
- When a venue's archival status is unclear, declare the overlap in the submission rather than
gambling on a chair's reading.
Output format
[Eligibility] clear / needs declaration / risky
[Closest venues] <SIGCOMM / NSDI / MobiCom / CoNEXT / IMC / journal>
[Nearest 3 works] <work -> distinction, each venue verified>
[Misattribution risk] <CCR-vs-main-track / sibling-venue traps checked>
[Novelty sentence] <SIGCOMM-ready mechanism contrast>
1---2name: sigcomm-related-work3description: Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.4---56# SIGCOMM Related Work78Use this to audit novelty and placement. SIGCOMM is the broad networking flagship, so a paper9is read against the strongest prior work in its exact subarea — and against results scattered10across sibling venues. Reopen the current CFP for concurrent-submission and anonymity rules11before advising.1213## Positioning checks1415- Separate the **mechanism** you contribute from engineering polish: a new protocol, transport16 signal, forwarding architecture, measurement-driven design, or programmable-data-plane17 technique.18- Sweep the whole networking literature, not just SIGCOMM: the nearest prior work may sit in19 NSDI, MobiCom, CoNEXT, IMC, SIGMETRICS, INFOCOM, or a journal like IEEE/ACM Transactions on20 Networking. A bibliography that cites only SIGCOMM signals a narrow read.21- **Prove each placement.** Verify the venue and year on dblp and the ACM DL before you assert22 it; do not rely on memory for where a famous result appeared.23- Distinguish **main-track proceedings** from **CCR editorial notes** — OpenFlow's famous CCR24 note is not a SIGCOMM conference paper, and citing it as one is a checkable error.25- Handle concurrent and prior versions honestly, and keep every self-citation phrased so26 double-blind review survives.2728## Venue-coverage table2930| Literature lane | Typical venues | What SIGCOMM reviewers check |31|---|---|---|32| Networking design flagships | SIGCOMM, NSDI, CoNEXT | Whether the nearest deployed mechanism is compared or distinguished |33| Wireless / mobile | MobiCom, SIGMOBILE venues | Whether relevant PHY/mobility work is acknowledged when adjacent |34| Measurement | IMC | Whether the motivating measurement rests on the right prior characterizations |35| Performance analysis | SIGMETRICS | Whether known models/bounds are credited |36| Archival journals | IEEE/ACM ToN, JSAC | Whether classical results are not being rediscovered |3738A missing state-of-the-art comparison from the *right* venue is a recognizable SIGCOMM reject39pattern that benchmark strength alone does not repair.4041## The misattribution guard4243```text44Before citing "X appeared at SIGCOMM YYYY":45 1. Find it on dblp.org/db/conf/sigcomm/ -> confirm the edition and page range46 2. Confirm ACM DL lists it in the SIGCOMM conference proceedings, not CCR editorial47 3. Rule out the sibling: Hedera is NSDI, RED is ToN, BBR is CACM48 4. If unresolved -> mark 待核实 and do not assert the venue49```5051## Positioning vignette5253A paper proposes a data-center transport that schedules flows in the fabric. Its nearest54neighbors: an earlier SIGCOMM congestion-signal paper (DCTCP), a fabric-scheduling paper in the55same lineage (pFabric), and an NSDI flow-scheduling system that is often confused with it. The56novelty sentence should name all three contrasts — a different signal than the first, a57different scheduling granularity than the second, and a design rather than the deployed-system58framing of the NSDI neighbor — with each venue verified.5960## Concurrent-work judgment calls6162- Independently concurrent work at another venue: cite neutrally, state the technical63 difference, and avoid priority claims reviewers cannot verify under blinding.64- Your own prior workshop or preprint version: cite in a blind-safe third person and confirm65 the current CFP's stance on overlap before relying on it.66- When a venue's archival status is unclear, declare the overlap in the submission rather than67 gambling on a chair's reading.6869## Output format7071```text72[Eligibility] clear / needs declaration / risky73[Closest venues] <SIGCOMM / NSDI / MobiCom / CoNEXT / IMC / journal>74[Nearest 3 works] <work -> distinction, each venue verified>75[Misattribution risk] <CCR-vs-main-track / sibling-venue traps checked>76[Novelty sentence] <SIGCOMM-ready mechanism contrast>77```
brycewang-stanford