Presentation on theme: "TCCC 2005 Miami, FL March 15, 2005."— Presentation transcript:
TCCC Meeting @Infocom 2005 Miami, FL March 15, 2005
Agenda Welcome Short presentation by Joe Evans (NSF) Announcements Report from TCCC chair Other business Presentation by Rick Summerhill: Research Opportunities with Internet2
TCCC meetings Held 3 meetings in 2004 –Infocom 2004, Hongkong –ICC 2004, Paris –Globecom 2004, Dallas Each meeting was attended by 40+ members
TCCC distinguished service award Goal: Recognize individuals with outstanding service contributions to the TCCC community Mark Karol chaired 2004 awards committee: –Committee announced awards for 2004 and 2005 today: 2004: John Daigle, John Silvester 2005: Henning Schulzrinne, Jim Kurose Proposed procedure: –TCCC chair appoints chair of awards committee –Awards committee makes open call for nominations and makes selection –One or two awardees in a yearyear –Award is announced at Infocom opening session
Involvement in ICC and Globecom TCCC Rep for in ICC and Globecom: –ICC 2005: Miguel A. Labrador –Globecom 2005: Byrav Ramamurthy –Globecom 2006: Hossam Hassanein Co-sponsored symposia Globecom 2005: "Toward an Autonomic Internet " Chair: Marco Ajmone Marsan (Politecnico di Torino, Italy) Co-chairs: Marcus Brunner (NEC Europe Ltd. Germany) Claudio Casetti (Politecnico di Torino, Italy) ICC 2006: "Network Security and Information Assurance" Chair: Bulent Yener (RPI) Co-Chair: Refik Molva (EUROCOM)
Issues with ICC and Globecom From the perspective of the TCCC, the organization of symposia at ICC and Globecom is less than satisfactory: –Procedures change from year to year GC 2006: only one symposium can be proposed by one TC GC 2005: Program co-chairs are added without consultation of people proposing the workshops Current status of ICC and Globecom: –Quality of symposia is highly variable –Many technical sessions of symposia are poorly attended –Many TCCC members no longer attend ICC/Globecom (This is bad since almost all ComSoc business meetings are at ICC and Globecom)
Technical Co-sponsorship of conferences Issues and changes Background: –Technical co-sponsorship is non-financial sponsorship –IEEE Policy 10.1.2: Technical Co-Sponsorship/Cooperation indicates direct and substantial involvement by the IEEE organizational unit solely in the organization of the technical program. –Permits the use of IEEE logos (but not IEEE in title) Requirement for technical co-sponsorship (Past): 1.Endorsement by a technical committee chair (e.g., TCCC) 2.Meeting and Conference (M&C) board makes quality checks (call for papers, program committee) and checks for involvement of TC 3.M&C board (generally) approves
Technical Co-sponsorship of conferences Issues and changes Issue: Co-sponsorship declined for vague reasons In 2004, M&C board declined technical co-sponsorship of Magda El Zarkis Packet Video workshop because it is not in line with our current strategic and financial goals. The decision could be turned around. In this and some other cases (e.g., QShine), decision is not communicated to TC. Issue: Co-sponsorship almost declined over copyright M&C board indicated to decline technical co-sponsorship for IWQOS 2005 unless it obtained copyright for the proceedings (which are published by Springer). The M&C board could be convinced otherwise. Change: Fees Starting in 2005, a U.S. $350 processing fee is required for all non-IEEE entities approved for IEEE Communications Society technical co- sponsorship only. Change: New procedure for approval ComSoc event application procedures now include review by the chairs of ALL technical committees. What this means in practice: Requests are broadcast to all TC chairs. Comments by TC chairs or ComSoc leadership for or against co- sponsorship for almost any reason: dilutes brand, topical overlap with existing conference, etc.
The meaning of technical co-sponsorship ComSoc may need to rethink its approach to technical co- sponsorship: Technical co-sponsorship should be granted without financial consideration Should be granted based on technical merit Should be granted if supported by a TC Should foster interactions between societies (ACM, IFIP, others) Should try to help conference organizers It is not in the spirit of technical co-sponsorship: –to use it as a revenue source –to impose requirements that do not relate to participation in the technical program –to use it as a tool to broaden copyright ownership –to decline co-sponsorship for non-technical reasons
Other business Comments, questions, suggestions …. Next TCCC meeting at ICC 2005 in Seoul, Korea.
IEEE Policy 10.1.2 Conferences/sponsorship TECHNICAL CO-SPONSORSHIP/COOPERATION Technical Co-Sponsorship/Cooperation indicates direct and substantial involvement by the IEEE organizational unit solely in the organization of the technical program. The IEEE organizational unit has no financial involvement in the conference. The organization that has financial sponsorship of the conference must be explicitly identified in the supporting documentation and promotional material for technical co-sponsorship cooperation to be granted. The IEEE organizational unit should encourage members to submit papers and attend the conference. The IEEE organizational unit may assist in publicity through the availability of the appropriate IEEE organizational unit mailing lists. It is recommended that the relationship between sponsoring organizations should also be explicitly defined in terms of a Memorandum of Understanding (MoU), (Policy 10.1.5). Technical co- sponsorship/cooperation does not guarantee that the papers accepted for presentation at the conference will be eligible for inclusion in the IEEE Conference Publications Program (CPP), which handles post-conference distribution of conference papers in all media. Inclusion in the CPP should be specifically addressed in the MoU regulating the technical co- sponsorship/cooperation, with the concurrence of the CPP staff. The IEEE name may not be used in the conference title, (Policy 10.1.16), but, the IEEE brand/logo and/or IEEE organizational unit brand/logomay be used in conference publications and promotional materials, (Policy 10.1.17).