Dear Alexander, On 7/10/12 10:46 AM, Alexander Gall wrote:
On Mon, 09 Jul 2012 15:24:31 +0200, Andrea Cima <andrea@ripe.net> said:
Dear colleagues, The RIPE Document ripe-555, "Address Space Managed by the RIPE NCC", has been published. The document is available at: https://www.ripe.net/ripe/docs/ripe-555/ This RIPE Document updates ripe-510 and now points to the extended delegated statistics containing the full list of resources that the RIPE NCC manages. The document also reflects the fact that the RIPE NCC needs to be able to issue blocks of any size from any /8, so the document was updated accordingly. Am I the only one who is confused by this document? I don't care much about IPv4, but this scares me:
The smallest prefix assigned by the RIPE NCC from any IPv6 range is a /48.
A /48 is the minimum assignment size for IPv6 PI and IXP assignments. Please see: http://www.ripe.net/ripe/docs/ripe-552#IPv6_PI_Assignments http://www.ripe.net/ripe/docs/ripe-451
At the same time, this text from RIPE-510, Section 4 has been removed
Network operators taking routing decisions based on prefix length are requested and encouraged to route at least blocks of sizes corresponding to the longest prefix and larger.
If this means what I naively think it does, I'd have missed the entire discussion about what I would perceive as a fundamental change in policy.
RIPE 555 is not a RIPE Policy document but a RIPE NCC organisational document. The scope of this document is to list the address space managed by the RIPE NCC.
So, I guess I'm just thoroughly confused. Can somebody help me understand what exactly RIPE-555 means?
I apologise if I have not been clear about the changes. I will try to clarify further. RIPE 510 listed only the /8s allocated to the RIPE NCC by IANA. With RIPE 555, our aim is to provide the full and current list of all address space managed by the RIPE NCC, therefore increasing the quality of the data provided. Please also note that not all blocks allocated to the RIPE NCC from IANA in the past are still fully managed by the RIPE NCC. Some IP address space was transferred to AFRINIC, for example. For this reason, we removed the static list and refer to the extended FTP stats, which contain accurate and up-to-date information. This is also the reason why the route sets for these /8s in the RIPE Database (see section 1 of RIPE 510) will be removed. I hope this clarifies. If not, please don't hesitate to contact me. Best regards, Andrea Cima RIPE NCC