On Sep 29, 2010, at 5:07 PM, Richard Cox wrote:
Peter Koch <pk@DENIC.DE> asked:
are you suggesting that the "mnt-by:" attribute should be made mandatory for person: objects?
No. I am suggesting that where an LIR represents to RIPE NCC that their customer is the party named on a request form, and that party meets the hardware etc requirement for allocation of RIPE resources, then the name of the LIR that made the representation should be included in the WHOIS output (for INETNUM and ASN objects). This would hopefully deter (the very small number of) LIRs that currently seem to be submitting resource requests that ultimately turn out to have been somewhat exaggerated.
Can you expand on this? It sounds like you are referring to provider independent assignments to end users. I just looked through the inetnums for assignments made in the 91.192/10 range, which seems to currently be in use for this purpose and didn't see any missing a company name. It might be that I am not familiar with all the relevant company naming formats used in the RIPE NCC's service region but the inetnum objects were full of LLC, Joint Stock Company, BV, Sarl etc… Based on my limited analysis I don't understand the complaint. On the other hand, you might be referring to assignments that LIRs make to customers using space from their own allocations: ASSIGNED PA space. I downloaded the file containing all the inetnum objects (sans personally identifying contact information) from the RIPE NCC's FTP site and I found just over 3m inetnum objects in total and just under 3m PA assignments made by LIRs. I think the number of objects in that pool is sufficiently large that it is not practical to police the level of detail used in assignments made to customers when the LIR's contact information is published on the RIPE NCC's web site anyway. Regards, Leo