VD-C JP-B JP-G Joint plenary meeting Zagreb, 4 September 2006

1. VD-C JP-B JP-G Joint plenary meeting Zagreb, 4 September 2006

2. WP-VD-C Optical Core Networks Plenary meeting year 1Zagreb, 4 September 2006 Franco Callegati DEIS University of Bologna

3. Objectives • Integrate and promote the research activity in the broad area of core network design and analysis • Close topics with • JP-B on OBS • JP-G on Grids and e-science

4. Involved Partners • Currently subscribed on the directory service • 71 researchers • 27 partners • BILKENT • UAM • TUW • FT • Alcatel • UPC • SSSUP • PoliTO • TID • GET • UST-IKR • FLE • TUB • AGH • AIT • UC3M • TELFER • FUB • TELENOR • UPVLC • ORC-CC2 • UoPelop • IBBT (Gent) • UEssex • CTI • PoliMI • KTH

5. Milestones • M.VD-C.1 [T0+2] • Designation of the VD advisory board, and draft list of actions • M.VD-C.2 [T0+4] currently T0+7 • First plenary technical meeting: checklist on integration of activities, proposals for joint publications and preliminary list of key issues in the VD research area • M.VD-C.3 [T0+18] • Second plenary technical meeting: summary of integration activities, and proposal for further actions; includes technical workshop on VD-C topics

6. Deliverables • D.VD-C.1 [T0+5] still pending to be issued after the plenary • List of VD-C key issues and planned activities • D.VD-C.2 [T0+12] First draft beginning 2007 • Yearly VD-C technical report, including collection of published joint papers • D.VD-C.3 [T0+19] • VD-C report on the e-Photon/ONe+ viewpoint on technologies, architectures and protocols for optical core networks, including list of key issues • D.VD-C.4 [T0+24] • Yearly VD-C technical report, including collection of published joint papers • All deliverables are public

7. VD Commitments • Meetings and workshops: First technical meeting to be jointly organized with JP-B/G at the summer school 2007 Second technical meeting at summer school 2008 Yearly meeting in conjunction with ONDM or E1+ Plenary? • Joint papers Joint papers reporting a summary of the activities of phase 1 already accepted (and acknowledging to e1+) Infocom 2006 ICTON 2006

8. M.VD-C.1 (T0+3) Discussed at the end the last plenary meeting of e1-VD1 • WP leader offered to pass the token but was unanimously confirmed :-( • WP advisory board widened • Include researchers with expertise in OCS topics • Javier Aracil (JP-B) – javier.aracil@unavarra.es • Franco Callegati – franco.callegati@unibo.it • Josep Solè Pareta – pareta@ac.upc.es • Harald Øverby – haraldov@item.ntnu.no • Dimitra Simeonidou (JP-G) – dsimeo@essex.ac.uk • Luca Valcarenghi – valcarenghi@sssup.it • Lena Wosinska – lena@it.kth.se

9. Deliverables Issues widely discussed during Phase 1 • What should go in the Deliverables by VDs (public documents)? • Unilateral research on topics related to the VD • Bi/Multi-lateral research based on joint activities defined in the framework of the VD • This second part is what reviewers want to see! • Other issues • Relationship between papers and deliverables • Answer: provide summaries of the papers in the deliverables • Editing of large deliverables • Using Latex and publish pdf

10. D.VD-C.2 • Why do we compile a public deliverable? • We promised to and we must make reviewers happy • A good chance to make our work known more widely and build consensus on our technical choices • If we rely on a deliverable we may advertise for it • Documents easy to read • Pointers to our work (publications, labs experiments etc.) • What kind of contributions: • Concise summary of problem and proposed solutions • All estensive mathematical or algorithmic derivations referenced • Some example of “significant” and “easy to read” results • Extensive investigation in references • Conclusions and pointers to the literature

11. Joint paper for Infocom • Was a good experiment to be applied to large deliverable compilation • Identify a “deliverable editor (DE)” (usually VD leader :-( • Collect a list of “tentative” contributions • Create sections of “related topics” and identify “section editors (SE)” • Send contributions to SEs • Text in Latex or plain text format (even in word file, but with limited formatting) • Graphs in eps format (plus raw data in plain text) • SEs provide a first review and submit contribution to DE • DE compile first draft of the whole document making section as uniform as possible • Draft disseminated for comments • Comments to SEs or DE and second draft etc. • Some room for post-deadline adjustments is available but only if new contributions fit in the general framework

12. Joint activities • OBS book writing (jointly managed with JP-B) • “Advanced connectivity service provisioning in GMPLS networks” by SSSUP, FUB and KTH (P. Castoldi) • “Congestion Resolution in Optical Burst/Packet Switching with Limited Wavelength Conversion” by DEIS-UNIBO and UNICAMP (F. Callegati) • “Impact of signalling and role of the off-set time in OBSN performances” by PoliMI and DEIS-UNIBO (to be decided whether to include it in JP-B) • “Comparison of end-to-end packet ordering issues in synchronous and asynchronous Optical Packet Switching networks” by UPC and UPCT • “Survivability in all-optical wavelength switching networks” by PoliMI, CTTC • “Multi-Domian routing, TE and Resilience including MD p-Cycles” by UC3M and BME • “Dynamic behaviour of two layer networks” by SSSA and BME • Joint activity by UPC and IBBT • “Dynamic optical circuit-switched transport networks: study of the efficiency in IP transport and technical implementation of network solution” by FT (Esther le Rouzic) • Joint activity by UPatras

13. Extra budget share • Plan for extra budget allocation to be filed to project office at the end of year 1 • I propose to: • Allocate 10 K€ to OBS book writing • Allocate 4/5 K€ to any activity • Budget shared between involved institutions • In case a collaborating institution is involved the budget will be allocated “in toto” to regular partner • Money access by collaborating institution will be based on “gentlemen agreement”