A "blueprint" for the Call for Papers Summer 99 (rev 7/24/2002) (rev 7/2/2003) 0) The Call for Papers will be distributed in many forms: * email msgs by the publicity chair * on the web (ideally with web page design, but that's an evolving activity) * 1 page (?2sides) handouts/flyers for the previous year's conference * optional handouts/flyers to distribute at other conferences or mail to key individuals * optional mailer to a subset of ACM subscribers (see the publicity web pages) NOTE: in sigcomm 2003 we chose NOT to mail hardcopy 1) Needs to be distributed at the previous year's conference (this may be just a draft, without all of the Prog. Comm. names, .... or without the final design) 2) Ideally at the same time, the cfp camera-ready original is given to ACM for printing and then mailing. (SIGCOMM99 was mailed out mid October which was a few weeks late.) The publicity chair should work with the ACM program director to decide what mailing labels to use, and how many extras to make for distribution to conferences and TPC sites, etc. I suggest that you aim to send it to ACM by Sept 15th. 3) Ideally, the web and any paper version of the CFP should have a striking design (if so, then it has historically been designed to relate to the location). While a nice design is preferable, work with your treasurer to see how much you can spend. This cost can easily exceed what the budget can tolerate. Look at the 2000,2001 designs for ideas. Also look at how the logo is used on the conference proceedings. Other design issues for paper and web: a) Think about what it will look like when it is printed out from the web page in black/white. b) paper --- typically has been white glossy since 97. If you have another concept, work with the SIGCOMM program director on costs and to order the paper ahead of time. c) Self mailer: set aside at least 1/3 of the cfp for addressing space (return address, postage info). d) Think about how it will look when folded, and also what it will look like taped to a wall. 4) Contents of an emailed or paper CFP (and contents of several web pages) a) location (city at least, plus ideally hotel or University) b) dates (written in the international style) for both the conference and the tutorials c) URL must be in this format: (www.acm.org/sigcomm/sigcomm2002) For other conferences besides the main sigcomm conference please do use an ACM URL (or a permanent one, even USENIX, if the conference is co-sponsored by USENIX) d) conference committee contact info at least the general chair(s), PC chairs, tutorial chair, workshop chair, (it would be nice to include as many of the conference committee as you can) e) Program Committee (See SIGCOMM TAC for more info) f) submission deadline dates: (these are NON-TRIVIAL decisions) have to be carefully coordinated with WHEN the advance program should be mailed out, and if you want to combine the PC mtg with some other event? I'll omit most of my advice here for now, and just say, that we have recently made the tutorial deadline after the paper deadline. PS - it takes longer to get the advance program to the printers than one would imagine, so be careful of when your notification of acceptance is (if you produce a hardcopy Advance Program). The deadline for SIGCOMM 2003 workshop proposals should be moved earlier for subsequent years, such that there is time to publicize the Call for Papers for the accepted workshops AND to finalize the workshop programs a bit earlier than we did in 2003. g) SIGCOMM award winner contact info: always check with the SIGCOMM chair to confirm info h) Are you soliciting anything new this year???? if so, highlight it. (such as workshop proposals, poster sessions, ....) i) student paper award, j) if you already have sponsors, please do include their logos k) we could include the announcement of student travel grant.... for more info see web page... l) ACM logo m) SIGCOMM logo n) areas of interest.... o) explicit warning from the SIGCOMM TAC about originality must be original material presenting ideas and results that have not been previously published nor are currently under review by another conference or journal. Any previous or simultaneous publication of related material should be explicitly noted in the submission p) student poster session (clarify if it is for students or is it open) 5) Tutorial descriptions (full-day is the most cost effective) Deadline background: In 98 - 2001 we had the tutorial proposal deadline AFTER (currently 2 weeks) the paper submission deadline. This was designed to allow people time to finish their papers and THEN think about making a tutorial proposal. (check with the previous tutorial chair) 6) Workshops officially included in the SIGCOMM adv. prog: Re - the workshop solicitation. Here's a bit of history.... The only workshops that SIGCOMM9x has officially sponsored are the workshops that were in 94(London by McAuley) and 95(Boston-Middleware topics- by Barry Leiner). Workshops such as one at Xerox Parc in 96 and Reliable Multicast and NS in 97 were not official (just friends of...). The workshops in 94/95 WERE actually announced in the call for papers, while the call-for-papers for 96/97 just requested proposals, but no contact person was provided. And for 96/97, you essentially had to "be in the know" in order to find out about the workshop.... No public SIGCOMM announcement was made about them. 2002: first time to put 2 workshops in the Adv Prog. 7) URL: I suggest that it be on both sides of the cfp. 8) Both the ACM program director and the SIGCOMM conference coordinator can help with advice, and also MUST review it before it can be printed.