+ Use of RPKI-based origin validation obviates the utility of + announcing many longer prefix when the covering prefix would do. + + To aid translation of ROAs into efficient search algorithms in + routers, ROAs SHOULD be as precise as possible, i.e. match prefixes + as announced in BGP. E.g. software and operators SHOULD avoid use of + excessive max length values in ROAs unless operationally necessary. + + Therefore, ROA generation software MUST use the prefix length as the + max length if the user does not specify a max length. + + Operators SHOULD be conservative in use of max length in ROAs. E.g., + if a prefix will have only a few sub-prefixes announced, multiple + ROAs for the specific announcements SHOULD be used as opposed to one + ROA with a long max length.
yes, i will fix s/prefix/prefixes/ in the next edition randy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
