[157545] in North American Network Operators' Group
Re: IOS architecture
daemon@ATHENA.MIT.EDU (Aled Morris)
Mon Oct 29 10:03:38 2012
In-Reply-To: <31508.1351514631@turing-police.cc.vt.edu>
Date: Mon, 29 Oct 2012 14:01:43 +0000
From: Aled Morris <aledm@qix.co.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 29 October 2012 12:43, <Valdis.Kletnieks@vt.edu> wrote:
> On Sat, 27 Oct 2012 11:16:10 +0100, "Darren O'Connor" said:
> > All vendors should be writing in depth architecture books. The Juniper
> MX
> > book is a great example. Tell us exactly what your product can do and
> we'll
> > likely use more of it
>
> On the flip side, if you document what your product is probably incapable
> of
> due to the design architecture, the salescritters won't be able to sell as
> many
> of them... :)
>
I think the biggest problem in that regard is the gap between what the
switch or router architecture is capable of and what the current release of
IOS actually supports.
This is generally what appears on the "roadmap" but, historically, not all
of it gets delivered in a timely manner, and some features aren't delivered
at all before the hardware is superseded.
Aled
