>> 1. It is common to use private ASNs in Confederations, > but the global RPKI can’t support that. draft-ietf-sidr-slurm seems > to address the issue of local management of private resources in the > RPKI. …
the issue is not how the confed AS validates ROAs of the private ASs in the confed. that is trivial and supported by existing software. my questions revolve around path processing. 4.3 confuses me by using 'private' ambiguously. i have tried to read that section yet again and drowned in the mass of words. perhaps more coffee will help; but i am not optimistic. i pity the implementors. randy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
