Weird allocation record for 192.114.0.0

Hi Lucas, 

not trying to comment on the address allocation records' changes on 
ripe's ftp website - just want to note 192/8 contains some "early 
registrations".  Authoritative source of information for these records
likely changed in the past.  

 Early Registration Transfer [ERX] Project
 Transfer of Networks in 192/8
  http://www.ripe.net/projects/erx/erx-ip/network-192.html

Also different rules apply to IP range registrations if status attribute 
is set to "EARLY-REGISTRATION" or "ALLOCATED UNSPECIFIED". 

 Early Registration Transfer Project FAQs
  http://www.ripe.net/info/faq/projects/erx.html#23
  http://www.ripe.net/info/faq/projects/erx.html#24
 IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Reg.
  http://www.ripe.net/ripe/docs/ripe-492.html

Martin


On Thu, Jul 15, 2010 at 06:09:03PM -0700, Lucas Wang wrote:
> I was doing some processing on the address allocation records published on ripe's ftp websites:
> ftp://ftp.ripe.net/pub/stats/ripencc
> 
> And I noticed that for some records the db is bizarre.
> 
> For instance, the address block starting from 192.114.0.0 appeared as
> as ripencc|IL|ipv4|192.114.0.0|327680|20010306|assigned
> on allocation files before 03/15/2005.
> Then it disappeared for several years, and popped out on 06/27/2009 as
> ripencc|EU|ipv4|192.114.0.0|327680|19930901|assigned
> Note that the country code and allocation date has been changed.
> It doesn't make sense if the address block was returned because allocation date(19930901)
> on 06/27/2009 was even before the previous record(20010306).
> 
> And on 07/31/2009, it shrunk into a smaller block:
> ripencc|EU|ipv4|192.114.0.0|21504|19930901|assigned
> Does this mean part of it was returned?
> 
> Any answer regarding how the allocation files are produced or
> whether the cases mentioned above are errors are greatly appreciated.
> Thanks in advance,
> 
> Lucas
>   
> 
> 
> 
> Lucas(Jiangzhe) Wang
> 
> 
> 
> 
>