4. EXPERIENCE
I’ve used this approach for the last 15 years to read con-ference proceedings, write reviews, do background research, and to quickly review papers before a discussion. This dis-ciplined approach prevents me from drowning in the details before getting a bird’s-eye-view. It allows me to estimate the amount of time required to review a set of papers. More-over, I can adjust the depth of paper evaluation depending on my needs and how much time I have.
5. RELATED WORK
If you are reading a paper to do a review, you should also read Timothy Roscoe’s paper on “Writing reviews for sys-tems conferences” [1]. If you’re planning to write a technical paper, you should refer both to Henning Schulzrinne’s com-prehensive web site [2] and George Whitesides’s excellent overview of the process [3].
6. A REQUEST
I would like to make this a living document, updating it as I receive comments. Please take a moment to email me any comments or suggestions for improvement. You can also add comments at CCRo, the online edition of CCR [4].
7. ACKNOWLEDGMENTS
The first version of this document was drafted by my stu-dents: Hossein Falaki, Earl Oliver, and Sumair Ur Rahman. My thanks to them. I also benefited from Christophe Diot’s perceptive comments and Nicole Keshav’s eagle-eyed copy-editing.
This work was supported by grants from the National Science and Engineering Council of Canada, the Canada Research Chair Program, Nortel Networks, Microsoft, Intel Corporation, and Sprint Corporation.