[100976] in North American Network Operators' Group
Re: NeXT Default Network
daemon@ATHENA.MIT.EDU (Fred Baker)
Tue Nov 27 19:25:46 2007
In-Reply-To: <Pine.GSO.4.64.0711280026550.22145@mono>
Cc: nanog <nanog@merit.edu>
From: Fred Baker <fred@cisco.com>
Date: Tue, 27 Nov 2007 16:21:32 -0800
To: JAKO Andras <jako.andras@eik.bme.hu>,
"Barry Greene (bgreene)" <bgreene@cisco.com>
Errors-To: owner-nanog@merit.edu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Could someone please tell me what 192.42.172.0/24 is or why it
> should be handled as a special prefix?
>
> ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-
> Templates/T-ip-prefix-filter-ingress-strict-check-v18.txt
You might review the notes I list below, and specifically RFC 3330.
They mention the prefix neither by name or by value...
I would expect that this had something to do with a company called
NeXT and an operating system called NextStep. It sounds like they
came up with a variety of site-local address pre-RFC1918 and pre-
RFC3927 that did something similar to RFC 3927 addresses. This is
mentioned in passing in RFCs 1117 and 1166. The big question is - are
there any NextStep systems still in use (I last used one in 1990),
and whether they have been configured with other addresses (seems
likely, especially in a DHCP world).
http://www.ietf.org/rfc/rfc3330.txt
3330 Special-Use IPv4 Addresses. IANA. September 2002. (Format:
TXT=16200 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc3789.txt
3789 Introduction to the Survey of IPv4 Addresses in Currently
Deployed IETF Standards Track and Experimental Documents. P.
Nesser,
II, A. Bergstrom, Ed.. June 2004. (Format: TXT=22842 bytes)
(Status:
INFORMATIONAL)
http://www.ietf.org/rfc/rfc3790.txt
3790 Survey of IPv4 Addresses in Currently Deployed IETF Internet Area
Standards Track and Experimental Documents. C. Mickles, Ed., P.
Nesser, II. June 2004. (Format: TXT=102694 bytes) (Status:
INFORMATIONAL)
http://www.ietf.org/rfc/rfc3791.txt
3791 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area
Standards Track and Experimental Documents. C. Olvera, P.
Nesser, II.
June 2004. (Format: TXT=27567 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc3792.txt
3792 Survey of IPv4 Addresses in Currently Deployed IETF Security Area
Standards Track and Experimental Documents. P. Nesser, II, A.
Bergstrom, Ed.. June 2004. (Format: TXT=46398 bytes) (Status:
INFORMATIONAL)
http://www.ietf.org/rfc/rfc3793.txt
3793 Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area
Standards Track and Experimental Documents. P. Nesser, II, A.
Bergstrom, Ed.. June 2004. (Format: TXT=11624 bytes) (Status:
INFORMATIONAL)
http://www.ietf.org/rfc/rfc3794.txt
3794 Survey of IPv4 Addresses in Currently Deployed IETF Transport
Area Standards Track and Experimental Documents. P. Nesser, II, A.
Bergstrom, Ed.. June 2004. (Format: TXT=60001 bytes) (Status:
INFORMATIONAL)
http://www.ietf.org/rfc/rfc3795.txt
3795 Survey of IPv4 Addresses in Currently Deployed IETF Application
Area Standards Track and Experimental Documents. R. Sofia, P.
Nesser,
II. June 2004. (Format: TXT=92584 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc3796.txt
3796 Survey of IPv4 Addresses in Currently Deployed IETF Operations &
Management Area Standards Track and Experimental Documents. P.
Nesser, II, A. Bergstrom, Ed.. June 2004. (Format: TXT=78400
bytes)
(Status: INFORMATIONAL)
-----BEGIN PGP SIGNATURE-----
iD8DBQFHTLSMbjEdbHIsm0MRAssIAKDxNy0f4IjveLjyfrxGTkGuslSZ9QCgroID
E53IZ9u0/CnSmbKfWn9j7wI=
=n0CU
-----END PGP SIGNATURE-----