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/address-policy-wg@ripe.net/
[address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Cosmetic Surgery Project: Extended Review Period until 9 July on revised RIPE Policy document for IPv6 database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lindqvist Kurt Erik
kurtis at kurtis.pp.se
Fri Jun 28 11:40:59 CEST 2013
On 26 jun 2013, at 21:48, Erik Bais <ebais at a2b-internet.com> wrote: > The idea of cleaning the RIPE db is noble and we should do that, however > there are also other locations where those AS numbers are referenced.. ( > PeeringDB or RADB comes to mind..) RADB contains so much garbage that I think best would be for people to stop using it....YMMV > Are we going to provide them with the list of current returned AS numbers to > make sure they can also do their housekeeping ? I think that publishing lists on ASNs in each stage in Randy's proposal for example would be prudent... Best regards, - kurtis -
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Cosmetic Surgery Project: Extended Review Period until 9 July on revised RIPE Policy document for IPv6 database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]