INTERNET DRAFT
Kenichi Nagami(INTEC Netcore)
Satoshi Uda (JAIST)
Nobuo Ogashiwa (JAIST)
Ryuji Wakikawa(Keio Univ.)
Hiroshi Esaki(Univ. Tokyo)
Hiroyuki Ohnishi(NTT)
Multi-homing for small scale fixed network Using Mobile IP and NEMO
<draft-nagami-mip6-nemo-multihome-fixed-network-00.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
Multi-homing technology improves the availability of host and network
connectivity. Since the node and network behavior of mobile
networking and fixed networking are different, the different
architecture has been discussed and proposed. This document proposes
the common architecture both for mobile and fixed networking
environment, using the mobile IP and NEMO. The proposed architecture
only requires a modification of the mobile IP and NEMO so that
multiple-CoA can be used. In addition, multiple HAs which are located
in different place, are required for redundancy.
1. Motivation
Users of small scale network need to improve the network availability
and to get load balance of several links by easy method. Multi-homing
technology is one of solutions to improve the
availability. Conventional major multi-homing network uses BGP. But
it has some issues as followings. Therefore, we propose a
multi-homing architecture using the mobile IP and NEMO for
small-scale fixed network.
Nagami, et al. [Page 1]
Internet Draft Multihoming for fixed network March 2004
(1) Increasing route entries in the Internet
In the multi-homing environments, each user's network needs to
advertise its address block to all ISPs connected to them. If
multi-homed user connects only one ISP, the ISP can advertise
routing information to aggregate them. But some multi-homed user
needs to connect with different ISPs in preparation for failure of
ISP. In this case, ISPs need to advertise routing information for
multi-homed user without aggregation. Therefore, the number of
routing entries in the Internet is increasing one by one.
(2) Difficulty to efficiently use multiple links
It is not easy to control in-coming traffics in the case of the
conventional multi-homing architecture using BGP. Therefore, load
balancing of connected links are difficult.
2. Multi-homing for small scale fixed network Using Mobile IP and NEMO
2.1 Mobile network includes fixed network
NEMO and Mobile IP must work with multi-homing by its nature. This is
because mobile nodes need to use multiple links for improving the
availability of network connectivity since the wireless link is not
always stable. Therefore, we propose that multihoming for fixed nodes
(routers and hosts) use the framework of NEMO and Mobile IP.
2.2 Overview multi-homing network architecture using Mobile IP
Figure 1 shows basic multi-homing network architecture. In this
architecture, a mobile router (MR), which is boarder router of
multi-homed network, sets up several tunnels between the MR and the
HA by multiple-CoA registration to provide redundancy and load
balancing. A HA or a router which the HA belongs advertise user's
network prefix to ISPs via routing protocol. If HA has several
multi-homed network, they can advertise an aggregated network prefix
to ISPs. Therefore, the Internet routing entries do not increase one
by one when multi-homed user is increased.
Packets to multi-homed users go to HA and the HA sends packets to MR
using CoA1 and CoA2. The HA selects a route which CoA is used. The
route selection algorithm is out of scope of this document. This can
improve availability of user network and control an in-coming traffic
between ISP and MR. In the basic architecture, HA1 is single point of
failure. In order to improve availability of user network, multiple
HA is needed. This is described in later section.
Nagami, et al. [Page 2]
Internet Draft Multihoming for fixed network March 2004
HA1
|
ISP-A ---- ISP-B
| |
| |
+--- MR ---+
CoA1 | CoA2
|
-------+---------
Multihomed Network
Fig.1 Basic Architecture
3. Requirements for Mobile IP and NEMO
3.1 Multiple Care-of-Addresses (CoA)
Multiple Care-of-Addresses needs to improve the availability and to
control in coming and out going traffic. The current Mobile IPv6 and
the NEMO Basic Support protocol does not allow to register more than
one care-of address bound to a home address to the home
agent. Therefore, [MCoA] is proposed to extend the MIP6
and the NEMO Basic Support to allow multiple care-of address
registrations for the particular Home Address.
3.2 Multiple Home Agents
Multiple Home Agents should be geographically distributed across the
Internet, for the improvement of service availability and for the
load balancing of HA. When all the networks that have HA advertise
the same network prefix to their adjacent router/network, the traffic
is automatically routed to the nearest Home Agent from the view point
of routing protocol topology. This operation has been already proven
operational technology in the area of web server application, such as
CDN (contents Delivery Network), regarding IGP and EGP.
In order to operate multiple HAs, all HAs must have the same
information such as binding information. This is the synchronization
of database among the HA. The HAHA protocol [HAHA] introduces the
binding synchornozation among HAs. This is the same architecture as
I-BGP. The database is synchronized by full-mesh topology. In
addition, in order to simplify operation of HA, the database is
synchronized using star topology. This is analogy with I-BGP route
reflector.
Nagami, et al. [Page 3]
Internet Draft Multihoming for fixed network March 2004
HA1 HA2
| |
ISP-A ---- ISP-B
| |
| |
+--- MR ---+
CoA1 | CoA2
|
-------+---------
Multihomed Network
Fig.2 Architecture with HA redundancy
4. Security considerations
This draft does not raise specific security issues beyond those of
existing mobile IP and NEMO and routing protocols.
References
[MCoA] R. Wakikawa, et al, "Multiple Care-of Addresses Registration",
Internet Draft, IETF. draft-wakikawa-mobileip-multiplecoa-02.txt
Sep., 2003.
[HAHA] R. Wakikawa, et al, Inter Home Agents Protocol (HAHA) Internet
Draft, IETF. draft-wakikawa-mip6-nemo-haha-01.txt, Feb., 2004.
Author's Addresses
Kenichi Nagami
INTEC NetCore Inc.
1-3-3, Shin-suna, Koto-ku, Tokyo, 135-0075, Japan
Email: nagami@inetcore.com
Satoshi Uda
School of Information Science Japan Advanced Institute of
Science and Technology
1-1 Asahidai, Tatsunokuchi, Ishikawa, 923-1292, Japan
Email: zin@jaist.ac.jp
Nobuo Ogashiwa
School of Information Science Japan Advanced Institute of
Science and Technology
1-1 Asahidai, Tatsunokuchi, Ishikawa, 923-1292, Japan
Email: n-ogashi@jaist.ac.jp
Hiroshi Esaki
Graduate School of Information Science and Technology,
The university of Tokyo
7-3-1 Hongo, Bunkyo-ku, Tokyo, 113-8656, Japan
Email: hiroshi@wide.ad.jp
Nagami, et al. [Page 4]
Internet Draft Multihoming for fixed network March 2004
Ryuji Wakikawa
Keio University and WIDE
5322 Endo Fujisawa Kanagawa, 252-8520, Japan
Email: ryuji@sfc.wide.ad.jp
Hiroyuki Ohnishi
NTT Network Service Systems Laboratories, NTT Corporation
9-11, Midori-Cho, 3-Chome
Musashino-Shi, Tokyo 180-8585, Japan
Email: ohnishi.hiroyuki@lab.ntt.co.jp
Nagami, et al. [Page 5]