Broadband CPE

From ARIN IPv6 Wiki

Jump to: navigation, search

The most important thing to know about Broadband CPE, is that the Broadband Forum, (formerly DSL Forum) has included IPv6 in its BroadbandSuite specification X.X which is intended to be released in 2009-2010. This will start appearing in devices soon after it is released. Some device manufactures who use embedded Linux and BSD on their CPE devices, are now doing closed trials with major customers, i.e. big ISPs who sell DSL access with the CPE device bundled. For more information on this, contact the chairs of the Architecture & Transport WG. They may be able to share with you the text of the WTT-177 document which was approved at the Broadband Forum meeting in March 2008. Additionally, WT-192 speaks to the requirements of residential gateways.

There is also an IETF draft entitled "Basic Requirements for IPv6 Customer Edge Routers" which addresses much of the same.

Contents

[edit] Cable

For cable, this is simple because all gateway devices certified by Cablelabs at DOCSIS 3.0 CM or CMTS will have IPv6 support. An example such device is the Cisco (formerly Scientific Atlanta) DRG2800. Of course, having a compliant cable modem or gateway only matters if the cable company's CMTS also supports IPv6.

The new 'DOCSIS 2.0 + IPv6' standard also supports IPv6, which may on the cable modem side only require a firmware upgrade [1] [2].

[edit] DSL

Not many DSL modem vendors support IPv6, most of them claiming that they will implement it when IPv6 is "launched".. I guess they missed the launchparty in 1998.

Seems to be vanished from the face off the earth or at least is not supported

[edit] Accesspoints/routers

  • D-Link's presentation on their commitment to IPv6
  • Airport Extreme (later model) details here
    • WARNING: Apple will NOT suppport IPv6, if it works it works, if it doesn't, their support will not talk to you
    • IPv6 on the WAN side
      • Static IPv6
      • DHCPv6 (stateful) with PD
      • DHCPv6 (stateless) with PD
      • 6to4 tunneling
    • IPv6 on the LAN side
      • stateless DHCPv6
      • no stateful DHCPv6
  • Linksys RVS4000 has a NAT-PT bug
    • IPv6 on the WAN side
      • 6to4 tunneling
    • IPv6 on the LAN side
      • Stateless
      • Stateful (DHCPv6)
  • Linksys WRVS4400N is the wireless version of the above
    • IPv6 on the WAN side
      • 6to4 tunneling
    • IPv6 on the LAN side
      • Stateless
      • Stateful (DHCPv6)
  • D-Link DIR-615 (Hardware Revision C)
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6 (stateful)
      • DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful (DHCPv6)
      • Stateless
  • D-Link DIR-825 (Hardware Revision B)
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6 (stateful)
      • DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful (DHCPv6)
      • Stateless

[edit] Trial and Test devices

In addition to the commercial products, some people are rolling their own using Linux/BSD servers or upgrading the firmware of existing devices. The typical broadband gateway currently on the market is a standard computer design loaded with custom firmware according to the spec of the company whose plastic case and logo are used. But in actual fact, all devices whatever the brand, are manufactured by factories in the Far East using a small set of standard hardware designs. Virtually all of these designs can be adapted to use IPv6 by simply changing the software, i.e. uploading a different set of firmware. The brand name sellers are using this fact to have very short product cycles to adjust to market demand. This means that as soon as there is any significant demand for IPv6 support, they could update their software and have new products on the market in two to three months.

[edit] The Far East

The Japanese market has many more IPv6 devices and services than most other countries. A good way to track what is going on there is to read through the announcements at IPv6Style in Japan. Don't click on the English version of the site since that is outdated and doesn't contain the product announcements. Instead, use a web translator to read the site. You can use Babelfish to produce an adequate Japanese-to-English translation for learning about new products. While many articles will still be almost incomprehensible, new product announcements are so formulaic that you can usually understand what the product will do, and the product name and model for further inquiries.

If you want to deploy IPv6 and cannot find CPE on the market to support your needs, it is worthwhile to send a detailled RFQ to the major brand name sellers like Linksys, Netgear, etc. Japanese or Korean brand name sellers are more likely to have already done the IPv6 development so make sure that companies like Billion and Buffalo get your RFQ.

Personal tools