Differences

This shows you the differences between two versions of the page.

imara:positions:2010_internship_ipv6security [2011/02/04 13:33]
Paulo RESENDE created
imara:positions:2010_internship_ipv6security [2011/04/05 14:17] (current)
Paulo RESENDE
Line 1: Line 1:
====== Open Position/Internship "Deployment of an IPv6 Security Platform" ====== ====== Open Position/Internship "Deployment of an IPv6 Security Platform" ======
 +
===== Context of the internship ===== ===== Context of the internship =====
Most ITS (Intelligent Transport Systems) applications require efficient communications between vehicles or between the vehicle and the infrastructure. An IPv6 vehicular mobile router is in charge of maintaining Internet access and session continuity for other in-vehicle network nodes. Mobile access to the Internet is maintained using NEMO Basic Support [RFC 3963] over various interfaces (802.11 a/b/g, 802.11p, infrared and 2G/3G) while a VANET (Vehicular Ad-hoc NETwork) routing protocol is running between the vehicles. IPv6 is natively supported in all access networks. All IP communications between the vehicle and its communication peers (other vehicles, roadside infrastructure, and Internet) must be secured. Security (IPsec/IKE/SeND) and access control (Diameter) mechanisms must thus be used. Most ITS (Intelligent Transport Systems) applications require efficient communications between vehicles or between the vehicle and the infrastructure. An IPv6 vehicular mobile router is in charge of maintaining Internet access and session continuity for other in-vehicle network nodes. Mobile access to the Internet is maintained using NEMO Basic Support [RFC 3963] over various interfaces (802.11 a/b/g, 802.11p, infrared and 2G/3G) while a VANET (Vehicular Ad-hoc NETwork) routing protocol is running between the vehicles. IPv6 is natively supported in all access networks. All IP communications between the vehicle and its communication peers (other vehicles, roadside infrastructure, and Internet) must be secured. Security (IPsec/IKE/SeND) and access control (Diameter) mechanisms must thus be used.
 +
 +----
===== Objective of the internship ===== ===== Objective of the internship =====
Line 11: Line 14:
If good progress is made, the system will be brought to the vehicular platform and further validation tests will be performed. If proven successful, access control will be configured in an operational mode so that the mechanisms could constantly be re-used in forthcoming experimentations using the vehicular platform and validated with ITS applications such as toll payment, emergency calls, and collision avoidance. If good progress is made, the system will be brought to the vehicular platform and further validation tests will be performed. If proven successful, access control will be configured in an operational mode so that the mechanisms could constantly be re-used in forthcoming experimentations using the vehicular platform and validated with ITS applications such as toll payment, emergency calls, and collision avoidance.
 +----
===== Key words ===== ===== Key words =====
Line 21: Line 25:
  * SeND   * SeND
-===== Profile of the candidate =====+----
 +===== Profile of the candidate =====
Student in its last year of engineering school (Master course) with Linux networking development experience seeking for technical development and hands-on experimentation. See below for the details of the required and desirable skills. The profile of the candidate is thus purely technical although the internship is conducted in a research environment. Candidates looking for a PhD position or for a research experience should abstrain from applying to this internship (other possibilities may exist within IMARA). Applications from candidates with no Linux networking development experience will not be considered. Student in its last year of engineering school (Master course) with Linux networking development experience seeking for technical development and hands-on experimentation. See below for the details of the required and desirable skills. The profile of the candidate is thus purely technical although the internship is conducted in a research environment. Candidates looking for a PhD position or for a research experience should abstrain from applying to this internship (other possibilities may exist within IMARA). Applications from candidates with no Linux networking development experience will not be considered.
 +
 +----
==== Required skills ==== ==== Required skills ====
Line 34: Line 41:
    * Good ability to communicate in English (written and spoken);     * Good ability to communicate in English (written and spoken);
    * Ability to take initiatives;     * Ability to take initiatives;
 +
 +----
==== Desirable experience ==== ==== Desirable experience ====
Line 42: Line 51:
    * Familiar with EAP, IKEv2, Diameter, Certificate, PKI, SeND     * Familiar with EAP, IKEv2, Diameter, Certificate, PKI, SeND
    * Familiar with security threats at the IP level     * Familiar with security threats at the IP level
-===== Administrative Details ===== 
 +----
 +
 +===== Administrative Details =====
  * Contact: [[:users:thierryernst|Thierry Ernst]]   * Contact: [[:users:thierryernst|Thierry Ernst]]
  * Expected start: February 2010   * Expected start: February 2010
Line 50: Line 61:
  * Host team: [[:imara|IMARA project-team]], working on self-driving vehicles and involved in several ITS (Intelligent Transport Systems) projects. IMARA is part of the [[:lara|LaRA]] joint-research unit.   * Host team: [[:imara|IMARA project-team]], working on self-driving vehicles and involved in several ITS (Intelligent Transport Systems) projects. IMARA is part of the [[:lara|LaRA]] joint-research unit.
 +----
-{{tag>position current imara IPv6 lara-com 2011}}+{{tag>position current imara internship IPv6 lara-com 2011}}
 
imara/positions/2010_internship_ipv6security.txt · Last modified: 2011/04/05 14:17 by Paulo RESENDE
Recent changes · Show pagesource · Login