multicast/broadcast, such as wireless LANs.
ND is designed so poorly that it barely works only over Ethernet
and PPP.
Don't expect ND reasonably work even over Ethernet.
Masataka Ohta
than IPv4 that it may
worth deploying.
Masataka Ohta
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
, ACK nor retransmission is a
lot less reliable.
Masataka Ohta
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman
not a problem if the station is running streaming applications,
which, anyway, consume considerable amount of power.
However, frequently multicast RAs to all-nodes multicast address
are really annoying.
Masataka Ohta
PS
A real difference
and SHOULD supress the all-nodes
multicast address.
A dirty workaround is to supress rate of L2 address of all-nodes
multicast and never use the same L2 address for other rate-unlimited
multicast addresses.
Masataka Ohta
Pars Mutaf wrote:
This threat is probably another good reason for not allowing
multicast.
Wrong.
As I already stated reasons, there is no point not allowing
broadcast.
Masataka Ohta
(johnsmith.local)
And the address is a multicast address joined by all the hosts with
64bithash(johnsmith.local)=64bithash(DNS name).
Masataka Ohta
IETF IPv6 working group mailing
not reuse existing mechanisms.
Or is there a common link type that
we can converge on by providing an adaptation layer (2.5) ?
Wrong question.
We can't say, in advance, that some mechanism work for yet
unknown link type.
Masataka Ohta
not only IP address resolution and forwarding,
it's also IP routing.
You should study the history on how IP over NBMA damaged the
routing architecture to develop NHRP.
Masataka Ohta
.
Anyway,
If 802.11 was successfully emulating an Ethernet I would say yes.
you must say no.
Masataka Ohta
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative
.
Masataka Ohta
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
ARP and is not good enough.
Unicast RAs are likely to increase the load
in the case many devices configure simultaneously though.
It's not a problem of modern networks, which has broad enough
bandwidth for small number of hosts.
Masataka Ohta
need further abstractions to design IP over 11 APs.
right problem. Sorry about that. It's not even IPv6-over-foo. It's more
It's your problem of insisting on layer 2.5.
It's simply IP over XXX.
Masataka Ohta
addresses?
I think you and Pascal are saying it's not ND but PPP. Right?
Masataka Ohta
- Original Message -
From: Pascal Thubert (pthubert) [EMAIL PROTECTED]
Date: Friday, June 11, 2004 11:24 pm
Subject: RE: WLAN (was Re: IPv6 Host
the case over
congested WLAN.
Masataka Ohta
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
.
Masataka Ohta
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
reliable
than unicast one and has little chance to be received by its target.
Masataka Ohta
PS
I'm not a member of ipv6 ML.
IETF IPv6 working group mailing list
[EMAIL PROTECTED
transmission.
Masataka Ohta
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
18 matches
Mail list logo
