#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 network." I am not sure it is worth the additional complexity, by opposition to just saying, "in case of collision, pick a new number."
-- -------------------------------------+------------------------------------- Reporter: [email protected] | Owner: draft-ietf-6man-stable- Type: defect | [email protected] Priority: minor | Status: new Component: stable-privacy- | Milestone: addresses | Version: Severity: Active WG Document | Keywords: -------------------------------------+------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/6man/trac/ticket/3> 6man <http://tools.ietf.org/wg/6man/> -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
