Everyone seems to agree that RFC compliance is very important. The argument appears to be is not whether we should change the behavior to be RFC compliant or not, it is more of a matter of when we should change the default.

Is the current default causing issues currently and breaking network setups for users?

Do users rely on the current default and take it for granted that a change would cause issues and break network setups?

No matter what we do we probably going to cause issues to some users. The goal should be reducing such disruption in service. So, let focus on how urgent the case (changing the default) is, and how to get there. Maybe we should agree on a set of event to get us there. We can for example have a big notice on the download/documentation pages that a change is coming and what to expect as a user and how to change the configuration to keep the current behavior once the change eventually rolls in. Maybe we should send out several emails (usr/dev lists...) making users aware of the coming change and advice them to add explicit configuration in the config files to be ready for the change.

Do we care about users? let us talk to them, otherwise changing the default now or two years from now will largely have the same consequences. :)

Cheers,
Jafar


On 2016-04-19 21:17, Lennart Sorensen wrote:
On Tue, Apr 19, 2016 at 07:39:48PM -0400, Lou Berger wrote:
Paul,

You have a valid point on absolutes.  One never should say never :-)

That said, we're not talking some obscure feature here . Does any non-quagga based vendor, major or otherwise, support the non standard behavior as the default? If so , there may be some basis for this discussion. If not , and in my experience , then the current behavior should be viewed as a bug.

Just one persons (my) opinion...

If upgrading from one version to another without changing anything in
the config causes a major change in behaviour, then that is a bug.

Especially since the config tends to NOT save default values so you can't even rely on having set something explicitly to make it keep doing that.
If you want what was the default but no longer is, you are screwed.
That is NOT good for the user.

_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to