Hi Lingli, "Writer" is a vague term. Section 7.3 Access Control describes validation around the "signer" of the stored data. A storage data can be stored (or written) by the signer and by the responsible peer as replica to its successors. The problem is not as simple as it may seem. During replication, successors will receive identical copies of the same StoredDataValue with a storage_time equals to the one it already has (previously received). Therefore, for replicas, storage_time equality is expected and must be allowed. This topic needs more discussions. Please add it to the Berlin agendas if none of the principal authors are able to respond before then. Thanks --Michael --------- Original Message --------- Subject: 答复: [P2PSIP] storage_time check wording inconsistency From: "邓灵莉/Lingli Deng" <[email protected]> Date: 7/4/13 3:46 pm To: "'Michael Chen'" <[email protected]>, [email protected]
Hi Michael, I agree with you that there is a hole when subsequent store requests have the same storage_time value. But should every equality case be responded with a TOO-OLD error? If there is only one writer to the data object, it seems like a repetition, and it makes sense to discard it like you said. Whereas if there are more than one writers to the data object, I am not sure what is expected. Do we have to consider the multi-writer case? BR Lingli
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
