Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

[[e-mail]]

> >     Gyan>  This topic has come up many times over the years in heated debate and this is another instance of that.  Agreed.  However, what makes this instance different is that we have a major problem to be solved with 4G  &  now as 5G is rolled out, segmentation is of utmost importance.  I think in the past we have not had a major problem to be solved and so this change being proposed did not gain traction,  but now as 5G becomes the "norm" as it will compete directly with broadband that customers will start using 5G in SOHO as well as other environments.   This is a major issue that has come up with the ramp up for 5G IPv6 only deployments.
> > 
> > There is already a solution to this: use DHCPv6 PD on 5G networks. It's been supported since 3GPP release 10 several years ago.
> > 
> > Has any mobile provider deployed dhcpv6 pd?
> > 
> > Perhaps the mobile providers have seen what an operational nightmare dhcpv6 pd is and... are like nope. 
> > 
> > I am in favor of the ietf opening their eyes to a better solution. 
> > 
> > Rfc7278 is universally deployed because it is easy. 
> > 
> > Can we do better (more /64s) and easy ?
> 
> It's difficult to design a better solution without understanding what "operational nightmares" mean.
> Would you mind elaborating?
> 
> I believe running a dhcp server supporting 120M mobile subscribers would be a nightmare.  I believe dhcpv6 is a larger stateful database and a not very forgiving protocol... and client implementations are ... heterogeneous. ... and server failover.. messy
> 
> None of that exists today in mobile. I feel the effort and scale are daunting, so i am not going to do it. 
> 
> But, getting a knob in the gateway to set the RA to be 60 (or other) instead of 64 would be easy. And, that knob could be constrained to only compatible device type (chef’s kisses!)... it can be done

You could operate DHCP PD the exact same way.

cheers,
Ole