aboutsummaryrefslogtreecommitdiff
path: root/docs/left-right-protocol
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2007-04-16 22:03:30 +0000
committerRob Austein <sra@hactrn.net>2007-04-16 22:03:30 +0000
commit53f45af5b2ce9b35748cc664298819b9457d1611 (patch)
tree1862ee1cb2eceeb085c14aa401aadb1cb6843c8f /docs/left-right-protocol
parent31c69bec553be70ee138b739343a1bce6791740a (diff)
Checkpointed confusion
svn path=/docs/left-right-protocol; revision=574
Diffstat (limited to 'docs/left-right-protocol')
-rw-r--r--docs/left-right-protocol8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/left-right-protocol b/docs/left-right-protocol
index d075335c..ba5d1019 100644
--- a/docs/left-right-protocol
+++ b/docs/left-right-protocol
@@ -63,6 +63,14 @@
;;; given with actual publication request. Thing that needs to be
;;; proven is that publication client A is not stepping on publication
;;; client B even when B is A's parent.
+;;;
+;;; Not yet sure into which object we need to be stuffing various bits
+;;; of this URI. The head portion is per, um, er, can we assume it's
+;;; per repository object? Maybe. The middle comes down on the fly
+;;; from the parent and is probably per class; dunno whether we store
+;;; it as is or just use it on the fly to construct the complete SIA
+;;; URI and store that. And where do we store the resulting computed
+;;; SIA URIs, in the CA objects?
;;; Operations on keys need to specify signature algorithm (currently
;;; only RSA, but need agility) and key length. Signing operations