[133242] in North American Network Operators' Group

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

Re: ARIN space not accepted

daemon@ATHENA.MIT.EDU (Steven Bellovin)
Tue Dec 7 14:19:22 2010

From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <20101204064309.2775B1CC0C@ptavv.es.net>
Date: Tue, 7 Dec 2010 14:19:15 -0500
To: Kevin Oberman <oberman@es.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Dec 4, 2010, at 1:43 09AM, Kevin Oberman wrote:

>> From: Valdis.Kletnieks@vt.edu
>>> From: Valdis.Kletnieks@vt.edu
>> Date: Fri, 03 Dec 2010 20:00:15 -0500
>>=20
>> On Fri, 03 Dec 2010 14:24:16 PST, Leo Bicknell said:
>>=20
>>> It is speculated that no later than Q1, two more /8's will be =
allocated,
>>> triggering a policy that will give the remaining 5 /8's out to the
>>> RIR's.  That means, prior to end of Q1, the bogon list will be:
>>>=20
>>> 0/8
>>> 10/8
>>> 127/8
>>> 172.16/12
>>> 192.168/16
>>> 224/3
>>=20
>> Oh. And don't forget to do *bidirectional* filtering of these =
addresses. ;)
>=20
> Ahh, not quite. Blocking 224/3 bi-directionally might cause a few =
issues
> if you accept multicast traffic from anyone.

Bidirectional blocking of traffic with source addresses in 224/3 -- that =
should never happen unless I badly misunderstand multicast.


		--Steve Bellovin, http://www.cs.columbia.edu/~smb







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