inetnum conversion

Dear colleagues,

As announced, we have converted all legacy inetnum objects in 
RIPE whois database into classless format, without any problem.
The conversion took place on 26 February, saturday.

We have sent notifications to the maintainers of the converted objects.

Please do not hesitate to contact <ripe-dbm at ripe.net> for any problems
or comments,

Regards,
Engin Gunduz

RIPE NCC Database Group
-----------------------


On Fri, 25 Feb 2000, Engin Gunduz wrote:

> 
> Dear colleagues,
> 
> Since we didn't get any comments/objections about this
> issue, we will be performing inetnum conversions in the
> early hours of 26 February, Saturday.
> 
> Best regards,
> 
> Engin Gunduz
> 
> RIPE NCC Database Group
> -----------------------
> 
> 
> 
> On Thu, 17 Feb 2000, Engin Gunduz wrote:
> 
> > 
> > Dear colleagues,
> > 
> > RIPE NCC will be converting the legacy inetnum objects which are in old classful
> > notation into classless range notation.  We provide the list of inetnum
> > objects to be converted during this process at: 
> > 
> > http://www.ripe.net/ripencc/pub-services/db/in_conversion/
> > 
> > There are 16404 such inetnums in the RIPE whois database, so we have divided
> > them in four parts, but the list is available also as a big single file. The
> > list contains the classful notation, new classless notation and the netname of
> > the inetnums. 
> > 
> > The conversion is planned to take place on 26-27 February.
> > 
> > You can check the list for your inetnum objects. If you detect a problem,
> > please contact <ripe-dbm at ripe.net>.
> > 
> > Also, please send your comments about the conversion to the list,
> > 
> > 
> > Regards,
> > Engin Gunduz
> > 
> > RIPE NCC Database Group
> > -----------------------
> > 
> > 
> > 
> 
>