: But I am concerned some people may build filters using
: only exact matches, so it seems safer to have route
: objects for more specifics.
:: I´d suggest to create each route object for each
:: announced prefix...IMHO you are very right - there are
:: for sure networks out there, which will
database and more specific routes
Hey!
I am updating the route/inetnum objects in the RIPE database and I am wondering
if I have to create more specific route objects. For example, I have the
following routes announced:
- 89.145.160.0/21
- 89.145.160.0/22 (FR7)
- 89.145.164.0/23 (DK2
Hi,
On Mon, Nov 20, 2017 at 11:03:18AM +0100, Vincent Bernat wrote:
> But I am concerned some people may build filters using only exact
> matches, so it seems safer to have route objects for more specifics.
Generally speaking, you should have route objects for what you intend
to announce.
*Some*
Hey!
I am updating the route/inetnum objects in the RIPE database and I am
wondering if I have to create more specific route objects. For example,
I have the following routes announced:
- 89.145.160.0/21
- 89.145.160.0/22 (FR7)
- 89.145.164.0/23 (DK2)
- 89.145.166.0/23 (GV2)
Each more specif
4 matches
Mail list logo