#3: Need for DAD counter
Comment (by fg...@si6networks.com):
Actually, it makes the algorithm simpler. By including DAD_counter, it's
trivial to generate another Interface-ID with the same algorithm. Whereas
if we were to select a random interface ID upon a DAD failure, the code
would
#3: Need for DAD counter
Changes (by fg...@si6networks.com):
* status: new = closed
* resolution: = wontfix
--
-+-
Reporter: otr...@employees.org | Owner: draft-ietf-6man-
Type: defect
#3: Need for DAD counter
Your draft attempts to make the fallback predictable, by incorporating a
DAD counter in the seeds of your nominal algorithm. But that means
redefining the solution a only a guarantee that the visiting host will
have one of the same 2 or 3 addresses on the visited
