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] Hа: Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitriy V Menzulskiy
DMenzulskiy at beeline.ru
Wed Jun 26 11:23:19 CEST 2013
> > Based on Randy's proposal: > > > inform owner of dangling reference. wait a week. inform again. > > wait a month. inform again. wait a week. remove dangling reference. > > wait a month to see if anything has broken enough to get the attention > > of folk who do not respond to email. reassign AS number. > > In my point of view, it is enough to inform once. Members have to > update their information, members have to be contactable by e-mail. > > So: > 1. Inform owner about its wrong objects (only once). > 2. If an owner doesn't clean up its objects, RIPE NCC should be able > to clean up by itself after a month. > 3. Re-assign AS numbers after two month. > I agree vith Olaf : - inform once - clean up after a month - re-assign after two months. WBR, Dmitry Menzulskiy OJSC "VimpelCom" Moscwo, Russia -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20130626/1294b592/attachment.html>
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]