North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: NeXT Default Network

  • From: Fred Baker
  • Date: Tue Nov 27 19:27:02 2007
  • Authentication-results: sj-dkim-2; [email protected]; dkim=pass (si g from cisco.com/sjdkim2002 verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3411; t=1196209296; x=1197073296; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; [email protected]; z=From:=20Fred=20Baker=20<[email protected]> |Subject:=20Re=3A=20NeXT=20Default=20Network |Sender:=20; bh=5wCZJx+9o1u00ep/ke+pOTHcuPtlXW/ltxPZLOKHDXM=; b=hU8yePyssALxq5G+dOTBTBFzac8NMtg+Hv3pOqkggJCJfYaVJxexgRi79NY4XwRpnONo8glH frATQBfCJkfHHKrtSgDoHFDDvmAT4yY6Xex+mpJeMYn5Oj/FySpaEmtb;


-----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-----