Without quotation or SIGNIFICANT paraphrasing, the use of ANY sentence from other people's work (e.g., paper, article, Internet document, etc), even with citation, in your paper constitutes plagiarism. No exception. Paraphrasing needs to be significant. Trivial paraphrasing other people's sentence still constitutes plagiarism.

Without quotation or paraphrasing or modification, any sentence/example/figure from our own prior papers either published or intended for future publication, no matter what section the the sentence is from and no matter the prior paper has been published or not, is strictly prohibited from being used in any submission of a different paper. Zero tolerance, period, no exceptions. Even for a submission addressing the same issue as our own prior paper, we have to rewrite the introduction, related work, etc, at least paraphrasing. For text that a slight change may alter the precise meaning, such as the definition of FDDs, we must use quotations. Paraphrasing includes the use of different words/notations. Any sentence that is copied from our own different paper and that you find no solution to paraphrase must be reported to me for resolution. This rule MUST be strictly enforced by each of you in preparing your draft. Each of you needs to read the article "Avoiding plagiarism, self-plagiarism, and other questionable writing practices: A guide to ethical writing".

We will have group meetings from 09/11 to 12/04 every Friday 2-7. We will try to finish before 7 of course. The room is EB 3112. In each meeting, one student needs to give a long presentation of 45 minutes (following 15 minutes discussion) and each other student gives a short presentation of 15 minutes. We will have a total of 12 meetings.

The long presentation requires my approval for the paper you choose at least one week before your presentation. You may also choose to present your own paper, but you need my approval as well. You should choose the paper from the following conferences: Sigcomm, Infocom, NSDI, Usenix Annual, Usenix security, SOSP, IMC, ANCS, CoNext, NDSS, Sigmetrics, S&P, ICNP, DSN, ICDCS, Mobicom, Mobihoc, etc. For long presentations, you need to do the following:
1. Find a top conference paper that is close to your research.
2. Read the paper in depth.
3. Prepare detailed slides.
4. Commit your slides to SVN: Seminar/2009Fall/"date". For example, for September 11, you need to commit your slides to Seminar/2009Fall/0911 before the meeting.

The short presentations do not require my approval. The requirement is that the paper should address a NEW problem, at least new to you. The goal of the short presentations is to expand our vision and get to know what problems that other people are working. The paper that you choose ideally should be from the above conferences, but you can choose from other conferences as well. To prepare the short presentation, you need to do the following:
1. Find a recent paper from a top conference and the paper should address a new and exciting problem. The problem should be related to your research. Again, the main criteria is that the PROBLEM MUST BE NEW.
2. Read the introduction and get to know the problem and motivation well. You do not need to read the paper in depth.
3. Prepare a roughly 5-page slide that show the background, the motivation, and the problem. You can also include one slide that briefly talks about the solution in the paper.
4. Commit your slides to SVN: Seminar/Spring2009/"date". For example, for Jan. 21, you need to commit your slides to Seminar/Spring2009/0121 before the meeting.

For the short presentation, you can choose to present you own work soliciting feedbacks. Be sure that you can justify your need of soliciting feedbacks. Please do not use this as a way to save effort of reading a paper.

You need to update from SVN server, you will see a directory called Seminar/2009Fall. In this directory, you will see a file ScheduleAndTopics.tex. Please choose 1 day that you want to make long presentations. After you fill in your name, please commit to SVN. So, act fast, first come first serve. For short presentations, you need to fill in your paper title before meeting. First come first serve. I suggest senior students choose early dates and new students to choose later days.

When you edit the references (.bib files), please follow the following rules.

• Use JabRef to add and edit entries to your .bib files.
• Use "\Proc.", "\Conf.", and "\Inte." to denote "Proceedings of the", "Conference", and "International" respectively. And add the following three commands in your major .tex file.
  \newcommand{\Proc}{Proceedings of the }
  \newcommand{\Conf}{Conference }
  \newcommand{\Inte}{International }
  If you want to save space for your paper, you can replace three above commands by
  \newcommand{\Proc}{Proc. }
  \newcommand{\Conf}{Conf. }
  \newcommand{\Inte}{Int. }
• Use full journal names instead of short names.
• Use short names of top conferences, such as Sigcomm, Infocom, Sigmetrics, etc..
• For any acronym of all capitalized letters, you must put them in curly brackets. Examples: {TCAM}, {SRAM}, {ACM}, and {IEEE}.
• Do not use publisher
• Do not add a year in a booktitle.

• Configure tex editors to pass IEEE PDF eXpress when error reports said "Font XXX is not embedded"
  1. For WinEdt users, you can configure the PS2PDF command line options at menu "Options->Execution Modes...", click "ps2pdf" on the left list box, then change the option "Switches" to the following command line:
  -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -r600 -dCompatibilityLevel=1.4 -dPDFSETTINGS=/printer -dMaxSubsetPct=100 -dSubsetFonts=true -dEmbedAllFonts=true
  2. For TeXnicCenter users, you can configure the PS2PDF command line options at menu "Build->Define Output Profiles...", click LaTeX=>PS=>PDF on the left-size list box, then click Postprocessor tag, click the "Ghostscript (ps2pdf)" entry in the list box on the right. The "Arguments" box on the bottom should be put with the following command line options:
  -sPAPERSIZE=a4 -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/printer -dMaxSubsetPct=100 -dSubsetFonts=true -dEmbedAllFonts=true -sOutputFile="%bm.pdf" -c save pop -f "%bm.ps"

• Email the weekly report before Monday 8:00 AM.

• When you are studying a problem, you should do comprehensive literature research. Particularly, you need to check the related papers in IEEE Digital Library, ACM Digital Library, CiteSeerX, and Google Scholar.

• Please check the webpage http://www.cse.msu.edu/?Pg=32&Col=2#a2_3_1

• Download tortoiseSVN from http://tortoisesvn.tigris.org/
• Doubleclick on the installer file and follow the instructions.
• To obtain a working copy you need to do a checkout from a repository.
  Select a directory in windows explorer where you want to place your working copy.
  Right click to pop up the context menu and select the command TortoiseSVN->Checkout..., which brings up a dialog box.
• Enter URL of repository: svn://tiger.cse.msu.edu, then click ok.
• Enter your username and password.

Attention:

• Sending the changes you made to your working copy is known as committing the changes. But before you commit, you have to make sure that your working copy is up to date. You can either use TortoiseSVN->Update directly. Or you can use TortoiseSVN->Check for Modifications first, to see which files have changed locally or on the server.
• DO NOT change the password that I send you because even you change it I can see it and I do not want to know any of your passwords.

• Please check the webpage http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-rename.html

• Only the files that you created such as .tex, .txt, .eps, .ppt, etc.
• Please do not upload any computer automatically generated files such as .dvi, .ps. .pdf (except for figure pdf files), .bak, .log, .blg, .bbl, .aux, etc.

This instruction assumes that you are using putty for ssh.

• At putty configuration, put 'arctic.cse.msu.edu' in the Host Name field.
• Click the category Connection -> SSH -> Tunnels.
• Input '3690' in the source port field.
• Input 'tiger.cse.msu.edu:3690' in the destination field.
• Click add.
• Click the category Session.
• Input 'arctic' in the saved sessions field.
• Click Save.
• Click Open.
• Log into arctic with your CSE account name and password.

After you follow the above steps, the tunnel profile has been created.

When you set up SVN remotely, use 'localhost' as the host name instead of tiger.cse.msu.edu. Putty will forward the request to tiger through the tunnel.

• Please check the webpage http://www.cse.msu.edu/pubs/submit.php