[179559] in North American Network Operators' Group
Re: 192.0.1.0/24?
daemon@ATHENA.MIT.EDU (Doug Barton)
Fri Apr 17 19:52:32 2015
X-Original-To: nanog@nanog.org
Date: Fri, 17 Apr 2015 16:52:28 -0700
From: Doug Barton <dougb@dougbarton.us>
To: Harley H <bobb.harley@gmail.com>
In-Reply-To: <CAGRHET_6i_J+Hc4fWHRhTJOu=5g9nD=B0Wf1fTgKOZv470rg2Q@mail.gmail.com>
Cc: leo.vegoda@icann.org, NANOG list <nanog@nanog.org>,
"Michelle S. Cotton" <michelle.cotton@icann.org>
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bMg1ibxBOVRcreLN6wbJh44cP1fRC0NOe
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Harley is correct that 192.0.1/24 is mentioned in 1166, but AFAICS after =
cursory examination it has fallen through the cracks since then. (Note,=20
this is not the same as 192.0.2/24, which has been updated in several=20
RFCs recently, including 6303 by Mark Andrews (cc'ed for his information)=
=2E
I've also cc'ed Leo and Michelle from ICANN so that hopefully they can=20
see about getting some whois info set up for that network. Michelle, let =
me know if it would be easier for you if I opened a ticket for this=20
request.
Doug
On 4/17/15 1:26 PM, Harley H wrote:
> It is mentioned in RFC 1166 as "BBN-TEST-C". I suppose it's still not
> publicly allocated.
>
>> On Fri, Apr 17, 2015 at 4:14 PM, Harley H <bobb.harley@gmail.com> wrot=
e:
>>
>>> Does anyone know the status of this netblock? I've come across a malw=
are
>>> sample configured to callback to an IP in that range but it does not
>>> appear
>>> to be routable. Yet, it is not mentioned in RFC 5735 nor does it have=
any
>>> whois information.
>>>
>>> Thanks,
>>> Harley
--=20
I am conducting an experiment in the efficacy of PGP/MIME signatures.=20
This message should be signed. If it is not, or the signature does not=20
validate, please let me know how you received this message (direct, or=20
to a list) and the mail software you use. Thanks!
--bMg1ibxBOVRcreLN6wbJh44cP1fRC0NOe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVMZy8AAoJEFzGhvEaGryEH14IAMuS15xqkQgKpC1yL/PaxQgi
GjAiX8sY9vWMt3dG3oR4Zds9jWT49GAi8glf5cO875r7Xuj679KQIQglP1eCIWEW
jgRaZjyuN9v0imAguXstxP0WBlU/M+Mdo6aIeMMctCxWSPBmQ/aWNLjpPtYspZ+n
JAEQF/9E3ndi9y8Y0uAAO0oJ0yUJajvG/F375A8yEKTVt89Dfx/G4Nymja85uMMg
fRAeLrvILL13KQ5KfxH6EmoFkERStjTgxsT9kOXnNj9KIk+yFg9Y9qnd8sNr33VH
Ut/4gOYD+QeBmAM9xX19lXVOY3oY2OiFO0nfIYnRqQk2yDuDtK6FYAZo591lpKk=
=a0P5
-----END PGP SIGNATURE-----
--bMg1ibxBOVRcreLN6wbJh44cP1fRC0NOe--
