nanog mailing list archives

Re: RFC 1918 network range choices


From: valdis.kletnieks () vt edu
Date: Thu, 05 Oct 2017 15:04:42 -0400

On Thu, 05 Oct 2017 13:39:04 -0400, Jay Ashworth said:

I have seen a number of versions of that in reading things people sent me and
things I found myself, and all of them seem to depend on ASICs that didn't
exist at the time the ranges were chosen, and probably also CIDR which also
didn't exist. They sound good, but I'm not buying em. :-)

Can't speak t the ASICs, but CIDR existed, even if your vendor was behind the
times and still calling stuff class A/B/C. (Such nonsense persisted well into
this century). Check the dates...

1918 Address Allocation for Private Internets. Y. Rekhter, B. Moskowitz,
     D. Karrenberg, G. J. de Groot, E. Lear. February 1996. (Format:
     TXT=22270 bytes) (Obsoletes RFC1627, RFC1597) (Updated by RFC6761)
     (Also BCP0005) (Status: BEST CURRENT PRACTICE) (DOI:
     10.17487/RFC1918)

1517 Applicability Statement for the Implementation of Classless
     Inter-Domain Routing (CIDR). Internet Engineering Steering Group, R.
     Hinden. September 1993. (Format: TXT=7357 bytes) (Status: HISTORIC)
     (DOI: 10.17487/RFC1517)

1518 An Architecture for IP Address Allocation with CIDR. Y. Rekhter, T.
     Li. September 1993. (Format: TXT=72609 bytes) (Status: HISTORIC)
     (DOI: 10.17487/RFC1518)

1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and
     Aggregation Strategy. V. Fuller, T. Li, J. Yu, K. Varadhan.
     September 1993. (Format: TXT=59998 bytes) (Obsoletes RFC1338)
     (Obsoleted by RFC4632) (Status: PROPOSED STANDARD) (DOI:
     10.17487/RFC1519)

1520 Exchanging Routing Information Across Provider Boundaries in the
     CIDR Environment. Y. Rekhter, C. Topolcic. September 1993. (Format:
     TXT=20389 bytes) (Status: HISTORIC) (DOI: 10.17487/RFC1520)


Attachment: _bin
Description:


Current thread: