16 Mar
2012
16 Mar
'12
6:30 p.m.
I think managing proper use of the address space (e.g. use for ham radio)
is better facilitated by having fewer BGP advertisements. E.g. if we only
allow /16 network BGP advertisements we only add 256 entries. All other
subnets under the /16 can be tunneled -- if you have a bad actor, simply
revoke their tunnel.
In most cases, I think, a smaller subnet advert is probably more of a
"vanity" thing, than a network need.
------------------------------
John D. Hays
K7VE
PO Box 1223, Edmonds, WA 98020-1223
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
On Fri, Mar 16, 2012 at 11:10, Tim Pozar <pozar(a)lns.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I have yet to find anything that is doing core BGP peering that is not
CIDR capable. The main reason for not doing anything less than a /24 is
lack of memory and not filling up the route table with a zillion prefixes.
Sprint started this in the early days. I find that few if any peers
enforce this of late as you can see a bunch of prefixes that are less than
a /24 being announced. Check out routeviews.org to see.
That being said, in order to be good neighbors out there and follow
conventions, we should not be announcing anything less than a /24.
Tim