2010/2/28 shen <[email protected]> > Dear All, > > I would like to ask a question about the synchronization of storage time > for Store Request. > > For a Store Request , “storage_time” field is used to prevent rollback > attacks. But if there are more than one peer to store the same resource , > there may be some problem of synchronization. > > Foe example, if node1’s clock is faster than node2s’ and node 1 has stored > the resource which the storage time followed node1 ‘s clock. When node 2 > stores the same resource, it is possible that the “storage_time” value of > “NEW” Store Request is smaller than the previous storage time. How does it > synchronize the clocks? Is there any mechanism to avoid the situation? >
In general, RELOAD attempts to segregate data from separate nodes so this doesn't happen much. However, if it does happen, then either node2 can update its clock correctly if its wrong do an effective remove (store with the storage time that's ahead of node1 but a lifetime of zero). I'm not sure if RELOAD explicitly says that a subsequent store with the right lifetime should succeed, but I think that would be a good rule. -Ekr
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
