[52685] in North American Network Operators' Group
Re: what's that smell?
daemon@ATHENA.MIT.EDU (John M. Brown)
Tue Oct 8 14:55:01 2002
Date: Tue, 8 Oct 2002 11:51:32 -0700
From: "John M. Brown" <john@chagresventures.com>
To: Jason Lixfeld <jlixfeld@andromedas.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
In-Reply-To: <003101c26efa$dc035340$890711ac@housekat>; from jlixfeld@andromedas.com on Tue, Oct 08, 2002 at 02:45:22PM -0400
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.
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.
>
