> => Right, but there is no need to have the O flag off. To me RFC 3736 is
(B> something useful for server vendors and should not be associated with
(B> setting the O flag.
(B
(BYou mean we can always set O flag ? I don't make sense why RFC3736
(Bshould not be associated with setting the O flag.
(B
(BRFC2461bis says O flag (when set) indicates a subset of
(BDHCPv6 [RFC3736] is available for autoconfiguration of other
(B(non-address) information...
(B
(B
(B
(B- Daniel (Soohong Daniel Park)
(B- Mobile Platform Lab. Samsung Electronics.
(B
(B
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(B[EMAIL PROTECTED]
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
