Most major wireline deployments provide /60, /56 or /48. Examples: free.fr, KDDI, AT&T. Exceptions are RCS+RDS (working on shorter prefixes) and some North American cable operators, which AIUI are crippled by sucky CPEs that fail to do anything useful when they receive more than a /64.
On Thu, Nov 15, 2012 at 2:27 AM, Randy Turner <[email protected]>wrote: > > Have their been any ISPs that have come forward to discuss their consumer > IPv6 allocation plans? I don't think we should wrap ourselves around a > model that says, "yeah, we need multiple /64s for consumers because that's > the way a particular protocol works (SLAAC). Maybe we need another > method. One /64 for a home network seems like overkill regarding address > space utilization -- A /32 would be overkill. I know some folks think we > have more address space than we'll ever use, but gee…. > > Randy > > > On Nov 14, 2012, at 7:07 AM, Ted Lemon wrote: > > > On Nov 14, 2012, at 3:31 AM, Brian E Carpenter < > [email protected]> wrote: > >> On 14/11/2012 02:34, Randy Turner wrote: > >>> I was thinking that, in an effort to reduce scope to something we can > deal with for now, that a /64 would be big enough > >> > >> It simply isn't, because it doesn't allow subnetting in the > home/car/small office or whatever. > > > > I don't see the point in working on the /64 case—if that's all we're > trying to accomplish, we've already accomplished it. The interesting work > Homenet is doing is in fact trying to solve the prefix distribution and > automatic setup problem. It's true that this is a hard problem. It's > also true that if we don't specify a solution, people will attempt to solve > it in their own ways. And if they do that, we will wind up in the > situation that Jim found himself in with his broken box with its own > built-in DHCP server. > > > > BTW, a little more on that topic: the reason that two DHCP servers on > the same wire broke Jim's network in a flaky way is that IPv4 doesn't > handle the multi-homing case. IPv6 deliberately places the multi-homing > case in-scope. This creates a bit of a problem for legacy apps that do > not support multi-homing, but it also creates the winning situation that if > one device is advertising a provisioning domain that doesn't work, > applications that do correctly handle multi-homing will simply use a > different provisioning domain. > > > > _______________________________________________ > > homenet mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/homenet > > > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
