This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management
- Previous message (by thread): [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management
- Next message (by thread): [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kaj Niemi
kajtzu at a51.org
Thu Jun 8 17:14:14 CEST 2023
In the GM a few weeks ago, resolution 4 or the proposal for charging 50 eur/ASN, which was presented by NCC management and supported by the board, I believe, was not adopted. The 67% of the membership votes cast or approximately 1500 votes were against. Kaj Sent from my iPad ________________________________ From: address-policy-wg <address-policy-wg-bounces at ripe.net> on behalf of Nick Hilliard <nick at foobar.org> Sent: Thursday, June 8, 2023 5:55 PM To: Marco Schmidt <mschmidt at ripe.net> Cc: address-policy-wg at ripe.net <address-policy-wg at ripe.net> Subject: Re: [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management Marco Schmidt wrote on 08/06/2023 14:30: > We also plan to intensify our ongoing project to clean up unused > Autonomous System (AS) Numbers [2]. Almost 2,000 unused ASNs have been > recovered as part of this work so far. Do you support our approach here? > And are there other ways we could improve the situation? Perhaps you > could add clarification on requesting and returning ASNs in the relevant > RIPE policy, or maybe we could give a stronger mandate and > responsibility to the sponsoring LIRs. Hi Marco, There are good reasons to clean up unused ASN16s, as they are categorised by policy as scarce resources. There isn't a compelling reason to get as excited about ASN32s, other than to say that normal good stewardship practices should apply. Unfortunately there is a disconnect between RIPE policy and RIPE NCC practice in regard to charges for ASNs. This is a real shame because paying for resources is one of the simpler ways of creating positive pressure to return them if they're unused. The community would benefit from the board re-thinking this. Nick -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20230608/b3bf44ed/attachment.html>
- Previous message (by thread): [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management
- Next message (by thread): [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]