[ncc-services-wg] legacy holders paying for registration services and 2012-07v2
- Previous message (by thread): [ncc-services-wg] legacy holders paying for registration services and 2012-07v2
- Next message (by thread): [ncc-services-wg] legacy holders paying for registration services and 2012-07v2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Sat Feb 23 02:13:12 CET 2013
>> - 393 inetnum objects have RIPE-NCC-LOCKED-MNT in the mnt-by line. These >> objects were registered in the RIPE DB before the ERX transfer took place, >> and were maintained using RIPE-NCC-NONE-MNT. When this was deprecated the >> RIPE NCC locked all objects referencing it. As these objects are still >> locked, no one is currently managing this data. possibly because they are correct and do not need change. we have no way of knowing. >> - 851 inetnum objects have the ERX auto-generated maintainer (in the form >> ERX-NET-138-81-MNT) as mnt-by. The holders 'may' have been given the >> password and are 'able' to manage this data, but may or may not have done >> so. Others were not given the password and are not managing the data. >> Without deeper analysis we can't separate these groups. again, the owners may be quite happy with the data as they are. > Interesting. So at the moment, it looks like between 30%-40% (i.e. from > (393+851)/4050 to (339+393+851)/4050) of the ERX address space is arguably > abandoned from a measurement point of view 'arguably' may be the most important word in that sentence unfortunately we have never come up with a method to classify space rigorously. hard problem. and i am not optimistic. look at the recent noise about the uk gov /8 that looked unmaintained. randy
- Previous message (by thread): [ncc-services-wg] legacy holders paying for registration services and 2012-07v2
- Next message (by thread): [ncc-services-wg] legacy holders paying for registration services and 2012-07v2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]