[143395] in North American Network Operators' Group
Re: IPv6 end user addressing
daemon@ATHENA.MIT.EDU (Matthew Moyle-Croft)
Mon Aug 8 20:43:10 2011
From: Matthew Moyle-Croft <mmc@internode.com.au>
To: Brian Mengel <bmengel@gmail.com>
Date: Tue, 9 Aug 2011 00:42:12 +0000
In-Reply-To: <CAAv0nWCfMtcGGyEfxP54J1SpydGj88A08iKGip8NfPjhm1az6A@mail.gmail.com>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi Brian,
From someone who's actually done this.
- Our customer base is primarily PPP connected broadband users (variety of =
technologies, mostly ADSL).
- We do a DYNAMIC /64 on the PPP interface so that people who terminate dir=
ectly on a PC can get IPv6 without DHCPv6 PD.
- In addition for the subnet assigned via DHCPv6 Prefix delegation which is=
STATIC as that's what customers have been asking for:
In our trial phase we did /60s to customers - this worked just fine. I don=
't recall anyone actually saying "I need more". (The /60 was the first nib=
ble boundary and it allowed us to do some dumb things for allocation which =
didn't compromise the allocation strategy later).
In production we've chosen a more conventional /56. At some point it beco=
mes a little arbitrary. Our feeling is that at the point your have 256 /64=
s in production then ADSL is probably NOT what you need or want as a techno=
logy so we can do things differently for ethernet connected customers.
We're getting there with support for customers bringing their own PI space.
(For an idea of scale - we're tiny globally, but have around 250k customers=
across mainly Australia. We run our own global dualstack network).
MMC
On 06/08/2011, at 1:47 AM, Brian Mengel wrote:
In reviewing IPv6 end user allocation policies, I can find little
agreement on what prefix length is appropriate for residential end
users. /64 and /56 seem to be the favorite candidates, with /56 being
slightly preferred.
I am most curious as to why a /60 prefix is not considered when trying
to address this problem. It provides 16 /64 subnetworks, which seems
like an adequate amount for an end user.
Does anyone have opinions on the BCP for end user addressing in IPv6?
--
Matthew Moyle-Croft
Peering Manager and Team Lead - Commercial and DSLAMs
Internode /Agile
Level 5, 150 Grenfell Street, Adelaide, SA 5000 Australia
Email: mmc@internode.com.au<mailto:mmc@internode.com.au> Web: http://www=
.on.net<http://www.on.net/>
Direct: +61-8-8228-2909 Mobile: +61-419-900-366
Reception: +61-8-8228-2999 Fax: +61-8-8235-6909
