As one of the founders of 6connect, we had initially, years ago, only allowed for delegation down to the /64. Client demand dictated support down to the /128 and has been that way for a couple of years. People still implement v6 in very odd ways. A common example I have seen is where someone uses .. say a /21 v4 per VLAN and matches it with a /118 of v6 to keep with their existing provisioning policy. We've had to build in all kinds of unrecommended capabilities for customers and I expect the rest will have to do the same. Same for DHCPv6 BTW.
Cheers, Aaron On Wed, Jan 29, 2014 at 08:22:19PM +0100, Nicolas CARTRON wrote: > Hi Brian, > > On Wed, Jan 29, 2014 at 7:54 PM, Brian E Carpenter < > [email protected]> wrote: > > > Hi, > > > > We're working on the next version of > > http://tools.ietf.org/html/draft-carpenter-6man-why64 > > > > Can anyone say whether existing IP Address Management tools that > > support IPv6 have built-in assumptions or dependencies on the > > /64 subnet prefix length, or whether they simply don't care about > > subnet size? > > > > I'm working at EfficientIP, a (DNS/DHCP) IPAM vendor, and our IPAM software > proposes by default /64 subnets, > but you can increase or decrease the size if needed, so no blocking point > IMO. > > Cheers, > > -- > Nicolas -- Aaron Hughes [email protected] +1-703-244-0427 Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 http://www.tcp0.com/
