[190921] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NFV Solution Evaluation Methodology

daemon@ATHENA.MIT.EDU (Randy Bush)
Wed Aug 3 03:56:41 2016

X-Original-To: nanog@nanog.org
Date: Wed, 03 Aug 2016 16:56:34 +0900
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLaYhadWDD0tdMitHR_R=53uRQzb2Au5XgsHGzs3tgjCy3A@mail.gmail.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

> but, NFV isn't necessarily 'cloud'... It CAN BE taking purpose built
> appliance garbage that can't scale in a cost effective manner and
> replacing it with some software solution on 'many' commodity
> unix-like-hosts that can scale horizontally.

my main worry about nfv is when they need more forwarding horsepower
than the household appliance <tm mo> has, and the data plan is is moved
out of the control plane and they are not congruent.  we've had too many
lessons debugging this situation (datakit, atm, ...).

beyond that, i am not sure i see that much difference whether it's a
YFRV or a SuperMicro.  but i sure wish bird and quagga had solid is-is,
supported communities, ...

randy

home help back first fref pref prev next nref lref last post