On 5/23/11 12:09 PM, Philip Homburg wrote:
In your letter dated Mon, 23 May 2011 11:46:29 -0700 you wrote:
This draft proposes to change the requirement that NUD can not
retransmit more than three times, so that NUD can be more robust against
temporary network outages.
Comments?
Do you have more data on how this problem actually shows up practice?
One place where is shows up is when you have a stable network where the
routers and hosts have neighbor cache entries for the peers they talk
to. But then there is a short outage on the LAN, e.g., due to a switch
or link failure causing spanning tree to recalculate things. Should
e.g., the router start NUD at that point in time, then NUD is likely to
discard the Neighbor Cache entries before STP is done.
Thus impact of the STP recalculation gets a lot worse, especially if
this is in a massively scaled datacenter.
The draft suggests that the main difference is more multicast traffic.
How many hosts do you need to have on a single link for this to significantly
impact the performance of the link?
Even if there are only two hosts, the issue is that the effect of an
event like a STP recalculation expands due to NUD. We don't have that
behavior with IPv4/ARP since it doesn't mandate short timeouts.
Erik
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
