Hi, On Sun, Jun 01, 2025 at 09:43:31AM -0500, David Farmer wrote: > > Maybe something long the lines "for subsequent ASNs, the requestor needs > > to document why existing ASNs can not be used"? There is some leeway in > > evaluating, and it might spur the requestor into actually thinking "why > > can I not use one of the ones I already have?" - writing down a reason > > often helps in reconsidering what one really wants :-) > > When requesting an additional ASN, asking how your current ASNs are used > doesn't seem unreasonable. Your old ASNs would not be reclaimed if they are > not being used. However, the new request should be denied if you > already have an unused ASN that could be used instead of requesting > an additional ASN.
This is along the lines I was thinking, so, this would work for me :-)
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard,
Karin Schuler, Sebastian Cler
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
signature.asc
Description: PGP signature
----- 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/
