Re: Policy Statement on Address Space Allocations

Howard Berkowitz <hcb@clark.net> Fri, 02 February 1996 15:49 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id ab11664; 2 Feb 96 10:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab11660; 2 Feb 96 10:49 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa08435; 2 Feb 96 10:49 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11652; 2 Feb 96 10:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11648; 2 Feb 96 10:49 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa08427; 2 Feb 96 10:49 EST
Received: from mail.clark.net by venera.isi.edu (5.65c/5.61+local-22) id <AA25632>; Fri, 2 Feb 1996 07:49:22 -0800
Received: from clark.net (hcb@clark.net [168.143.0.7]) by mail.Clark.Net (8.7.3/8.6.5) with ESMTP id KAA26997; Fri, 2 Feb 1996 10:48:23 -0500 (EST)
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Howard Berkowitz <hcb@clark.net>
Received: (from hcb@localhost) by clark.net (8.7.1/8.7.1) id KAA09058; Fri, 2 Feb 1996 10:48:19 -0500 (EST)
Message-Id: <199602021548.KAA09058@clark.net>
Subject: Re: Policy Statement on Address Space Allocations
To: Jon Zeeff <jon@branch.com>
Date: Fri, 02 Feb 1996 10:48:18 -0500
Cc: bmanning@isi.edu, jon@branch.com, 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: <m0ti99m-000NiyC@aero.branch.com> from "Jon Zeeff" at Feb 1, 96 07:15:13 pm
X-Mailer: ELM [version 2.4 PL24alpha3]
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

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

This is not a trivial question, because I am aware, at least, of an
assortment of military networks who have registered addresses, connect with
other arbitrary military networks with their own registered addresses,
and really need some assurance that these internetworks will have unique
addresses.  Internetworks != Internet,  so valid assignments may not be
Internet reachable.