Hi,   I reviewed draft-ietf-ospf-ospfv3-autoconfig-10 for its operational impact.   Intended status: standard track   Summary: This document describes a self configured mechanism for OSPF that can provide automatically configured network. So Configuration manager or server is not required in this scenario. I believe this document is ready for publication. Here are a few suggestions and editorial comments: 1.   Section 7.2 said: “ If the fingerprints are not equal, there is a duplicate Router ID conflict    and the OSPFv3 router with the numerically smaller router hardware    fingerprint MUST select a new Router ID as described in Section 7.3. ” How does router ID duplication is detected? Receiving OSPF packet with the same routerID? I don ’ t think router ID duplication conflict is the result of two fingerprints unequal; suggest to make the following change: “ If the fingerprints are not equal and there is a duplicate Router ID conflict, the OSPFv3 router with the numerically smaller router hardware fingerprint MUST select a new Router ID as described in Section 7.3. “ 2.   Section 7.4 mentions some changes to RFC 2328 Section 13.4 are introduced, I am wondering whether these changes cause an update to RFC2328? Or this change is only applied to auto configuration in the home network? 3.   Section 9 said: “ This is in addition to the authentication    key configuration recommended in Section 4.  However, it is    acknowledged that there may be some deployment scenarios where manual    authentication key configuration is not required.   ” Is authentication key configuration in section 4 about manual authentication key configuration? If not, how manual authentication key configuration is different from authentication key configuration in section 4? If yes, it seems the last two sentences are disconnected. E.g, when manual authentication key configuration is used? In which deployment scenario? 4.        Section 7.2, last paragraph: “ This new LSA is designated for information related to OSPFv3 Auto-    configuration and, in the future, could be used other auto-    configuration information, e.g., global IPv6 prefixes.  However, this    is beyond the scope of this document. ” s/used other auto-configuration information/used for other auto-configuration information   Regards! -Qin