>By the latter group, 416 Route Origin Authorization (ROA) objects have been >created, covering the equivalent of 230,000 /24 prefixes and 8,600 /32 IPv6 >prefixes. >MaxLength in ROAs is sorely misunderstood, lots of education is needed there. >Most leave the field blank, causing more specific announcements to be invalid.
Alex, Can you comment if (a) the more specifics are announced from the same AS as seen in the ROA, or (b) they are announced from a different AS (e.g., customer AS)? If it is the latter, then even the ROA creation (for the less specific) is possibly in violation of: "Before issuing a ROA for a super-block, an operator MUST ensure that any sub-allocations from that block which are announced by other ASs, e.g. customers, have correct ROAs in the RPKI." from the origin-ops doc. http://tools.ietf.org/html/draft-ietf-sidr-origin-ops-13#section-3 As for education, the origin-ops document as well as the use-cases document (Sections 3, 7) http://tools.ietf.org/html/draft-ietf-sidr-usecases-03 can be referred. Sriram _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
