Re: Policy Statement on Address Space Allocations

Hank Nussbacher <HANK@taunivm.tau.ac.il> Sun, 04 February 1996 06:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05713; 4 Feb 96 1:08 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05709; 4 Feb 96 1:08 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa01503; 4 Feb 96 1:08 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05702; 4 Feb 96 1:08 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05698; 4 Feb 96 1:08 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa01498; 4 Feb 96 1:08 EST
Received: from VM.TAU.AC.IL (taunivm.tau.ac.il) by venera.isi.edu (5.65c/5.61+local-22) id <AA09806>; Sat, 3 Feb 1996 22:08:14 -0800
Message-Id: <199602040608.AA09806@venera.isi.edu>
Received: from VM.TAU.AC.IL by VM.TAU.AC.IL (IBM VM SMTP V2R2) with BSMTP id 7984; Sun, 04 Feb 96 08:08:38 IST
Received: from VM.TAU.AC.IL (NJE origin HANK@TAUNIVM) by VM.TAU.AC.IL (LMail V1.2a/1.8a) with BSMTP id 5707; Sun, 4 Feb 1996 08:08:39 +0200
Date: Sun, 04 Feb 1996 08:06:49 -0000
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Hank Nussbacher <HANK@taunivm.tau.ac.il>
Subject: Re: Policy Statement on Address Space Allocations
To: David Miller <david@dirigo.mint.net>, Howard Berkowitz <hcb@clark.net>
Cc: Jon Zeeff <jon@branch.com>, bmanning@isi.edu, curtis@ans.net, jnc@ginger.lcs.mit.edu, G.Huston@aarnet.edu.au, asp@uunet.uu.net, cidrd@iepg.org, iesg@isi.edu, local-ir@ripe.net, nanog@merit.edu
In-Reply-To: Message of Fri, 2 Feb 1996 14:29:09 -0500 (EST) from <david@dirigo.mint.net>
Mime-Version: 1.0
Content-Type: Text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

On Fri, 2 Feb 1996 14:29:09 -0500 (EST) you said:
>On Fri, 2 Feb 1996, Howard Berkowitz wrote:
>
>> > > 	We are working on the 192.x.x.x swamp right now.
>> > > 	Rough estimates (with much more accurate data @ NANOG)
>> > >
>> > > 		60% - invalid or missing contact information
>> >
>> > This is interesting.  How about a policy that says if nobody can contact
>you
>> > and none of your addresses are reachable, then after some period, your
>> > addresses get recycled.
>> >
>> >
>> By addresses not being reachable, are you effectively saying that any
>> enterprise that does not want to connect to the Internet must use
>> RFC1597 address space?
>>
>> Anyone have an idea how much of the address space is used for
>> registered addresses of organizations that do not connect to the Internet?
>
>I would also be curious how the 60% missing is counted.
>
>If an organization places 99% of their addresses behind a firewall do all
>those not count?

If you have a class B and use a firewall, then a /27 should be more
than is needed on the global Internet and they should use an address
from RFC1597 internally and return the /16.

>
>Unfortunately, I don't think we can base much policy on whether or what %
>of addresses are reachable from the internet.
>
>--- David Miller
>----------------------------------------------------------------------------
>		It's *amazing* what one can accomplish when
>		    one doesn't know what one can't do!
>

Hank