On Thu, Feb 23, 2017 at 5:17 PM, Fernando Gont <fgont@xxxxxxxxxxxxxxx> wrote:
> And it is absolutely inappropriate to change this now in given that the
> /64 boundary has been the standard for the last 20 years. It will break
> deployed code that relies on the current standard. (That includes
> concrete code I can point to that I know runs on tens of millions of
> devices.) That's not acceptable to do in a standard reclassification.
If the above will break your code, then your code is already broken. Fix it.
Nope. That code implements the standard, and thus by definition it's not broken.