Re: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt

[Ole Troan <[e-mail]>]

>>> It is _way_ too much software to run both odhcpd _and_ radvd, while
>>> also pretending that radvd is deprecated.
>>> It is not only too much in terms of RAM needed by these software packages, but too much also in terms of skills needed by the sysadmin or the student, documentation, config files, and more.
>>> I do not understand how one does not see this as being a problem.
>> Neither do we understand you seeing it as a problem. ;-)
> 
> We do not understand what in draft-naveen should we add to explain to you.
> 
> What small suggestion you have to us to add in the draft?

I am making an assertion. The assertion is: if you specify Prefix Delegation within the ND protocol, it will when you are done look very much like DHCP PD.

Your only justifications for doing this seems to be: “I don’t want to implement DHCP”, or “DHCP takes too much space”.
Writing code is cheap, writing standards is expensive.

If I am correct then it is not justifiable to spend time standardizing a redundant specification.
(Also because that will force everyone else, to have to implementation of the same thing).

How can you convince me?
Write two implementations for your constrained device.
One with DHCP PD + ND and one with ND and ND PD.
Compare. Both implementations must be written specifically for this environment (don’t go pull packages from a Linux distro and claim that as a reason why it’s not a fit).

Cheers,
Ole