WIDE Technical-Report in 2008

The WIDE Nautilus6 Working
Group Report 2007
wide-tr-nautilus6-report2007-00.pdf

WIDE Project : http://www.wide.ad.jp/

If you have any comments on this document, please contact to ad@wide.ad.jp

The WIDE Nautilus6 Working Group Report 2007
Nautilus6 Working Group• Manabu TSUKADA (INRIA Rocquencourt, France)

Abstract• Cesar VIHO (IRISA/INRIA Rennes, France)

This report summarizes the activities realized within the
WIDE Nautilus6 Working Group during the year 2007.

3
1

Introduction

The WIDE [1] Nautilus6 Working Group [2] was established in fall 2002 to provide a better IPv6 mobility environment to the users. We concentrate our work on research, implementations and demonstrations on various topics aroundIPv6 and IPv6 mobility: host and network mobility, multihoming, seamless mobility, AAA, security, applications andoperations.

2

Contributors

The following people have contributed to this report (inalphabetical order):• Martin ANDRÉ (University of Tokyo, Japan)• Jean-Marie BONNIN (ENST-Bretagne, France)• Antoine BOUTET (IRISA/INRIA Rennes, France)• Sébastien DECUGIS (University of Tokyo, Japan)• Thierry ERNST (INRIA Rocquencourt, France)• Satomi FUJIMAKI (Keio University, Japan)• Romain KUNTZ (LSIIT / Louis Pasteur University,
France [3])• Benoit LE TEXIER (ENST-Bretagne, France)• Jean LORCHAT (Keio University, Japan)• Olivier MEHANI (INRIA Rocquencourt, France)• Koshiro MITSUYA (Keio University, Japan)• Nicolas MONTAVONT (ENST-Bretagne, France)• Keiichi SHIMA (Internet Initiative Japan, Japan)

3.1

Implementation
NEPL

The NEMO Platform for Linux (NEPL) is a NEMO Basic Support [4] implementation for the GNU/Linux operating system. It has originally been developed as an extension
to the Mobile IPv6 implementation for Linux (MIPL2 [5])by the Helsinki University of Technology in cooperation
with Nautilus6.
This year, the USAGI WIDE Working Group has released UMIP [6], an improved version of MIPL2 that aims
at providing the necessary changes to run on the latest kernels while improving the software to respect the standards.
Nautilus6 has thus proposed and continuously maintained
NEPL for UMIP [7]. It is freely available as a patch, andseveral releases have been done this year. The latest one
from November 2007 is available through the NEPL Howtothat we also maintain [8]. Nautilus6 provides binary packages as well for Debian and Ubuntu available on our Mobile
IPv6 package repositories (section 5.4).
Nautilus6 also proposes a Multiple Care-of Addresses
registration (MCoA [9]) implementation for NEPL [10]. It
brings multihoming features to NEPL, thus ensuring seamless and fault tolerant communication to a node running
NEPL. This implementation is released as a patch alsoavailable through the NEPL Howto [8]. We recently released an updated version in November 2007.
NEPL and MCoA are used in a number of academical
and industrial projects. The Nautilus6 operational Service
operated in Keio University (Japan), Louis Pasteur University (France) and ENST-Bretagne (France) uses NEPL on
their operational Home Agents (section 6) and in Homeguy, the Mobile IPv6 oriented Live-CD developed by Nautilus6 (section 5.3). The ANEMONE European testbed [11]uses NEPL and MCoA in their IPv6 mobility testbed. The
French REMORA project [12] also uses both NEPL andMCoA as the core feature of their demonstration testbed.
NEPL and MCoA have also been used within the WIDE

project to provide reliable IPv6 connectivity during the
WIDE Camp [13].

3.2

SHISA

SHISA is a Mobile IPv6/NEMO BS implementation
built on top of BSD Operating Systems. This year, westarted the activity to import the stack to the BSD mainline kernel. At the same time, we also tried to provide apractical usage example using the stack.
3.2.1

Merging Approach

The ﬁnal goal of the SHISA development project is to integrate the developed stack into the BSD system so thatevery BSD users can utilize the IPv6 mobility function.
SHISA was originally developed on top of the KAME IPv6
stack [14] for NetBSD 2.0 and FreeBSD 5.4. We ported
SHISA to the NetBSD-current tree as the ﬁrst step of porting effort. There are two reasons why we chose NetBSD
as the ﬁrst platform for the porting work. The ﬁrst reason
is that it supports various kinds of architectures. The mobility functions are useful especially when it is integrated toa moving entities such as PDAs and cars or trains, and soon. They usually use an architecture that runs with limited
resources. NetBSD supports many such architectures thatis suitable for embedded use, and we wanted to realize suchsmall devices using our code. The other reason is the difference between the KAME tree (that was based on NetBSD
2.0) and the latest NetBSD is relatively small compared toother BSD variants that KAME supported. This makes it
easier to port the SHISA code from KAME to NetBSDcurrent.
The ﬁrst approach to the NetBSD developer was to havea presentation [15] in the Asia BSD Conference which washeld in Tokyo in March 2007. In this conference, we introduced our IPv6 mobility architecture to the other BSD developers. In last April, one of our developer was registeredas a NetBSD developer and was given access to the IPv6
network code to add IPv6 mobility functions. Currently weare following the latest NetBSD current code and preparinga patch ﬁle for the latest code.
3.2.2

Practical Usage

We also utilize the SHISA stack as an experimental network
mobility router. The activity was done as a part of the Internet CAR Working Group [16] activity. The router is basedon the Soekris platform. The router has two external network interfaces, one is a 802.11 wireless interface, the otheris a PHS data communication interface. The router connects
to the Internet through the wireless interface, whenever it isreachable to one of the known wireless access points thatare pre-registered to the router. Otherwise, it connects to

the Internet through the PHS interface. Currently, the PHS
data communication service does not provide IPv6 accessservice. In this system, the router connects to the IPv4 Internet through the PHS interface ﬁrst, and creates an IPv6
over IPv4 tunnel to get IPv6 connectivity.
The router is also equipped with another wireless network interface, which is used for direct communication with
the neighbouring mobile routers. On the wireless interface, the OSPFv3 protocol is operated on top of the adhoc
mode 802.11 network operation, and if two or more mobilerouters are in the range of the wireless communication area,
these routers become direct reachable entities. This shortcut path reduces the redundant communication path, whichusually occurs when two mobile routers are communicatingeach other. In this case, the packets between the two routers
are usually go through their home agents. Using the second
wireless network interface makes route optimization when
two routers are located closely.
The summary is reported as a conference paper [17] atthe last Asia BSD Conference.
3.2.3

SHISA Project Summary

As an milestone of the SHISA development project, wehave summarized our previous work on developing Mobile
IPv6 stack on BSD systems in [18]. We implemented theIPv6 mobility stacks based on the IETF standard mobility
speciﬁcations and released the stacks to accelerate the deployment of the IPv6 mobility technology. The ﬁrst versionof the stack (KAME Mobile IPv6) was implemented in the
kernel, but the kernel stack design and its implementation
had problems in extensibility and ease of development. We
redesigned the stack moving the mobility signal processing code to user space. To keep the normal packet processing performance, the normal packet input/output processing
code was kept in the kernel. The new stack (SHISA) can beeasily extended to support new features. Thanks to this design, we could add NEMO BS, Multiple CoA Registration
and IPv4 mobile network support to the SHISA stack easily.
Also the SHISA stack will more readily attract third party
development activities [19, 20] thanks to the user space implementation that is easier to develop than the kernel development. We made several experiments and demonstrations [21, 22, 23, 24] proving the applicability and stabilityof the SHISA stack, and to advertise the IPv6 mobility technology. We are now focusing on adapting the SHISA stack
to the original BSD distributions so that the SHISA stack
can be merged into these distributions.

3.3

DSMIPv6 for BSD

Dual Stack Mobile IPv6 (DSMIPv6) is an extension of
Mobile IPv6 to support IPv4 care-of address and to carryIPv4 trafﬁc via bi-directional tunnels between mobile nodes
and their home agents. Using DSMIPv6, mobile nodes only
need the Mobile IPv6 protocol to manage mobility whilemoving within both the IPv4 and IPv6 Internet. This is an
important feature for IPv6 mobility during its deployment
phase because IPv6 access network is not widely deployedyet. We thus decided to develop DSMIPv6 implementationfor SHISA, our open source Mobile IPv6 and NEMO implementation for BSD operating sysytems.
The DSMIPv6 implementation was designed to separate the signaling function and the forwarding function, andto minimize modiﬁcations on the existing kernel and user
land programs. The binding management code is sharedwith both IPv4 and IPv6 mobility functions by using IPv4mapped IPv6 address format. When care-of or home addresses are used, new or modiﬁed correspondent functions
are called according to its address family. An IPv4 careof address detection feature is also added to the user land
programs.
By evaluating the implementation, it is conﬁrmed thatthe DSMIPv6 implementation works in the all situations
without adding remarkable header processing overhead.
It is thus said that the speciﬁcation is stable to forward
IPv4/IPv6 packets address to their home addresses/mobile
networks. The result was presented at [25].

3.4

4Integration of IPv6 Mobility and IKEv2

This year we have focused our work on providing dynamic keying for Mobile IPv6 as deﬁned in RFC4877 [26]on the Linux platform, using the racoon2 [27] implementation for IKEv2. This is the ﬁrst step to achieve MIPv6
bootstrapping in AAA environments as deﬁned by RFC
5026 [28].

4.1

Racoon2 modiﬁcations

We have made several modiﬁcations to the racoon2 implementation in order to make it compliant to the MIPv6 requirements. For example, when used with UMIP, racoon2
does not handle the SPD entries related to the MIPv6 messages, but it must be able to negotiate the security parameters (SA) for these entries. Another issue, the IKE session
endpoints differ from the SA endpoints, which was also notsupported by racoon2. The daemon must also be able tonegotiate pairs of SA for asymmetrical trafﬁc selectors (forexample to protect BU in one way and BA in the other way.)
All these modiﬁcations have been released as patches(see next section for detail) and the racoon2 core team hasplans to integrate it in their daemon. Nautilus6 also provides binary packages for Debian and Ubuntu available on
the Mobile IPv6 package repositories (section 5.4).

DSMIPv6 for Linux
4.2

The Linux counterpart of the DSMIPv6 implementation is also being developped within the Nautilus6 Working
Group, in collaboration with the USAGI Working Group. It
is currently working with Linux Kernel 2.6.23 and umip-0.4
daemon codes provided by the USAGI git server.
The implementation itself is based on an old IETF draft(draft-ietf-mip6-nemo-v4traversal-04). It is split in kernel
and userland parts according to what processing is required.
On the userland side, separate functions are called according to the type of IP address (either v4 or v6) whenever
speciﬁc handling is required, whereas on the kernel sidemuch of the XFRM modular framework is reused for UDP
encapsulation / decapsulation. This makes the code very
lightweight and portable to more recent versions of the kernel and MIPL daemon code.
The implementation currently supports IPv4 Care-of Addresses to provide IPv6 connectivity in legacy IPv4-only access networks. It has been succesfully experimented during
Spring 2007 and the results will be shown in a paper to becompleted. Support for IPv4 Home Address is planned aswell as interoperability testing with the SHISA implementation described previously as soon as compliance will bereached with latest version of the document (either draft or
RFC).

Dynamic Keying HowTo

We have published a HowTo document [29] describing
the installation and conﬁguration of mip6d and racoon2 inorder to achieve dynamic keying in MIPv6 and NEMO in
Linux.
This document describes the steps to build the needed
environment (kernel, mip6d and racoon2 with appropriate
patches) and the conﬁguration of each part. The authentication method is certiﬁcate-based.

4.3

New MIGRATE format

The current implementation of dynamic keying uses the
MIGRATE message as deﬁned in draft 03 [30] for the communication between the MIPv6 daemon and the IKEv2 daemon.
We have identiﬁed several problems with this interface.
The SADB X EXT PACKET message for example can not
be efﬁciently implemented in Linux. Moreover, it requires
the IKE daemon to parse the BU message to acquire theCare-of Address that must be used in the IKE exchange.
This adds a lot of complexity. Another issue is that using
the MIGRATE message to migrate the IKE session is notalways suitable (see next section for detail). For example,

if no tunnel-mode SA is deﬁned, the IKE session would notsurvive movement.
Considering all these issues, we have written a new proposal for the interface between MIPv6 and IKEv2, basedon the MIGRATE message. This new proposal has been
submitted to the previous draft authors and will serve
as a base for the release 05 of the document (not published yet). The main changes are: we do not use the
SADB X EXT PACKET extension anymore, but we have a
new extension SADB X KMADDRESS in the MIGRATE
message, to pass the IKE session endpoints from the MIPv6
daemon to the IKE or IKEv2 daemon. We also change a little bit the ordering of the events, issuing the ﬁrst MIGRATE
before sending the BU message.
This new solution has been implemented and works perfectly. It will be made available through the Nautilus6 package repository as soon as the new version of the draft ispublished at the IETF.
Figure 1. Interaction in Operational service

4.4(K) ﬂag

We have found another issue related to dynamic keying
in the previous MIGRATE implementation. It is an interoperability issue.
RFC 3775 speciﬁes a ﬂag in BU and BA messages representing ”Key Management Mobility Capability (K)”. This
ﬂag represents the ability of the peer to move the IKE session endpoints when the MN moves.
We have submitted an Internet Draft [31] to detailthe sequence of events that can happen when the ﬂag
is not used properly, as it is the case with the current racoon2 implementation (but ﬁxed thanks to the new
SADB X KMADDRESS extension). This document willserve as a base to propose a new clariﬁcation in the RFC
3775 that is being prepared in the MEXT IETF workgroup(RFC3775bis).
At the time of writing this document, it is not known
whether the new proposal is accepted.

5Operation Support

The Nautilus6 operational MIPv6 service is meant toprovide a full featured IPv6 Mobility service to promote
the use of mobility and as a playground for experimental
protocols deployment. Our Operational service consists indifferent parts cooperating together as shown on Figure 1.

5.1

HAiku

We have released a simple and intuitive web interface
called HAiku [32] which goal is to simplify the procedures
involving the administrators and the users of a Home Agent.
It is developed within the operational activity and initiallydesigned for our public operation (section 6), however wewant to make a tool adapted to all Home Agents. The
ﬁrst public release has been made in May 2007 and gave
full support for Mobile IPv6 support and static keying with
IPsec. This version let the users register to a Home Agentand create Mobile Nodes with the static security bindings
managed by the software. A live CD with Mobile IPv6 support (section 5.3) and customized for each created Mobile
Nodes is also available to help in using the service. On theadministrative side, operators can manage the list of registered users and disable temporarily or delete users’ accounts. They have also a basic control on the conﬁgurationof the Home Agent.
The version 0.2, released in October added among others
the support for NEMO and the support for protecting all
the trafﬁc between the Mobile Node and the Home Agent.
This version also added the possibility to send a mail fromthe interface to registered users and display Home Agentstatistics retrieved thanks to SONAR.
The upcoming version 0.3 adds the support for Dynamic
Keying and rails migrations.
Our work on HAiku has led to modiﬁcation on existing
software to add features needed for an operational use. Oneof these change was to add the capability to the MIPv6 daemon to dynamically reload its conﬁguration. Until then, it
was not possible to authorize a new node to register with theHome Agent without restarting the daemon. This was unacceptable for our operational service and we made it possible
to reload the conﬁguration without closing existing bindings.
Another change was to provide the support for nested
conﬁguration ﬁles to avoid doing change on the ﬂy on theMIPv6 daemon conﬁguration ﬁle. We made it possible touse one main conﬁguration ﬁle for the daemon and one ﬁlefor each Mobile Node. The main conﬁguration ﬁle doesn’tchange and we create or delete additional ﬁles for Mobile
Node management. This is a clean way to proceed.

5.2

SONAR

SONAR [33] is ﬁrst designed to be a set of free tools tobuild a statistics repository containing detailed informationof mobile nodes. Users can send statistics information about
their mobility system to a statistics repository by using thesetools. The repository shows the history and analysis resultsof the collected data. The analysis includes classiﬁcation ofmobility, MIPv6/NEMO protocol evaluation, network access technologies benchmark and correlation between L2and L3 technologies.
In 2007 we developed the home agent client and use its
output to produce live statistics and monitoring of the Home
Agent through HAiku interface (section 5.1). Preliminary
tests and experiment have been covered in a paper [34].
The mobile node client (mobile host and mobile router)is available for Linux, FreeBSD and NetBSD. The homeagent client is available for Linux and NetBSD.

5.3

Homeguy

We developed Homeguy [35] to be used jointly with ouroperational Home Agent but it soon proved to be also a very
elegant way to install a full Mobile IPv6 distribution in amatter of minutes. Homeguy is a complete Operating System on CD-ROM with Mobile IPv6 capability that can beinstalled easily on hard drive. It is based on latest Ubuntu(currently gutsy) and has support for Mobile Host or Mobile
Router. We bundled many Mobile IPv6 related software including implementations or networking tools, multimedia
software, administration scripts, etc. We release a beta version of Homeguy in October and the 1.0 at the end of theyear 2007.

5.4

Packages repositories

One of the difﬁculties of Mobile IPv6 deployment is thelack of packaged solutions. We started to package Mobile
IPv6 related software for Debian and Ubuntu in order tofacilitate the development of Homeguy (section 5.3). The
need was motivated by the fact that setting up a complete
Mobile IPv6 environment required to build a new kernel
with MIPv6 extension enabled, build daemons, patch software, etc. We decided to provide our packages publicly to
spread the use of Mobile IPv6 technology. Today, our Debian and Ubuntu packages repository containing softwarethat had no binary packages yet or that had to be modiﬁed

to support mobility are widely used and are a great help for
those who want to setup MIPv6 environment.

5.5

IPv6 streaming server

We have set up an IPv6 streaming server within Nautilus6 to face the lack of IPv6 content. Video playlists areserved by a web server in IPv6 and we have conﬁgured
Homeguy to have direct access to these media. This is very
useful to test your IPv6 connectivity and visually experience
network handovers.

5.6

Global HAHA

Global HA to HA (Global HAHA) protocol is an extension of Mobile IPv6 and NEMO to remove their link layer
dependencies on the Home Link and distribute the homeagents at IP layer. In this mechanism every home agents areconnected as a mesh topology using IP over IP tunnel andadvertise the same home preﬁx to the Internet. A Binding
Update message sent from a mobile node will be thus routed
to the nearest home agent based on the routing information.
All the trafﬁc from the mobile node to other Internet nodes
is received by the nearest home agent and then forwarded tothe ﬁnal nodes. All the trafﬁc to the mobile node from theInternet nodes is received by the home agent that is nearest
to the sending nodes and forwarded to the mobile node.
We are now preparing the experimental Global HAHA
network on the actual IPv6 Internet. Currently, three homeagents are placed at IIJ (Japan), WIDE (San Francisco) and
WIDE (Keio University). Each home agent (or upstream
router of the home agent) are advertising the same preﬁx
used for the home network preﬁx using the BGP routing
protocol. Next year we will have some experiments related
to home agent distribution/redundancy technique using thislive experiment network.

6
6.1

Public Operation
K2

Nautilus6 operates a Home Agent in K2 campus (ShinKawasaki, Japan) that has been made available publicly forany personal or scientiﬁc use at [36] in April 2007 and provides IPv6 mobility to more than eighty registered users.
This Home Agent is running the latest stable version of
HAiku (section 5.1) and Homeguy (section 5.3), and is themain Home Agent of Nautilus6 operational service.
A test Home Agent is also available and has features tobe included in main service. It runs development version of
HAiku and Homeguy. K2 moreover hosts an IPv6 streaming server (section 5.5), the Debian and Ubuntu package

repositories (section 5.4) and the documentation of the Operational service.

6.2

Louis Pasteur University

The Louis Pasteur University Network and Protocols
team [3] operates a Mobile IPv6 Home Agent as part of the
Nautilus6 operational service. This Home Agent is locatedin Strasbourg, France. Thirteen users (mainly academics)
subscribed to the service. We also use this Home Agent for
educational purposes amongst the Louis Pasteur University
students.
This Home Agent currently runs HAiku 0.1 (section 5.1)
though we plan to upgrade the service to HAiku 0.2 for the
beginning of year 2008.
The Network and Protocols team also participated to the
publication of the HAiku installation documentation on the
GNU/Linux operating system.

6.3

ENST-Bretagne and IRISA/INRIA
RennesThe University campus called Beaulieu in Rennes,
France has both GPRS and Wi-Fi connectivity.
An outdoor Wi-Fi access has been deployed on the campus in order to provide an IPv6 access which can be viewed
as Wi-Fi hotspots (Figure 2). The outdoor Wi-Fi coverageis represented by the red areas in the above ﬁgure. These
access points are completely managed by the project, thus
we can set up conﬁgurations to answer speciﬁc needs. The
IPv6 preﬁx advertised by an access point depends on thelocalization on the campus.
The blue areas are the indoor coverage of the project.
However, this coverage is not yet operational for the demonstration. Moreover, the campus is fully covered with a
GPRS access. As this GPRS network only provides currently IPv4 connectivity, an IPv6 over IPv4 tunnel is set up
in the ANEMONE testbed.

6.4

Figure 2. Overview of indoor and outdoor
testbed in Rennes

INRIA Rocquencourt

Mobile Adhoc Network (MANET) routing protocol and
NEMO basic support protocol are considered key technologies for vehicle networks. Cooperation between MANET
and NEMO (MANEMO) brings several beneﬁts especiallyfor route optimization and multihoming. We made a realﬁeld vehicle communication environment with NEMO andMANET. By switching from NEMO to MANET, routes between vehicles are optimized and network performances
improved in terms of latency and bandwidth. Experiments result shows that network performances are further improved with simultaneous utilization of NEMO andMANET. Network performances were shown on a web site

Figure 3. Geographical Position Mapped Network Performancein real time and mapped at locations using GPS information.
Figure 3 is the screen shot of the website.

7
7.1

Demonstrations
Ubiquitous Network Symposium

We had a demonstration at the Ubiquitous Network Symposium, which was held in Akihabara (Tokyo) on November 29th and 30th 2007.
The purpose of the demonstration was to show our workon the MIPv6 and IKEv2 interaction mechanism (Figure 4
is the poster used at the demonstration to show the purpose
in Japanese). We demonstrated a working implementationof RFC 4877 [26], where we had NEMO (NEPL implementation, section 3.1) using IKEv2 (racoon2 [27]) to dynam-

Figure 6. UNS demonstration principles

Figure 4. UNS demonstration poster

Figure 7. Mobile Network

Figure 5. UNS demonstration testbed

ically establish the security associations parameters used
to protect NEMO signaling and optionally tunneled trafﬁc.
The protection of trafﬁc payload between the Home Agentand a Mobile Router was the main focus of the demonstration.
The demonstration testbed (Figure 5) was set as described in Figure 6.
We had two mobile routers registered to a home agent
running our HAiku interface. One Mobile Router was using
IPsec to protect all trafﬁc tunneled to the Home Agent, theother Mobile Router was protecting only the signaling messages (BU, BA, ...). In the mobile networks (Figure 7) attached to these routers, we had IPv6 cameras and other sensors. A correspondent node in the home link was displaying

pictures from the cameras. The routers could move between
a wired network and a wireless network, which was used torepresent a non-controlled and insecure environment. A spy
computer (Figure 8) was listening to all wireless trafﬁc andrunning a custom version of driftnet – a tool that can extract
pictures from TCP streams and display these pictures – that
was able to capture in IPv6 and tunneled trafﬁc. When themobile router without protected payload was moving to thewireless network, the spy computer was able to capture anddisplay the pictures sent by the camera. When the mobilerouter with tunnel protection was moving, the spy computer
failed to display the camera pictures.
This demonstration helped people to visualize the roleof IPsec protection for the tunneled trafﬁc. When using
IPv6 mobility, and NEMO in particular, the mobile router
may traverse insecure networks, especially in the case of
ubiquitous networking. In situations where the exchanged
data requires conﬁdentiality (sensors data for example), itFigure 9. The overview of E-bike 2007

Figure 8. Spy computeris mandatory to use IPsec to protect the exchanges on theinsecure path. This protection is transparent to the peers.
The demonstration was also a good opportunity to show
some tools we have developed in Nautilus6 in action, the
HAiku web interface and the Homeguy Linux distribution.
People were interested to hear that they could experimentquite easily with IPsec in their own testbed thanks to our
packages repositories for Debian and Ubuntu Linux distributions.

7.2

Tour de France 2006

A demonstration of the IPv6 mobility protocols was set
during the Tour de France event in summer 2006. This
demonstration has been reported in the 2006 Nautilus6
WIDE report and further analyzed in a paper published in2007 [37].

7.3

E-bike 2007,
Bindings

Advantages of Flow

Three bicycles equipped with user terminals evolved on
the university campus named Beaulieu in Rennes, France.
All user terminals were connected to the IPv6 Internet via amobile and multi-interfaced router with Network Mobility
Basic Support protocol shown as Figure 9. This protocol included for the ﬁrst time the Flow Bindings support in orderto optimize the different network accesses. This demonstration shows why it is important to install ﬂow policies onan embedded mobile network in order to distribute and ﬁlter
applications according to the connectivity of the mobile network. As a demonstration, a web interface were prepared
for all the attendants shown in section 7.5. More details areappeared in some documents [38, 39].

7.4

ANEMONE Promotion day

ENST-Bretagne, INRIA Rennes and INRIA Rocquencourt made a demonstration in ANEMONE project 1 promotion day on 14th December 2007. There were more than
90 attendants.
Two Citroen C3 move through an itinerary across theuniversity campus (Beaulieu) where both GPRS and Wi-Fi
connectivity is available. Each access network has its own
characteristics in terms of price, bandwidth, latency, etc.
Occupants are equipped of user terminal (i.e. Tablet PC,
PDA) and have a Wi-Fi Internet connectivity via the Mobile Router embedded in each vehicle. They beneﬁt fromthe ANEMONE services such as Video on Demand and cancommunicate with the audience thanks to instant messaging
and Voice over IP. Web interface were prepared for all theattendants shown in section 7.5.

7.5

Web interface for Demonstration

A web interface based on PHP and Javascript application
allows anyone from the Internet to monitor and follows thedemonstrations without the need to install any software orsystem. The web server receives all information of each
mobile network component. This web interface displaysa description of each components, the localization and theitinerary followed by the mobile network, the pictures fromthe cameras, the data from the different sensors, and several
parameters on each network interface of the mobile network
components during the trip.
This web interface has been used during the demonstration E-Bike 2007 and ANEMONE Promotion Day to allow
the audience to follow the demonstration. The screen shotsof the web interface appear in Figure 10 for E-Bike 2007
and Figure 11 for the promotion day of ANEMONE project.
1 http://www.anemone.irisa.fr/event/Figure 10. Web interface for E-bike 2007
demonstration

operation support technologies. The web interface (HAiku)
for the home agent server eases the load of the operatorsand the Live-CD system (Homeguy) eases the difﬁculty ofmobile users who are not well trained on installing Mobile
IPv6 stack on the laptop PCs. The pre-packaged mobility
related software will also help experienced users to maketheir Linux operating system mobility enabled (section 5).
On the security area, we focused on the integration effort
of IKEv2 and Mobile IPv6 this year. As a result of this activity, we have published a working implementation basedon racoon2 (the open source Internet key exchange daemon
program), and have proposed some issues and solutions of
the current IKEv2/Mobile IPv6 integration techniques being discussed at the IETF (section 4).
We had several demonstration activities this year. At the
Ubiquitous Network Symposium 2007, we demonstrated
the technology of IKEv2 and Mobile IPv6 interaction (section 7.1). We improved our E-Bike demonstration testbed tosupport ﬂow binding technology to effectively utilize multiple network connections (section 7.3). At the ANEMONE
promotion day, we demonstrated mobile cars equipped with
the GPRS and Wi-Fi connections running in the university
campus of Beaulieu connected to the Internet seamlessly
using the ANEMONE platform (section 7.4).

9Figure 11. Web interface for ANEMONE promotion day

8Conclusion

This year, we worked on IPv6 mobility implementation,
IPv6 mobility operation support technology and demonstration activity to accelerate IPv6 mobility deployment. In theimplementation activity, we worked on NEPL and SHISA
implementations which provides the base IPv6 mobility
stacks for Linux and BSD respectively (section 3.1 and 3.2).
We also worked on the DSMIPv6 technology that is a kindof interoperability technology between IPv4 to IPv6 mobility for both Linux and BSD (section 3.3 and 3.4).
To realize the actual deployment of the IPv6 mobility
technology, operation technologies are important as wellas implementation activities. We have started public homeagent service that is open to every users worldwide inJapanese, and two other public services open to academic
users in France (section 6). We have been also working on

Next Steps

We have developed several core software that will help
IPv6 mobility deployment. We have also shown that thesesoftware work well at many events such as conferences andexhibitions. The next steps are to make these software easily available to normal users. For example, the Mobile
IPv6/NEMO BS stacks have to be integrated to the Linuxand BSD’s main trees so that every users of these operating
systems can use mobility technology by default. We also
have many other supportive software, for example HAiku,
SONAR, IKEv2 integration patch, and other mobility related software. These software will help mobile service
providers and we will keep working on these activities.

Acknowledgments
The Working Group Chairs would like to thanks all the Nautilus6 members for their participation in the group during this year,
through their contributions in our activities and participation to our
Mailing Lists.

References[1] WIDE
project,
http://www.wide.ad.jp/.

December2007.

[2] WIDE
project.
Nautilus6
Working
Group,
December
2007.
http://www.wide.ad.jp/project/wg/nautilus6.html.

[16] WIDE
project.
Internet
CAR
Working
Group,
December
2007.
http://www.wide.ad.jp/project/wg/iCAR.html.

[3] LSIIT, Université Louis Pasteur (ULP), France. Web
page. http://lsiit.u-strasbg.fr/rp-en/index.php.

[17] Jean Lorchat, Koshiro Mitsuya, and Romain Kuntz. A
NetBSD-based IPv6 NEMO Mobile Router. In Asia
BSD Conference (AsiaBSDCon2007), March 2007.

[4] Vijay Devarapalli, Ryuji Wakikawa, Alexandru Petrescu, and Pascal Thubert.
Network Mobility(NEMO) Basic Support Protocol. Request For Comments 3963, IETF, January 2005.
[5] MIPL, Mobile IPv6 for Linux.
http://www.mobile-ipv6.org.

Web page.

[6] USAGI Working Group: IPv6 and IPsec protocol
stack for the Linux system, WIDE Project. Web page.
http://www.linux-ipv6.org.
[7] NEMO Platform for Linux (NEPL) patch for UMIP.
Web page.
http://software.nautilus6.org/NEPLUMIP/.

[18] Keiichi Shima, Koshiro Mitsuya, Tsuyoshi Momose,
Shuichi Karino, Ryuji Wakikawa, Kazushi Sugyou,
and Keisuke Uehara. Designing and Implementing IPv6 Mobility stack on BSD Operating Systems.
Computer Software – Japan Society for Software Science and Technology (JSSST) Journal, 24(4):23–39,
October 2007.
[19] Christian Vogt and Jari Arkko. Credit-Based Authorization for Concurrent Reachability Veriﬁcation.
Technical Report draft-vogt-mobopts-simple-cba-00,
IETF, August 2006.

[8] NEMO Platform for Linux (NEPL) Howto. Web page.
http://www.nautilus6.org/doc/nepl-howto/.

[20] Christian Vogt. Early Binding Updates for Mobile
IPv6. Technical Report draft-vogt-mobopts-simpleebu-00, IETF, August 2006.

[9] R. Wakikawa, T. Ernst, K. Nagami, and V. Devarapalli. Multiple Care-of Addresses Registration, Workin Progress, Internet Engineering Task Force, draftietf-monami6-multiplecoa-04.txt, November 2007.

[21] Thierry Ernst and Keiichi Shima. Nautilus6 Activiy Report in 2004. Technical Report wide-draftnautilus6-2004activityreport-00, WIDE Project, January 2005.

[10] Romain Kuntz and Jean Lorchat. Multiple Careof Addresses Registration for NEPL. Web page.
http://software.nautilus6.org/MCoA/.

[22] Thierry Ernst (Editor) and Keiichi Shima (Edirtor).
Nautilus6 Project Activity Report 2005. Technical Report wide-tr-nautilus6-report2005-01, WIDE Project,
January 2006.

[11] The European ANEMONE Consortium. Web page.
https://www.ist-anemone.eu/index.php/Home Page.
[12] The RNRT REMORA project.
Web
page.
https://www.labo4g.rennes.enstbretagne.fr/twiki/bin/view/Remora/RemoraHome.

[23] Romain KUNTZ (Editor), Keiichi Shima (Edirtor),and Koshiro Mitsuya (Editor). The WIDE Nautilus6
Working Group Report 2006. Technical Report widetr-nautilus6-report2006-03, WIDE Project, February
2007.

[13] Romain Kuntz. Deploying reliable IPv6 temporary
networks thanks to NEMO Basic Support and Multiple Care-of Addresses registration. In The Second International Workshop on Network Mobility(WONEMO), Hiroshima, Japan, Jan 2007.

[24] Keiichi Shima, Yojiro Uo, Nobuo Ogashiwa, andSatoshi Uda. Operational Experiment of Seamless
Handover of a Mobile Router using Multiple Care-of
Address Registration. Academy Publisher Journal of
Networks, 1(3):23–30, July 2006.

[14] Tatuya Jinmei, Kazuhiko Yamamoto, Jun-ichiro
Hagino, Shoichi Sakane, Hiroshi Esaki, and Jun Murai. The IPv6 Software Platform for BSD. IEICE
Transactions on Communications, E86-B(2):464–
471, February 2003.

[25] Koshiro Mitsuya, Ryuji Wakikawa, and Jun Murai.
Implementation and Evaluation of the Dual Stack
Mobile IPv6. In Asia BSD Conference (AsiaBSDCon2007), March 2007.

[15] Keiichi Shima, Koshiro Mitsuya, Ryuji Wakikawa,
Tsuyoshi Momose, and Keisuke Uehara. SHISA:
The Mobile IPv6/NEMO BS Stack Implementation
Current Status. In Asia BSD Conference (AsiaBSDCon2007), March 2007.

[26] V. Devarapalli and F. Dupont. Mobile IPv6 Operation
with IKEv2 and the Revised IPsec Architecture. Technical Report 4877, April 2007.
[27] Racoon2: IKE / IKEv2 open-source implementation.
Web page. http://www.racoon2.wide.ad.jp/.

[28] G. Giaretta and J. Kempf and V. Devarapalli. Mobile
IPv6 Bootstrapping in Split Scenario. RFC 5026 (Proposed Standard), October 2007.
[29] HowTo:
Dynamic keying for Mobile IPv6
using racoon2 and mip6d.
Web page.
http://www.nautilus6.org/doc/dk-howto/.
[30] S. Sugimoto, F. Dupont, and M. Nakamura. PF KEY
Extension as an Interface between Mobile IPv6 andIPsec/IKE. Technical Report draft-sugimoto-mip6pfkey-migrate-03, September 2006.
[31] S. Decugis. Key Management Mobility Capability(K) ﬂag in Mobile IPv6 BU/BA messages. Technical Report draft-sdecugis-mextkbitissues-00, December 2007.
[32] HAiku: the web interface for Home Agents. Web
page. http://software.nautilus6.org/HAiku/.
[33] SONAR: A Statistic Repository of Mobile Platforms.
Web page. http://sonar.nautilus6.org.
[34] Martin André. A Practical Evaluation of the Nautilus6
Operational Home Agent Service. In IPv6 Today Technology and Deployment (IPv6 TD’07). International Academy, Research, and Industry Association,
IEEE Computer Society, March 2007.
[35] Homeguy: the Mobile IPv6 Live CD.
http://software.nautilus6.org/homeguy/.

Web page.

[36] Nautilus6 Home Agent Service. Web page. https://opha.nautilus6.org/.
[37] Amine Dhraief, Nicolas Montavont, Romain Kuntz,
and Manabu Tsukada. E-bicycle demonstration on
Tour de France. In IPv6TD 2007, Guadeloupe, French
Caribbean, March 2007.
[38] Boutet Antoine, Romain Kuntz, Montavont Julien,
Montavont Nicolas, Le Texier Benoit, Ropitault Tanguy, Schreiner Guillaume, and Tsukada Manabu. ABike Demonstration of the IPv6 Network Mobility,
June 2007. Pracom (Pole de Recherche Avance en
Telecommunicaiton) Seminar 2007.
[39] Boutet Antoine, Le Texier Benoit, Montavont Julien,
Montavont Nicolas, and Schreiner Guillaume. Advantages of Flow Bindings: an embedded mobile network
use case, March 2008. TridentCom08: Fourth International Conference on Testbeds and Research Infastructures for the Development of Netwoks & Communities and Workshops (under submission).