>> a customer leaked a full table to smellstra, and they had not filtered. >> hence the $subject. > > Ahh, this is I think the customer "leak" problem I'm trying to illustrate > that an RPKI/BGPSEC-enabled world alone (as currently prescribed) > does NOT protect against.
the problem is that you have yet to rigorously define it and how to unambiguously and rigorously detect it. lack of that will prevent anyone from helping you prevent it. randy
