The existing wave protocol (in common.proto) already supports having more than one signature in the ProtocolSignedDelta. So why not change the client to server protocol so that the client can submit either the existing ProtocolWaveletDelta or a ProtocolSignedDelta that is signed with the clients cert. Then the server would verify the signature if provided, add its own signature and apply or forward depending on where the wavelet is hosted. For deltas originating at a federation remote, the federation host would add it's own signature before sending it back out.
A Server would be responsible for answering signer requests for its hosted participants as well as itself. This would allow a complete verifiable chain of custody. Clients could also submit a signature in an annotation. The annotation would contain a signature of the content (all doc ops) it spans. This would allow users to "sign" a specific version of a document (or part of a document) within a wavelet. The signature should probably also support a comment indicating the reason for the signature (maybe some reason codes plus the option for a free-form text of limited size). I'm not sure what utility this has but it does present an alternative to the "signed" posts you see in forums. -Tad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
