[184354] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: /27 the new /24

daemon@ATHENA.MIT.EDU (Matthew Kaufman)
Fri Oct 2 10:49:14 2015

X-Original-To: nanog@nanog.org
In-Reply-To: <80BBB162-5EB8-49F9-AF94-98D8B4C25DCB@mtin.net>
From: Matthew Kaufman <matthew@matthew.at>
Date: Fri, 2 Oct 2015 07:48:33 -0700
To: Justin Wilson - MTIN <lists@mtin.net>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

A /24 isn't that expensive yet...

Matthew Kaufman

(Sent from my iPhone)

> On Oct 2, 2015, at 7:32 AM, Justin Wilson - MTIN <lists@mtin.net> wrote:
>=20
> I was in a discussion the other day and several Tier2 providers were talki=
ng about the idea of adjusting their BGP filters to accept prefixes smaller t=
han a /24.  A few were saying they thought about going down to as small as a=
 /27.  This was mainly due to more networks coming online and not having eve=
n a /24 of IPv4 space.  The first argument is against this is the potential b=
loat the global routing table could have.  Many folks have worked hard for y=
ears to summarize and such. others were saying they would do a /26 or bigger=
. =20
>=20
> However, what do we do about the new networks which want to do BGP but onl=
y can get small allocations from someone (either a RIR or one of their upstr=
eams)?
>=20
> Just throwing that out there. Seems like an interesting discussion.
>=20
>=20
> Justin Wilson
> j2sw@mtin.net
>=20
> ---
> http://www.mtin.net Owner/CEO
> xISP Solutions- Consulting =E2=80=93 Data Centers - Bandwidth
>=20
> http://www.midwest-ix.com  COO/Chairman
> Internet Exchange - Peering - Distributed Fabric
>=20

home help back first fref pref prev next nref lref last post