#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 follow a different path (a.g., a call to rand()).
Additionally, it's certainly better to, in the worst case scenario, have
the address vary among, say, two options, than having a different address
each time the host is bootstrapped.
--
-------------------------------------+-------------------------------------
Reporter: otr...@employees.org | Owner: draft-ietf-6man-
Type: defect | stable-privacy-
Priority: minor | addres...@tools.ietf.org
Component: stable-privacy- | Status: new
addresses | Milestone:
Severity: Active WG Document | Version:
Keywords: | Resolution:
-------------------------------------+-------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/6man/trac/ticket/3#comment:1>
6man <http://tools.ietf.org/wg/6man/>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
