[52687] in North American Network Operators' Group
RE: what's that smell?
daemon@ATHENA.MIT.EDU (Jason Lixfeld)
Tue Oct 8 15:02:51 2002
From: "Jason Lixfeld" <jlixfeld@andromedas.com>
To: "'John M. Brown'" <john@chagresventures.com>
Cc: "'Dan Hollis'" <goemon@anime.net>,
"'Petri Helenius'" <pete@he.iki.fi>, "'Joe Abley'" <jabley@isc.org>,
"'Mike Tancsa'" <mike@sentex.net>, <nanog@merit.edu>
Date: Tue, 8 Oct 2002 14:59:18 -0400
In-Reply-To: <20021008115132.F26874@oso.greenflash.net>
Errors-To: owner-nanog-outgoing@merit.edu
> Those are reasons against.
>
> We in the technical community need to develop or modify our tools to
> make those tasks easier.
My point, exactly.
> Hire a lazy but smart admin! :)
>
>
> On Tue, Oct 08, 2002 at 02:45:22PM -0400, Jason Lixfeld wrote:
> >
> > > On Tue, 8 Oct 2002, Jason Lixfeld wrote:
> > > > In more cases than not, especially now adays with lots
> of networks
> > > > peering all over gods creation, RPF can have some
> pretty detrimental
> > > > effects if your routing is somewhat asymmetrical.
> > >
> > > actually RPF is extremely effective especially where its highly
> > > asymmetrical, eg at the edge. theres virtually no reason
> not to RPF
> > > dialup/isdn/cable/dsl/etc customers for example.
> >
> > Sure, but to RPF so many customer facing edge ports in
> comparison to the
> > far fewer number of egress ports makes the implementation procedure
> > quite extensive. The more configuration, the more room for
> errors or
> > "oops, forgot to configure that there", not to mention change
> > management.
> >
>
