Invalid data in the RIPE database

 * >	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