Hi, On Mon, May 02, 2016 at 02:12:40PM +0200, Marco Schmidt wrote:
You can find the full proposal at:
https://www.ripe.net/participate/policies/proposals/2016-02
We encourage you to review this proposal and send your comments to <ncc-services-wg@ripe.net> before 31 May 2016.
I might be a bit old and stupid, but let me paraphrase if I understand this right: - people put crap into the RADB all day long - so we add an API for the RIPE DB so that the RADB operators can auto-check whether a given (prefix,as) tupel has been authorized by the owner in their corresponding registry (here: RIPE) correct? If yes, I don't think this is a good approach - because if the RADB and other operators actually were *interested* in reducing the amount of crap in their database, they could cross-check RIPE route:/route6: objects already today, without any new API needed. Evidence shows that they are not interested, even when presented with "hey, there is garbage in your database, look at the RIPE DB for the correct route: object" nothing happens. Ceterum censeo: RADB must die, and as this proposal will not speed up the process, so it's not helping. (NTT, on the other side, is already cross-checking - so I'm not sure I see the benefit for them. But if Job convinces me that it makes life easier for them, I stand corrected) Gert Doering -- router operator, and victim of RADB garbage -> hijacks -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279