<skiped> > You can see by now is that my point is that architecturally you shouldn't say > where NVEs are or how they are implemented (in software, hardware or combo > software/hardware).
> I will argue that if you push an NVE further out there are less of them to > manage so you get OpEx benefits. I definitely agree with Dino's points. Since this is an architecture draft, rather than a solution draft, it should be flexible if possible. Best regards, Xiaohu > Dino _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
