Skip to main content
European Commission logo
italiano italiano
CORDIS - Risultati della ricerca dell’UE
CORDIS
CORDIS Web 30th anniversary CORDIS Web 30th anniversary
Contenuto archiviato il 2024-05-27

EUROpean IPv6 Internet eXchanges backbone

CORDIS fornisce collegamenti ai risultati finali pubblici e alle pubblicazioni dei progetti ORIZZONTE.

I link ai risultati e alle pubblicazioni dei progetti del 7° PQ, così come i link ad alcuni tipi di risultati specifici come dataset e software, sono recuperati dinamicamente da .OpenAIRE .

Risultati finali

This document summarizes the 2nd Year Internal Trial of the Euro6IX project. Lots of investigation activities with respect to IPv6 network services and applications in an IPv6 IX based backbone network have taken place in the first and in the second year of the project and a subset of them has been compiled and demonstrated in several events as the "2nd Year Internal Trial", which was realized mainly during the months September and October 2003. (M4.4). This deliverable describes the trial activities of the 2nd Internal Trial in more detail and shows, how these activities are related to the special conditions of the Euro6IX networking scenario. The four main objectives of the Euro6IX project are, as indicated in the Technical Annex: 1) To research an appropriate architecture to design and deploy the first Pan-European non-commercial IPv6 Internet Exchange (IX) Network 2) To use the deployed IPv6 IX infrastructure to research, test and validate IPv6-based applications and services 3) To open the Euro6IX network to specific user groups and 4) To do dissemination, liaison and coordination with clusters, fora, and standards organizations. In order to fulfil the second of these main project objectives, several trial activities (Internal Trials and Public Trials) are scheduled on a yearly basis. These trials are organized and carried out in Activity 4.3 of Work package 4. This document describes the organization, realization and the results of the 2nd Year Internal Trial, which was scheduled for Month 21 of the project lifetime (September 2003) to Milestone 4.4 and which was realized mainly during September and October 2003. The structure of this deliverable 4.7 "2nd Year Internal Trial" is as follows: - Chapter 1 gives a short introduction to the 2nd Year Internal Trial and clarifies the objectives of such kind of internal trial. -·Chapter 2 contains a short overview about the approach to this trial and a table of the chosen and later on realized trial scenarios. -·Chapter 3 is dedicated to the Time Planning, Preparation and the Realization of this trial. -·Chapter 4 enhances this deliverable with some remarks respectively the results, conclusions, identified open issues and future plans within activity 4.3. -·Chapter 5 contains the annex of this deliverable 4.7 and describes the trial scenarios of the 2nd Year Internal Trial in more detail. In the future the activities of A4.3 will be enhanced and directed to more specific trials for connected IPv6 Internet Exchanges, but from the today's status quo of the Euro6IX network this 2nd Year Internal Trial highlighted once more the comprehensive possibilities for interesting and new IPv6 Networking Services and Applications in an IPv6 IX based Networking Environment, as it is given with the Euro6IX backbone.
The 6NET and Euro6IX projects both focus on large-scale IPv6 deployment, but for different market segments. 6NET is deploying an IPv6 infrastructure in an academic and research environment, with a high-capacity native IPv6 backbone spanning many countries. Euro6IX is deploying a number of pre-commercial IPv6 exchange points (IXs), with relatively lower connectivity speeds between the IXs. The two projects 6NET and Euro6IX both have as a common objective the dissemination of results related to IPv6 technology, standards, coexistence and transition, applications, internetworking and interoperability, users requirement, constraints, research activities related to deployment issues, among others. In this context, both projects had organized a joint workshop at Limerick, co-located with Terena conference on 5th of June, in collaboration with IPv6 cluster facilitated by 6LINK project. This report summarizes the result of this workshop in Limerick on 5th June 2002.
The general objective of this activity was to develop and implement a Host Centric Multi-homing solution, aligned with the proposals made on IETF multi6 and shim6 working groups. In this context, the following developments have been achieved: -·Source address selection policies management tool. A kernel patch and a user space utility were developed for USAGI IPv6 implementation, in order to easily change the kernel label table configuration described in RFC 3484, and providing the related support in the kernel. -·Basic host centric multi-homing solution and web based demonstration scenario. A basic multi-homing solution based on tunnelling between site exit routers was developed. It was implemented in site exit routers and had two parts: - Configuration of 6in6 tunnels among each exit router. - Source address dependent routing in the routers, implemented using ipfilter in FreeBSD and ip6tables in Linux. This scenario has been emulated inside a Linux based personal computer using VNUML virtualisation tool and a web-based interface was developed in order to allow remote users to test and understand the multi-homing solution. -·Multi-homing Policy language definition and tools. In order to simplify the configuration of tunnels in exit routers, we designed and implemented a solution based on the definition of the multi-homing policies of an organization using XML based specifications, which can be later processed by some especially developed tools to automatically generate router configurations. This solution was later integrated in the Policy Based Management system developed by UMU. ·Automatic tunnelling solution based on anycast addresses. Another approach was developed to solve the multi-homing ingress filtering problem based on the automatic establishment of tunnels among site-exit routers based on the use of site-exit anycast addresses distributed through the organization IGP. This approach has been implemented over quagga routing software and works in both GNU/Linux and FreeBSD operating systems Delivering source address selection policies to hosts. We have implemented solutions to deliver source address selection policies to final multi-homing hosts. Two different approaches have been taken: - Source address selection policies distribution using Router Advertisements. - Source address selection policies distribution using DHCPv6 option (partially implemented).
This Document provides Euro6IX project's web site used as a platform for public information dissemination and as an on-line private project level document exchange, including the mail archive. The project site is rich with project information, an introductory power point presentation, and list of all deliverables with downloadable function as soon as they are submitted. The site also links all partner information, IPv6 information from the press, related IPv6 projects, and maintains an agenda of important events and conferences.
"Multicast Billboard" provides a way to receive a multicast flux with no previous subscription, because the system does it automatically. This automation makes possible that the client uses any multimedia application. At Telefonica Investigacion Y Desarrollo (TID) there are two multicast sources. The user may select between one of them, or more if they are installed.
This deliverable represents the final result of the work done in the context of the A2.2 activity inside the WP2 in first year of the Euro6IX project. The A2.2 activity has the main objective fixed in the design of the Euro6IX backbone network. Once the IX model to be implemented was chosen in the six months of the Euro6IX project, A2.2 covers the way to interconnect the different Euro6IX Exchanges (IXs), and the routing policies of the whole Euro6IX backbone. Deliverable D2.2 aims to give the technical basis needed for the design and deployment of the routing policies needed for the Euro6IX backbone. After a presentation of several IPv6 backbones, a comparison between IPv4 and IPv6 backbones, and the explanation of the objectives of the Euro6IX backbone, several sections complete this document. First section (Chapter 2: Study of IPv6 IXs Models) covers the architecture of the different IXs models proposed since the beginning of the Euro6IX project. Second section (Chapter 3: Backbone Euro6IX Network Architecture) contains the information related to the implementation of the routing policy applied to the Euro6IX backbone. At the end, the third section (Chapter 4: Interconnection with other IPv6 Backbones) is focused in the different connections between Euro6IX partners and external networks, such as 6NET, 6Bone, etc.
This document is a summary of the Euro6IX project more relevant information, including the objectives, technical approach, key issues, and expected impact. Includes also the list of participants. The first objective of the Euro6IX project is to research an appropriate architecture to design and deploy the first Pan-European non-commercial IPv6 Internet Exchange (IX) Network. It will connect several regional neutral IPv6 Internet Exchange points across Europe, and achieve the same level of robustness and service quality as currently offered by IPv4 Internet Exchange Networks. The second objective is to use the deployed IPv6 IX infrastructure to research, test and validate IPv6-based applications and services. As a third objective, the network built within the Euro6IX project will be open to specific user groups (existing and to be created), who will be connecting to the Euro6IX network by means of a variety of access technologies - mobile, xDSL, cable - and internetworking with legacy IPv4 networks and services, to test the performance of future IPv6 networks, and non-commercial native IPv6 advanced services and applications. The fourth objective of the project will be dissemination, liaison and coordination with clusters, fora, standards organizations (e.g. the IETF and RIPE) and third parties, with particular consideration for inter-working and coordination with peer projects, such as GEANT, 6WINIT, LONG, MIND, 6NET and any other projects related to our work, that might be available during the Euro6IX project lifetime.
VNUML (Virtual Network User Mode Linux)is an open-source general purpose virtualisation tool designed to quickly define and test complex network simulation scenarios based on User Mode Lunix (UML) virtualisation software. It has been initially developed in the context of Euro 6IX research project to simulate IPv6 IX scenarios based on Linux and zebra/quagga routing daemons. However, it is a useful tool that can be used to simulate general Linux based virtual network scenarios. VNUML is made of two components: a simple and descriptive XML-based language to write a text file with the specification of the desired scenario; and a parser that interprets the language and builds and run the scenario described in the file, hiding all the UML booting complex details from the user. Being VNUML a general virtualisation tool, it can be applied in a wide variety of fields, for example, to create network testbeds to text new applications or network services, to create honey-pots for security environments, or to complement computer network laboratories. VNUML has been used in several activities inside Euro6IX and it is also being used outside the project by several universities, research centres and companies. Besides, since its release as an open-source tool hosted by Sourceforge, several important contributions have been received from external developers. VNUML Tool is available at: http://www.dit.upm.es/vnuml
Yearly summary report of activities undertaken by the project related with the dissemination activity. The Euro6IX project started its activity even before it started officially on January 2002, with several important dissemination activities. The website was created also just before the start of the project and is both IPv4 and IPv6 compatible with an access to all latest IPv6 related information, the public deliverables of the project and links to all important IPv6 related activities known within IST and other foras. The results of the project have been presented in several international events. The complete list of attended conferences and events, trials carried out, and practical experiments, is available in this document. Euro6IX project also took active role in the clustering events and is one of the driving forces in organizing the IPv6 Cluster project demonstration booth in IST2002. Global IPv6 Summits organized around the world are considered as a good platform to reach the targeted audience for the Euro6IX project and hence the project has participated in almost all IPv6 Summits. The IPv6 Task Force is another important group where Euro6IX project members are active in achieving consensus based IPv6 development and deployment discussions and have contributed to several strategic documents. The close collaboration achieved between 6NET and Euro6IX was clearly demonstrated during IST2002 with a collaborative work in providing the European wide native IPv6 connectivity among the partners to demonstrate the IPv6 applications. Euro6IX project is also very active in standardization activity in IETF and RIPE groups. The project proposed neutral exchange based address allocation system to RIPE.
This deliverable summarizes the work done during the Euro6IX project regarding the implementation of systems to perform managing, monitoring, statistics reports and security control activities of each IPv6 Internet Exchanges and IPv6 networks. The definition of most systems finally implemented during the second and third years of the Euro6IX project were quite concretely defined in D3.2a -Update on the definition of statistics, management and security control systems. This deliverable has been re-scheduled from its original contractual date March 2004 (M27) to September 2004 (M33) as part of the Contract Amendment II. This document describes the implementation of network management, statistics monitoring and security control issues in the context of Euro6IX IPv6 Exchangers and IPv6 networks. All these platforms were discussed in previous Euro6IX meetings in the context of activity A3.3. An initial definition was available in D3.2 Definition of statistics, management and security control systems (draft): and an updated one was produced in D3.2A Update on the definition of statistics, management and security control systems.
In the context of the Euro6IX activity that studied the IPv6 IX address delegation model based on a BGP route server, several pieces of software were developed: - A route server implementation for the Quagga open source routing daemon. It was developed as a patch to Quagga's code, but it is already integrated and available in Quagga's distribution since version 0.97. - A patch to the RtConfig tool has been generated to support Quagga's configuration file format and to support the generation of Route Server configuration files. - Minor bug corrections to the dbupdate tool of RIPE database and to the IRRd RPSLng database. Besides, a complete set of virtual scenarios based on the VNUML tool have been generated and tested that show how the IX services can be offered to the IX customers using IPv6 addresses assigned by the IX. The scenarios include all the detailed configuration of all the routers involved, the configuration of the enhanced route server controlling the IX services, the content of the RPSLng databases, and all the tools needed to set up the scenarios (routing daemons, RPSLng databases, IRRToolSet, etc), as well as the linux kernels and rootfile systems used by VNUML. All the software mentioned above, together with the virtual scenarios created can be very valuable for an organization trying to implement the IX architecture designed in Euro6IX, as it will allow to virtually test the scenarios before implementing it.
UMU-PBNM tool is Policy-based network management architecture. It aims to provide a security framework for the management of policies in IPv6/IPv4 networks. It is based on the use of public key cryptography (as provided by the UMU-PKIv6 implementation) as a way to deal with the security concerns associated with today's networked environments. Policies allows the administrator of a system to specify the behaviour they want it to exhibit, through a set of selections made from a range of options provided by the designer of the policy-controlled component (e.g. network node). Some of the features developed for this tool are: -·Comfortably entry point to system using a simple Internet browser (Policy console) -·Support of administration based on role, interface and template concepts. -·Administration and monitoring of VPN-IPsec, routing and multi-homing. -·Integration with DNSSec as storage of device certificates. -·Extensible design: it allows the management of future advanced network services.
The Euro6IX bandwidth on demand architecture follows the state of the art Internet design. Complexity is moved to systems in the network periphery, while the network core mainly forwards packets. Operational systems and standards are used and adapted with minimum changes. Backwards compatibility is maintained to the largest extent. The fundamental Quality of Service mechanism used by Euro6IX is DiffServ. A SIP-based Voice over IP application was chosen to apply the bandwidth on demand feature. The Session Initiation Protocol (SIP) was selected to signal for the telephony service. The architecture can be extended to any other application supported by SIP. Routers usually don't support SIP signalling, hence a protocol signalling QoS was chosen for this purpose. Euro6IX decided on the Next Steps In Signalling (NSIS) protocol suite, which was "work in progress" during the Euro6IX project execution. Euro6IX choose the Extensible Authentication Protocol as a means for flexible adaptation to RADIUS and DIAMETER AAA infrastructures. The resulting on demand Quality of service architecture can be implemented stepwise, beginning with a simple scenario with trusted users and ending with a commercial service like environment. Euro6IX specified all components and started implementation and testing. For that reason a SIP-based VoIP application was adapted to use NSIS signalling in order to communicate with the on-link router about the needed network resources for a SIP call. During the call-setup phase the SIP application signals to the communication peer that it is able to support End-systems based admission control and in the case that the on-link router acknowledges the resource request (via NSIS) from the SIP client for the link both communication peers send test traffic between each other in order to check the availability of resources as well in the backbone network part (End-system based admission control). Only in the case that this test traffic is received without any loss, the SIP call-setup is finished successfully - otherwise a busy signal is assumed. TSN implemented this NSIS functionality and the end system based admission control into a SIP VoIP client and provided this demonstrator within the Euro6IX.
The work done to port FreeRadius to IPv6 has been about: -·Porting of IPv4 sockets structures to IPv6 socket structures. -·IP addresses structures modified to support IPv6 addresses. -·Modification of the process to identify source IPv6. -·Parsing of file clients.conf to understand IPv6 addresses and IPv6 networks of RADIUS clients. -·New attribute introduced in the dictionary: ip6addr used to store IPv6 addresses. -·The accounting system was also modified to get and account IPv6 addresses. This result is widely used in another Euro6IX results such as: Magalia (authentication and authorization system), and Dynamic Euro6IX Nodes (authentication, authorization and accounting system).
This is the first legal deliverable which examines the legal implications of IPv6 on privacy and civil liberty, a crucial issue which needs to be dealt with comprehensively in order that privacy concerns do not create an obstacle to the widespread implementation of IPv6 in Europe. In particular we focus on the issue of whether the use of unique identifiers in some types of IPv6 addresses are as potentially dangerous to privacy as some commentators suggest or whether this issue has been dealt with in a satisfactory manner within the IPv6 design. The deliverable sets out the European legislative background to privacy (and data protection) and puts the IPv6 privacy issue into perspective against this background providing answers to the questions above. The privacy concerns about IPv6 centre on the use of unique identifiers in a certain type of IPv6 address. Some argue that this will leave a digital fingerprint every time someone enters the web allowing detailed automated profiling of an individual. This issue was first raised in the US at the end of the 90's where stories began to appear that IPv6 was bad for privacy. The debate has now moved across to Europe where concerns have been raised by an official publication of the Article 29 Data Protection Working Party, an independent advisory body on data protection and privacy established under the first Data Protection Directive (95/46/EC) ('Opinion 2/2002 on the use of unique identifiers in telecommunication terminal equipment: The example of IPv6 adopted on 30th May 2002'). Also prior to this Article 29 Opinion, another EU body, the Commission to the Council and the European Parliament published a paper in February 2002 entitled Next Generation Internet priorities for action in migrating to the new Internet Protocol IPv6, which set out a list of issues to be dealt with to assist the successful deployment of IPv6 in Europe. One of the specific tasks called for was an extensive study into any privacy issues raised by the new Protocol. One of the tasks of the Euro6IX project is to undertake such an extensive study in order to deal with the potential privacy issues in IPv6 and specifically in this first deliverable we confront the issue concerning the use of unique identifiers raised in the Article 29 Data Protection Opinion. We have analysed the issues against the background and development of European privacy and data protection laws to identify what are the privacy obligations for the designers of the new Protocol and whether they have fulfilled these obligations particularly in respect of addressing. This is the first of three deliverables due from Euro6IX dealing with the legal aspects of IPv6. The second deliverable due in December 2003 will concentrate on the data protection legislation in more detail (rather than the general concept of privacy) and the final paper in October 2004 will deal with a various issues such as IPsec and IPRs (Intellectual Property Rights).
This document summarizes the 3rd and last Year Internal Trial of the Euro6IX project. Lots of investigation activities with regards to IPv6 network services and applications in an IPv6 IX based backbone network have taken place in the first, second and in the third year of the project and a subset of them has been compiled and demonstrated in several events as the "3rd Year Internal Trial", which was realized mainly during the months October and November 2004 (M4.6). This deliverable describes the trial activities of the 3rd Internal Trial in more detail and shows, how these activities are related to the special conditions of the Euro6IX networking scenario. The four main objectives of the Euro6IX project are, as indicated in the Technical Annex: 1) To research an appropriate architecture to design and deploy the first Pan-European non-commercial IPv6 Internet Exchange (IX) Network 2) To use the deployed IPv6 IX infrastructure to research, test and validate IPv6-based applications and services 3) To open the Euro6IX network to specific user groups and 4) To do dissemination, liaison and coordination with clusters, fora, and standards organizations. In order to fulfil the second of these main project objectives, several trial activities (Internal Trials and Public Trials) are scheduled on a yearly basis. These trials are organized and carried out in Activity 4.3 of Work package 4. This document describes the organization, realization and the results of the 3rd Year Internal Trial, which was scheduled for Month 39 of the project lifetime (March 2005) to Milestone 4.6 and which was already realized mainly during October and November 2004. The structure of this deliverable 4.9 "3rd Year Internal Trial" is as follows: -·Chapter 1 gives a short introduction to the 3rd Year Internal Trial and clarifies the objectives of such kind of internal trial. -·Chapter 2 contains a short overview about the approach to this trial and a table of the chosen and later on realized trial scenarios. -·Chapter 3 is dedicated to the Time Planning, Preparation and the Realization of this trial. -·Chapter 4 enhances this deliverable with some remarks respectively the results, conclusions and identified open issues. -·Chapter 5 contains the annex of this deliverable 4.9 and illustrates the trial scenarios of the 3rd Year Internal Trial in more detail. Since this 3rd Year Internal Trial has been the last internal trial activity within the Euro6IX project context it can be stated from the today's status quo of the Euro6IX project that the method of an internal trial series was well chosen and successful in order to demonstrate and illustrate the achievements of the project. Once more these 3rd Year Internal Trial highlighted the comprehensive possibilities for interesting and new IPv6 Networking Services and Applications in an IPv6 IX based Networking Environment, as it is given with the Euro6IX backbone
This document describes the overall trial scenario of the 1st Year Public Trial of the Euro6IX project that was scheduled at the Madrid 2003 Global IPv6 Summit during May 2003. Because of the actual lack of big numbers of Euro6IX "native" customers the 1st Year Public Trial was realized as a big trial at the GIS2003 event that attracted lots of visitors of the conference as well as the representatives from the European Commission and from other European projects. This deliverable D4.3p describes the trial activities of the 1st Year Public Trial in more detail and shows, how these activities are related to the special conditions of the Euro6IX networking scenario and which project results were shown within this public trial. In summary it can be said that the 1st Year Public Trial of the Euro6IX project contained besides a very sophisticated IPv6 network setup within the GIS2003 conference hotel, lots of very interesting and successful IPv6 applications, network and service trials. The 1st Year Public trial highlighted the achievements of the Euro6IX project and attracted the attendees of the GIS2003 conference. Hence the objectives of the 1st Public Trial, as written down in the Technical Annex, were met.
This document describes the requirements for the address delegation process of the IPv6 IX and the Layer 3 Mediation Function (L3MF) as a means of performing IPv6 IX based address delegation. It goes on to describe possible implementations of the L3MF, and some currently implemented solutions that are variations of L3MF.
This document summarizes the results of the research and innovative tasks carried out during the third year and fourth year of Euro6IX project in the context of WP4 activities A4.1 (Advanced Network Services Design and Evaluation) and A4.2 (IPv6 Application Development). WP4 main aim is the design, consolidation and validation of an IPv6 based integrated end user service scenario, which integrates advanced network services and applications into a common framework. This document summarizes the results of the research and innovative tasks carried out along the third and fourth years of Euro6IX project in the context of WP4 activities A4.1 (Advanced Network Services Design and Evaluation) and A4.2 (IPv6 Application Development). WP4 main aim is the design, consolidation and validation of an IPv6 based integrated end user service scenario, which integrates advanced network services and applications into a common framework, which we call the 'Euro6IX Integrated Service Framework'. Therefore WP4 considers the integration of several advanced network services together with applications, which exploit the new features as one important goal. Being this the last period of the project, the work has been mainly focused on the consolidation and final integration of results. All the effort has been gradually reoriented to the integration of all results in a final demonstration scenario. This scenario have been organized around the IX model being proposed in the project, showing how the advanced network services can be offered from and IX and how the applications can benefit from those services. Work during this period has covered a wide variety of project objectives: The study and experimentation with the address delegation services provided by the advanced IPv6 IX Model, the deployment of multicast services based on SSM, the documentation of University Campus IPv6 transition cases, the development of tools to achieve Policy Provision, the deployment of QoS in the network, the development of new proposals to IETF in the field of transition and distributed security, the experimentation of new protocols to achieve secure authentication in IX and mobile environments, as well as the implementation of a host centric multi-homing solution. Besides, work has continued to consolidate the ongoing developments on the applications area. The document is organized as follows. The next two subsections summarize the results obtained in the context of advanced network services and applications development activities. Later in Section 2 and 3, these results are described in more detail for each of the sub-activities planned for this period, showing the partners involved, the objectives, a brief description, the relevance for the project and the main results achieved so far, as well as the future activities planned till the end of the project.
NAS-SAML is an access control infrastructure developed over the DIAMETER protocol, which makes use of SAML statements to represent the user authorization data and XACML policies to represent access control sentences. The main features of this architecture are: -·NAS-SAML provides two different access methods. Authorization can be performed in a transparent way, from the user's point of view, using the pull model. The push model slightly overloads the system in relation to the previous model, but it provides more options to the users, who can select a set of desired attributes to present to the system. - This infrastructure provides a flexible, scalable and manageable high-level authorization system. -·Organizations assign attributes to users to define its specific access profile. -·Organizations define the set of attributes needed by an user to perform a specific action, such as network access. -·This infrastructure can be easily extended to provide authorization decisions in other high level applications, such as the grid.
The Public Key Infrastructure with IPv6 support (UMU'PKIv6) is based on the design and later implementation of a complete and robust group of certification services for any organization type that wants to provide its clients and/or users of security mechanisms in their communications and data protection. UMU﷓ PKIv6 offers basic and advanced certification services both end users and VPN devices. By means of their services, a user will be able to carry out any operation type from his own navigator: request a certificate, renew or revoke it, look for other user certificates which wants to establish a secure communication, etc. Moreover, it allows users use of smart cards (which can be distributed by the own organization) to store cryptographic information, so that it facilitates the mobility of these. Some of the features developed for this infrastructure are: -·Requests of certification, renewal and revocation can be done for the users using a simple Internet browser. -·Users can storage cryptographic information (private key, certificate and CAs certificate) in their smart cards. This allows total mobility. -·Policy definition will establish the opportune restrictions inside an organization. -·Cross-certification is allowed in two ways, peer-to-peer (Bridge CA) and hierarchical cross-certification. -·It offers support to VPN devices. -·Public repositories (DNSSEC and LDAP) are used to store users and CAs certificates and CRLs/ARLs. -·The entities can consult to the Validation Service the online validity of the certificates using standard protocols like OCSP, SCVP or DVCS. -·CMC can be used for the entities as a Key Management Protocol (KMP), which provides a complete certificate lifecycle management. -·It offers services of Time Stamping (TSP).
Web application to establish an IPv6 over IPv4 tunnel and to provide an IPv6 (or a /48 prefix) address to the user.TID TunnelBroker has the following features: -·Dynamic Tunnels Feature. -·Provision of /64 and /48 prefixes. -·Actualisation Agent (oriented to IPv4 dynamic address ADSL connections). -·Mechanisms of communication with the TB users. Future Plans: As an exploitation activity of Euro6IX it is plan not only to continue the operation of TID Tunnel Broker but also to improve and evolve it as much as possible: - Provide DNS name resolution for up to 16 nodes per user, - Delegation of "user.portalv6.com" DNS domains,- Provide Multicast SSM Replication Service, - etc.
Multicast Content Management is a easy to use replication service for ISPs offering Multimedia Streaming Services to their customers with proxies facilities. Main features are: - Bandwidth Reduction - Easy to Use, - Web Interface Profile driven authorization system - Use of a A4C server with charging and accounting possibilities.
This document summarizes the results of the research and innovative tasks planned for the first year of Euro6IX project in the context of WP4 activities A4.1 (Advanced Network Services Design and Evaluation) and A4.2 (IPv6 Application Development). WP4 main aim is the design, consolidation and validation of an IPv6 based integrated end user service scenario, which integrates advanced network services and applications into a common framework. For that purpose, work has been organized around sub-activities covering: Mobility, multicast, QoS, AAA, and a broad range of security aspects like IPsec based VPNs, PKIv6 or DNSSEC, in the case of A4.1 activity; and basic and advanced IPv6 applications, network management and operation tools, IX support tools and code porting in the case of A4.2. As the number of sub-activities and the effort invested is high, the document just outlines the main objectives and results of each sub-activity. More detailed information can be found in the associated Technical Reports referenced at the end of the document.
Xpider is a P2P tool to be used in IPv6 Networks. It is compound of three elements: -·The server, which has the list of all the files shared by the clients connected to it. -·The core client, which connects to the server, asks to the server for the files and downloads them, connecting directly to the client owner of the file. -·And the User Interface, which connects to a core client and sends the user request to it. It also shows the progress of the download, the files shared by the core client, and the uploads in real time. Functionalities -·Multiple Sources Download. -·File Search: Name or Checksum. -·Files Unicast Search (List of Servers). -·Files Multicast Search (Multicast Group)
This document summarizes the 1st Year Internal Trial of the Euro6IX project. Lot s of investigation activities with respect to IPv6 network services and applications in an IPv6 IX based backbone network have taken place in the first year and a subset of them has been compiled and united as the '1st Year Internal Trial', which was realized mainly in November 2002 (M4.2).This deliverable describes the trial activities of the First Internal Trial in more detail and shows, how these activities are related to the special conditions of the Euro6IX networking scenario and which results were reached within the trials.
MoneyPenny is a graphical console for PDAs, in order to access to the Topaz kernel, either using IPv4 or IPv6. It has been developed with Microsoft Embedded Visual C++ 4.0 and allows receiving Topaz alers for PDA user. However, it doesn't allows modifying the detection logics
Deliverables D3.3.x will be produced every month, and this document is the first one of them, corresponding to month number 7 (July 2002). The deliverables have been produced in the context of activities A3.1 and A3.2. Activity A3.1 covers the deployment of the local networks attached to the different Euro6IX IXs nodes. Activity A3.2 deals with all deployments related to Euro6IX Backbone network. As a first approach, the structure of these network usage reports is the following: - First section (Current Network Status) is intended to clarify which links have been already deployed and which concrete networks have been attached. - Second section (Network Stability and Global Traffic Reports) is intended to show the reachability of all network sections as well as a global view of the total traffic exchanged in Euro6IX network. - Third section (Detailed Network and Services Usage in Events/Trials) is intended to show and analyse the traffic produced in some internal trials and in all public events where Euro6IX contributes in any way.
The 6NET and Euro6IX projects both focus on large-scale IPv6 deployment, but for different market segments. 6NET is deploying an IPv6 infrastructure in an academic research environment, with a high-capacity native IPv6 backbone spanning many countries. Euro6IX is deploying a number of pre-commercial IPv6 exchange points (IXs), with relatively lower connectivity speeds between the IXs. The projects work closely together and exchange information freely (as witnessed by this common Deliverable). This Deliverable describes areas in which they have identified some potential common activities. It also includes: -·The minutes of two joint workshops that have been held (March: Madrid and June: Limerick). Plans for future joint events (workshops and trials) are given. -·Potential plans for interconnectivity between the projects, and shared external connectivity (including to the Far East and Internet 2). -·General areas of potential collaboration, identifying the activities in each project where these activities are carried out, and the people/organizations who may liaise between the projects. -·Specific trials and scenarios for collaboration, focusing on areas where trials can be established and run between one or more partners on each project. We expect the plans presented in this document to evolve as the projects proceed. This document is a starting point for collaboration, both between the projects and beyond. We expect the collaboration results to date, and future plans, to be reviewed at the next joint 6NET-Euro6IX workshop.
Web Portal to interact with the experiences of the IPv6 users. Implemented with PHP-Nuke it offers sections with surveys, helpful documents, forums to exchange information and to solve problems related to the service offered by Telefonica I+D and one section to download IPv6 applications only available through IPv6.It has 747 users registered, and it offers information about the number of users connected.
This document describes all the systems deployed by Euro6IX partners to control, manage and secure Euro6IX network. It is also described all the systems to get statistics of the stability of the network and statistics of each partner's web service access. Revised deliverable to report the updates and new features added.
This document describes the chosen demonstration scenarios of the 2nd Years Public Trial of the Euro6IX project that was scheduled at the "Global IPv6 Service Launch Event" in Brussels, January 2004. Because of the actual lack of big number of Euro6IX "native" customers the 2nd Year Public Trial was again realized as an impressive demonstration at this very important IPv6 event that attracted lots of international visitors of this conference as well as the representatives from the European Commission and from other European projects. This deliverable D4.7p describes the demonstration activities of the 2nd Year Public Trial in more detail and show how these scenarios are related to the Euro6IX specific project conditions. The four main objectives of the Euro6IX project are: 1) To research an appropriate architecture to design and deploy the first Pan-European non-commercial IPv6 Internet Exchange (IX) Network 2) To use the deployed IPv6 IX infrastructure to research, test and validate IPv6-based applications and services 3) To open the Euro6IX network to specific user groups and 4) To do dissemination, liaison and coordination with clusters, fora, and standards organizations. In order to fulfil the second of these main project objectives, several trial activities (Internal Trials and Public Trials) are scheduled on a yearly basis. These trials are organized and carried out in Activity 4.3 of Work package 4. This document describes the organization, realization and the results of the 2nd Year Public Trial event, which was scheduled for Month 30 of the project lifetime (June 2004) and was realized already as Milestone 4.7 in the form of a very successful demonstration at the Global IPv6 Service Launch Event in Brussels/Belgium already in January 2004. The structure of this deliverable D4.7p "2nd 'Trials and Evaluation' Report" is as follows: -·Chapter 1 gives a short introduction to the 2nd Year Public Trial and clarifies the objectives of this kind of public trial. -·Chapter 2 contains an overview about the general approach of the 2nd Year Public Trial and the preparation of these trials -·Chapter 3 enhances this deliverable with a detailed description of the shown demonstration scenarios of the Global IPv6 Service Launch Event (including the achieved results). -·Chapter 4 concludes this deliverable D4.7p with a short summary of the 2nd Year Public Trial and some lessons learned during preparation and realization of the "Global IPv6 Service Launch Event" demo. In summary it can be said that the 2nd Year Public Trial of the Euro6IX project contained besides a very sophisticated IPv6 network set-up, lots of very interesting and successful IPv6 scenario demonstrations. The 2nd Year Public trial highlighted the achievements of the Euro6IX project and attracted the attendees of the Global IPv6 Service Launch Event and the EC very much. Hence the objectives of the 2nd Public Trial, as written down in the Technical Annex of the Euro6IX project, were met.
"Dynamic Euro6IX Nodes" (DEN) is a web-based portal where clients may subscribe to network services offered by their IX.This system is used at Alcobendas IX (MAD6IX) as a provisioning tool for services such as "bandwidth on demand", "L3MF"or "quality of service". DEN integrates several results of the Euro6IX project, for example, the IPv6 implementation of Free Radius server or Magalia monitoring tool. Actually, there are two experiences with TID and Consulintel clients at MAD6IX.
This deliverable summarizes the efforts and activities related to the maintenance, operation, issues and evolution of the Euro6IX network platforms in order to intensify the trials during the extension of the project.It includes also the activities related to the deployment of an IX Services provision system, three advanced Multimedia Services over IPv6 Multicast SSM enabled sites and trial experiences such as an IPv6 WiFi ISP and external parties trials. This document describes the main activities developed in the Euro6IX project extension (January to June 2005) in order to keep the Euro6IX network operational, provide new advanced network features as widely as possible in the Euro6IX backbone such as the Multicast SSM support, develop advanced end-user applications using advanced network features and perform internal tests and trials with external users. In order to have a complete picture, it is highly recommended to review the following Euro6IX documents: - D3.3 Statistics, management and security control systems Development, - D3.4 Final Description of overall Network Architecture implemented.
The four main objectives of the Euro6IX project are: 1) To research an appropriate architecture, to design and deploy the first Pan-European non-commercial IPv6 Internet Exchange (IX) Network 2) To use the deployed IPv6 IX infrastructure to research, test and validate IPv6-based applications and services 3) To open the Euro6IX network to specific user groups and 4) To do dissemination, liaison and coordination with clusters, standardization bodies and standards organizations. In order to fulfil the second of these main project objectives, several trial activities (Internal Trials and Public Trials) are scheduled on a yearly basis. These trials are organized and carried out in Activity 4.3 of Work package 4. This document describes the organization, realization and the results of the 3rd Year Public Trial event, which was scheduled for Month 42 of the project lifetime (June 2005) and was realized as Milestone 4.9 in the form of a very successful demonstration at the Global IPv6 Summit 2005 in Barcelona/Spain during June 2005. The structure of this deliverable D4.9p 3rd Trials and Evaluation Report is as follows: - Chapter 1 introduces the 3rd Year Public Trial and clarifies the objectives of this kind of public trials. - Chapter 2 contains an overview about the general approach of the 3rd Year Public Trial and the preparation of these trials - Chapter 3 enhances this deliverable with a detailed description of the shown demonstration scenarios of the Global IPv6 Summit 2005 Event (including the achieved results). - Chapter 4 concludes this deliverable D4.9p with a short summary of the 3rd Year Public Trial and some lessons learned during preparation and realization of the "Global IPv6 Summit 2005" demo. In summary, it can be said that the 3rd Year Public Trial of the Euro6IX project contained besides a very sophisticated IPv6 network set-up, a bunch of very interesting and successful IPv6 scenario demonstrations. The 3rd Year Public trial highlighted the achievements of the Euro6IX project and attracted the attendees of the Global IPv6 Summit 2005 Event very much. Hence, the objectives of the 3rd Public Trial, as written down in the Technical Annex of the Euro6IX project, have been fully met.
Magalia is a Real Time Monitoring Tool for IPv6 NOCs. The features developed for this tool are: -·Network Maps Grpahical Edition -·Shared Management Functionality -·Nodes (Hosts, Routers) Status Monitoring -·Links Status (SNMP): Load (colour and figure), physical failures, admin shut. - Communication with Topaz: module to show topaz alerts in XGES -·Attended Configuration -·Module to send alerts via e-mail -·TCP Services Monitoring Module (Services Contextual maps) -·WEB Access to Xges maps -·Communication among NOCs (Voice Module) -·Module to retrieve network data from other networks webs (example: abilene). -·Support of MIPv6.
This Document provides Euro6IX project's dissemination plans over the project life period. It identifies the on-line dissemination, project and IST level communication, events to be organized by the project, participation in standards activities, and presentation of project results in workshops and conferences as well as publication initiatives. The deliverable also provides early exploitation plans from the project partners and their associated sponsors and user groups that can be identified in the early phase of the project.
Isabel is a multipoint group collaboration tool running on PCs. Isabel implements a very effective floor and session control for real-time collaborations over the Internet were participants can be audiences in classrooms, auditoriums or meeting rooms, as well as individuals sitting in front of their desktops. Isabel has been used for several years to perform various kinds of distributed activities. In the context of Euro6IX project, ISABEL CSCW application has been extensively used as a useful and demanding tool for testing new advanced services. In particular, ISABEL has been adapted to: - Source Specific Multicast service. Isabel already supported IPv6 Any Source Multicast. The adaptation to SSM required the design and implementation of a mechanism for SSM source address discovery, adapted to work in conjunction with the ISABEL MCU control protocol. Version 4.8 fully supports SSM and has been successfully tested over Euro6IX SSM network. - A new advanced tool to deploy and manage advanced services platforms automatically. This tool is based on an XML-like language named XEDL and allows the automatic deployment and management of an ISABEL session from one of the sites, including services like IPsec based security or QoS. The session description in XEDL is automatically generated by a management tool starting from the data supplied by the participants.
Topaz is one of the first intrusion detection systems (IDS) for IPv6 networks. It's wide used at Telefonica Investigacion Y Desarrollo (TID) laboratories as one of the main tools used to secure its IPv6 network. "Topaz" offers both a text and graphical language to configure new pattern attacks, including specific future IPv6-based attacks. Another interesting characteristic about "Topaz" it's that this IDS may detect both IPv4 or IPv6 intrusions, so it's ideal for dual stack networks, or networks that are migrating to IPv6.
Deliverable 4.5 analyses the personal data issues that the deployment and use of IPv6 may involve in the information society by means of the precise analysis of different cases to which this protocol shall be applicable. In particular, we analyse legal issues arising out of the use of this protocol in mobile telephony, personal computers and household appliances. After the analysis of these matters, we suggest certain alternatives or proposals with the purpose of sorting out or, if applicable, minimizing the legal issues explained throughout this Deliverable. The widespread use of IPv6 could have legal consequences that have been taken into account whilst developing the Protocol. Some of these legal consequences are the implications that IPv6 might have on the right to privacy and data protection. These matters are based on the fact that, under some circumstances, an IP address based on the Internet Protocol version 6 could be considered personal data because it could contain in its configuration a Unique Identifier which could be linked directly to the interface of the terminal that is using this IP and indirectly to its user, whom might be an individual. One of the main scopes of this document is to analyse the current legislation on data protection adopted by the different Member States of the European Union with the purpose of determining if it might be applied initially to IPv6 or, on the other hand, if it would be necessary to adopt a specific legal legislation for IPv6. Therefore, there are two Directives which are going to be analysed by this Deliverable: Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995, on the protection of individuals with regard to the processing of personal data and on the free movement of such data, and the Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector. Also, the implementation of IPv6 has some important consequences regarding the processing of personal data. First of all, the IP address itself is considered personal data and, therefore, its processing is bound by this legislation. Secondly, all the information that could be related by a third party to an IP address based on an Unique Identifier, for example the information obtained by this third party about the Internet use or the results of surfing the Net by a specific user, might also be considered as personal data because at the end, it could be linked, using certain means, to its owner or data subject. There are some means that could be used by a company or individual to link an IP address to its holder, for example, a contract or using public directories. The creation and use of these means will be analysed in detail in this document. To conclude, this Deliverable aims to provide a wide perspective concerning the implications, problems and advantages that the implementation of IPv6 would have regarding the privacy and data protection of its users.

È in corso la ricerca di dati su OpenAIRE...

Si è verificato un errore durante la ricerca dei dati su OpenAIRE

Nessun risultato disponibile