[131045] in North American Network Operators' Group
Re: Only 5x IPv4 /8 remaining at IANA
daemon@ATHENA.MIT.EDU (Kevin Stange)
Tue Oct 19 15:55:57 2010
Date: Tue, 19 Oct 2010 14:55:42 -0500
From: Kevin Stange <kevin@steadfast.net>
To: nanog@nanog.org
In-Reply-To: <AF24AE2D4A4D334FB9B667985E2AE763757959@mail1-sea.office.spectrumnet.us>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7D937DF06902677F474D5B75
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 10/19/2010 10:15 AM, John van Oppen wrote:
> I would say for most of our customers, especially in the hosting space,=
a "class C" is a /24, they just don't know networking at all and build t=
heir hosting lans using /24s for each vlan.
>=20
> Very few of the requests that we get are submitted using CIDR notation.=
Personally, I think this is a big reason for random table bloat, I hav=
e had so many arguments about customers being able to aggregate announcem=
ents for BGP it is not even funny... the "I want to announce the blocks=
as a class Cs" request is irritatingly common.
It's been our general policy to always respond in CIDR notation whenever
we get a request in class notation and to hope that our customers either
figure out what that means on their own or ask us for clarification and
learn something.
IPv6 is helping because a lot of people seem to be making the connection
that the "slash" notation is related between the two.
--=20
Kevin Stange
Chief Technology Officer
Steadfast Networks
http://steadfast.net
Phone: 312-602-2689 ext. 203 | Fax: 312-602-2688 | Cell: 312-320-5867
--------------enig7D937DF06902677F474D5B75
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAky998IACgkQkd/BoeKjg0gY4wCeNw9EXobQNL30H9j36g8s35f9
VREAnirAVAyX0o7uaxRwcsz2CjoTKRCK
=jNXv
-----END PGP SIGNATURE-----
--------------enig7D937DF06902677F474D5B75--
