diff options
| author | Rob Austein <sra@hactrn.net> | 2007-03-22 09:59:49 +0000 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2007-03-22 09:59:49 +0000 |
| commit | 5e26567eafee48738b2290c48bb97422879307e2 (patch) | |
| tree | fca85054c76742bfab8e57fd75a2006b31264de1 | |
| parent | 332130c792e9042a52f6038f0cf2a4f4f8a4b81d (diff) | |
child ids
svn path=/scripts/regeng-api; revision=523
| -rw-r--r-- | scripts/regeng-api | 23 |
1 files changed, 20 insertions, 3 deletions
diff --git a/scripts/regeng-api b/scripts/regeng-api index 4307be05..7b19ea00 100644 --- a/scripts/regeng-api +++ b/scripts/regeng-api @@ -62,6 +62,14 @@ ;;; proven is that publication client A is not stepping on publication ;;; client B even when B is A's parent. +;;; Perhaps "cust-id" is really a bad choice, as we have two different +;;; models in which it means different thigs. In this model the +;;; cust-id is the entity which is executing, which is -issuing- +;;; stuff. In the other model, cust-id refers to the entity to which +;;; we are issuing, which is a subject-id; in the terms used below, +;;; this is a child-id. We probably need better names, because people +;;; keep getting confused by this conflict. + ;;; Protocol operations between RE and signing engine. This assumes @@ -202,6 +210,15 @@ (list-children :cust-id id) => (child ...) +(get-child-id :cust-id 42 + :child foo) +=> (child-id) + +(set-child-id :cust-id 42 + :child foo + :id bar) +=> () + (set-child-ta :cust-id 42 :child foo :ta bar) @@ -262,9 +279,9 @@ ;;; ;;; This set of operations are initiated by the RE. -(list-resources :cust-id 42 - &optional - :ca ca) ; If left off, we're asking about self rather than child +(list-resources :cust-id 42 ; issuer id + &optional ; If left off, we're asking about self rather than child + :child id) ; subject id => ((:ipv4-address "10.0.0.44/32" "10.3.0.44/32") (:ipv6-address "fe80:dead:beef::/24") ...) |