- address-policy-wg - mailman.ripe.net

Decision on 2024-02 (IPv6 Initial Allocations /28 and extension to /28) Discussion Phase
by Leo Vegoda 27 Nov '25

27 Nov '25

Dear Address Policy WG, The proposers have decided to prepare an updated proposal, taking account of the feedback provided during the most recent Discussion Phase. A new Discussion Phase will start when their new proposal is available on the website. We'd like to thank Jordi and Rinse for their work on this proposal, along with everyone who reviewed and commented on the most recent version. Thank you, Alex, Franziska, Leo Your co-chairs

1 0

Re: Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status
by Brander Group 25 Nov '25

25 Nov '25

Hello Clara, We have always appreciate your contributions to the community; they have never gone unnoticed. Thank you for the opportunity to review the draft proposal. After evaluating the rationale presented, we would like to offer several important considerations before this moves forward. 1. The proposal seems to extend beyond a simple clarification of legacy status Framing this as a clarification minimizes the actual substantive change being introduced. The draft attempts to modify how legacy resources are treated within RIPE. This looks like more of a policy change request — rather than a clarification — and should probably be evaluated as such. 2. RIPE service fees already apply when members choose to adopt additional services such as RPKI Opting into RPKI is a voluntary operational decision and already incurs a RIPE service fee. This is not an example of a loophole or unfair circumvention. The current system already aligns incentives without requiring a change to legacy status inheritance. 3. The operational burden described does not appear to represent a systemic or material issue The referenced 0.5 FTE and the stated processing times should be evaluated in context. The minimal legacy transfers annually (which can be clarified as a percentage of total requests by RIPE) does not constitute a large-scale operational problem. Before moving forward with a policy change of this magnitude, it would be prudent to directly audit the RIPE NCC Registration Services teams workload to determine if these transfers materially impede normal levels of service level as compared to previous years. A policy change intended to reduce operational strain should be based on explicit confirmation from the impacted teams that the strain is significant enough to warrant structural change. All the best, Jake Brander President | Brander Group Inc. O: (702) 560-5616 x700 | M: (310) 595-6266 jake(a)brandergroup.net<mailto:jake@brandergroup.net> | www.brandergroup.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brandergroup.net&d=…> Take Advantage of our Free IPAM Software– Learn More<https://urldefense.proofpoint.com/v2/url?u=https-3A__brandergroup.net_brand…> Award Winners for Revenue Growth & Support – Read More<https://urldefense.proofpoint.com/v2/url?u=https-3A__brandergroup.net_press…> Provider Agnostic Solutions with Wholesale Prices – Learn More<https://urldefense.proofpoint.com/v2/url?u=https-3A__brandergroup.net_solut…> From: Mike Burns <mike(a)iptrading.com<mailto:mike@iptrading.com>> Sent: Monday, November 17, 2025 6:56 PM To: 'denis walker' <ripedenis(a)gmail.com<mailto:ripedenis@gmail.com>>; 'Antonis Chariton' <daknob(a)daknob.net<mailto:daknob@daknob.net>> Cc: 'address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>' <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>>; 'peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>' <peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>>; 'Wade, Clara' <clarawad(a)amazon.com<mailto:clarawad@amazon.com>> Subject: RE: [address-policy-wg] Re: Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status Hello, My problem with the upcoming proposal is this inaccurate statement: “This is currently being used as a loophole by certain actors to opt out of having a contractual relationship with the RIPE NCC in order to circumvent: RIPE registration services fees. 1. The 24-month transfer lock that was introduced by this working group to prevent flipping of scarce resources. 2. Needs-based inter-RIR transfer policy utilization requirements in the case of transfers from another RIR to a recipient of a legacy resource transfer in the RIPE region.” Point 2 is plainly incorrect. Please take this as feedback that this should be removed from any policy proposal. The truth is that utilization requirements apply only to inbound transfers from ARIN, and those transfers are treated the same whether legacy status or not. Regards, Mike Burns IPTrading. From: denis walker <ripedenis(a)gmail.com<mailto:ripedenis@gmail.com>> Sent: Thursday, October 30, 2025 4:30 PM To: Antonis Chariton <daknob(a)daknob.net<mailto:daknob@daknob.net>> Cc: address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>; peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>; Wade, Clara <clarawad(a)amazon.com<mailto:clarawad@amazon.com>> Subject: [address-policy-wg] Re: Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status Hi Antonis Maybe I am missing something here. But all I am hearing is: LEGACY-GREED LEGACY-MONEY LEGACY-PROFIT LEGACY-LOW SECURITY LEGACY-ATTRACTIVE TO PEOPLE WHO DON'T WANT TO BE IDENTIFIED Maybe it is time to end any LEGACY special considerations. There is nothing special about LEGACY space. These people were just lucky to be given a huge chunk of address space at a time when people didn't understand the potential or value of addresses. Since then society, technology, internet structures, e-governance have all moved on. We became more organised and structured, Everything has moved on except LEGACY holders. Maybe it is time we had one simple rule. ALL address space usage must be registered and managed in the same way, with an RIR, regardless of how you acquired it. You say this will force LEGACY holders to operate outside of the RIR system. What if all the RIR members blocked all addresses that are not properly registered (with one of the RIRs) and accountable? I have no operator experience so I don't know if it is technically (or politically / financially) possible to shut out ALL un-registered address space. If it is, I think we should do it. Have one last showdown. Join the club or stay out in the cold. I don't want your insecure, unaccountable customers connected to my internet. I am not an operator or routing expert, so I may be talking complete rubbish here. But I think you understand the principle I am suggesting. Maybe someone more knowledgeable can outline if/how we can collectively shut out LEGACY space if they refuse to join the club? There is of course another path that may be forced onto LEGACY holders and the RIRs...legislation. LEAs are getting more involved now in registry activities. While they have one foot in our camp, maybe their other foot is in the legislators camp. Especially the European Commision (EC). Operators no longer have full control over operations. Some of the LEGACY space is trying to operate outside of 'the system'. In an area where they are less accountable and they may attract 'undesirable' customers who are not easy to identify or locate. I suspect the timespan for the RIPE community to sort this out is shrinking. Look at some of the legislation that has come from the EC in recent years. Things like the e-evidence act. They have adopted ways of spreading the impact of their legislation beyond the borders of the EU. Another thought came to mind. I have never seen one of these agreements under which LEGACY holders were 'given' this address space. Do these agreements say that the terms and conditions are transferable? Can someone who 'buys' LEGACY space legitimately claim to 'own' it under the same conditions as the previous owner? Just a few thoughts... cheers denis On Thu, 30 Oct 2025 at 17:53, Antonis Chariton via address-policy-wg <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>> wrote: Thanks for the quick response Clara! Perhaps my feedback was not too clear, no worries :) — Existing resource holders will indeed keep their status, but I see a couple of things here: 1) When / if you transfer IPv4 you’ll be faced with a decision (and I guess most people will choose the status over RPKI) 2) When / if the charging scheme changes and doesn’t take the status into account (e.g. legacy counts towards the tier / membership fee) people will cancel the RIPE NCC legacy agreement (and just lose IRR / RPKI) The only reason I brought up #2 here, despite it not being related to your policy proposal, is that since both are public documents enough entities may connect the dots and realize that their legacy status is far more valuable than before. I’d argue that this current proposal increases the value of legacy, especially when combined with a new charging scheme. I hope that’s clearer now. Finally, in my experience at least, money is always a good reason to follow anti-patterns :( It’s true that there’s increased risk from IPv4 legacy but I’d argue that for most entities that will be affected this risk is lower than the costs that are or will be associated with it. Legacy cannot (easily?) be touched today by RIRs (we can only make the holders’ life more difficult) while PA is far more “vulnerable” to new policies and changes. PA also carries some risk at the end of the day and comes without any warranty. Antonis On 30 Oct 2025, at 17:38, Wade, Clara via address-policy-wg <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>> wrote: Antonis, Thanks for taking the time to provide feedback. It seems there’s a misunderstanding here. This policy proposal is forward-looking. We are not going to attempt to backfill/retrofit this change as we are trying to reduce overhead for the NCC, not generate more. We are simply trying to close a loophole that keeps getting exploited. As I mentioned in my response to Dominik, changing the holdership without going through due process is an anti-pattern and it also goes explicitly against the RIPE NCC process for legacy resource transfers outlined here: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/tra…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ripe.net_manage-2D…> As I said before, hopefully, anyone engaging in these practices understands the risks they are assuming (for them and their customers if they are a service provider) by doing so. I would hope the community strives to build reliable networks rather than go against database accuracy and routing security best practices to avoid paying very reasonable registration service fees to safekeep important resources (especially in the case of most organizations where they do not pose a material cost). Thank you, Clara From: Antonis Chariton <daknob(a)daknob.net<mailto:daknob@daknob.net>> Date: Thursday, October 30, 2025 at 11:06 AM To: "address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>" <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>> Cc: "Wade, Clara" <clarawad(a)amazon.com<mailto:clarawad@amazon.com>>, "peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>" <peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>>, Max Emig <ripe(a)emigm.ax<mailto:ripe@emigm.ax>> Subject: RE: [EXTERNAL] [address-policy-wg] Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hello everyone, Although I’m not an expert in this area I’d also like to voice my agreement with Max’ point. Due to the nature of legacy IPv4 and ASes there’s no requirement for registration or notification of an RIR as far as I understand. That said, any sale can be conducted with a single contract between two parties and nobody is required to know about it. As far as I see it, these holders will face the following dilemma: RIPE IRR + RPKI or lower membership fees and retaining this status / flexibility. I think for most organizations the choice will be clear and they’ll choose the second, with the database slowly drifting away from the truth and fewer spaces being covered by ROAs. If someone has or buys an IPv4 /16 they’ll probably choose to opt-out of higher membership fees and will be fine losing a ROA or using RADB / ALTDB. This will also affect IXPs and other heavy users of IRR as more members / customers will require something in addition to RIPE’s database. If more and more entities start requesting the use of non-RIR sources of route objects this will undo progress for routing security. Finally, I expect that such policy can affect any votes for the proposed charging scheme that you’ve been working hard for all this time. Legacy blocks are usually larger and they will increase the cost / tier of someone significantly, making them naturally opposed to this change even if they believe it’s the right direction. Based on what Randy suggested and Marco’s information about the resources we spend I think keeping everything the same between LIRs and adding a transfer fee paid once as Capex / acquisition cost when e.g. the recipient is not an LIR would probably work better. If a fee cannot be applied, I’d also explore the possibility of only allowing inter-LIR transfers which means that either or both parties would have to create an LIR and the setup fee would more than cover the cost of the transaction, even if it’s only kept for a year and we get 1'000+1'800 = 2'800 EUR. That’s probably less than 1 EUR / address, reusable within the calendar year, and could cover the 0.5 FTE. I understand that a legacy-free world would simplify things for everyone, especially RIPE, and it sounds more fair, but we need to model the impact of every policy like this one realistically. Are we certain that RPKI is that good and worth the large cost we plan to impose? Are we causing harmful side effects by re-increasing the reliance and dependency on data sources we know are not meeting the same quality criteria? My personal belief is that this RIR is investing a lot more than 0.5 / 1 FTE for the benefit of the Internet so even if we treat this as a public service it may still be worth it. As an LIR and IXP member and operator I’d get more value than the cost of leaving everything as is completely. It centralizes some costs to RIPE instead of externalizing them, but economies of scale work here. Do you have any predictions as to which % of transfers or addresses will opt-in to this policy instead of just doing everything outside the RIR world? My expectation is that most transfers will opt-out at no cost to them and probably > 1 FTE worth of cost across all LIRs or IXPs / providers outside our service region. Antonis On 30 Oct 2025, at 16:17, Max Emig via address-policy-wg <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>> wrote: Hi Clara, a large Tier 1 carrier in the ARIN region did not update the ARIN Whois in 20 years and did not offer RPKI ROA until very recently over legal concerns and maintained their own whois along with the non-authoritative RADB. I would like to avoid any situations where organisations would have to choose between RIPE DB accuracy and routing security using RPKI ROA and legal-risks regarding out-of-region use among other concerns. Thanks Max On 30 October, 2025 15:29 CET, "Wade, Clara" <clarawad(a)amazon.com<mailto:clarawad@amazon.com>> wrote: Hi Max, I’m a little confused by the counter-argument here. Could you clarify how you believe this proposal would this lead to out-of-date data and less RPKI adoption? 1. Keeping legacy status when the resources are no longer held by the organization that received these pre-RIR administration is not really keeping the database accurate/up-to-date. 2. Legacy resource holders by default do not have access to RPKI. (You may get access by signing an agreement with the NCC, but unless you do, RPKI services are not included in the basic package offered to legacy resource holders who are not members.) Thank you, Clara From: Max Emig <ripe(a)emigm.ax<mailto:ripe@emigm.ax>> Date: Wednesday, October 29, 2025 at 4:54 PM To: "Wade, Clara" <clarawad(a)amazon.com<mailto:clarawad@amazon.com>> Cc: "address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>" <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>>, "peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>" <peter.hessler(a)zayo.com<mailto:peter.hessler@zayo.com>> Subject: RE: [EXTERNAL] [address-policy-wg] Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Good evening all, I oppose this policy proposal as it may lead to an increase on out-of-date data and less RPKI adoption. However, I would support adding a fee or another disincentive for keeping legacy status. Thanks Max On 27 October, 2025 17:12 CET, "Wade, Clara via address-policy-wg" <address-policy-wg(a)ripe.net<mailto:address-policy-wg@ripe.net>> wrote: Hello everyone, Following the suggestion of the RIPE NCC, we are seeking early feedback on an upcoming policy proposal we currently have in draft status. As mentioned last week after the Registration Services update from Marco at the AP-WG session - Peter Hessler and I, members of the now concluded Charging Scheme Task Force, are drafting a policy proposal to clarify the non-transferability of legacy status to address the issues of increasing overhead for the RIPE NCC, increasing market speculation around a scarce resource and its impact on the adoption of best practices like RPKI. Our proposal will modify these existing policies: 1. “RIPE Resource Transfer Policies” (RIPE-807) with additional clarifications in the Transfer Restrictions section and the Inter-RIR policy section. M&A/org restructuring transfers will be explicitly excluded. 2. “RIPE NCC Services to Legacy Internet Resource Holders” (RIPE-639) with modifications to remove the language implying new holders can keep legacy status after transfer. For background, legacy status was meant to indicate when an Internet resource had been directly assigned to the holder by IANA, before the RIRs were established. As such, ARIN, LACNIC and AFRINIC policies dictate that IPv4 legacy resources will no longer be regarded as legacy resources after a policy transfer takes place (excluding M&A transfers). RIPE is the only RIR that currently allows the recipient of a legacy transfer the ability to inherit the legacy status that was assigned to the original holder by IANA. This is currently being used as a loophole by certain actors to opt out of having a contractual relationship with the RIPE NCC in order to circumvent: 1. RIPE registration services fees. 2. The 24-month transfer lock that was introduced by this working group to prevent flipping of scarce resources. 3. Needs-based inter-RIR transfer policy utilization requirements in the case of transfers from another RIR to a recipient of a legacy resource transfer in the RIPE region. Following the publication of the Report of the RIPE NCC Charging Scheme Task Force, the membership learned that the RIPE NCC currently needs to dedicate a 0.5FTE to process legacy transfers. There are currently around 2,400 legacy resources held by 1,600 holders with no contractual relationship with the RIPE NCC (neither direct nor via a sponsor). That is around 40M IPs total or 5% of RIPE IPv4 space. In the last four years, NCC staff have processed between 370-280 legacy transfers per year, of which roughly a third do not involve a party with a contractual relationship with the NCC. Legacy transfers are more labor-intensive than other transfer types because the due diligence process requires the Registration Services team to manually source and verify pertaining documentation without the benefits of the automated processes for standard allocations. Legacy transfers take an average seven working hours to process when neither party has a contractual relationship with the NCC (around a third of legacy transfers), and six working hours to process when the parties have a contractual relationship with the NCC. If resources lost their legacy status after a transfer, these would then become standard allocations and staff could leverage enhanced compliance checks and automated processes to facilitate any future updates/transfers. These just take 1-3 working hours to process instead. Given that the task force was deemed out of scope for a policy change to address this gap, this is being brought to the attention of the Address Policy Working Group for action. If there are any concerns, questions or considerations you would like to bring up before we submit this proposal for discussion in the next week or two, we would really appreciate hearing from you so we can address these and/or incorporate them. Thanks in advance, Clara Wade ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.ripe.net_mailm…> 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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ripe.net_membershi…> ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.ripe.net_mailm…> 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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ripe.net_membershi…> ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.ripe.net_mailm…> 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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ripe.net_membershi…>

1 0

Decision on 2025-01 (ASN assignment criteria revisited) Discussion Phase
by Leo Vegoda 24 Nov '25

24 Nov '25

Dear Address Policy WG, Urban and Tobias have confirmed that they are working on an updated version of their proposal. When that is ready we will start a new discussion phase. We'd like to thank them for their work and everyone who commented on their proposal. Kind regards, Alex, Franziska, Leo Your co-chairs

1 0

Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status
by Vincentas Grinius 19 Nov '25

19 Nov '25

Hi all, I want to address the underlying logic behind this proposal, because several arguments being used to justify a policy change actually demonstrate something else. The data about processing times and the 0.5 FTE burden are symptoms of a process that has not been modernized. They are no evidence that the policy itself is flawed. We have seen this dynamic before. The workflow for legacy transfers still resembles something from the 1990s, where everything relied on manual checks, email loops, and individual hostmasters. The operational Internet has long since evolved into an automated environment. Yet here we are trying to solve process gaps with policy restrictions instead of technology. That approach does not move the community forward. Marco confirmed that manual provenance checks and fragmented historical documentation create an additional workload. This is precisely the type of work that disappears once resources are onboarded into standardized and automated processes. Gaps in onboarding and documentation primarily drive the lengthy processing time for legacy cases. Once a resource is fully onboarded, it behaves exactly like any other allocation. This shows clearly that the bottleneck is procedural, not policy-based. It is worth recognizing that RIPE NCC has already taken meaningful steps in the right direction. The new fully automated process for ending PI sponsorship shows that automation can reduce workload while improving accuracy. This is exactly the mindset we should encourage, and it would be great to see the same approach applied to legacy onboarding and transfers. Multiple people in this thread have raised legitimate concerns that this proposal would effectively push transfers off the registry altogether. If that happens, we lose accuracy in the RIPE Database, we lose RPKI coverage, and we increase reliance on non-authoritative IRRs. That is real harm to routing security. Trying to close loopholes by tightening restrictions may feel tidy, but it ignores predictable side effects. Regarding John Curran’s comment about ARIN providing basic services to legacy holders, I do not think ARIN’s model should be held up as a success story. ARIN’s strict transfer and needs-based environment has created prolonged processing timelines, significant procedural friction, and one of the most burdensome governance models in the RIR system. I do not think that is something the industry should replicate or admire, and I hope RIPE does not follow that path. If the goal here is to reduce NCC workload, then the answer is obvious. It is automation, not new restrictions, not rebranding resources, and not creating incentives for people to avoid the registry altogether. Modernizing the legacy transfer workflow with the same automated checks used for standard resources would eliminate most of the processing burden without compromising transparency or routing security. Before moving this proposal forward, I strongly recommend that the working group step back and evaluate what a fully automated legacy onboarding and transfer model looks like, and how it can preserve accuracy without pushing operators into the shadows. Policy should not replace engineering. Policy should enable it. One final point, Clara. You mentioned that legacy status is being used as a loophole to increase market speculation. Can you provide concrete evidence for this statement? Before the community proceeds, we need to see the specific data or cases that clearly show legacy space being used as a speculative instrument. Best regards, Vincentas Grinius IPXO

1 0

Re: Early Feedback on Legacy Status Transfer Proposal
by Vincentas Grinius 19 Nov '25

19 Nov '25

Hi all, I want to address the underlying logic behind this proposal, because several arguments being used to justify a policy change actually demonstrate something else. The data about processing times and the 0.5 FTE burden are symptoms of a process that has not been modernized. They are no evidence that the policy itself is flawed. We have seen this dynamic before. The workflow for legacy transfers still resembles something from the 1990s, where everything relied on manual checks, email loops, and individual hostmasters. The operational Internet has long since evolved into an automated environment. Yet here we are trying to solve process gaps with policy restrictions instead of technology. That approach does not move the community forward. Marco confirmed that manual provenance checks and fragmented historical documentation create an additional workload. This is precisely the type of work that disappears once resources are onboarded into standardized and automated processes. Gaps in onboarding and documentation primarily drive the lengthy processing time for legacy cases. Once a resource is fully onboarded, it behaves exactly like any other allocation. This shows clearly that the bottleneck is procedural, not policy-based. It is worth recognizing that RIPE NCC has already taken meaningful steps in the right direction. The new fully automated process for ending PI sponsorship shows that automation can reduce workload while improving accuracy. This is exactly the mindset we should encourage, and it would be great to see the same approach applied to legacy onboarding and transfers. Multiple people in this thread have raised legitimate concerns that this proposal would effectively push transfers off the registry altogether. If that happens, we lose accuracy in the RIPE Database, we lose RPKI coverage, and we increase reliance on non-authoritative IRRs. That is real harm to routing security. Trying to close loopholes by tightening restrictions may feel tidy, but it ignores predictable side effects. Regarding John Curran’s comment about ARIN providing basic services to legacy holders, I do not think ARIN’s model should be held up as a success story. ARIN’s strict transfer and needs-based environment has created prolonged processing timelines, significant procedural friction, and one of the most burdensome governance models in the RIR system. I do not think that is something the industry should replicate or admire, and I hope RIPE does not follow that path. If the goal here is to reduce NCC workload, then the answer is obvious. It is automation, not new restrictions, not rebranding resources, and not creating incentives for people to avoid the registry altogether. Modernizing the legacy transfer workflow with the same automated checks used for standard resources would eliminate most of the processing burden without compromising transparency or routing security. Before moving this proposal forward, I strongly recommend that the working group step back and evaluate what a fully automated legacy onboarding and transfer model looks like, and how it can preserve accuracy without pushing operators into the shadows. Policy should not replace engineering. Policy should enable it. One final point, Clara. You mentioned that legacy status is being used as a loophole to increase market speculation. Can you provide concrete evidence for this statement? Before the community proceeds, we need to see the specific data or cases that clearly show legacy space being used as a speculative instrument. Best regards, Vincentas Grinius IPXO

1 0

Re: Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status
by Tom Fantacone 18 Nov '25

18 Nov '25

Hi All, I'm a bit perplexed about whether or how much this proposal would actually do much to lessen RIPE's workload. Marco wrote: >The Legacy Updates group is similar. Randy is correct, updates of legacy resources under contract between two existing members are typically far below the 360-minute average, but they represent only a small portion of this group. >The longer processing times mainly occur when a new contract must be signed with the RIPE NCC or a sponsoring member, or when only one party has a contractual relationship. In particular, cases where the offering party has no >contract (while the receiving party has or will have one) can take significantly longer, as the RIPE NCC must perform extensive due-diligence checks before the Legacy update can be completed." Correct me if I'm wrong, but it seems that if a legacy holder with no contract transfers space to another legacy holder who wants no contract, as current policy allows, we might expect long processing times since RIPE must, to some degree, vet the recipient for the first time. If this policy were in effect, we have the case where a new contract must be signed by the recipient (no more legacy status), but this also incurs longer processing times, so in this case I don't see any workload savings. Now if, under current policy, a recipient of a legacy transfer with no contract later decided to transfer the space elsewhere, I would expect the initial vetting of the recipient of the first transfer would extend so it wouldn't require RIPE to start from scratch in vetting them as the source of the 2nd transfer. I guess in principle it's possible the RIPE workload would be greater if the same space were being transferred over and over again to different, new, unvetted recipients who would keep the space as legacy. Is this something we could get some statistics on? Are there a significant number of cases where the same legacy space is churned over and over again to different recipients who all need to be vetted by RIPE, or are these just fringe cases? Otherwise, it seems the policy doesn't do much to mitigate the higher "legacy workload". Regarding RPKI and its cost-load, ARIN chose the path of requiring legacy holders to sign a Registration Services Agreement and relinquish legacy status to receive RPKI services. While this incentivizes entities to become ARIN members and reduces the amount of legacy space out there, it also incentivizes legacy holders who wish to remain legacy holders to forego RPKI entirely, reducing RPKI adoption. RIPE chose the path of allowing legacy holders to adopt RPKI without foregoing legacy status, as long as they enter into a contractual agreement with RIPE, generally as a member or via a sponsoring LIR. So they pay the same fees to receive the service as non-legacy holders, but aren't dissuaded by being forced to give up their legacy status. I think the current system strikes the perfect middle-ground in encouraging legacy holders to adopt RPKI and to pay for it. Finally, I agree with Niall's comment that "clarifying" should not be the operative word in the proposal's title. It implies that this policy was RIPE's actual intent when it formulated the rules governing legacy transfers, but I don't think that's the case at all. For these reasons, I'm opposed to the policy as written. Best Regards, Tom Fantacone

2 1

Early Feedback Requested on Upcoming Policy Proposal: Clarifying the non-transferability of legacy status
by Wade, Clara 18 Nov '25

18 Nov '25

Hello everyone, Following the suggestion of the RIPE NCC, we are seeking early feedback on an upcoming policy proposal we currently have in draft status. As mentioned last week after the Registration Services update from Marco at the AP-WG session - Peter Hessler and I, members of the now concluded Charging Scheme Task Force, are drafting a policy proposal to clarify the non-transferability of legacy status to address the issues of increasing overhead for the RIPE NCC, increasing market speculation around a scarce resource and its impact on the adoption of best practices like RPKI. Our proposal will modify these existing policies: 1. “RIPE Resource Transfer Policies” (RIPE-807) with additional clarifications in the Transfer Restrictions section and the Inter-RIR policy section. M&A/org restructuring transfers will be explicitly excluded. 2. “RIPE NCC Services to Legacy Internet Resource Holders” (RIPE-639) with modifications to remove the language implying new holders can keep legacy status after transfer. For background, legacy status was meant to indicate when an Internet resource had been directly assigned to the holder by IANA, before the RIRs were established. As such, ARIN, LACNIC and AFRINIC policies dictate that IPv4 legacy resources will no longer be regarded as legacy resources after a policy transfer takes place (excluding M&A transfers). RIPE is the only RIR that currently allows the recipient of a legacy transfer the ability to inherit the legacy status that was assigned to the original holder by IANA. This is currently being used as a loophole by certain actors to opt out of having a contractual relationship with the RIPE NCC in order to circumvent: 1. RIPE registration services fees. 2. The 24-month transfer lock that was introduced by this working group to prevent flipping of scarce resources. 3. Needs-based inter-RIR transfer policy utilization requirements in the case of transfers from another RIR to a recipient of a legacy resource transfer in the RIPE region. Following the publication of the Report of the RIPE NCC Charging Scheme Task Force, the membership learned that the RIPE NCC currently needs to dedicate a 0.5FTE to process legacy transfers. There are currently around 2,400 legacy resources held by 1,600 holders with no contractual relationship with the RIPE NCC (neither direct nor via a sponsor). That is around 40M IPs total or 5% of RIPE IPv4 space. In the last four years, NCC staff have processed between 370-280 legacy transfers per year, of which roughly a third do not involve a party with a contractual relationship with the NCC. Legacy transfers are more labor-intensive than other transfer types because the due diligence process requires the Registration Services team to manually source and verify pertaining documentation without the benefits of the automated processes for standard allocations. Legacy transfers take an average seven working hours to process when neither party has a contractual relationship with the NCC (around a third of legacy transfers), and six working hours to process when the parties have a contractual relationship with the NCC. If resources lost their legacy status after a transfer, these would then become standard allocations and staff could leverage enhanced compliance checks and automated processes to facilitate any future updates/transfers. These just take 1-3 working hours to process instead. Given that the task force was deemed out of scope for a policy change to address this gap, this is being brought to the attention of the Address Policy Working Group for action. If there are any concerns, questions or considerations you would like to bring up before we submit this proposal for discussion in the next week or two, we would really appreciate hearing from you so we can address these and/or incorporate them. Thanks in advance, Clara Wade

17 26

2024-02 New Version Policy Proposal (IPv6 Initial Allocations /28 and extension to /28)
by Angela Dall'Ara 14 Nov '25

14 Nov '25

Dear colleagues,   A new version of RIPE policy proposal 2024-02 "IPv6 Initial Allocations /28 and extension to /28" is now available for discussion.  Following the last round of discussion, this proposal has been updated and it is now at version 4.0.  The main difference from version 3.0 is that it allows the extension without additional documentation of a single allocation per LIR instead of per Member. You can find the full proposal at: https://www.ripe.net/community/policies/proposals/2024-02/ As per the RIPE Policy Development Process (PDP), the purpose of this six-week Discussion Phase is to discuss the proposal and provide feedback to the proposers. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal.   The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781  We encourage you to review this proposal and send your comments to  address-policy-wg(a)ripe.net before 7 November 2025.   Kind regards,   Angela Dall'Ara Policy Officer RIPE NCC

16 23

New Self-Service Form for Ending Sponsorships Now Live
by Marco Schmidt 04 Nov '25

04 Nov '25

Dear colleagues, As announced during the Address Policy session at RIPE 91, we have now deployed a new request form that allows RIPE NCC members to easily stop the sponsorship of Provider Independent (PI) resources (IPv4 PI, IPv6 PI, and AS Numbers). This new form introduces our first true self-service workflow in Registry Services. It enables immediate execution of the request, offers a clearer process, and significantly reduces manual handling. You will find the form in the LIR Portal under the same section previously used to notify the RIPE NCC about changes. Full details are available in this RIPE Labs article: https://labs.ripe.net/author/marco_schmidt/automated-self-service-to-end-sp… If your organisation sponsors independent resources, please take a moment to review your current customer agreements and use the new form to notify us of any sponsorships that have ended. Thank you for helping us maintain accurate registry data. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC

1 0

Re: 2024-02 New Version Policy Proposal (IPv6 Initial Allocations /28 and extension to /28)
by ember 30 Oct '25

30 Oct '25

> If you support this draft of the proposal, please indicate that with a > simple message. It can be a +1 or a 👍. Absolutely in favor of this! +1 from me ~ ember

1 0