Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!verber
From: verber@pacific.mps.ohio-state.edu (Mark Verber)
Newsgroups: comp.admin.policy
Subject: Re: IP Number management
Message-ID: <VERBER.91May22113348@revere.mps.ohio-state.edu>
Date: 22 May 91 15:33:48 GMT
References: <1991May21.203820.11396@ariel.unm.edu>
Sender: news@pacific.mps.ohio-state.edu
Organization: Ohio State University; Physics Department
Lines: 28
In-reply-to: pkrause@triton.unm.edu's message of 21 May 91 20:38:20 GMT

In article <1991May21.203820.11396@ariel.unm.edu> pkrause@triton.unm.edu (Paul Krause CIRT) writes:

   Perhaps this is a good group for a discussion of IP number management.  I
   posted to comp.protocols.tcp-ip without much response.  

I am sure that IETF has a working group that is looking at this.  I don't
recall which group it might be.. but I assume UNM has someone who has been
involve with IETF and can help you out.

   We have several thousand numbers out there and while we have a database of
   who is assigned each number, it is static.  With the way people 
   move around, hard drives get trashed, employees are hired or replaced, etc.
   the data gets stale real fast. 

Well... this is one of the reasons for subnets and delegated
authority.  Except in very rare situations there should be no need for
a central database with 1000s of IP addresses.  In the university
environment let departments colleges, or whatever division of labor
makes sense in your environment to take responcibility for pieces
of your address space.

Having people move around is a good reason *not* to bind IP addresses
to people.  It would be routing hell.  I don't see why hard drives
getting trashed should change IP number.


Mark Verber
Ohio State Physics Dept / Computing Services