On Fri, 24 Jan 1997 06:10:01 -0800 (PST), Paul Goyette  
<paul@pgoyette.bdt.com> wrote:
> On Thu, 23 Jan 1997, Christian Kuhtz wrote:
>
> > What you are talking about requires source routing, and is impossible per
> > se.
>
> Well, in _my_ business (Internetworking Consulting), "source routing"

Well, thank you for the knowledge demonstration.  I'm not that stupid, thank  
you very much.

Source routing by policy is just one kind of source routing.  Source routing  
means, the source determines where packets go.  Whether this is done by IP  
options or policy is irrelevant, key is that it happens based on information  
specific to the source.

Besides, either way is a theoretical possibility in this case and no point in  
splitting hairs.  Source routing based on policy won't be available for  
NetBSD anytime soon, IP options are impractical.

> Which isn't what was being asked for...

He wanted to split up traffic based on source, that's what he's getting w/  
that kludge.  What was asked for in your opinion?

> Hmm.  There's an awful lot of mission-critical SNA networks running out
> there, with source-routing.  Might be a bad design but it sure works!

SNA networks do other much more disgusting things, too, which can hardly be  
called industry's best practices.  It is frightening to see so much  
mission-critical stuff run across SNA.  I'd like to put that "sure works" in  
quotes where it belongs.  But then again, VM, for instance, always was "a neat  
idea" -- hardly something I want to use in everyday life, though.

Regards,
Chris

--
Christian Kuhtz <ckuhtz@paranet.com>
                                                          ".com is a mistake."