[AusNOG] What does an IPv6 broadband service look like? WAS Re:IPv4 Exhaustion

[Adam Griffiths]

MMC/Barry,

Might be worth having a look at RFC4241.
http://www.rfc-editor.org/rfc/rfc4241.txt

This is the model that NTT are using for their Dual stack service.  They
also have a tunnel service similar to what internode are already offering.

Cheers,

Adam
adam at griffiths.org.au

On Fri, Aug 1, 2008 at 3:02 PM, Matthew Moyle-Croft <mmc at internode.com.au>wrote:

> Clever CPE is a very interesting approach - why do v4 to v4 NAT at the ISP
> when you can do v4 to IPv6 at the consumer.
> MMC
>
> On 01/08/2008, at 2:24 PM, Barrie Hall wrote:
>
> Very good question.
>
> The thinking around here goes like this (with all the usual "my thoughts,
> not my employer disclaimer"):
>
> Pre-V4 Exhaustion: Dual stack 4/4 and 6/6  (and maybe 4/6)
>
> As we approach exhaustion: Dual Stack 4/4/4 and 6/6  (and maybe 4/6)
>
> That middle '4' is a bone of great contention which I am not going to let
> go of. Failed to get it APNIC 25.
>
> Getting into more general terms I think we all need to acknowledge that for
> 99.99% of our customers, there is nothing in V6 for them. For the industry,
> it's all about keeping the lights on in world depleted of V4 address space.
>
> My personal view is that, from a customer's perspective, we should not be
> insisting that they upgrade their home network devices (PC's) to support V6.
> That implies some clever CPE and thats the real problem. The CPE vendors are
> behind.
>
> Regards,
> Barrie
>
>
> ----- Original Message -----
> *From:* Matthew Moyle-Croft <mmc at internode.com.au>
> *To:* Mark Newton <newton at internode.com.au>
> *Cc:* Chris Chaundy <CChaundy at soulaustralia.com.au> ; ausnog at ausnog.net
> *Sent:* Friday, August 01, 2008 11:48 AM
> *Subject:* [AusNOG] What does an IPv6 broadband service look like? WAS
> Re:IPv4 Exhaustion
>
> To change direction a little here to focus this on something other than
> NAT:
> One thing that is on my mind and we have internally been struggling with
> is:
>
> What DOES an IPv6 broadband service really look and smell like?
>
> It's not that easy to map our existing ingrained views on an IPv4 broadband
> service onto a v6 or dual stack world.
>
> What IP ranges do customers get with IPv6?  /128 and NAT/Proxy?  /96? /64?
> /48? etc
> Do they necessarily get a static subnet?  Why/Why Not?  What implications
> does it have for your internal IGP?
> If they get a static subnet then do they get to play with reverse mappings?
> How will the transition from v4 to dual stack to some interim step to v6
> only go?
>
> I know a lot of the geeks will go "well, obviously a static /48 with our
> own controllable reverse mappings" but on a LARGE scale with mostly non-geek
> home users then what exactly does it look like?
>
> What do the CPE vendors need to support?   What do we need to support?
>
> MMC
>
> --
> Matthew Moyle-Croft Internode/Agile Peering and Core Networks
> Level 4, 150 Grenfell Street, Adelaide, SA 5000 Australia
> Email: mmc at internode.com.au    Web: http://www.on.net
> Direct: +61-8-8228-2909      Mobile: +61-419-900-366
> Reception: +61-8-8228-2999        Fax: +61-8-8235-6909
>
>
> ------------------------------
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> --
> Matthew Moyle-Croft Internode/Agile Peering and Core Networks
> Level 4, 150 Grenfell Street, Adelaide, SA 5000 Australia
> Email: mmc at internode.com.au    Web: http://www.on.net
> Direct: +61-8-8228-2909      Mobile: +61-419-900-366
> Reception: +61-8-8228-2999        Fax: +61-8-8235-6909
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20080801/8d90d899/attachment.html>