INFOCOM Skills
A 12-skill depth pack for IEEE INFOCOM (International Conference on Computer Communications), the IEEE ComSoc networking flagship: routing among the networking venues, the large-scale EDAS double-blind pipeline with its automated review assignment and early-reject phase, the IEEEtran two-column 10-page budget (9 pages of text with appendices counted, plus references), analytical/optimization-and-s
Skills in this plugin
12- ▌ Infocom Workflow · brycewang-stanfordUse when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
- ▌ Infocom Submission · brycewang-stanfordUse when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
- ▌ Infocom Experiments · brycewang-stanfordUse when designing or auditing IEEE INFOCOM evaluations, covering analytical results with stated and justified assumptions, simulation with a named simulator and logged seeds, testbed and measurement studies with real traffic, honest and tuned baselines, and matching evidence to the shape of each networking claim across the analysis-simulation-testbed spectrum.
- ▌ Infocom Camera Ready · brycewang-stanfordUse when preparing an accepted IEEE INFOCOM paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran final format and page budget, the IEEE electronic Copyright Form (eCF), PDF eXpress validation, the author-registration requirement, integrating reviewer-required changes without scope creep, and permanentizing any released artifact links.
- ▌ Infocom Related Work · brycewang-stanfordUse when positioning an IEEE INFOCOM submission against the networking literature across INFOCOM, SIGCOMM, NSDI, MobiCom, ICNP, and the journals (IEEE/ACM ToN, IEEE JSAC/TMC), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind on EDAS, and handling concurrent, preprint, and prior-version overlap.
- ▌ Infocom Supplementary · brycewang-stanfordUse when deciding what fits inside an IEEE INFOCOM paper's tight IEEEtran budget, covering the rule that appendices count toward the nine pages of text, the absence of a separate supplementary channel at review time, double-blind handling of any released material, and how to split an analytical or systems networking paper between the body and an optional external release.
- ▌ Infocom Writing Style · brycewang-stanfordUse when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.
- ▌ Infocom Review Process · brycewang-stanfordUse when reasoning about how an IEEE INFOCOM submission is evaluated, covering the large-scale double-blind pipeline, automated paper-reviewer assignment, the two-tier TPC and early-reject phase, the (traditional) absence of an author rebuttal, TPC discussion, and how INFOCOM's process differs from SIGCOMM/NSDI rebuttal-driven reviewing.
- ▌ Infocom Author Response · brycewang-stanfordUse when handling the IEEE INFOCOM post-submission reality — that the venue has traditionally offered no author rebuttal — covering how to write a self-defending submission, how to read and act on an early-reject, what to do after a final reject, and how to use any response window a given cycle does introduce (verify per cycle).
- ▌ Infocom Reproducibility · brycewang-stanfordUse when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
- ▌ Infocom Topic Selection · brycewang-stanfordUse when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside systems, and the modeling-vs-building axis.
- ▌ Infocom Artifact Evaluation · brycewang-stanfordUse when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.