On Sat, 2012-04-14 at 14:24 +0800, Washam Fan wrote: > So what is the next step if the autoconfiguration fails? static > configure? If yes. Will the next reboot try autoconfiguration again? > If yes, you may have non-stable addresses within the same network. If > no, when you move to another network you should explicitly revoke the > static configuration and enable autoconfiguration again.
If autoconfiguration fails, then it fails. There is no automated fallback; the host stays address-less (or at least stable-address-less :-) until the situation is resolved by external action. How the conflict should be resolved is out of the scope of the draft. > I think the author should clarify this DAD failure issue in the next > version. Yes in any case. But I don't think it has to be more complicated than "if Duplicate Address Detection (DAD) detects an address conflict, the host MUST NOT use the address." Maybe also add "A host MAY continue to attempt DAD in the hope that the address conflict is resolved; in this case additional DAD attempts should be infrequent." The latter allows an unattended host to recover without assistance. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer ([email protected]) http://www.biplane.com.au/kauer GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017 Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
signature.asc
Description: This is a digitally signed message part
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
