[145005] in North American Network Operators' Group
Re: Strange static route
daemon@ATHENA.MIT.EDU (Jimmy Hess)
Sat Sep 24 19:02:15 2011
In-Reply-To: <CAJL_ZMNm6u=JQA9prKiyyAkzPwPJf22zxZjRXKS8HPh+2+JRkA@mail.gmail.com>
Date: Sat, 24 Sep 2011 18:02:05 -0500
From: Jimmy Hess <mysidia@gmail.com>
To: jim deleskie <deleskie@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Sep 23, 2011 at 8:57 PM, jim deleskie <deleskie@gmail.com> wrote:
> Wouldn't it make more sense to filter in bound default? =A0or use a singl=
e
> static default if you where worried about that?
Yes, the aesthetics of using a "/1 route" for that purpose are very poor=
.
Don't implement design objectives using subtle side-effects, when a
proper tool
is available -- human errors later are likely.
Using a /1 static to achieve a "longer prefix" to override a
default falls in that
category, when routers have a filtering mechanism capable of
explicitly expressing
the desired policy :)
> -jim
--
-JH
