On Wed, 20 Apr 2016, Lou Berger wrote:
implementation. I think it's fine for quagga to do something
non-standard, but it should default to standard/interoperable modes of
operation.
The aim of the patch I offered is to move toward standards-conformant
behaviour, with the fewest interoperability problems, and the least
amount of behavioural churn.
The whole point of it is to get to the place where we can change that
default while being sure it can _not_ impact any users running a network
with:
- RFC2328 or old Quagga users, for the 'transit allowed' case
- H-bit capable speakers or old Quagga users, for the 'no transit' case
With config options to take care of the remaining cases.
Objecting to this with "RFC Compliance!", without offering something
better than just flipping the default with no config option, is not very
useful.
Provide a better option than the 2 existing offerings, that'd help.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Going to church does not make a person religious, nor does going to school
make a person educated, any more than going to a garage makes a person a car.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
