-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Sander, Sander Steffann wrote:
Hi,
The whois already says they are reclaiming the /14 - but I think it'd have been better to improve their vetting procedures to ensure that such allocations never did take place.
They do scrutinize paperwork for IP justification, hardware etc so it would be interesting to see what justification needs to be done to get a /14, and what is done to verify the accuracy of said paperwork.
To quote from Andrea Cima, who said the following at the last RIPE meeting (taken from stenography report at http://ripe61.ripe.net/archives/steno/13/):
"Now, with regards to transparency, what our intention is, is to publish all the RIPE NCC Registration Services procedures on?line, and in this way, it will be very clear to everyone that is requesting some resources, what is expected from them, what kind of information, we will ask or we may ask and what kind of documentation we will need. We will do this per type of ? request, per type of service and, of course, we will start with IPv4 address space resources because of the run?out situation. So this will be up on?line pretty soon from now. "
So the procedure documentation you ask for should be available soon.
Andrea: can you provide further information here?
We are currently working on the IPv4 allocation and assignment procedure and expect it to be finalised and published in March. If the IPv4 allocation and assignment procedure is considered useful by the RIPE NCC membership, we will then publish procedure documents for IPv6 and AS Numbers. Best regards, Andrea Cima RIPE NCC
Thanks, Sander
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1VMswACgkQXOgsmPkFrjPCHACg01H/3RVkKcH+eZC+JslS6C5N 1i4AoJMm93myDaZ40F1/+diMQawueQ5j =xzVc -----END PGP SIGNATURE-----