Call for agenda items, DB-WG meeting during RIPE71, Bucharest, Romania
Dear DB-WG participants We are reaching out to you for agenda items for the Database Working Group session during the RIPE71 meeting in Bucharest, Romania, 16-20 November 2015. The DB-WG session is currently scheduled as usual for Thursday (Nov 19th), starting at 16:00 local time, after the coffee break. The length of our timeslot is 90 minutes. Please submit your items or topic suggestions directly to the WG chairs or to the list for public discussion. The draft agenda will be published soon. Looking forward to see you all in Bucharest. All the best, Job, Nigel & Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
On 02/10/2015 20:16, Piotr Strzyzewski wrote:
We are reaching out to you for agenda items for the Database Working Group session during the RIPE71 meeting in Bucharest, Romania, 16-20 November 2015.
limiting RIPE-NCC-RPSL-MNT usage. Nick
On 10/2/15 10:42 PM, Nick Hilliard wrote:
We are reaching out to you for agenda items for the Database Working Group session during the RIPE71 meeting in Bucharest, Romania, 16-20 November 2015.
On 02/10/2015 20:16, Piotr Strzyzewski wrote: limiting RIPE-NCC-RPSL-MNT usage.
Nick
+1 cheers, elvis
We are reaching out to you for agenda items for the Database Working Group session during the RIPE71 meeting in Bucharest, Romania, 16-20 November 2015.
limiting RIPE-NCC-RPSL-MNT usage.
i worry that 'improving' the data by throwing much of it away is not operationally productive. there are many isps who got their space out of region who peer at european exchanges where route:s in the ripe irr are expected. randy
On 03/10/2015 10:57, Randy Bush wrote:
i worry that 'improving' the data by throwing much of it away is not operationally productive. there are many isps who got their space out of region who peer at european exchanges where route:s in the ripe irr are expected.
there's two categories of data in the irrdb: data which is protected by the hierarchical authentication mechanism, and other entries which are authenticated by RIPE-NCC-RPSL-MNT. The RIPE area objects are probably reasonably good quality but many of the external entries are unmaintained junk. There's no real way of telling which is which, unless you build smartness into the query agent to filter out all non ripe address space. It would be nice to have a server-side way of determining which is which. Regarding IXP filtering, if irrdb filtering is a requirement, then it's not really possible to depend on a single irr source. The only practical way to handle this is either to query RADB and accept all sources or else to allow each connected ixp participant to choose their own set of irrdbs and a source: policy. RADB includes a large quantity of junk from third party databases and is also regularly targeted by hijackers in the same way that RIPE-NCC-RPSL-MNT is abused. Nick
The RIPE area objects are probably reasonably good quality but many of the external entries are unmaintained junk.
i would say of mixed quality
There's no real way of telling
ageee
Regarding IXP filtering, if irrdb filtering is a requirement, then it's not really possible to depend on a single irr source. The only practical way to handle this is either to query RADB and accept all sources
there are more sources than are to be found in the radb, many of them of reasonable quality.
or else to allow each connected ixp participant to choose their own set of irrdbs and a source: policy.
i do kinda the opposite. each peer says what irr instance they use and what their as-set is.
RADB includes a large quantity of junk from third party databases and is also regularly targeted by hijackers in the same way that RIPE-NCC-RPSL-MNT is abused.
welcome to the internet. work on fixing the abuse peoblem not jailing the abused; leave that to the american courts [0]. randy -- [0] - http://www.correctionalassociation.org/issue/domestic-violence
On Sat, Oct 03, 2015 at 05:57:07AM -0400, Randy Bush wrote:
We are reaching out to you for agenda items for the Database Working Group session during the RIPE71 meeting in Bucharest, Romania, 16-20 November 2015.
limiting RIPE-NCC-RPSL-MNT usage.
there are many isps who got their space out of region who peer at european exchanges where route:s in the ripe irr are expected.
The above statement is detached from reality.
How would solving this issue, fix the issue of incorrect prefix / route object filters as you can also pay a small fee for the RAdb and put anything you like in it ... Without any rir authorization ? ... Companies that are knowingly trying to register incorrect should have their resources de-registered via arbitration. That should be a (top) prio across all RIR's if we ever want to fix this kind of abusive behaviour. Database accuracy and database usage / behaviour are very important .. We have all these policies / rules that state what we need to do .. And if someone is just entering false/ fake info in the databse, it should be reason enough for arbitration and initiate a complete de-registration of resources. The system as it is, is required to be able to register AS numbers from other RIR's into the RIPE db to be able to create route objects ... In order to be able to get your upstreams to route your prefixes.. Not many peering parties are doing actual per peer prefix list creation is my experience... I think there might be a solution between a federated RIR DB authentication solution and arbitration for this abusive behaviour... I fear that just quiting this feature will break lots of other stuff.. Regards, Erik Bais
participants (6)
-
Elvis Daniel Velea -
Erik Bais - A2B Internet -
Job Snijders -
Nick Hilliard -
Piotr Strzyzewski -
Randy Bush