If so, that is one of the ways in which we intended to signal that the RA does not carry any default router information.
To be clear, we should probably add text to that effect to the doc. In addition, we need to add a little more text treating "Router Lifetime" as a special case; if the existing text is interpreted literally, setting the "Router Lifetime" to 0 in an RA and non-zero in the DHCP option results in the host receiving conflicting information about that router from the RA and from DHCP. So, we also need text like "If the host chooses to ask for default router information from the DHCP server when it receives no default router information from RAs, the host MUST ignore the Router Lifetime values in the RAs and MUST use the Router Lifetime information from the DHCP options. The presence of the Router Lifetime values in RAs and DHCP options is not considered to be a conflict resulting from misconfiguration as described in section XXX."
If I understand the discussion Ted summarized as having no good solution, the problem is about signaling the host to use RAs or DHCP, and the host has to explicitly request the default router and prefixes from the DHCP server by including those options in the ORO. Can the host use these rules:
* if it receives no default routers with lifetime > 0, add the default router option to the ORO
* if it receives no prefixes, add the prefixes option to the OROIf I've got this right, the rules also work in the case when the host receives no RAs, because it will have receives no default routers or prefixes.
- Ralph On Mar 11, 2009, at 2:47 PM 3/11/09, Iljitsch van Beijnum wrote:
On 11 mrt 2009, at 19:43, sthaug at nethelp.no wrote:I would prefer to be able to operate entirely without RA. However, I can live with RA which only contains the MO bits and no prefix information.That's not a problem.If you then also set the RA lifetime to 0 hosts won't use the router as a default router._______________________________________________ dhcwg mailing list dhcwg at ietf.org https://www.ietf.org/mailman/listinfo/dhcwg