Hi all, Here is my summary from an online discussion. We know this affect alot of different things, RFCs, documents, not to forget many religious views, but _try_ to put all that aside for a while...
We all think it's time to address this reoccurring issue and discussion on RAs and DHCP. RA isn't perfect, neither is DHCP but sometime there is a need to use DHCP instead of RAs. In short - DHCP need to be able to supply default gateway independing of RAs or no RAs. That is a client should be able to get only in a IPv6 only network _if_ there is no RAs, only DHCP there. The core change we're suggesting are to change things so: Supporting RAs is mandatory so no change there. However it is recommended to have it on by default, but NOT mandatory. We're _only_ opening up so anything else can provide defaultroute. DHCP must support defaultroute and must be decoupled from RAs, no M-bit or whatever. If DHCP and RA shows up, all should be added to the routing table and the kernel should sort it out. That is the implementer have a choice here but that's a completely other discussion thread all together. (tons of options on how DHCP and RAs can live together, all with their own pitfalls. From the simple one that dhcpclient can disable the kernel from accepting RAs with it's own pitfalls, to let the kernel sorting them out, and over to preferring either one - RAs or DHCPs defaultroute) -- ------------------------------ Roger Jorgensen | - ROJO9-RIPE - RJ1866P-NORID ro...@jorgensen.no | - The Future is IPv6 ------------------------------------------------------- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?