1 / 33

The TERENA Technical Programme

The TERENA Technical Programme. Claudio Allocchio VP Technical Programme TERENA General Assembly Limerick, 6-7 June 2002. Terms of Reference. The scope of the TERENA Technical Programme is:

sshuffler
Télécharger la présentation

The TERENA Technical Programme

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The TERENA Technical Programme Claudio Allocchio VP Technical Programme TERENA General Assembly Limerick, 6-7 June 2002

  2. Terms of Reference The scope of the TERENA Technical Programme is: • To supports joint European work in developing, evaluating, testing, integrating and promoting new networking, middleware and application technologies. • To bring together technical specialists from TERENA member organisations and the wider European research networking community. • To organise topical workshops and ad-hoc meetings to exchange experiences and information, and to plan for joint activities. • To liaises with similar activities in other continents.

  3. Terms of Reference (2) Inside the Technical Programme we have the • Technical Advisory Council, • TERENA Technical Committee, • a number of Special Interest Areas, • Task Forces, • Projects.

  4. Technical Advisory Council The TAC consists of representatives of the TERENA member organisations (= the senior technical managers of those organisations), the Task Force leaders, the VP Technical Programme, the Chief Technical Officer and the Secretary General. TheTAC is a main instrument for the TERENA member organisations to steer the direction of the technical work under the TERENA umbrella.

  5. Technical Advisory Council The TAC meets at least once a year to: • Review the progress of the Technical Programme • Advise on the future direction of the Technical Programme • Propose new initiatives • Exchange information about networking activities • Propose TTC members At least once every two years, the TAC also reviews the Special Interest Areas (done on Monday June 3rd 2002)

  6. TERENA Technical Committee The TTC co-ordinates and supervises the Technical Programme. It has the functions to: • Create and dissolve Task Forces • Consider project proposals and recommend to the TEC whether they should be approved as TERENA projects and, if applicable, whether they should receive TERENA funding • Assess the progress of Task Forces and projects

  7. TERENA Technical Committee The current composition of the TTC is: • Claudio Allocchio - VP Technical Programme • Roberto Barbera - GRID • David Chadwick - Directories • Christoph Graf - Security • Dimitrios Kalogeras - High Speed Networking • Olav Kvittem - Diffserv and Quality of Service • Ton Verschuren - Middleware • John Dyer - Chief Technical Officer • Karel Vietsch - Secretary General Liaison with US-MACE Committee: • Brian Gilmore

  8. Special Interest Areas The TEC may create a maximum ofsixSpecial Interest Areas, usually based on the recommendation of the TAC. The Special Interest Areas • determine the focus of the TERENA Technical Programme • offer a forum for discussion and exchange of information • provide a platform for creating new Task Forces and projects

  9. Special Interest Areas The current Special Interest Areas (June 2002) are: • Lower Layers (IPv6, MPLS, VPNs etc.) • Quality of Service (including DiffServ) • Videoconferencing and Streaming (Including IP Telephony) • Content Delivery, Indexing and Searching • Middleware • Mobility • In addition, Grid and Campus coordination across the SIAs

  10. Task Forces and Projects A Task Force is a focused group with a specific charter, which defines its objectives, its lifetime and the deliverables that the group will produce A Minor Project is a limited activity that produces specific deliverables within a few months and that is (partially) funded directly from TERENA’s own resources A Major Project is a larger activity covering a longer period. Major projects are funded by additional contributions from TERENA member organisations and possibly other sources An External Project is an activity in which TERENA staff members themselves take an active part and that is co-funded by third parties such as the EU

  11. Lower Layers and QoSTF-NGN TF-NGN investigates the suitability of advanced networking technologies for future implementation in research networks in Europe. The work includes the piloting of new services on GÉANT. Very active Task Force with a large membership and a large number of activity areas, including: • testing of MPLS Guaranteed Capacity Service on GÉANT • Premium IP (in collaboration with GÉANT and SEQUIN) • LBE (Less than Best Effort) service • multicast monitoring • IPv6 (including preparatory work for 6NET project) • flow-based monitoring and analysis • optical networking (see ASTON) • ………………………

  12. Lower Layers and QoS6NET project Very large FP5 project for a large-scale international IPv6 testbed. January 2002 – December 2004. Total estimated budget 17 million euro. More than 30 participants, including a large number of TERENA member organisations (national networks and DANTE, and industry - Cisco project co-ordinator) • Latest news: IPv6 test network fully deployed and operational since end of May! TERENA’s role: • Leading the workpackage on dissemination and exploitation of results • Maintaining the 6NET website: www.6net.org • Organising workshops (e.g. Joint 6NET-Euro6IX workshop, Limerick 5 June 2002)

  13. Lower Layers and QoS6LINK project Small accompanying measure in FP5 to support the IPv6 cluster activities. March 2002 – February 2005. Total estimated budget 1 million euro. Project partners are: BT Exact, Telscom, T-Nova, University of Southampton, Consulintel, University College London, Polytechnical University of Madrid, Motorola, DANTE, TERENA, Universidad Carlos III de Madrid TERENA’s role is very small: 1 man-month per year www.6link.org

  14. Lower Layers and QoSTEQUILA project FP5 project to specify, implement and test a set of service definition and traffic engineering tools to obtain QoS guarantees across IP networks. Total estimated budget 5.9 million euro. January 2000 – June 2002, but may be extended by 4 months. Project participants are: Alcatel, Algosystems, France Telecom R&D, Global Crossing, University of Surrey, IMEC, NTU Athens, University College London. TERENA is assistant contractor to UCL. TERENA’s role: • Maintaining the TEQUILA website: www.ist-tequila.org • Organising workshops (last one in Maastricht on 14-15 May 2002)

  15. Lower Layers and QoSSCAMPI project Large FP5 project to develop a SCAlable Monitoring Platform for the Internet. April 2002 – September 2004. Total estimated budget 5.5 million euro. Project participants are: TERENA, IMEC, FORTH, Leiden University, Netikos, UNINETT, CESNET, FORTHNET, 4PLUS, Siemens TERENA’s role: • Project co-ordinator • Leading the workpackage on project management and dissemination • Maintaining the SCAMPI website • Organising workshops

  16. Videoconferencing and Streaming TF-STREAM • January 2000 – June 2001 • Undertook several experiments setting up a distributed infrastructure for streaming live events • Carried out end-to-end H.323 QoS tests on GÉANT • Developed directory of information on videoconferencing services provided by national research and education networks • Final report on TF-STREAM distributed at Limerick conference • Final meeting in Limerick on 2 June 2002 • Proposal being actively prepared for TF-STREAM Successor

  17. Videoconferencing and Streaming IP telephony • Poll in second half of 2001 revealed substantial interest in IP telephony among TERENA members • Successful first meeting in Amsterdam on 6 March 2002 (24 attendees) • Second meeting combined with TF-STREAM in Limerick on 2 June 2002

  18. Content Delivery, Indexing and SearchingPortal Coordination TERENA has organised series of informal meetings on co-ordination of portal initiatives. Most recent meeting: Limerick, 2 June 2002. RENARDUS Project Partners approached TERENA in late 2001: our community data (IT) as an interesting and missing piece of their system. March 2002 meeting resulted in project proposal from RENARDUS partners.

  19. Content Delivery, Indexing and SearchingRENARDUS project proposal (1) RENARDUS is: • Freely available Web-based service for integrated, multilingual access to a range of existing, distributed quality-controlled subject gateways across Europe • Built on international standards such as Dublin Core and Z39.50 • RENARDUS browsing structure based on Dewey Decimal Classification (DDC)

  20. Content Delivery, Indexing and SearchingRENARDUS project proposal (2) RENARDUS proposal asked for two years’ maintenance (July 2002 – June 2004) for: • Monitoring server’s service running in Germany • Assuring data back-up • Checking record normalisation • Support for new partners (during their initial normalisation process) Maintenance cost per year: 49.5 kEUR

  21. Content Delivery, Indexing and SearchingRENARDUS project proposal (3) TTC (April 2002) recommended: • Assure funding for first year and then evaluate results • Fund as major project with 10 kEUR funding from TERENA and 40 kEUR from number of other parties • Response needed from TERENA members on request to contribute to that 40 kEUR TTC and TAC (June 2002) cncluded: • There is very little response from the community • There are not yet data from our community to be inserted into Renardus work • There are too many different opinions on what we need for portals

  22. Questions from Discussion • Which is OUR community? • Are NRENs users (customers) the community? • What the NRENs do for these users? • Who is doing the portal service in NRENs? • "end users" are asking for it… coordinating people usually are not directly involved with the NRENs. • Aren't the NRENs moving towards "value added" providers, expecially in the fields of middleware and applications?

  23. MiddlewareSecurity: TF-CSIRT TF-CSIRT provides a platform for information exchange and collaboration between Computer Security Incident Response Teams from NRENs, industry and government. Very active Task Force with a large membership. Some 30 CSIRTs actively participate, meetings have some 50 attendees. Revised Terms of Reference discussed in May 2002, with number of plans for the next two years. Activities include: • Development of Incident Object Description Exchange Format (IODEF), now taken up further in IETF context. Small IODEF pilot implementation project of UKERNA and SURFnet is co-funded by TERENA. • IRT object in RIPE database • Clearinghouse for incident handling tools • Much exchange of information and discussion of best practice • (see next slides)

  24. MiddlewareSecurity: Trusted Introducer pilot service TI provides a form of accreditation of CSIRTs, thereby assisting the development of a ‘Web of Trust’. Currently 26 CSIRTs accredited. TI pilot September 2000 – August 2002. Pilot positively reviewed by TI Review Board. Review Board and TF-CSIRT recommend to continue the Trusted Introducer as a permanent service, with TERENA continuing to provide clearinghouse function. Very successful activity, attracting much positive interest also in other continents, among policy makers etc.

  25. MiddlewareSecurity: TRANSITS project FP5 project to provide TRAining of Network Security Incident Teams Staff. Expected to start July 2002, will run for 3 years. Total estimated budget 250,000 euro. Will develop and maintain course materials to train staff members of new CSIRTs and new staff members of existing CSIRTs. EU funding covers logistics costs, expenses of teachers and includes small budget to support participants from “poor” countries. Project participants areTERENA and UKERNA TERENA’s role: • Project co-ordinator • Workshop logistics • Maintaining the TRANSITS website

  26. MiddlewareDirectories TF-LSD investigates the usability of LDAPv3 as a base for a wide range of Internet services • Completed work on the reference between the X.521 naming and the Domain Component naming and the referral mechanisms in LDAP • Work on a number of other deliverables continuing • Led to major project “Adding certificate retrieval to OpenLDAP”, carried out by University of Salford and co-funded jointly by TERENA (26 kEUR) and CESNET, RedIRIS, SURFnet, SWITCH and UNINETT (10 kEUR each). • Led to project proposal DEEP2 (Schema for the European academia) of which first phase was approved for funding by TERENA as a minor project • Led to project proposal Directory Schema Registry, which was recommended by TTC for funding as a major project (TERENA to contribute 16 kEUR if number of NRENs together also contribute 16 kEUR). Responses from NRENs is arriving.

  27. MiddlewareAuthentication and authorisation Since late 2000, TERENA has organised series of informal meetings on the co-ordination of PKI and Certification Authority initiatives in Europe. Meeting in March 2002 led to list of deliverables and Terms of Reference for a new Task Force TF-AACE. Task Force was officially established by TTC in April 2002. First official TF-AACE meeting in Limerick, 2 June 2002. Work items include: • Defining interoperability requirements for European academic PKIs, including guidelines for PKI deployment at NRENs • Defining common requirements for inter-institutional authentication and authorisation, providing a framework for harmonising NREN initiatives • Investigation/comparison of use of hierarchical and bridge PKI/CA and making recommendation for European NRENs

  28. Mobility TERENA involvement still in early stages, discussing status and issues, and investigating possibilities for activities in TERENA Technical Programme. Successful workshop in Amsterdam on 6 March 2002. Successful meeting in Limerick on 2 June 2002. NOW it is a new SIA proposed by the TAC

  29. GRIDs • TERENA staff and TTC closely following developments, e.g. in Global Grid Forum, exchanging information and knowledge • Active discussion in TAC meeting • Special BoF at the conference • Which relationship with GRID people?

  30. GNRTGuide to Network Resource Tools • A completely revised, modularly structured new edition of the GNRT will be produced in the second half of 2002 • Going out on the WEB • Maybe… again as a book (2003)

  31. Certificate Retrival in OpenLDAP • Project started Sep 1st 2001 and approaching now final delivarables and results • Minor improvements discussed inside the project, and endorsed by TTC

  32. TERENA Technical ProgrammeOther Activities Decision making by email • TERENA will actively use the tools developed by Jacob Palme (co-funded by TERENA as a minor project) for decision making in Task Forces and other TERENA bodies DEEP2 • Schema for the European Academia (EuroEduPerson) • Investigation Questionnaire being sent out in order to evaluate the need of the work (2KEuro by TERENA) Directory Schema • set up an LDAP schema registry, with an easy browsable and searchable Web interface, as well as an interface based on MIME types defined in RFC2927 for submissions of new schema • In the final phase of getting the needed funding (waiting for letters of intents), and then start activity (46KEuro: 14K DAASI, 16K TERENA, 16K TERENA members contributions)

  33. Questions?

More Related