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/db-wg@ripe.net/
Invalid data in the RIPE database
- Previous message (by thread): Invalid data in the RIPE database
- Next message (by thread): Invalid data in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Tue Apr 26 15:37:00 CEST 1994
* > Why not deciding this by mail and doing it *now*? (since everybody * > seems to agree) Oh, it seems that I never got Wilfried's message, which is why I said things about waiting till the RIPE meeting, sorry about that. We propose the following: - make one announcment to local-ir and ripe-op (all others should know by now) that nsf-in and nsf-out will be obsoleted Wednesday next week. - next Wednesday, remove all nsf-in and nsf-out lines from the database - every update made with nsf-in and nsf-out will be accepted, but with the warning that these lines have been obsoleted and removed from the object. I do not think I want to bounce objects with nsf-in and out in it, just remove these lines and warn. How does this sound? -MT
- Previous message (by thread): Invalid data in the RIPE database
- Next message (by thread): Invalid data in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]