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] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources
- Previous message (by thread): [address-policy-wg] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources
- Next message (by thread): [address-policy-wg] [routing-wg] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Mon Jun 9 15:04:08 CEST 2014
On 09/06/2014 13:49, João Damas wrote: > The observed consensus during the meeting was that: > > - the RIPE NCC should not to remove references to recovered ASNs from import and export lines, and neither from as-set objects; routing policies are the realm of the object owner and are not related to allocation data. > - the RIPE NCC will inform the maintainer of the object containing the obsolete reference about this reference. The RIPE NCC will also offer support to the maintainer to delete the reference; > - the RIPE NCC will start re-assigning referenced AS numbers once the unreferenced pool of 16-bit AS numbers has been exhausted. wfm. Nick
- Previous message (by thread): [address-policy-wg] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources
- Next message (by thread): [address-policy-wg] [routing-wg] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]