Dear all, As already mentioned, the RIPE NCC Executive Board proposes the charging scheme and the membership votes on whether to approve it or not. So while policy and charging are independent of each other, the Board will of course try to propose charging schemes that comply with RIPE Policy while providing the RIPE NCC with the funding it needs in a financially responsible way. The annual charges for PI assignments were introduced in 2010 following approval of the relevant charging scheme at the General Meeting in October 2009. At that GM, the Board made clear that the charges for independent resources were introduced to implement RIPE Policy Proposal 2007-01 (current policy ripe-637 [1]). The Board also noted that the charges for PI assignments were not related to the amount of addresses but to the assignment itself, which could contain a small or larger amount of address space. The Charging Scheme Task Force report in 2012 [2] also recommended to the Board that PI assignments should continue to be charged per assignment rather than be based on the size of the assignment. The RIPE NCC has always charged an assignment for any that is made in a single day. The idea here is not to negatively affect anyone for a decision made by the RIPE NCC or for other factors that might result in them receiving multiple prefixes based on a single request. For example, if somebody asks for a /44 IPv6 PI (equals 16x /48) but only qualifies for 5 /48's - it wouldn't be fair to charge them five times more than for one single block. Similarly, if somebody transfers part of their IPv4 PI, maybe a /24 out of a /22, this will leave them with two prefixes (/23 and /24) and potentially a double charge. Of course, guidance on how we interpret policy is always welcome from the community. It is also worth noting that handling End Users for PI assignments and ASNs is an ongoing workload when it comes to keeping the Registry up to date and also with regards to sanctions. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://www.ripe.net/publications/docs/ripe-637/ [2] https://www.ripe.net/media/documents/Final_Report_of_the_Charging_Scheme_Tas... On 29/08/2024 13:19, Tore Anderson wrote:
Hi Jori,
@Tore: I currently hold 4x/48 PI, and I can confirm, these are charged "per ticket" and not per object.
E.g: If you received 4x/48 PI in a single request from the NCC, you pay the PI fee *once* for those 4x/48PI.
Wow, that's surprising to hear. You learn something every day!
I've already understood the word «assignment» in the charging scheme (e.g., «the separate charge of EUR 50 per independent Internet number resource assignment» from ripe-800) to refer to the actual *num object(s) in the database, not to the one-time action of issuing the assignment(s). To me it doesn't really make much sense to issue a recurring charge for a one-time action like that.
Tore
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/