Greenfield IPv4 + IPv6 broadband deployment

[Frank Bulk]

If someone figures out how to do (4) and (5) automated and in scale, please share.  I don't know how one would reserve multiple /64's in a /56 for just one CE and have it function in a way that a CE could get successive /64's within their /56.  Would seem much easier to hand the full /56 to the CE and have it dole it out.

We're doing DHCPv6-relay for everything.

Frank

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de] On Behalf Of Martin Millnert
Sent: Saturday, February 26, 2011 2:57 PM
To: Adam Armstrong
Cc: Mateusz Pawlowski; IPv6 operators forum
Subject: Re: Greenfield IPv4 + IPv6 broadband deployment

On Sat, 2011-02-26 at 20:23 +0000, Adam Armstrong wrote:
> Different access medium. I'm specifically looking for experience with 
> large scale ethernet dhcpv6+v4 deployments :)

The proper way to do v4+v6 *from scratch* (from scratch implies you can
buy equipment compatible with your requirements) on ethernet, to me,
seems to be along the following lines:
  1) L2 separation of each customer,
  2) Statically mapped address spaces per customer, both v4 and v6
  3) DHCPv4 with Option 82 to deliver v4-addresses to the customer,
  4) Baseline DHCPv6 RA:ed /64 on the cust ethernet. /64 taken from a
reserved /56 or shorter for the customer in question,
  5) DHCPv6 PD delivering more prefixes from that same /56 (minus the 1
link /64 done with RA, obviously), 
  6) Option 82 equivalence for DHCPv6 allows for having a DHCPv6 PD
server not running on the PE itself, but further away (dhcp-helper
functionality to assist getting packets there)

That's the way to do the access IMO.  Interface/link separation of users
lets you map addresses more easily and forget entirely about customer
device mappings, which to me seems like such an ease of administrative
overhead/burden that it is absolutely worth investing extra to get.

Above based on experiences running a 2400-ports Ethernet access network,
that fork-lift morphed into the above. Have no operational scaling
experiences with larger networks than above, but with routed access
interfaces and IGP on the inside, it ought to scale pretty far.

My $0.02.

Cheers,
Martin