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]/

[db-wg] [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs

Previous message (by thread): [db-wg] Guidance Requested: Reassigning Referenced ASNs
Next message (by thread): [db-wg] [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 ]

James Blessing james.blessing at despres.co.uk
Tue Jun 25 15:38:32 CEST 2013

On 25 June 2013 14:02, Andrea Cima <andrea at ripe.net> wrote:

> C. Clean up the RIPE Database from references and then reassign the AS
> numbers
>     C.1. "Silent" update; or
>     C.2. Informing the object holder of the update

Okay couple of questions...

1. Have people with these objects been notified yet (might be a good
place to start)? As a matter of course are returns actually
announced/published anywhere?
2. Is there a single list of returned and referenced ASNs that a
concerned netcitizen could parse and then fix their records from?

I think cart and horse spring to mind

J

--

James Blessing
07989 039 476

Previous message (by thread): [db-wg] Guidance Requested: Reassigning Referenced ASNs
Next message (by thread): [db-wg] [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 ]

[ db-wg Archives ]