Below you can find the planned schedule and assignment of papers that students will present during the theory classes of the last two weeks of the course (May 16 - May 27). 

Important Notes: 

- Presentations will last 17 minutes, followed by 5 minutes for Questions and Answers.

- To maximize fairness, we have decided to assign papers to groups and papers to dates randomly. Groups are free to pairwise swap papers, provided that i) papers are presented according to the currently planned dates, AND ii) they inform Prof. Rodrigo Rodrigues via email at least one day in advance. 

 - While it is OK to borrow text or figures from the original presentations from the authors, this is discouraged and must be properly credited by indicating with >=20 pt font, for each line of text or figure borrowed, “source: authors’ presentation”. 

 - The presentation must clearly convey the technical contents of the paper, explaining:
  •  what is the problem being solved? 
  •  what are the challenges? 
  • what makes the problem difficult? 
  •  what are the key insights/techniques/lessons used to address those challenges? 
- In addition, the presentation must include a personal critique in the style of a paper review, covering at least the following:
  • is this a relevant problem, for which it is important to find a solution? 
  • is the solution original? 
  • are the ideas novel and insightful? 
  •  is the solution technically sound? 
  • does it adequately solve the problem? 
  •  did the authors demonstrate through an experimental evaluation the good and bad points about the solution? 
 More info on how to review a paper:

Schedule of papers' presentations

May 17

- Consensus in a Box: Inexpensive Coordination in Hardware,
Group: 8

- Sieve: Cryptographically Enforced Access Control for User Data in Untrusted Clouds,
Group: 6

- Neither Snow Nor Rain Nor MITM ... An Empirical Analysis of Email Delivery Security,
Group: 13

- Moving Fast with Software Verification,
Group: 11

May 20
- Dynamo: Facebook’s Data Center-Wide Power Management System,
Group: 7

- Cloak of Visibility: Detecting When Machines Browse A Different Web,
Group: 3

- SoK: Research Perspectives and Challenges for Bitcoin and Cryptocurrencies,
Group: 1

- Revisiting Memory Errors in Large-Scale Production Data Centers: Analysis and Modeling of New Trends from the Field
Group: 14

May 24

- Visigoth Fault Tolerance.
Group: 4

- Using ARM TrustZone to Build a Trusted Language Runtime for Mobile Applications, 
Group: 5

- REAP: Reporting Errors Using Alternative Paths,
Group: 2

May 25 at 3:30pm

- Shielding applications from an untrusted cloud with Haven,
Group: 10

- OnionBots: Subverting Privacy Infrastructure for Cyber Attacks,
Group: 12

Under-Constrained Symbolic Execution: Correctness Checking for Real Code. David A. Ramos and Dawson Engler.
Group: 9