>> - we also want a delimited interval for RPs so that they can >> acquire a new CA key prior to the transition to that key for >> subordinate signed products. > > Not at all obvious. So long as the new CA key is published before the > subordinate signed product, either it just works or you're into the > grey area of loose consistency, where there are so many ways to lose > that it's almost not worth trying to enumerate them. The net could > partition. One of the rsync servers could be down. Your clock could > be wrong. Etc ad nausium.
this way lies breakage. is this new way to get things wrongly really needed? >> Because of the naming conventions adopted by the repository design, >> most of these new products overwrite old ones, so we want to maximize >> the likelihood that an RP gets a consistent set of data. > > You appear to be assuming a model in which an RP discards old good > data before fetching new bad data, thus potentially shooting itself in > the foot whenever anything changes. the rp code in the routers goes the complete opposite way. if it has good data, those data are kept until new good data are completely fetched and assured. a router can even peer with multiple sources and hang on to 42 copies of good data. > perfect consistency is possible and cash could fall from the sky. sure it is possible. and so is brownian motion moving all the air molecules in the room into one corner. >> As a compromise, we could re-phrase the staging period discussion to >> RECOMMEND a 24-hour minimum (vs. using MUST here), if the WG (not >> just you, Rob, :-)) feels strongly. > > I would strongly prefer MAY to either MUST or SHOULD here. That > said, I would strongly prefer SHOULD to MUST. :) i do not see how the router rps can deal with SHOULD. maybe MIGHT. or modify 2119 to add BLUE MOON. randy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
