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] Cleaning up Unused AS Numbers
- Previous message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
- Next message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aled Morris
aled.w.morris at googlemail.com
Fri Mar 24 12:02:26 CET 2017
On 24 March 2017 at 10:43, Jim Reid <jim at rfc1035.com> wrote: > > > On 24 Mar 2017, at 10:29, Dickinson, Ian <Ian.Dickinson at sky.uk> wrote: > > > > Requiring an ASN to be visible on the public Internet is a non-starter > IMHO. > > +1. > > There is no comparable requirement in any of the RIRs which demand LIRs > make their IP address allocations visible on the Internet. I fail to > understand why this obligation should apply to ASNs. > > It’s not as if we’ll be running out of AS numbers any time soon. What are > the actual (or perceived?) problems that would be solved by reclaiming the > ASNs that are not seen in the Internet’s routing tables? > +1 from me too. I've worked in many companies where mergers and acquisitions resulted in conflicting "private" addressing schemes. If ASN scarcity was a real problem, it wouldn't be too hard to write an RFC for 128-bit ASNs. Aled -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20170324/89ae4927/attachment.html>
- Previous message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
- Next message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]