SEED 2022 Home

SEED 2022

September 26 - September 27, 2022

Held Virtually

SUBMISSIONS AND INSTRUCTIONS

SEED 2022 submission site: https://seed22.hotcrp.com

Prospective authors must submit papers electronically by the submission deadline via the conference submission website. Please make sure your submission adheres to the following guidelines.

Paper Type and Length: Please select one of the following two categories for your paper: (1) regular papers, (2) SoK papers, (3) WiP papers. Authors are also required to indicate the category of the paper as part of the submitted manuscript's title. The last line of the title should indicate the paper type by using one of the two phrases (1) Paper Type: Regular, or (2) Paper Type: SoK, or (3) Paper Type: WiP.

Papers in the WiP category with relatively shorter length (6 pages) are welcome if the contributions can be well articulated and substantiated in 6 pages. However, all submissions in the regular and SoK categories have the flexibility of using all 11 pages (excluding references).

If you can express your contributions in fewer pages than the page-limit, the PC encourages you to do so. Papers must be in a printable PDF format and must use the two-column IEEE Proceedings format. A LaTeX template is available at https://www.ieee.org/conferences/publishing/templates.html. There is no page limit for references. References must include all authors to facilitate the reviewing process (no et al.). Text must be minimum 10pt Times font. Please number the pages of your submission.

Double-blind Review: Paper submission is double-blind to reduce the reviewers' bias against the authors and/or their institutions. Thus, the submissions must not include author names or institutions. Careful writing should be used to preserve anonymity for submission. We recognize that building on your prior work may indirectly reveal your identity. Please reference your previous work in third person. Do not omit references to ensure anonymity, as this leaves reviewers unable to understand the full context. If you need to refer to another submission at SEED currently under review, please mark the reference as anonymous under submission at SEED’22, but alert the program chairs regarding this.

Concurrent Submissions: By submitting a manuscript to SEED 2022, the authors guarantee that the manuscript has not been previously published or accepted for publication in a substantially similar form in any conference, journal, or workshop. The only exceptions are (1) workshops without archived proceedings such as in the ACM digital library (or where the authors chose not to have their paper appear in the archived proceedings), or (2) venues, such as IEEE CAL, where there is an explicit policy that such publication does not preclude longer conference submissions. These are not considered prior publications. Technical reports and papers posted on public social media sites, web pages, or online repositories, such as arxiv.org, are not considered prior publications either. In these cases, the submitted manuscript may ignore the posted work to preserve author anonymity. For regular and SoK manuscripts, the authors also guarantee that no paper that contains significant overlap with the contributions of the submitted paper will be under review for any other conference, journal, or workshop during the SEED 2022 review period. Violation of any of these conditions will lead to rejection. As always, if you are in doubt, it is best to contact the program chairs. More details on the IEEE policies can be found in https://www.ieee.org/publications_standards/publications/authors/index.html

WiP submissions can be submitted concurrently to other conferences, journals, or workshops. Authors need to verify with the organizers of the concurrently submitted venue to ensure that they accept the submission. We confirm that WiP submissions will not be included in the proceedings.

Optional Supplemental Information about Revisions: Authors can upload a document listing the improvements made in response to the reviews received from a previously submitted version. Authors have two options: (1) not provide this information, or (2) provide this information, and the visibility is set to all the reviewers. The intent is to improve the efficiency of the over-burdened review process and benefit the authors who faithfully revise the paper to incorporate feedback from previous reviewers.

Author list after acceptance: Please note that the author list cannot be changed after acceptance.

Conflict of Interest Declaration: Authors must register all their conflicts on the paper submission site. Conflicts are needed to ensure appropriate assignment of reviewers. If a paper is found to have an undeclared conflict that causes a problem OR if a paper is found to declare false conflicts in order to abuse or “game” the review system, the paper may be summarily rejected. Please declare a conflict of interest (COI) with the following for any author of your paper:

Your Ph.D. advisor(s), post-doctoral advisor(s), Ph.D. students, and post-doctoral advisees, forever.

Family relations by blood or marriage and close friends, forever (if they might be potential reviewers). You are a close friend with someone if you have or would spend a night at their home if you were visiting them, or vice versa.

People with whom you have collaborated in the last five years, including

co-authors of accepted/rejected/pending papers.
co-PIs of accepted/rejected/pending grant proposals.
funders (decision-makers) of your research grants, and researchers whom you fund.

People who shared your primary institution(s) and with whom you had research interactions (including brainstorming, reading groups, etc) in the last five years.

“Service” collaborations such as co-authoring a report for a professional organization, serving on a program committee, or co-presenting tutorials, do not themselves create a conflict of interest. Co-authoring a paper that is a compendium of various projects with no true collaboration among the projects does not constitute a conflict among the authors of the different projects. On the other hand, there may be others not covered by the above with whom you believe a COI exists, for example, close personal friends. Please report such COIs; however, you may be asked to justify them. Please be reasonable. For example, you must not declare a COI with a reviewer just because that reviewer works on topics similar to or related to those in your paper. The program chairs may contact co-authors to explain a COI whose origin is unclear. We hope to draw most reviewers from the PC, but others from the community may also write reviews. Please declare all your conflicts (not just restricted to the PC). When in doubt, contact the program chairs.

Inclusive Description of Research Contributions: Please consider making your research contribution description inclusive in nature. For example, consider using gender-neutral pronouns, consider using examples that are ethnicity/culture rich, consider engaging users from diverse background if your research involves survey, etc. Best efforts should be made to make the paper accessible to visually-impaired or color-blind readers.

Ethical Guidelines:

Authors are not allowed to contact reviewers or PC members to encourage or solicit them to bid on any paper.

Authors are not allowed to attempt to sway a reviewer to review any paper positively or negatively.

Authors are not allowed to contact reviewers or PC members requesting any type of information about the reviewing process, either in general or specifically about submitted papers.

Authors are not allowed to contact reviewers or PC members to ask about the outcomes of any papers.

While a paper is under submission to SEED’22, authors may choose to give talks about their work, post a preprint of the paper to an archival repository such as arXiv, and disclose security vulnerabilities to vendors. Authors should refrain from widely advertising their results, but in special circumstances they should contact the PC chairs to discuss exceptions. Authors are not allowed to directly contact PC members to discuss their submission.

If the research identifies a vulnerability in deployed systems, researchers are expected to notify affected vendors and allow a disclosure window of at least 45 days before the results become public. The submitted version of the paper must discuss the steps taken or planned for disclosing the vulnerability.

Acknowledgements: Several ideas in this document and parts of the text have been taken from previous conferences, so we thank their program chairs. In particular, Thomas Ristenpart and Patrick Traynor (IEEESP’22), Tim Rogers and Huiyang Zhang (IISWC’21), David Kaeli and Devesh Tiwari (IISWC’20), Shan Lu and Tom Wenisch (ASPLOS’21), Luis Ceze and Karin Strauss (ASPLOS’20), Emmett Witchel and Alvy Lebeck (ASPLOS ’19), Ricardo Bianchini and Vivek Sarkar (ASPLOS ’18), John Carter (ASPLOS ’17), Yuanyuan Zhou (ASPLOS ’16), Sandhya Dwarkadas (ASPLOS ’15), Sarita Adve (ASPLOS ’14), Steve Keckler (ISCA ’14), Christos Kozyrakis (MICRO ’13), Margaret Martonosi (ISCA ’13), Onur Mutlu (MICRO ’12), and Michael L. Scott (ASPLOS ’12).

If you are uncertain whether your submission meets SEED submission guidelines, contact the program co-chairs:
Hsien-Hsin Sean Lee (leehs@fb.com) and Yuval Yarom (yval@cs.adelaide.edu.au)).