[95924] in North American Network Operators' Group
Re: New RIPE NCC IPv4 blocks pingable addresses
daemon@ATHENA.MIT.EDU (Steven M. Bellovin)
Tue Apr 10 11:36:23 2007
Date: Tue, 10 Apr 2007 11:35:27 -0400
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: Alex Le Heux <alexlh@ripe.net>
Cc: Address Policy WG <address-policy-wg@ripe.net>,
Routing WG <routing-wg@ripe.net>, NANOG <nanog@merit.edu>,
AfNOG List <afnog@afnog.org>, SANOG List <sanog@sanog.org>,
Inet Ops List <inet-ops@puck.nether.net>,
PacNOG List <pacnog@pacnog.org>, UKNOF List <uknof@uknof.org.uk>
In-Reply-To: <F5083440-437F-4D14-9DA6-1D72C28AE58A@ripe.net>
Errors-To: owner-nanog@merit.edu
On Tue, 10 Apr 2007 11:56:57 +0200
Alex Le Heux <alexlh@ripe.net> wrote:
>
> [Apologies for duplicate emails]
>
> Dear Colleages,
>
> The IANA recently allocated the IPv4 address ranges 92/8 and 93/8 to
> the RIPE NCC.
>
> The following pingable addresses are now available in these blocks:
>
> 92.192.0.1
> 92.255.248.1
> 93.192.0.1
> 93.255.248.1
I was relieved to read the body of this note -- from the subject line,
I thought that RIPE was blocking pings to certain addresses...
--Steve Bellovin, http://www.cs.columbia.edu/~smb
