A proper support for communications has to provide fault tolerance capabilities such as the preservation of established connections in case of failures. Multihoming addresses this issue, but the currently available solution based in massive BGP route injection presents serious scalability limitations, since it contributes to the exponential growth of the BGP table size. An alternative solution based on the configuration of tunnels between the multihomed site exit routers and the ISP border routers has been proposed for IPv6 in RFC 3178. However, the amount of manual configuration imposed by this solution on the ISP side prevents its wide adoption. In particular, this solution requires at the ISP the manual configuration of a tunnel endpoint per each multihomed client that it serves. We present a multihoming tunnel broker (MHTB) that provides automatic creation of the tunnel endpoint at the ISP side.
[1]
Erik Nordmark.
Strong Identity Multihoming using 128 bit Identifiers (SIM/CBID128)
,
2003
.
[2]
Vijay Gill,et al.
Goals for IPv6 Site-Multihoming Architectures
,
2003,
RFC.
[3]
Mark Handley,et al.
Datagram Congestion Control Protocol (DCCP)
,
2006,
RFC.
[4]
Jun-ichiro itojun Hagino,et al.
IPv6 Multihoming Support at Site Exit Routers
,
2001,
RFC.
[5]
Arifumi Matsumoto.
TCP Multi-Home Options
,
2003
.
[6]
Pekka Nikander,et al.
End-Host Mobility and Multi-Homing with Host Identity Protocol
,
2004
.
[7]
Alain Durand,et al.
IPv6 Tunnel Broker
,
2001,
RFC.
[8]
Paul Ferguson,et al.
Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
,
1998,
RFC.