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] AS Number Assignments - Transitioning to Policy Compliance Completed
- Previous message (by thread): [address-policy-wg] AS Number Assignments - Transitioning to Policy Compliance Completed
- Next message (by thread): [address-policy-wg] AS Number Assignments - Transitioning to Policy Compliance Completed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Thu Jan 25 16:07:23 CET 2024
On Thu, 25 Jan 2024, Marco Schmidt wrote: > Dear colleagues, > > In November 2023, I shared with you during the RIPE meeting and on this > mailing list that the RIPE NCC intends to assign Autonomous System Numbers > (ASNs) from an undifferentiated 32-bit AS Number pool, as defined in the > Autonomous System (AS) Number Assignment Policies. > > I am pleased to inform you that this change has been successfully > implemented. The option to choose between a 16-bit or 32-bit AS Number as > been removed. When submitting a request, the RIPE NCC will assign the next > available AS Number from the undifferentiated allocation pool. Hi, could you please elaborate on what this "undifferentiated 32-bit AS Number pool" is? I'm mainly curious if it means we'll deplete 16 bit ASNs (allocate from the lowest available number)? Thanks. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] AS Number Assignments - Transitioning to Policy Compliance Completed
- Next message (by thread): [address-policy-wg] AS Number Assignments - Transitioning to Policy Compliance Completed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]