WIDE Technical-Report in 2007

The WIDE Nautilus6 Working Group Report 2006
wide-tr-nautilus6-report2006-03.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 2006
Editors: Romain KUNTZ, Keiichi SHIMA, Koshiro MITSUYA
nautilus6-wg@wide.ad.jp

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

1. Introduction
The WIDE [13] Nautilus6 Working Group [7] has been
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 around IPv6 and IPv6 mobility: host and network mobility, multihoming, seamless mobility, AAA, security, applications and operations.

2. Contributors
The following people have contributed to this report (inalphabetical order):• Martin ANDRÉ (The University of Tokyo, Japan),• Angeline DELEPLACE (Keio University, Japan andLouis Pasteur University, France),• Thierry ERNST (Institut National de Recherche en Informatique et en Automatique, France)• Satomi FUJIMAKI (Keio University, Japan),• Romain KUNTZ (The University of Tokyo, Japan),• Jean LORCHAT (Keio University, Japan),• Koshiro MITSUYA (Keio University, Japan),• Keiichi SHIMA (Internet Initiative Japan Inc., Japan),• Manabu TSUKADA (Keio University, Japan),• Saber ZRELLI (Japan Advanced Institute of Scienceand Technology, Japan).

3. NEMO Basic Support
3.1

NEMO Basic Support implementation

Some efforts have been done on NEPL [8], the NEMO
Basic Support implementation for the GNU/Linux operating system, to improve the performance or bring new features to comply to the speciﬁcation (RFC3963 [18]). We
thus have contributed some code for optimistic handovers(to reduce the handover time) and Home Address conﬁguration from the Mobile Network Preﬁx.
We also maintain a NEPL Howto [9], which is a stepby-step documentation to allow any users to build easily a
NEMO testbed from scratch.

3.2

Evaluation of the NEMO implementation

Evaluation of implementations is an important step in a
protocol development, in order to check if the protocol behaves as expected and with good performances.
Basic performances of SHISA [10], a Mobile IPv6 andNEMO Basic Support stack for the BSD operating systems,
has been evaluated and results gathered in a paper [33].
NEPL, the NEMO Platform for Linux [8], has also been
evaluated in [33], as well as in [34] using an hybrid measurement method.
Although both implementations are still work inprogress, results show that they are already useable withdecent performances.

3.3

SHISA NetBSD-current PortSHISA (further described in [44]) is a Mobile IPv6 andNEMO Basic Support implementation for the BSD operating systems built on top of the KAME IPv6 stack. Although
the KAME project concluded its activity in March 2006, the
SHISA project is still going on as a separate project to support IETF standard based mobility protocol stack for BSD.
Our next step is to port the stack that depends on the
KAME code to the plain BSD operating systems. We arenow focusing on the NetBSD-current operating system as
the ﬁrst target operating system. We have completed the
porting work of the latest SHISA code to the almost current version of the NetBSD source code. We are periodically catching up the latest NetBSD code (almost every
month) and will continue our effort to merge it to the original NetBSD.

3.4

SHISA Gumstix Port

When considering a personal mobile environment, mobile technologies are not very useful if we cannot use themwith small devices.
We started an effort to run our SHISA mobility stackon an environment with limited resources. The target platform we chose was the Gumstix products1 . We ported the
NetBSD-current operating system and the SHISA mobility
stack to that platform. As of December 2006, the mobile
node and mobile router functions are running on the Gumstix connex 400xm hardware. The NetBSD source code for
the Gumstix platform has already been merged to the original NetBSD tree. The mobility part will be available publicly when our merging work has been completed.

3.5

NEMO BS IPv4 Network Support

Most of the users in the Internet are now mainly using
IPv4. It is impossible for all users to change their infrastructure from IPv4 to IPv6 in a very short time, even if IPv6
has several advantages over IPv4.
We designed a mechanism to distribute IPv4 network
preﬁxes using the NEMO Basic Support (NEMO BS) protocol, and enabled the protocol to support both IPv6 andIPv4 mobile networks. This extension allows the users tokeep using the IPv4 Internet as before, and adds all the
beneﬁts of the network mobility with NEMO BS. For example, the users can subscribe to multiple upstream ISPs
for redundancy, or can distribute outgoing/incoming trafﬁc
between multiple NEMO tunnels for load balancing. The
idea was ﬁrst presented in a paper [41], then ﬁnally integrated in an IETF draft speciﬁcation “Dual Stack Mobile
IPv6 (DSMIPv6) for Hosts and Routers” [46].

4. Multihoming
4.1

State of the Art of Multihoming

A site (or a host) is multihomed when it has more than
one Internet connection (from one or several providers).
Multihoming is common for large networks like company
networks or Internet Service Providers: they connect at least
1 http://www.gumstix.com

to two (or more) providers. The main reasons are for link
redundancy (when a link fails, another one is available)and performances (increasing bandwidth, QoS). With thehigh development of wireless networks, hosts and small networks (e.g. Personal Area Networks, PANs) would also beeasily multihomed.
IPv4 multihoming is achieved with BGP that broadcasts
routing information, but having for consequence the growthof BGP tables: one multihoming site adds one entry in the
global routing system. That multihoming solution could not
be applied to IPv6 (except for larger ISPs) as it will imply
an explosion of routing tables.
A solution needs to be found in order to perform IPv6
multihoming. Many approaches are studied [20]. They
could be classiﬁed as follow:• Routing approches: they use IPv4 approaches but add
some mecanisms in order to alleviate the scalability
problems (e.g. IPv6 multihoming with Route Aggregation, IPv6 Multihoming at Site Exit Router, NAROS,
Routing Support for IPv6 Multihoming, etc.),• Mobility approach: it is based on Mobile IPv6,• Identiﬁer and locator approaches: those solutions separate the function of identiﬁer and locator of the IP addresses (e.g. Layer 3 Shim, Hash Based Addresses,
HIP, LIN6, etc.),• Transport approaches: the transport layer does not support the notion of multihoming. The change of the
IPv6 address usually breaks ongoing sessions. Somemechanisms could be added (or new protocols could bedeﬁned) in order to support multihoming (e.g. SCTP,
DCCP, TCP-MH, etc.),• Site exit router and host behaviour: some multihoming solutions could be achieved by changing the behaviour of a site’s exit router and/or end hosts. For
example, packet headers could be manipulated at site’s
exit routers to perform multihoming.

4.2

Multihoming in nested mobile networks

Multihoming issues in NEMO Basic Support have beenstudied in [39]. In [17], we discuss about multihoming in nested cases and focus on ONEMO (Optimzed
NEMO [51]). We propose a solution in order to choose
the path according to some parameters and by using policies. In [37], a ﬁrst proposition was done to select the pathaccording to the nested level. We propose to use such information combined with the root mobile router (a mobilerouter that is directly connected to the Internet) connectivity’s information to decide which path is the best to use in anested topology.

4.3

Multiple Care-of Addresses Registration for NEPL

Multiple Care-of Addresses (MCoA) registration [50] allows a multihomed mobile host (node or router) to efﬁciently use its multiple interfaces with load balancing, load
sharing, and fault recovery mechanisms.
So far, no implementations of this protocol were freely
available on the GNU/Linux operating system. We thus
have implemented and released this year a beta version of
MCoA registration for NEPL [4]. The implementation includes a kernel patch that has been merged in the linux kernel tree as of 2.6.19 (2006 Nov 29th). We are still working
on this implementation, however it is already useable withdecent performances. We have already successfully used
this implementation in several demonstrations this year (seesection 10.1). The implementation design and performance
tests results have been described in [32].

4.4

Policy Distribution

A multihomed mobile host has to deﬁne routing policies
in order to efﬁciently distribute the trafﬁc over its multiple interfaces. Policies must also be installed on the Home
Agent where the node is registered. In order to simplify
the administrative tasks and keep the hosts synchronized, apolicy distribution mechanism between hosts is mandatory.
We are working on the top of the Multiple Care-of Addresses registration protocol [50] to deﬁne a solution for
Flow Distribution Policy. This solution explains how packets are forwarded from and to a mobile node by using its
multiple CoAs, and how to exchange the ﬂow distribution
policies between the endpoints of the multiple virtual paths.
Our approach supports the separation of registering bindings and exchanging ﬂow distribution policies, unlike otherproposed protocols.
We submitted the speciﬁcation as an IETF draft [36] andpresented twice the protocol at the IETF MONAMI6 Working Group meetings this year.
We also have partially implemented the solution for the
GNU/Linux operating system (See Fig.1 for an overview ofthe system). Although the framework can be easily ported
to other operating systems (such as *BSD), some part depends on the policy framework which is tightly integrated
into the system. On linux, we have extended the ip6tables
software of the netﬁlter framework2 . Further technical information can be read in [31]. Our implementation is freely
available on our software server [6].
2 http://www.netﬁlter.org

Internet
ip6tablesserver

MR

3. SSL connection
2. Authentication (certificates)

1. Listen
ip6tablesserver

HA

4. Policy Exchange (encrypted)

5. Policy
IntallFigure 1. Overview of the policy exchange

4.5

Multiple NEMOs collaboration

Since NEMO Basic Support was standardized, Internetconnected vehicles and Internet connected Personal Area
Networks (PANs) are being deployed. NEMO clusters arethus very likely to appear, for example drivers and passengers who all have a PAN in an Internet-connected vehicle.
At the moment, each Mobile Router of each PAN orvehicle is independently working and maintaining multiple tunnels with their Home Agents. A collaboration
among those Mobile Routers could be considered in orderto achieve reliability, load sharing, preference settings andefﬁcient battery consumption.
To realize those improvements in the overall NEMO
cluster, the Mobile Routers Resource Sharing (MRRS) system was designed. The scenario considered in our MRRS
system corresponds to Multiple MRs, multiple HAs andmultiple MNPs, referred as the case (n,n,n) in [39].
Evaluation results show that the redundancy and theoverall bandwidth for the nodes in the mobile network increase while the overall energy consumption is saved. This
work will appear as a thesis in [48].

5. Seamless Mobility
5.1

FMIPv6.org Implementation

The goal of the fmipv6.org project [1] is to provide afully compliant implementation of the ”Fast Handovers for
Mobile IPv6” protocol (FMIPv6 [29]) and thus to allow
improving the handover latency due to Mobile IPv6 procedures on platforms running a Linux kernel.
Efforts have been done to port the FMIPv6.org implementation to work against the latest version of MIPL [2]with newer kernel.

5.2

Layer 2 abstractions

For efﬁcient network communication, it is vital for a
protocol layer to know or utilize other layer’s control information. There are several proposals for seamless handovers in IPv6 network such as Fast Handovers for Mobile IPv6 (FMIPv6 [29]) and Hierarchical Mobile IPv6

(HMIPv6 [45]). In FMIPv6, the network layer must know
in advance the indication of a handover from the link layer
to achieve seamless handovers. However, control information exchange between protocol layers is not allowed because each protocol layer is designed independently.
To address this problem, we proposed an IETF draft
which deﬁnes nine kinds of L2 abstractions in the form of”primitive” to achieve fast handovers in the network layer.
This mechanism is called ”L3-driven fast handovers” because the network layer initiates L2 and L3 handovers byusing the ”primitives”.
We started this works in 2002. The ﬁrst version of
the draft (draft-koki-mobopts-l2-abstractions) was submitted in July 2004. We had several presentations in the
Mobopts meetings. We also had a presentation at the IEEE
802.21 meeting in March 2005. Finally, it became an IRTF
Mobopts Working Group document this year [47].

Figure 2. The SONAR architecture• PANA[27]: Implemented by INT (France), used in thefront-end of the AAA framework to carry EAP messages.

6.3

Conclusion

6. AAA framework

The AAA framework deployement was successful andthe readiness of the existing implementations of AAA technologies could be tested.

An AAA framework aiming at demonstrating the applicability of AAA technologies in NEMO environments was
deployed in our indoor testbed in January 2006.

7. Security
7.1

6.1

Test scenarios

The following scenarios were tested:
1. Single realm (f-isp.com), authenticating an MR: thisﬁrst scenario consists in authenticating an MR (that belongs f-isp.com) to the access network before granting
IPv6 connectivity.
2. Multi-Realm, authentication of a visiting MR: in this
scenario, the MR that belongs to the AAA realm(m-isp.com) is authenticated by the visited realm (fisp.com).
3. Multi-Realm, authentication of a MNN: In this scenario, the MR that belongs to the AAA realm (misp.com) authenticats an MNN that belongs to therealm (f-isp.com).

6.2

Software used

• FreeBSD 5.4• MR / HA: KAME snapshot:frebsd54-snap.tgz

kame-20060123-• WIDEDiameter: WIDE implementation of Diameter [16], the WIDEDiameter API was used to implement and deploy a Diameter-EAP [26] application.

Security
Setup
SHISA/MIPL

How-tofor

One of the most difﬁcult tasks when conﬁguring Mobile IPv6 function is to set up IPsec security parameters.
We summarized the required security parameters to operate
Mobile IPv6 service and published a document as a WIDE
Technical-Report [40].

8. Applications
8.1

SONAR

It is important for both network researchers and operators to know the behavior of mobile nodes (mobile hosts
and mobile routers), and to ﬁnd anomalies in their behavior.
SONAR [12] is a set of free tools to build a statistics
repository containing detailed information of mobile nodes.
Users can send statistics information about their mobility
system to a statistics repository by using these tools. The
repository shows the history and analysis results of the collected data (Fig.2). The analysis includes classiﬁcation ofmobility, MIPv6/NEMO protocol evaluation, network access technologies benchmark and correlation between L2and L3 technologies. We further describe the overview of
the SONAR project in [35].
We ﬁnished to develop the mobile host clients for Linux(MIPL [2] and NEPL [8]), FreeBSD (SHISA [10]), andNetBSD (SHISA) and some experiments using this clientwere performed. The source code of the sonar mobile hostclient has been released [12] in order to get a larger userbase and more statistics into the repository. However, moredevelopments are needed because security features are lacking and the statistic module of the mobility protocols is notwell tested yet. We are working on this with the developersof the mobility protocols.
We just started to develop the home agent client andsome features were tested during a conference [15]. It currently supports only NetBSD (SHISA). We will continue
the development next year.
The data repository server has also been updated because
the new clients are capable of retrieving more statistics parameters than at the begining. This was ﬁnished at end of
September 2006. We are also discussing how to provide
the statistic information to the public regarding user privacy
issues.

8.2

SIP Communicator

SIP Communicator [11] is a project which aims to provide a full solution for communication with Instant Messaging – currently the Jabber, ICQ/AIM and MSN protocols
are supported – as well as audio and video call with SIP.
It is mainly developed by the Louis Pasteur University in
Strasbourg, France. The SIP Communicator supports both
IPv4 and IPv6 and is thus a great tool to be used in ourdemonstrations.
We have contributed to this software by providing,among others, speciﬁc packages for the MacOS X and Debian GNU/Linux operating systems, and adding the support
for Growl3 notiﬁcations to the MacOS X SIP Communicator client. Also, we contributed a java version of the ilbc
codec [14] and are working on a linux native datasource tolower audio latency.

9. Operation
9.1

Operational Home Agent Service

The Operational Home Agent Service is meant to provide a full featured IPv6 Mobility service to promote theuse of mobility and as a playground for experimental protocols deployment.
The service has already been opened for WIDE members
and will shortly be opening publicly. It is composed of three
distinct elements:• Home Agents – currently a NetBSD 2.0.2 server setup
in K2 campus with the SHISA Mobile IPv6 implementation [10] – providing the mobility service;
3 http://growl.info• Web interface aiming at simplifying all the operations
in which the user is involved (see section 9.2 and 9.3);• Live CD supporting MIPv6 to enjoy quickly the mobility service (see section 9.4).

9.2

Current web interface

The purpose of the web based interface is to provide easily to the users a Home Address (HoA) and the Security Associations (SAs) needed to conﬁgure a Mobile Node. This
interface provides also the means to create a personalized
LiveCD (see section 9.4) to easily test the IPv6 mobility.
The current version of the web interface is available on
Nautilus6 servers [5]. It is developed in PHP. This system
uses a MySQL database for users, HoA and SAs management. The ﬁrst version of the web interface was released in
the middle of July. The service has already been opened to
WIDE, Nautilus6 and CNRS members. We further describe
the web based interface in [28].
A new version of the interface is currently under development and should be soon released (see section 9.3).

9.3

New web interface

The original web interface could hardly be extended andadapted to newer functionalities. We decided to redesign it
as well as the associated database from scratch to take inaccount the problematics related to the upcoming mobility
technologies, such as multihoming, MCoA, NEMO Basic
Support and Home Agent Redundancy. The new web interface is also designed to propose support for internationalization and to offer simple administration of the Home Agent(monitoring of the Home Agent with SONAR, user management, HA conﬁguration). With the new web interface,
the service gains in functionalities and reliability.
The ﬁrst version of the new web interface has been presented presented during the WIDE meeting in December
and is to be released at the beginning of 2007.
This interface is based on the Ruby on Rails web framework.

9.4

Nautilus6 Live CD

The Nautilus6 Live CD is part of the Operational Home
Agent Service and was originally developed to get instantaccess to the Mobility service. It is capable of connecting
to the Home Agent at boot time thanks to the MIPL Mobile IPv6 implementation [2] and includes many softwares
related to IPv6 and mobility.
The Live CD is generated through the web interface andcontains personal security parameters to register with theHome Agent.

10. Demonstrations
10.1

Demonstrations at the WIDE Camp,
Spring and Autumn 2006

The WIDE Camps are a very good place to hold network
experiments. During those events, IPv6 connectivity is offered to the camp attendees. We have taken this opportunity
to setup several mobility demonstration to both the Springand Autumn camp this year.

10.1.1

Smooth Handover Demonstration using SHISANEMO Basic Support (NEMO BS) adds mobility functions
to the IPv6 routers. The network behind the mobile router
becomes logically static. This function is useful when a network has a lot of nodes that do not have any mobility functions but move with the whole network. The typical usageof this technology is the network provided in transportation
systems like buses, trains or airplanes.
In the base speciﬁcation of NEMO BS, a mobile routercan use only one IPv6 address at a time as its attachment
point to the Internet. Therefore, the mobile router and its
mobile network will face service disruption of the network
connectivity while the mobile router is moving from one
network to another network.
We had performed two operational experiments of network mobility. The ﬁrst one is an experiment using only
the base NEMO BS function, this experiment was reported
as a part of the last year’s activity report. The second one,held on March 2006, is a seamless handover experiment byusing multiple network interfaces.
In these experiments, the mobile networks were real conference networks which held a few hundred people. The result shows that the multiple interfaces usage provides onethird to one-tenth of the packet loss rate compared to thecase that is not using such multihoming technology. Also,
most of the attendees at the conference did not notice themovement, which means that the technology can be used asa realistic solution to achieve seamless handovers. Resultsof this experiment are further described in [43].

10.1.2

Fault-Tolerant Network using NEPLThe IPv6 camp network was actually a mobile network connected via an IPv6 Mobile Router. We have setup several multihoming conﬁgurations, including the usage ofMultiple Care-of Addresses registration, to perform loadbalancing and fault-tolerance at the gateway, thus ensuring
a good service transparently to the IPv6 camp users. A summary of those experiments can be read in [31].

Figure 3. The Tour de France Demonstration
Scenario

10.1.3Home Agent Service Demonstration

The WIDE Camp 2006 held in Autumn was also the occasion for the Home Agent Service demonstration. The attendees of the camp could register to the service and movefrom one room to another while being reachable all along.
We monitored the activity of the Home Agent during thewhole camp with the SONAR monitoring tool. This was
the ﬁrst ”real-life” testing session for the Operational Service and the output of the latter experiment served as a basis
for the evaluation of the service [15].

10.2

E-Bicycle demonstration on the Tourde France

We have setup an E-Bicycle demonstration on the Tourde France4 in July 2006. The Tour de France is a bicycle
race event all around France every year in July. This demonstration has been setup in collaboration with French partners: the ENST Rennes, INRIA Rocquencourt, and Louis
Pasteur University in Strasbourg.
It has involved two bicycles and a car that embedded
a Mobile Network (Fig.3). Anybody in the Internet could
monitor the bicycle’s whereabouts from a web-browser
thanks to the MonNemo application [3]: location on a map,
pictures of the surrounding, temperature and humidity in thearea etc. Video from the vehicle was sent using XCAST65 ,a new and ﬂexible scheme for multicast.
The motivation and scenario have been further explained in a paper [19] and all the technical information
4 http://www.letour.fr/indexus.html
5 http://www.xcast.jp

to setup such demonstration has been gathered in a WIDE
Technical-Report [30].

10.3

September 2006 (Volume 24 number 9) and published several papers [51, 21, 23] which are direct outputs of Nautilus6 activities completed at Keio University in 2006.

The First Thailand IPv6 summit

12. IPv6 Mobility Standardization at IETF
The Thailand IPv6 Forum has organized the First Thailand IPv6 Summit, an international seminar, in order to create public awareness about the necessity of IPv6 technologies.
We have prepared two IPv6 Network Mobility (NEMO)
demonstrations to be presented to the public during thisSummit, on May 3rd and 4th 2006. The ﬁrst demonstration explained the basic principles of the NEMO technology through the E-Bag (a Personal Area Network that canbe easily carried by people). The second demonstration
aimed at explaining the need of Dual Stack Mobile IPv6
(DSMIPv6 [46]). Besides those demonstrations, we havepresented two Open Source NEMO Basic Support implementations, that were used to setup those demonstrations:
SHISA [10], a mobility stack for BSD Operating Sytems,
and NEPL [8] which is developped for the GNU/Linux Operating System.
More information can be read in a WIDE TechnicalReport [42].

10.4

Ubiquitous Network Symposium

We had a demonstration at the CEATEC Japan 2006,
which is the biggest exhibition for consumer electronics
products in Japan, as a part of the Ubiquitous Network Symposium partners. The contents of the demonstration were
almost the same as the demonstration held at the First Thailand IPv6 Summit (see Section 10.3), with new versions of
the SHISA and NEPL implementations.

11. IPv6 Mobility Promotion & Publication
As part of its IPv6 mobility promotion goal, Nautilus6
has successfully organized the 1st International WOrkshop
on NEtwork MObility which was collocated with ICOIN
held in January 2006 in Sendai, Japan, and the 2nd edition,
which will be held next year, still in Japan, this time collocated with the SAINT conference. Nautilus6 contributed
to the set up and organization of the workshop by chairing
the workshop and leading the review process and providing
some facilities like holding the web pages and mailing lists.
Nautilus6 also contributed numerous papers to both events([17, 49, 41, 35, 33, 31]).
Thierry Ernst also served as guest-editor in a special issue on Mobile Routers and Network Mobility in the IEEE
Journal on Selected Areas in Communications published in

Nautilus6 is heavily involved in IETF standardization,with its members chairing two working groups (IETF
NEMO WG and IETF MONAMI6 WG). The set up of
the MONAMI6 WG in 2005 is a direct output of Nautilus6 whose members contributed most of the lobbying
and problem statement work. Nautilus6 members coauthored numerous working group or individual drafts: ourcontribution include the update of existing WG internet
drafts [39, 24, 22] and the revision of former individual
drafts accepted this year as WG internet drafts [38, 25, 50],
Nautilus6 members also provided some insight and implementation feedback which helped improving several protocol speciﬁcations ([39, 24, 22, 38, 25, 50, 46, 47, 36, 27]).

13. IPv6 Mobility Standardization at ISO
Through Thierry Ernst’s participation to ISO TC204
Working Group 16 which is standardizing the CALM protocol architecture for Intelligent System Transportation, Nautilus6 is providing some insight on IPv6 protocols and isserving as a non-ofﬁcial liaison with the IETF. In 2006, wewere less active than in previous years, but we still contributed on the ISO mailing list and attended the meeting
held in Sophia-Antipolis in February 2007.

14. Conclusion
This year, the WIDE Nautilus6 Working Group has madeimportant progress in the multihoming and operational activities. We have tried to demonstrate our work as muchas possible to the public through various demonstrations allover the year, using attractive applications developed in ourgroup. Next year will be an important step as we expect toopen our operational service to anyone, bringing the mobility to the end-users. Such operation will need the supportof our other activities in the research, implementation, anddemonstration sides.

15. Next Steps
During the past several years, the WIDE Nautilus6
Working Group developed many core protocol stacks (e.g.
MIPv6/NEMO BS protocols) and important applications(e.g. the home agent web interface) to utilize them. In
next year, we will focus on integrating these technologies
into one. We set the home agent service as the core part ofthe integration work and merge necessary technologies for
deployment into the service. The ﬁnal goal of the integration is to create a complete service package that provides all
mobility functions for operators.

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 participations to
our Mailing Lists.

Copyright Notice
All rights are reserved to the contributors listed in Section 2.

References[1] FMIPv6.org, the Fast Handovers implementation for Linux.
Web page. http://www.fmipv6.org.
[2] MIPL, Mobile IPv6 for Linux.
Web page.
http://www.mobile-ipv6.org.
[3] MonNemo: A Monitoring application for Mobile Networks.
Web page. http://software.nautilus6.org/MonNemo.
[4] Multiple Care-of Addresses Registration for NEPL.
http://software.nautilus6.org/MCoA/.
[5] Nautilus6 Operational Service. Home page. https://opha.nautilus6.org.
[6] Nautilus6 softwares repository.
Web page.
http://software.nautilus6.org.
[7] Nautilus6 Working Group, WIDE Project. Web page.
http://www.nautilus6.org.
[8] NEPL, NEMO Platform for Linux.
Web page.
http://www.mobile-ipv6.org.
[9] NEPL (NEMO Platform for Linux) HOWTO. Web page.
http://www.nautilus6.org/doc/nepl-howto/.
[10] SHISA: an implementation of Mobile IPv6 and NEMO
within the KAME IPv6 stack. http://www.mobileip.jp.
[11] SIP Communicator, the Java VoIP and Instant Messaging
client. Web page. http://www.sip-communicator.org/.
[12] SONAR: A Statistic Repository of Mobile Platforms. Web
page. http://sonar.nautilus6.org.
[13] WIDE Project (Widely Integrated Distributed Environment).
Web page. http://www.wide.ad.jp.
[14] S. Andersen, A. Duric, H. Astrom, R. Hagen, W. Kleijn, and
J. Linden. Internet Low Bit Rate Codec (iLBC). Request
For Comments 3951, IETF, December 2004.
[15] M. 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.
[16] P. Calhoun, J. Loughney, E. Guttman, G. Zorn, and J. Arkko.
Diameter Base Protocol. RFC 3588 (Proposed Standard),
Sept. 2003.

[17] A. Deleplace, T. Ernst, and T. Noël. Multihoming in Nested
Mobile Networks with Route Optimization. In 2nd International Workshop on Network Mobility (WONEMO) colocated with the International Symposium on Applications
and the Internet (SAINT), Hiroshima, Japan, January 2007.
[18] V. Devarapalli, R. Wakikawa, A. Petrescu, and P. Thubert.
Network Mobility (NEMO) Basic Support Protocol. Request For Comments 3963, IETF, January 2005.
[19] A. Dhraief, N. Montavont, R. Kuntz, and M. Tsukada. Ebicycle demonstration on Tour de France. In The Second International Workshop on IPv6 Today - Technology and Deployment (IPv6TD 2007), Guadeloupe, French Caribbean,
March 2007.
[20] M. Dunmore. Evaluation of Multihoming Solutions. Technical Report D4.5.3, 6NET project, February 2005.
[21] T. Ernst. Le Support des Réseaux Mobiles dans IPv6. Technique et Science Informatiques (TSI), 25(5), Juillet 2006.
[22] T. Ernst. Network Mobility Support Requirements. Internet
Draft draft-ietf-nemo-requirements-06.txt, IETF, November
2006. Work in progress.
[23] T. Ernst. The Information Technology Era of the Vehicular
Industry. ACM SIGCOMM Computer Communication Review (CCR), Volume 36(Issue 2), April 2006.
[24] T. Ernst and H.-Y. Lach. Network Mobility Support Terminology. Internet Draft draft-ietf-nemo-terminology-06.txt,
IETF, November 2006. Work in progress.
[25] T. Ernst, N. Montavont, R. Wakikawa, C. Ng, and K. Kuladinithi. Scenarios for Using Multiple Interfaces and Global
Addresses. Internet Draft draft-ietf-monami6-multihomingmotivation-scenario-01.txt, IETF, October 2006. Work inprogress.
[26] P. Eronen, T. Hiller, and G. Zorn. Diameter Extensible Authentication Protocol (EAP) Application. RFC 4072 (Proposed Standard), Aug. 2005.
[27] D. Forsberg, Y. Ohba, B. Patil, H. Tschofenig, and A. Yegin.
Protocol for Carrying Authentication for Network Access.
Internet draft, IETF, January 2005. Work in progress.
[28] S. Fujimaki, K. Shima, K. Uehara, and F. Teraoka. The Deployment of Mobility Protocols Based on the Home Agent
Service with Easy Interface. In The Internet Conference,
Tokyo, Japan, Oct 2006.
[29] R. Koodli. Fast Handovers for Mobile IPv6. Request For
Comments 4068, IETF, July 2005.
[30] R. Kuntz.
The E-Bicycle Demonstration Setup on
Tour de France 2006.
Wide draft, September 2006.
http://member.wide.ad.jp/tr/wide-tr-nautilus6-ebicycletour-de-france-00.pdf.
[31] R. Kuntz. Deploying reliable IPv6 temporary networks
thanks to NEMO Basic Support and Multiple Care-of Addresses registration. In Second International Workshop on
Network Mobility (WONEMO), Hiroshima, Japan, January
2007.
[32] R. Kuntz and J. Lorchat. Building Fault Tolerant Networks
using a multihomed Mobile Router: a Case Study. In AsianInternet Engineering Conference (AINTEC) 2006, Bangkok,
Thailand, November 2006.
[33] R. Kuntz, K. Mitsuya, and R. Wakikawa. Performance
Evaluation of NEMO Basic Support Implementations. In
The First International Workshop on Network Mobility(WONEMO), Sendai, Japan, Jan 2006.

[34] J. Lorchat and R. Kuntz. Evaluation of NEMO Communications Using Hybrid Measurement. In 6th International
Conference on ITS Telecommunications (ITST), Chengdu,
China, June 2006.
[35] K. Mitsuya, J. Lorchat, T. Noel, and K. Uehara. ”SONAR:
A Statistic Repository of Mobility Platforms. In The FirstInternational Workshop on Network Mobility (WONEMO),
Sendai, Japan, Jan 2006.
[36] K. Mitsuya, K. Tasaka, and R. Wakikawa. A Policy Data
Set for Flow Distribution. Internet Draft draft-mitsuyamonami6-ﬂow-distribution-policy-02.txt, IETF, October
2006.
[37] N. Montavont, T. Noel, and T. Ernst. Multihoming in nested
mobile networking. In SAINT, Tokyo, Japan, January 2004.
[38] N. Montavont, R. Wakikawa, T. Ernst, C. W. Ng, and K. Kuladinithi. Analysis of Multihoming in Mobile IPv6. Internet
Draft draft-ietf-monami6-mipv6-analysis-01.txt, IETF, June
2006. Work in progress.
[39] C. Ng, E. Paik, T. Ernst, and M. Bagnulo. Analysis of Multihoming in Network Mobility Support. Internet Draft draftietf-nemo-multihoming-issues-06, IETF, June 2006.
[40] K. Shima. Conﬁguring IPsec for SHISA/MIPL. Technicalreport, WIDE Project, June 2006.
[41] K. Shima. The design and implementation of a dual-stackmobile network using IPv6 only network infrastructure.
In The First International Workshop on Network Mobility(WONEMO). ICOIN, January 2006.
[42] K. Shima, R. Kuntz, and K. Mitsuya. Nautilus6 mobile technology demonstration at the First IPv6 Summit in Thailand.
Wide draft, July 2006. http://member.wide.ad.jp/tr/wide-trnautilus6-mobility-demo-thai-ipv6-summit-00.pdf.
[43] K. Shima, Y. Uo, N. Ogashiwa, and S. 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.
[44] K. Shima, R. Wakikawa, K. Mitsuya, T. Momose, andK. Uehara. SHISA: The IPv6 Mobility Framework for
BSD Operating Systems. In IPv6 Today – Technology and
Deployment (IPv6TD’06). International Academy Researchand Industry Association, IEEE Computer Society, August
2006.
[45] H. Soliman, C. Castelluccia, K. El Malki, and L. Bellier.
Hierarchical Mobile IPv6 Mobility Management (HMIPv6).
Request For Comments 4140, IETF, August 2005.
[46] H. Soliman, G. Tsirtsis, V. Deverapalli, J. Kempf, H. Levkowetz, P. Thubert, and R. Wakikawa. Dual Stack Mobile
IPv6 (DSMIPv6) for Hosts and Routers. Technical Report
draft-ietf-mip6-nemo-v4traversal-03, IETF, October 2006.
[47] F. Teraoka, K. Gogo, K. Mitsuya, R. Shibui, and K. Mitani.
Uniﬁed L2 Abstractions for L3-Driven Fast Handover. Internet Draft draft-irtf-mobopts-l2-abstractions-01.txt, IETF,
September 2006.
[48] M. Tsukada. Multiple NEMOs collaboration, January 2007.
Master Thesis, Graduate School of Media and Governance,
Keio University, Japan.
[49] M. Tsukada and T. Ernst. Vehicle Communication Experiment Environment With MANET And NEMO. In 2nd International Workshop on Network Mobility (WONEMO) colocated with the International Symposium on Applications
and the Internet (SAINT), Hiroshima, Japan, January 2007.

[50] R. Wakikawa, T. Ernst, and K. Nagami. Multiple Care-of
Address Registration on Mobile IPv6. Internet Draft draftietf-monami6-multiplecoa-01.txt, IETF, October 2006.
[51] M. Watari, T. Ernst, and R. Wakikawa.
Designand Analysis of Resource Management Softwarefor In-Vehicle IPv6 Networks.
IEICE Transactions on Communications, E87-B(7):1874, July 2004.
http://search.ieice.org/2004/ﬁles/e000b07.htm#e87b,7,1874.