On 19/09/2009, at 3:23 AM, Stephen Kent wrote:
We were told over a year ago that, because of legitimate transfers, looking for duplicates was bad idea, in the repository system. So, I'm not sure if we want to do it in the 'assimilated relying party rpki.'
So legitimate transfers will breed duplicates? My recollection of that discussion that there would be timing in place that certificate validity times would be tuned (with sparse use of CRLs) to effect the transfers. Or am I mistaken?
I think, if anywhere you needed to go looking for duplicates it would be the relying party software (either your software or rcynic) before it mades it to the router "decision"
OK, we'll look into generating one.
:-)
One cannot prevent 3rd parties from asserting themselves as TAs, but the CP does not accommodate such entities as CAs, nor does the repository system facilitate their use.
If your software can change the contents of the 3779 extensions, would it not be a simple exercise to change the SIA value?
Cheers Terry _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
