It’s almost unbelievable: more than 10 years after the IPv6 specs have been completed, someone finally realized it would be a good idea to specify the minimum requirements for a decent IPv6 CPE router. While this document will not solve the lack of low-cost IPv6-ready CPE devices, it’s definitely a step in the right direction, more so as it clearly acknowledges the need for DHCPv6 (some people still believe SLAAC is the solution to every problem ever invented).
You will find an overview of the Service Provider-related IPv6 challenges in my Market trends in Service Provider networks workshop (register for the online webinar). Advanced backbone designs and configurations are explained in the Building IPv6 Service Provider core workshop (register for the online webinar).
Here are a few highlights from the document:
- The same mechanisms are used on the WAN side regardless of the physical media. With ND, SLAAC and DHCPv6 running on top of IPv6, there’s no need for link-layer-specific procedures (like the IPCP negotiations in IPv4).
- The DHCPv6 must be used to get the IPv6 prefix from the Service Provider.
- When no other routing protocols are configured, Router Discovery must be used to find upstream routers and install static default routes.
- DHCPv6 server must be supported on LAN interfaces (this is how you propagate DNS information to the end hosts).
- The CPE router should support stateless filters (= access lists) and must filter obviously spoofed source IP addresses.
Now that the minimum requirements have been written, all we have to do is to wait for the vendors to implement them. Want to take a guess at when Linksys will support them?