On 31/10/2009, at 5:58 PM, TreeNet Admin wrote:
The huge problem is all the home customers with ancient second-hand CPE.
I don't think they're a huge problem as they're the least likely to notice the implementation of SP-NAT in front of their connection. I know at least one large ISP in our region considering this as phase #1 of an SP-NAT implementation. The big issue right now is: the lack of IPv6 native support in CPE at all. If we had the larger CPE vendors starting to implement (*) then with a 2 year replacement time for most CPE we'd be fine by the time a lack of v4 addresses starts to pinch. In NZ at the moment with VDSL2 starting to be rolled out it'd be a PERFECT time to start squirrelling (or whatever marsuipal/mammal you guys have) it into people's houses as people replace CPE. But I'm guessing that it's not happening that way alas. We need to start getting IPv6 out there to end-customers to start the ball rolling to start shaking the problems down. (And believe me there a whole LOT of problems with IPv6 in actual real production to DSL customers ...) (*) Let's face it - given that almost all the CPE is Linux based it's just laziness on the CPE vendor's part as it's already bloody well done for them. MMC -- Matthew Moyle-Croft Peering Manager and Team Lead - Commercial and DSLAMs Internode /Agile