[anti-abuse-wg] WHOIS (AS204224)
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri Nov 6 09:54:29 CET 2015
Hi, On Thu, Nov 05, 2015 at 03:58:26PM -0800, Ronald F. Guilmette wrote: [..] > >This really does matter. Even with a valid RIPE ASN they cannot 'steal' > >RIPE address space. > > Really??? > > If so, that's great news! > > Did everyone finally agree to use only fully authenticated route > announcement protocols while I was sleeping?? Or is BGP fundamentally > still wide open? Upstreams that accept unfiltered BGP announcements from their downstreams still exist, and are a huge problem - but *this* is something we cannot solve by changes to the RIPE DB. But since the original thread was also about "people putting bogus route: objects for APNIC space into the RIPE DB", Denis' statement explains why the creation of bogus route: objects cannot be done for RIPE address space. Gert Doering -- NetMaster -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20151106/53cca313/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]