It seems, you exclusively assume incremental as-an-upgrade deployability. There are also other scenarios. Take Ethernet, for instance. It incrementally ate a lot of competing/legacy technologies without compromising own architectural purity. Hypothetically, if some new **layer** of routing is able to a) substitute the need for "serious tools" (AS, PI addresses) b) eat other layers upwards and downwards Then you'll get both purity and incremental deployment. Just a counter-example.
On 16/03/2008, Robin Whittle <[EMAIL PROTECTED]> wrote: > I conclude that if your solution space is limited to architecturally > pure outcomes, then it almost certainly cannot include solutions > which are incrementally deployable. > If your solution space includes all solutions which are > incrementally deployable, then I think it must include architectures > which are not completely clean. > I am only really interested in incrementally deployable solutions. -- Victor -- to unsubscribe send a message to [EMAIL PROTECTED] with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
