On 02/23/2017 01:13 AM, Lorenzo Colitti wrote:
On Thu, Feb 23, 2017 at 11:11 AM, Randy Bush <randy(_at_)psg(_dot_)com
<mailto:randy(_at_)psg(_dot_)com>> wrote:
[...]
> And it is absolutely inappropriate to change this nowin given that
the /64
> boundary has been the standard for the last 20 years.
the other week you were saying i should be patient and we could change
it in another decade from now. now you say forever, it's cast in
concrete.
Sorry, let me clarify: it is inappropriate to change that now *in this
document*. As I said elsewhere, the IETF and 6man absolutely have the
ability to change the standard, but it should follow the proper process:
write a draft, get consensus, update whatever RFC RFC 4291bis eventually
becomes. I'm not saying we need to wait a decade.
(I do also happen to think that it would be better if we waited a decade
before changing this, because we're only 5 or so years into large-scale
deployment that will hopefully last at least 3 or 4 decades. However, I
don't expect many people to agree with me on that, so I'm not trying to
make that argument here.)
Isn't that actually an argument for waiting before moving rfc4291bis to
full standard?
If you'd wait to change it, why would you want to cast this into stone
now? So that, later you can argue that "it's a full standard document...
so we shouldn't change it"?
--
Fernando Gont
SI6 Networks
e-mail: fgont(_at_)si6networks(_dot_)com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492