On Mon, Dec 21, 2015 at 12:38 PM, Jafar Al-Gharaibeh <[email protected]> wrote:
> > On 12/20/2015 11:51 PM, Andrew Qu wrote: > > In order to support MTR, we worked hard as well to design our ASIC in > catalyst 6500 family. J > > That feature is very ASIC resource demanding and I think that was latest > HW piece can do MTR forwarding. > > > > Without ASIC that can support MTR in the industry now, could Jafar share > something with us why we need to > > develop MTR routing? > > I don't know if I fully understand the ASIC/lack-of-MTR-support comment > and why that should stop Quagga from getting this support. We run Quagga on > platforms that can do MTR if Quagga supports it. > As of why do we need MTR - are you suggesting that it is not needed at all? > or it doesn't bring anything to the table that we can't do using other > techniques? Can you please elaborate? > I remember one customer using a combination of policy-based-routing and MPLS TE as an alternate solution. Daniel
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
