And so it begins...

Well, we have clearly made an impression.

I think we now have around 3 different DSL router manufacturers finally getting some clue and ask *us* to test their latest IPv6 offerings.

Most seem to be going for new kit to do it, and typically starting with the more up-market WiFi models rather than entry level single port Ethernet models.

My staff have a directive to test everything they can - we are after a cheap, (give-away price), single port DSL router with a good DSL level chipset that will do IPv6 native over PPP (as well as IPv4 non-NAT and NAT) and offer sensible fire-walling options to the end user.

We are also after really cheap modems that will with PPPoA/PPPoE bridge or PPPoE/PPPoE bridge with 1508 byte frames (1500 IP over PPP) and just work, including annex M ADSL2+.

We are happy to look at changes on the LNS end to work with such kit, but to be honest DHCPv6 looks so much the wrong protocol for the job I am tempted to try and write an RFC on this. It should be PPP for prefix delegation, IMHO.


  1. I can understand some of the logic on DHCPv6: it means there is one configuration protocol running over IP that can be used on any network type, rather than repeating it for each link layer protocol.
    However, it isn't obviously the most natural way to do it, particularly coming from an IPv4 background.

    You're not the first to suggest an IPv6CP option, e.g.:
    However, it doesn't look like this approach is going anywhere, e.g. see the recent threads with ipv6cp in the subject in the pppext archives:

    I'm reaching the view that we've spent long enough fiddling around with the specification of IPv6 (including plenty of second system syndrome), and so am tempted to just go with the flow (i.e. draft-ietf-v6ops-ipv6-cpe-router-09) on this.

    It might not be the best solution. It might not be the most beautiful solution. But it is a solution.

  2. To be honest I can't see the argument for using one protocol DHCPv6. You need RADIUS already on the LNS end which uses another protocol which already exists and the LNS has to map this to something.

    The LNS already does PPP and already does IP6CP. A few extra parameters on there is not complicated at all. However a whole new protocol on there that is not needed anywhere else is a pain.

    It is not as if the LNS can sensibly pass the DHCPv6 out on to the LAN as there is no routing for the return traffic as it is not using the IPv6 addresses assigned to the line by RADIUS. Well, unless you create some incredible bodge somehow). Even withing the LNS you need some horrible routing bodge to handle DHCPv6 or any IP where the traffic is not to the assigned IP addresses, where as PPP routing already exists.

    Also, I see no reason we have to decide DHCPv6 or PPP. Surely there are merits in both.

    I am tempted to just get on am implement it.


Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

NOTSCO (Not TOTSCO) One Touch Switching test platform (now launched)

I posted about how inept TOTSCO seem to be, and the call today with them was no improvement. It seems they have test stages... A "simul...