http://info.us.bb.verio.net/routing.html#PeerFilter
It seems if I were one of their customers they would accept my
66.11.168/23 announcement and re-announce it to their peers, but they
won't accept it from any of their peers.
Announcing a covering /20 along with the regional more specifics I have
will only serve to increase the size of the routing table for most
backbones, and lead to sub optimal routing in some cases since I'm
announcing the more specifics due to geographical diversity.
Ralph Doncaster
principal, IStop.com
http://info.us.bb.verio.net/routing.html#PeerFilter
It seems if I were one of their customers they would accept my
66.11.168/23 announcement and re-announce it to their peers, but they
won't accept it from any of their peers.
As a customer you pay them to announce your /23, as a peer you don't.
Their line of logic is that if you are a peer of theirs you don't have to
accept that /23 either.
Announcing a covering /20 along with the regional more specifics I have
will only serve to increase the size of the routing table for most
backbones, and lead to sub optimal routing in some cases since I'm
announcing the more specifics due to geographical diversity.
Announce the /20 to your transit providers, and the more specifics with
no-export. Verio's position is that they don't want to or need to hear
your /23s unless you are a customer, and for the most part they are right.
This is really old news...actually, I seem to recall that they would only
accept /19 or shorter prefixes from former Class A & B space...I pressed
Sprint for a /21 from the swamp (instead of the former Class A space /21
they initially assigned) because of Verio's policy, in fact. They must
have softened the policy within the past year or so to /21 or shorter.
Unless you are in "the swamp" - the old Class C, where I believe that they do accept /24's.
Regards
Marshall Eubanks
Richard A Steenbergen wrote:
But I've broken my /20 into a /21 for Ottawa, a /22 for Toronto, a /23 for
Montreal, and a /23 for expansion. I'm currently only getting transit in
Toronto, but will have a second transit provider restored in Ottawa (I was
using GT for a short while). While announcing the the /20 will my network
is reachable for single-homed Verio customers, it won't provide the true
best path that simply accepting the regional more specifics.
-Ralph
They tend to match the size of the smallest block assigned by the
registries.
Austin
:
: They tend to match the size of the smallest block assigned by the
:registries.
:
Calling it a tendency is probably a stretch. They only bowed to RIR
policy once in recent memory, when ARIN began allocating /20 PI
blocks. Prior to that, they nearly got their logo placed in Webster's
dictionaries under "anal".
That said, their current policy of refusing to accept de-aggregated
prefixes from peers (while accepting such from paying customers) makes
perfect sense, IMHO. Not arrogant, just a smart & reasonable business
decision.
cheers,
brian
NOC +861066418121/22 noc@cn.net FAX +861066418105
German
That said, their current policy of refusing to accept de-aggregated
prefixes from peers (while accepting such from paying customers) makes
perfect sense, IMHO. Not arrogant, just a smart & reasonable business
decision.
You could turn this around and ask what reasons there are to not filter the more specifics out from your peers...
- kurtis -
Brian Wallingford wrote:
[...]
That said, their current policy of refusing to accept de-aggregated
prefixes from peers (while accepting such from paying customers) makes
perfect sense, IMHO. Not arrogant, just a smart & reasonable business
decision.
Interesting. Looking around, it seems that Verio allocates /24 and
larger (all I saw offhand were /24s and /23s) address blocks for
customers from the Class C space. Can't fault 'em for consistency.
Peter E. Fry
Ralph,
Welcome to the Internet. This has been the case for years, now. If you don't
like it, you have a couple options.
1) You can go on hunger strike and chain yourself to the front door at NTT,
demanding a change to the policy.
2) You can lobby Verio's peers to drop peering with them, unless they change
their ways.
3) You can pay Verio to accept your routes.
4) You can live with it.
May I suggest #4?
I'm not a big fan of Verio's filtering policies, but as long as you announce
the /20 as an aggregate, you'll be fine.
- Daniel Golding
That said, their current policy of refusing to accept de-aggregated
prefixes from peers (while accepting such from paying customers) makes
perfect sense, IMHO. Not arrogant, just a smart & reasonable business
decision.
I have one downstream ISP customer that explicitly asked for "full BGP
routes" to be written into the contract. Why Verio's customer's wouldn't
want full routes makes no business sense to me.
However a NANOG list subscriber was kind enough to help me get past
Verio's NOC monkeys and get their filters updated to allow my
announcements.
-Ralph
I have one downstream ISP customer that explicitly asked for "full BGP
routes" to be written into the contract. Why Verio's customer's wouldn't
want full routes makes no business sense to me.
The reasons are related to the law of diminishing returns.
-mark