Re: concerns about CLNP
John Curran <jcurran@nic.near.net> Fri, 23 October 1992 16:16 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa05399; 23 Oct 92 12:16 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa05393; 23 Oct 92 12:16 EDT
Received: from p.lanl.gov by NRI.Reston.VA.US id aa11618; 23 Oct 92 12:17 EDT
Received: from noc-gw.lanl.gov by p.lanl.gov (5.65/1.14) id AA25512; Fri, 23 Oct 92 10:16:01 -0600
Received: by noc-gw.lanl.gov (4.1/SMI-4.1) id AA24071; Fri, 23 Oct 92 10:15:40 MDT
Return-Path: <jcurran@nic.near.net>
Received: from p.lanl.gov by noc-gw.lanl.gov (4.1/SMI-4.1) id AA24067; Fri, 23 Oct 92 10:15:39 MDT
Received: from nic.near.net by p.lanl.gov (5.65/1.14) id AA25486; Fri, 23 Oct 92 10:15:39 -0600
Message-Id: <9210231615.AA25486@p.lanl.gov>
To: kasten@ftp.com
Cc: henryc@oar.net, desjardi@boa.gsfc.nasa.gov, jnc@ginger.lcs.mit.edu, tuba@lanl.gov
Subject: Re: concerns about CLNP
In-Reply-To: Your message of Fri, 23 Oct 92 09:52:21 -0400. <9210231352.AA01602@ftp.com>
Date: Fri, 23 Oct 1992 12:15:23 -0400
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: John Curran <jcurran@nic.near.net>
-------- ] From: Frank Kastenholz <kasten@ftp.com> ] Subject: Re: concerns about CLNP ] Date: Fri, 23 Oct 92 09:52:21 -0400 ] > [From: henry@oar.net] ] > Have there been any copmrehensive analysis done about exactly when we think ] > the IP address space will really be exhausted or routing will collapse upon ] > itself? I've heard lots of people do numbers off the top of their heads -- ] > are these numbers in the neighborhood? ] ] This work has been done, at least as far as address space exhaustion ] is concerned. Frank Solensky started tracking and making these predictions ] over two years ago. He periodically updates and publishes the information. ] You can reach him at solensky@andr.ub.com. Effectively, we are already in address exhaustion, and the consequential increase in routing entries in the routing tables due to class C usage. The recently announced rfc1366 and rfc1367 documents specify multiple C assignments (up to 16) for organizations that would have previously used a class B address. Recent NACR reports from Merit indicate that many blocks of C addresses are now announced. What remains to be seen is how great CIDR's aggregation will be, and how much entropy we'll see when organizations change their network providers. /John
- concerns about CLNP yakov
- concerns about CLNP Craig Partridge
- Re: concerns about CLNP John Curran
- Re: concerns about CLNP Jon Crowcroft
- Re: concerns about CLNP Dennis Perry
- Re: concerns about CLNP Dick desJardins
- concerns about CLNP yakov
- Re: concerns about CLNP Craig Partridge
- concerns about CLNP yakov
- Re: concerns about CLNP Dennis Perry
- Re: concerns about CLNP David Oran
- Re: concerns about CLNP Jon Crowcroft
- re: concerns about CLNP Craig Partridge
- re: concerns about CLNP Craig Partridge
- concerns about CLNP yakov
- re: concerns about CLNP Craig Partridge
- re: concerns about CLNP Craig Partridge
- Re: concerns about CLNP Noel Chiappa
- concerns about CLNP Dave Katz
- Re: concerns about CLNP Noel Chiappa
- Re: concerns about CLNP Jon Crowcroft
- Re: concerns about CLNP Noel Chiappa
- Re: concerns about CLNP Dick desJardins
- Re: concerns about CLNP henryc
- Re: concerns about CLNP henryc
- re: concerns about CLNP Ross Callon
- re: re: concerns about CLNP Ross Callon
- Re: concerns about CLNP Dick desJardins
- Re: concerns about CLNP practic!brunner@uunet.uu.net
- Re: concerns about CLNP Frank Kastenholz
- Re: concerns about CLNP Noel Chiappa
- Re: concerns about CLNP Noel Chiappa
- Re: concerns about CLNP John Curran
- re: concerns about CLNP Noel Chiappa
- Re: concerns about CLNP Dennis Ferguson