[AusNOG] What does an IPv6 broadband service look like?
scott at doc.net.au
Sun Aug 3 21:33:21 EST 2008
InterNode are doing consumer IPv6, both native and tunneled.
Basically they appear to have just ignored the charging issues and are just
charging for all IPv6 traffic, including traffic that would otherwise have
been "free" as well as the IPv6 tunnel overheads. Details at
As you stated very few of the higher level vendors are doing much with IPv6
at the moment - it's basically the good old catch-22 situation where there's
no point supporting it until people are using it, and you can't use it until
people support it...
Speaking with a vendor hat on the subject of this thread is probably as much
as anything what's holding things back - until we know what real-world IPv6
deployments look like it's hard to architect a product. eg, consider a spam
RBL - today many of them work at the individual IP address level, but is
that still valid if ISPs start handing out a million IPv6 addresses to each
On Sun, Aug 3, 2008 at 12:54 PM, Kevin Littlejohn
> That, and billing - I missed the start of the conversation, but is
> anyone actually offering native IPv6 atm, and if so, are you billing
> per Mb for it (and if so, how? :)?
> So far, the edge devices we deal with (SCE, PacketLogic, Packeteer,
> BlueCoat) don't, AFAIK, support IPv6. The RADIUS-based ones (SSG/ISG/
> 802.1x etc), one would assume, will just continue to report bulk
> traffic across v6 the same way they do across v4 (I haven't tested
> that, tho). Similarly anything pipe-centric like SNMP, if anyone's
> actually still using that for billing - but RADIUS and SNMP share the
> same problems for tracking _what_ the traffic is.
> I also don't know how the app-layer inspection devices (see list above
> mainly) deal with IPv6 traffic - I'm fairly certain most of them don't
> grok it, therefore may not play nicely if you're filtering or proxying
> or shaping.
> This would seem to be a particular issue also if you're billing, say,
> on-net versus off-net as the universities do (or peering), where you
> need to track different classes of traffic based on source/dest.
> Vendors don't seem to be showing a huge interest in moving to solve
> this quite yet, and at that "every bit counts" level of speed they're
> going for with transparent inspection devices, I'd imagine it's not
> necessarily an easy fix for some of them.
> AusNOG mailing list
> AusNOG at ausnog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the AusNOG