Hi, On 2007/08/02, at 17:12, H E wrote: > I am just wandering what specification multihoming support in MIPL > conforms to. As far as I know there is no multihoming support in > MIPv6 specifications. Is it implementation specific or does it use > other specifications?
The basic multihoming support in MIPL2 does not refer to any specifications. However the MCoA implementation I was talking about is based on an IETF draft (draft-ietf-monami6-multiplecoa-01). > As I can see on my testbeds MIPL failure recovery operates in a > similar way to SHIM6. does it use SHIM6? Please help me find > answers to those questions. No, Shim6 is a different mechanism based on different concepts. MIPL2 does not implement any part of the SHIM6 specification. But if you are interested in the topic, there is some discussion at the IETF about SHIM6 and MIPv6 integration. Romain > > From: [EMAIL PROTECTED] > > Date: Tue, 31 Jul 2007 09:21:09 +0200 > > To: [email protected] > > Subject: Re: [mipl] MIPL Multihoming and Failure Recovery > > > > Hi, > > > > On 2007/07/31, at 0:20, H E wrote: > > > I am testing MIPL on systems with multiple interfaces and checking > > > for failure detection and recovery in MIPL. Is there documentation > > > or more information on the operation of MIPL in multihomed > > > environment. > > > > MIPL2 has some interface preference mechanism implemented. You can > > get more information in the mip6d.conf manpage (see the > > MnIfPreference item). > > > > > If an interface fails on the MN, how does the other interface > > > provide a means for recovery by redirect traffic through it? from > > > the debug screen of mip6d it seems to me that HoA of the working > > > interface is used as a CoA for the failed address? > > > > > > > The MnIfPreference allows to use several interfaces sequentially: > the > > interface with the lowest preference will be preferred. If this > > interface becomes down, another one with a higher preference will be > > used. The tunnel is moved from the failed interface to another, thus > > redirecting the traffic through this new interface. The CoA of this > > new interface is used as a new CoA (to replace the one that was on > > the failed interface), thus a new binding update is sent to the > HA to > > update the binding. Note that the HoA is never used as a CoA. > > > > If you want to use multiple interfaces at the same time, you may be > > interested in the Multiple CoA implementation available here: > http:// > > software.nautilus6.org/MCoA/ > > > > Regards, > > -- > > Romain KUNTZ > > [EMAIL PROTECTED] > > Louis Pasteur University - Networks and Protocols Team > > > > > > > > _______________________________________________ > > mipl mailing list > > [email protected] > > http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl > > PC Magazine’s 2007 editors’ choice for best web mail—award-winning > Windows Live Hotmail. Check it out! > _______________________________________________ > mipl mailing list > [email protected] > http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl _______________________________________________ mipl mailing list [email protected] http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
