Re: Why, technically, MIP and IPv6 can't be deployed

Masataka,

Your crusade aside, IPv6 works perfectly well/stably on many, many other
WLAN infrastructures, but not this one.   I'm interested in why this
specific hardware has problems, and what the hardware is.   Unless named,
we can only assume it is Alcatel equipment that is problematic.

And I don't remember asking about MIP :)

Tim

On Tue, Nov 09, 2004 at 09:14:51PM +0900, Masataka Ohta wrote:
> Tim Chown wrote:
>
> IPv6 is defective in so many ways. But, w.r.t. WLAN, here is the
> reason.
>
> > Could you describe why exactly IPv6 can't run on the (layer 2?) WLAN
> > infrastructure?
> That ND extensively, without any valid reason to do so, use
> multicast, which is not acknowledged at WLAN L2, means IPv6
> or its ND is unreliable over congested WLAN. If multicast
> ND packet is lost by congestion, it is not retransmitted by L2.
>
> MIP failed mostly because there has been no standards MIP over
> link technologies, which are adaptation layers between L2 and L3.
>
> RFC2002 does not specify anything about how CoA addresses can
> be obtained, which is fine, if and only if there are other
> specifications on link or provider dependent ways to do so.
>
> IPv6 made it worse by trying to standardize ND as *THE* adaptation
> mechanism, even though the mechanism *MUST* depend on details of
> L2 and *MUST* be different L2 by L2.
>
> As a result, IPv6 won't stably run over WLAN, multicast over which
> has characteristics much different from wired Ether.
>
>                                               Masataka Ohta
-- 
Tim

North American IPv6 Task Force Technologist Seminar
More info at http://www.ipv6seminar.com/

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf