Hello, I am working on a presentation giving some recommendations for RPKI early adopters. I want to provide some guidelines on how they should go about creating their ROAs, and I would love to receive some input from this list.
Broadly speaking, and looking at what people have created in the repositories so far, there seem to be two different views on the matter: - ROAs that mirror BGP announcements and/or block de-aggregation within networks For example, an organization with as 100 holding 10.1/16 and having sub-allocated 10.1.128/18 to as 200 creates something like this: ROA #1: 10.1.0/17-18, 10.1.192/18-18 origin-as 100 ROA #2: 10.1.128/18-18 origin-as 200 - ROAs that protect all the way to /32 (in IPv4) Using the same example as above, they would have: ROA #1: 10.1/16-32 origin-as 100 ROA #2: 10.1.128/18-32 origin-as 200 Your input and thoughts are much appreciated! Warm regards, Carlos -- -- ========================= Carlos M. Martinez-Cagnazzo http://www.labs.lacnic.net ========================= _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
