Wilfried Woeber: Fwd: Re: Invalid data in the RIPE database
- Date: Tue, 26 Apr 1994 16:39:21 +0200
Wilfried has some mail connectivity problems to the RIPE NCC,
therefore he asked me to resend the mail below concerning the as-in
and as-out attributes.
-Marten
------- Forwarded Message
Date: Tue, 26 Apr 1994 16:36:51 +0100
From: "Wilfried Woeber, UniVie/ACOnet" woeber@localhost
Sender: woeber@localhost
To: marten@localhost
cc: woeber@localhost
Subject: Fwd: Re: Invalid data in the RIPE database
Marten,
this was (one of) the message(s) that made it to L.Joncheray,
but didn't reach you personally and the -wg lists.
Maybe you could forward them, to keep the chaos down to a reasonable
level.
Sorry,
Wilfried.
From: ACCESS::WOEBER "Wilfried Woeber, UniVie/ACOnet" 26-APR-1994 11:31
:48.07
To: MX%"Marten.Terpstra@localhost"
CC: MX%"lpj@localhost",MX%"routing-wg@localhost",MX%"db-wg@localhost",WOEBER
Subj: Re: Invalid data in the RIPE database
=Daniel Karrenberg <Daniel.Karrenberg@localhost writes
= *
= * > Laurent Joncheray lpj@localhost writes:
= * > Dear database managers,
= * > i had a look at some entries in the RIPE database and at the
= * > 'nsf-in' network attribute. For a lot of them the value in the RIPE
= * > db is inconsistant with the Merit (NSF) database...
= *
= * More radical question: Considering that the NSFnet is going away and
= * the routing registry has routing policy, should these attributes
= * be deprecated or even removed totally?
=
=Jean-Michel writes
=
= * 1- obsolete this field.
= * 2- Implement what Laurent proposes (automatic download from Merit).
=
=I feel for Daniels and Jean-Michel's first option. They should
=definately be deprecated (although I have always viewed them as info
=only attibutes) and preferably removed. Although some people may find
I agree with this point of view.
I'm going to put it on the agenda for the DB-WG at the Amsterdam
RIPE-Meeting. We should have a *short* review and then agree on a
proposal and a *timeschedule* to remove this information from the
database.
=this information useful currently, wrong information is worse than no
=information. I'd say obsolete.
Agreed.
At the same time we should come up with a recommendation for new
ways of storing pieces of information that people maybe still want to
record in the DB. (Like connect, gateway, and the like).
Wilfried.
--------------------------------------------------------------------------
Wilfried Woeber : e-mail: Wilfried.Woeber@localhost
Computer Center - ACOnet :
Vienna University : Tel: +43 1 4065822 355
Universitaetsstrasse 7 : Fax: +43 1 4065822 170
A-1010 Vienna, Austria, Europe : NIC: WW144
--------------------------------------------------------------------------
------- End of Forwarded Message
|