On Wed, 3 Jun 2015, Paul Jakma wrote:
At present, we are not clear on the design because several people seem
to think the ZServ API added by this patch-set adds still is compatible
with multiple-processes.
Oh, and this isn't about VRFs and zebra generally. I'm fine with that.
This is very specifically about the static, unnegotiated VRF ID added to
the header that allows a client to expect that it can send any command it
wants to the remote zebra for whatever VRF context and expect that the
remote zebra must be able to deal with it.
It's purely about this public API that is being added.
It seems to me that the claim that this is future-compatible with multiple
zebra processes would require more finessing of this API (which should be
done before we're committed). Alternatively show how. Alternatively, that
claim shouldn't be made.
That's all.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Those who can, do; those who can't, simulate.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
