NSDI '22 Call for Papers

The 19th USENIX Symposium on Networked Systems Design and Implementation (NSDI '22) will be held on April 4–6, 2022, in Renton, WA, USA.

Sponsored by USENIX in cooperation with ACM SIGCOMM and ACM SIGOPS

Important Dates

Spring deadline:

  • Paper titles and abstracts due: Thursday, March 4, 2021, 8:59 pm US PST
  • Full paper submissions due: Wednesday, March 10, 2021, 8:59 pm US PST
  • Notification to authors: Friday, June 11, 2021
  • Final paper files due: Thursday, August 26, 2021

Fall deadline:

  • Paper titles and abstracts due: Thursday, September 9, 2021, 8:59 pm US PDT
  • Full paper submissions due: Wednesday, September 15, 2021, 8:59 pm US PDT
  • Notification to authors: Wednesday, December 15, 2021
  • Final paper files due: Tuesday, March 1, 2022

Conference Organizers

Program Co-Chairs

Amar Phanishayee, Microsoft Research
Vyas Sekar, Carnegie Mellon University

Program Committee

Sangeetha Abdu-Jyothi, University of California, Irvine, and VMware Research
Fadel Adib, Massachusetts Institute of Technology
Behnaz Arzani, Microsoft Research
Anirudh Badam, Microsoft Research
Mahesh Balakrishnan, Facebook
Aruna Balasubramanian, Stony Brook University
Hitesh Ballani, Microsoft Research
Sujata Banerjee, VMware Research
Theo Benson, Brown University
Matthew Caesar, University of Illinois at Urbana–Champaign
Vijay Chidambaram, The University of Texas at Austin
Asaf Cidon, Columbia University
Angela Demke Brown, University of Toronto
Fahad Dogar, Tufts University
Giulia Fanti, Carnegie Mellon University
Rodrigo Fonseca, Microsoft Research
Manya Ghobadi, Massachusetts Institute of Technology
Soudeh Ghorbani, Johns Hopkins University
Phillipa Gill, Google
Brighten Godfrey, University of Illinois at Urbana–Champaign and VMware
Shyam Gollakota, University of Washington
Ramesh Govindan, University of Southern California
Chuanxiong Guo, ByteDance
Andreas Haeberlen, University of Pennsylvania
Kurtis Heimerl, University of Washington
Wenjun Hu, Yale University
Kyle Jamieson, Princeton University
Junchen Jiang, University of Chicago
Anuj Kalia, Microsoft Research
Anurag Khandelwal, Yale University
Ana Klimovic, ETH Zurich
Dejan Kostic, KTH Royal Institute of Technology
Franck Le, IBM Research
Kate Lin, National Chiao Tung University
Zaoxing Alan Liu, Boston University
Jay Lorch, Microsoft Research
Jonathan Mace, Max Planck Institute for Software Systems (MPI-SWS)
Harsha Madhyastha, University of Michigan
Aurojit Panda, New York University
Kyoongsoo Park, Korea Advanced Institute of Science and Technology (KAIST)
Chunyi Peng, Purdue University
Ben Pfaff, VMware Research
George Porter, University of California, San Diego
Costin Raiciu, University Politehnica of Bucharest and Correct Networks
Robert Ricci, University of Utah
Michael Schapira, The Hebrew University of Jerusalem
Stefan Schmid, Technische Universität Berlin and University of Vienna
Brent Stephens, University of Utah
Laurent Vanbever, ETH Zurich
Shivaram Venkataraman, University of Wisconsin—Madison
David Walker, Princeton University
Jia Wang, AT&T Labs
Michael Wei, VMware Research
John Wilkes, Google
Xiaowei Yang, Duke University
Minlan Yu, Harvard University
Ellen Zegura, Georgia Institute of Technology
Ying Zhang, Facebook
Yiying Zhang, University of California, San Diego
Ben Zhao, University of Chicago
Wenting Zheng, Carnegie Mellon University
Lin Zhong, Yale University
Danyang Zhuo, Duke University

Test of Time Awards Committee

Aditya Akella, University of Wisconsin–Madison
Thomas E. Anderson, University of Washington
Sujata Banerjee, VMware Research
Ranjita Bhagwan, Microsoft Research India
Jon Howell, VMware Research
Arvind Krishnamurthy, University of Washington
Jay Lorch, Microsoft Research
James Mickens, Harvard University
Jeff Mogul, Google
George Porter, University of California, San Diego
Timothy Roscoe, ETH Zurich
Srinivasan Seshan, Carnegie Mellon University
Renata Teixeira, Netflix
Minlan Yu, Harvard University

Steering Committee

Aditya Akella, University of Wisconsin–Madison
Sujata Banerjee, VMware Research
Ranjita Bhagwan, Microsoft Research India
Casey Henderson, USENIX Association
Jon Howell, VMware Research
Arvind Krishnamurthy, University of Washington
Jay Lorch, Microsoft Research
James Mickens, Harvard University
Jeff Mogul, Google
George Porter, University of California, San Diego
Timothy Roscoe, ETH Zurich
Srinivasan Seshan, Carnegie Mellon University
Renata Teixeira, Netflix
Minlan Yu, Harvard University


NSDI focuses on the design principles, implementation, and practical evaluation of networked and distributed systems. Our goal is to bring together researchers from across the networking and systems community to foster a broad approach to addressing overlapping research challenges.

NSDI provides a high-quality forum for presenting results and discussing ideas that further the knowledge and understanding of the networked systems community as a whole, continue a significant research dialog, or push the architectural boundaries of network services.


We solicit papers describing original and previously unpublished research. Specific topics of interest include but are not limited to:

  • Highly available and reliable networked systems
  • Security and privacy of networked systems
  • Distributed storage, caching, and query processing systems
  • Energy-efficient computing in networked systems
  • Cloud/multi-tenant systems
  • Mobile and embedded/sensor applications and systems
  • Wireless networked systems
  • Network and workload measurement systems
  • Self-organizing, autonomous, and federated networked systems
  • Managing, debugging, and diagnosing problems in networked systems
  • Virtualization and resource management for networked systems
  • Systems aspects of networking hardware
  • Experience with deployed networked systems
  • Communication and computing over big data on networked systems
  • Practical aspects of economics and verification applied to networked systems
  • Systems for Machine Learning (ML) and ML for Systems
  • Any innovative solution for a significant problem involving networked systems

The program committee will be diligent in ensuring that papers are in-scope and relevant to the NSDI community. If you have questions about whether your paper would be in-scope, please contact the PC chairs.

Like the last three NSDI editions, we are offering two submission deadlines, and we are providing the possibility of getting one-shot-revision decisions in lieu of rejection. To see a detailed explanation of the expected benefits from these changes, see Additional Information about Multiple Deadlines Process.

Conference Format

As the systems and networking community has grown, there has been a corresponding growth in the amount of high-quality research being done. To ensure the timely dissemination of this research, the co-chairs will work with the steering committee to ensure that the symposium program will accommodate presentations for all accepted papers. For example, talks may be shorter than in prior years, or some parts of the conference may be multi-tracked. Regardless, all accepted papers will receive equitable treatment with respect to talk length (i.e., no division of accepted papers into "short talks" and "long talks”), access to the poster session, and so on.

Two Deadlines

NSDI '22 offers authors the choice of two submission deadlines. Any paper submitted to one of these deadlines and accepted during the subsequent reviewing period will be presented at the conference and will appear as part of the proceedings. In the meantime, authors are permitted to advertise their papers as accepted by NSDI, for example listing them on CVs.

A paper submitted at the spring deadline for NSDI '22 and rejected may not be submitted again until the spring deadline for NSDI '23. A paper submitted at the fall deadline for NSDI '22 and rejected may not be submitted again until the fall deadline for NSDI '23.

One-Shot Revision

Each paper may be accepted, rejected, or given the option of one-shot revision. Such a revision decision includes a summary of the paper's merits and a list of necessary changes that are required for the paper to be accepted at NSDI. Authors may then submit a version of their work addressing those needs during the subsequent deadline. At that point, the paper will be reviewed to judge whether it addresses the requirements requested; this review will be conducted, to the extent possible, by the same reviewers as earlier. To enable this, PC members who give one-shot-revision decisions late in a year are obligated to participate as external reviewers in the following year to review those papers' resubmissions, which would be considered for the following year's conference. Papers revised and resubmitted following a one-shot-revision decision can only receive a decision of accept or reject, not revise; this is what makes revisions "one-shot."

The judgment about whether to accept a revised paper will be made as follows. Reviewers will primarily judge whether the authors have satisfied the requests accompanying the revision decision. They will also judge the resubmission on its independent merits, but should avoid rejecting it for non-fatal concerns that they could have raised during the first round of reviews. The reviewers should also ensure that the revised paper doesn't introduce new assertions without sufficient support. Unlike the shepherding process, the requested action points may include running additional experiments that obtain specific results, e.g., comparing performance against a certain alternative and beating it by at least 10%.

During the revision period, the paper is still considered under review to NSDI and therefore cannot be submitted to other conferences unless the authors first withdraw it from consideration. To make this obligation clear, authors who receive a one-shot-revision notification must, within two weeks of the notification, explicitly send an email acknowledging their participation in the one-shot-revision process. That e-mail should indicate they understand that this means the USENIX Submission Policy precludes concurrent submission to other conferences.

To make a one-shot-revision decision, reviewers must be comfortable accepting the paper if the authors make all the changes requested in it. Most notably, if a paper makes an insufficient contribution, or is incremental, then it should be rejected, not given a one-shot-revision decision. After all, the point of one-shot revision is not to produce highly-polished uninteresting papers, but rather to allow publication of exciting work that's unfortunately submitted in a form that's flawed in a way that can't be fixed with mere shepherding.

Reviewers will also be instructed to not offer a one-shot-revision option if they can't determine that the paper is adequate modulo the proposed revisions. For instance, if the paper is written so sloppily that there may be a hidden deep flaw, then the paper should be rejected, not given a one-shot-revision request to fix the inadequate writing.

Authors given a one-shot-revision decision will be sent, within a few days of the decision, detailed instructions about how to resubmit. These instructions will include the list of necessary changes that are required for the paper to be accepted. They will also explain how the authors should accompany their resubmission with auxiliary material to demonstrate how they've satisfied that list of changes. This auxiliary material will consist of (1) an additional version of the resubmission in which revision changes since the first submission are clearly marked, and (2) a separate textual explanation of the high-level differences between the two versions.

If authors receive a one-shot-revision decision but don't want to submit a revised version, they may withdraw it. In this case, they may not submit the paper to NSDI again until 11 months after the deadline they originally it submitted to.

If authors receive a one-shot-revision decision for a paper submitted to the fall deadline of NSDI '22, this gives them the option to make the requested changes and resubmit it to the next NSDI deadline, which is the first deadline of NSDI '23. If the paper is accepted then, it will appear at NSDI '23, not NSDI '22.

Operational Systems Track

NSDI '22 also solicits papers that describe the design, implementation, analysis, and experience with large-scale, operational systems and networks. We encourage submission of papers that disprove or strengthen existing assumptions, deepen the understanding of existing problems, and validate known techniques at scales or environments in which they were never used or tested before. Such operational papers need not present new ideas or results to be accepted; indeed, new ideas or results will not influence whether the papers are accepted. Note that the rules regarding submission and anonymization are different for operational systems track papers. Since the evaluation of operational systems track papers requires understanding the real-world use of the system, papers in this track will be reviewed in a more limited double-blind process. Authors' names should be withheld, as usual. However, in contrast to other papers, authors need not anonymize the content of their submission in any other way—they may keep company names, links, real system names, etc. as appropriate for the paper.

Please note that you cannot switch tracks for your paper after submission since the submission rules differ.

Authors should indicate on the title page of the paper and in the submission form that they are submitting to this track.

The final program will explicitly identify papers accepted from the operational track to distinguish papers accepted from the regular track.

What to Submit

NSDI '22 is double-blind, meaning that authors should make a good faith effort to anonymize papers. Note that the operational track papers have different rules as described above. As an author, you should not identify yourself in the paper either explicitly or by implication (e.g., through the references or acknowledgments). However, only non-destructive anonymization is required. For example, system names may be left de-anonymized, if the system name is important for a reviewer to be able to evaluate the work. Please take the following steps when preparing your submission:

  • Remove authors' names and affiliations from the title page.
  • Remove acknowledgment of identifying names and funding sources.
  • Do not provide links to your own online content. If this online content is critical to the content of your paper, please see the submission form, which allows for some forms of content upload, or contact the PC chairs.
  • Use care in naming your files. Source file names, e.g., Joe.Smith.dvi, are often embedded in the final output as readily accessible comments.
  • Use care in referring to related work, particularly your own. Do not omit references to provide anonymity, as this leaves the reviewer unable to grasp the context. Instead, a good solution is to reference your past work in the third person, just as you would any other piece of related work. If you cite anonymous work, you will need to enter the deanonymized reference(s) on the online submission form.
  • If you need to reference another submission at NSDI '22 on a related topic, reference it as follows: "A related paper describes the design and implementation of our compiler [Anonymous 2022]." with the corresponding citation: "[Anonymous 2022] Under submission. Details omitted for double-blind reviewing."
  • Work that extends an author's previous workshop paper is welcome, but the paper should (a) acknowledge their own previous workshop publications with an anonymous citation and (b) explain the differences between the NSDI submission and the prior workshop paper. The online submission form will also require authors to submit the deanonymized citation and a short explanation of the differences from the prior workshop paper.
  • Blinding is not intended to be a great burden. If blinding your paper seems too burdensome, please contact the program co-chairs and discuss your specific situation.

Submissions—as well as final papers—must be no longer than 12 pages, including footnotes, figures, and tables. Submissions may include as many additional pages as needed for references and for supplementary material in appendices. The paper should stand alone without the supplementary material, but authors may use this space for content that may be of interest to some readers but is peripheral to the main technical contributions of the paper. Note that members of the program committee are free to not read this material when reviewing the paper.

Submissions must be in two-column format, using 10-point type on 12-point (single-spaced) leading, in a text block 7" wide x 9" deep, with .33" inter-column space, formatted for 8.5" x 11" paper.

Papers not meeting these criteria will be rejected without review, and no deadline extensions will be granted for reformatting. Pages should be numbered, and figures and tables should be legible when printed without requiring magnification. Authors may use color in their figures, but the figures should be readable when printed in black and white. If you wish, you may use the template for LaTeX available on the conference paper templates page. All papers must be submitted via the submission form. Please do not email submissions.


Simultaneous submission of the same work to multiple venues, submission of previously published work, or plagiarism constitutes dishonesty or fraud. USENIX, like other scientific and technical conferences and journals, prohibits these practices and may take action against authors who have committed them. See the USENIX Conference Submissions Policy for details.

Previous publication at a workshop is acceptable as long as the NSDI submission includes substantial new material that has been developed since the publication of any earlier version. However, NSDI submissions cannot be concurrent with submission to a workshop venue. If the notification date for the workshop submission is after the submission date for NSDI, this would be considered a concurrent submission and would be rejected without review. Such concurrent submissions would have limited the possibility of substantially extending the prior work, which would violate the intent of policies allowing for extended submissions (as described in http://www.sigcomm.org/about/policies/frequently-asked-questions-faq/) See remarks above about how to cite and contrast with a workshop paper.

Authors uncertain whether their submission meets USENIX's guidelines should contact the Program Co-Chairs, nsdi22chairs@usenix.org.

Papers accompanied by nondisclosure agreement forms will not be considered. All submissions will be treated as confidential prior to publication on the USENIX NSDI '22 website; rejected submissions will be permanently treated as confidential.


At submission time, you must provide information about conflicts with PC members. A PC member is a conflict if any of the following three circumstances applies:

Institution: You are currently employed at the same institution, have been previously employed at the same institution within the past two years (not counting concluded internships), or are going to begin employment at the same institution during the review period.

Advisor: You have a past or present association as thesis advisor or advised.

Collaboration: You have a collaboration on a project, publication, grant proposal, program co-chairship, or editorship within the past two years (March 2019 through August 2021).

You must not improperly identify a PC member as a conflict if none of these three circumstances applies, even if for some other reason you want to avoid them reviewing your paper. For instance, the following are not sufficient grounds to specify a conflict with a PC member: they have reviewed the work before, they are employed by your competitor, they are your personal friend, they were your post-doc advisor or advisee, or they had the same advisor as you.

The chairs will review paper conflicts to ensure the integrity of the reviewing process, adding or removing conflicts if necessary. The chairs may reject abstracts or papers on the basis of egregious missing or extraneous conflicts. If you have any questions about conflicts, please contact the program co-chairs.

Ethical Considerations

Papers describing experiments with users or user data (e.g., network traffic, passwords, social network information), should follow the basic principles of ethical research, e.g., beneficence (maximizing the benefits to an individual or to society while minimizing harm to the individual), minimal risk (appropriateness of the risk versus benefit ratio), voluntary consent, respect for privacy, and limited deception. When appropriate, authors are encouraged to include a subsection describing these issues. Authors may want to consult the Menlo Report for further information on ethical principles, or the Allman/Paxson IMC '07 paper for guidance on ethical data sharing.

Authors must, as part of the submission process, attest that their work complies with all applicable ethical standards of their home institution(s), including, but not limited to privacy policies and policies on experiments involving humans. Note that submitting research for approval by one's institution's ethics review body is necessary, but not sufficient—in cases where the PC has concerns about the ethics of the work in a submission, the PC will have its own discussion of the ethics of that work. The PC's review process may examine the ethical soundness of the paper just as it examines the technical soundness.

Processes for Accepted Papers

If your paper is accepted and you need an invitation letter to apply for a visa to attend the conference, please contact conference@usenix.org as soon as possible. (Visa applications can take at least 30 working days to process.) Please identify yourself as a presenter and include your mailing address in your email.

Accepted papers may be shepherded through an editorial review process by a member of the Program Committee. Based on initial feedback from the Program Committee, authors of shepherded papers will submit an editorial revision of their paper to their Program Committee shepherd. The shepherd will review the paper and give the author additional comments. All authors, shepherded or not, will upload their final file to the submissions system by the final paper deadline for the conference Proceedings.

By submitting a paper, you agree that at least one of the authors will attend the conference to present it. If the conference registration fee will pose a hardship for the presenter of the accepted paper, please contact conference@usenix.org.

Paper publishing schedule: A list of papers accepted from the spring submissions will be posted on the NSDI '22 website in August. In December, when the full program is available, paper titles will be posted for all accepted papers from both the spring and fall deadlines. At this time, the spring final paper PDFs will also be posted, accessible only to registered attendees. In April, the full Proceedings, as well as all of the final paper PDFs, will be posted.

All papers will be available online to registered attendees before the conference. If your accepted paper should not be published prior to the event, please notify production@usenix.org. The papers will be available online to everyone beginning on the first day of the conference.

Best Paper Awards

Awards will be given for the best paper(s) at the conference.

Community Award

To encourage broader code and data sharing within the NSDI community, the conference will also present a "Community Award" for the best paper whose code and/or data set is made publicly available by the final papers deadline. Authors who would like their paper to be considered for this award will have the opportunity to tag their paper during the submission process.