This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP
- Previous message (by thread): [routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP
- Next message (by thread): [routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Hoogsteder
paul at meanie.nl
Tue May 29 09:05:56 CEST 2018
> On 28/05/2018 14:53, Job Snijders wrote: >> On Thu, May 17, 2018 at 07:16:34PM +0300, Hank Nussbacher wrote: >>> On 17/05/2018 17:02, Benno Overeinder wrote: >>> >>> Maybe I'm missing it when reading the website and the BCOP but where >>> does it state to *not *allow /25 or more specifics? >> If someone registers a /25, and announces it, and the RPKI ROA allows >> it, then what is the problem? :-) >> >> - Job >> > I am not talking about a registered /25. I am talking about someone > hijacking your /24 or your /21 by announcing a bunch of /25s. That shouldn't get far because they can't create the ROA. You SHOULD NOT filter all /25s (or /26s or /27s) as some of these have been assigned by RIPE NCC. Paul.
- Previous message (by thread): [routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP
- Next message (by thread): [routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]