Tallinn meeting comments

svn path=/docs/left-right-protocol-message-passing; revision=595

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/left-right-protocol-message-passing b/docs/left-right-protocol-message-passing
index e541cb74..44f2ea14 100644
--- a/docs/left-right-protocol-message-passing
+++ b/docs/left-right-protocol-message-passing
@@ -314,6 +314,9 @@
 ;;;
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 
+;; The following probably needs expansion to cover issuing subsets
+;; (transfer support).
+
 (list-resources :self-id 42		; issuer id
 		&optional		; If left off, we're asking about self rather than child
 		:child id)		; subject id
@@ -323,12 +326,21 @@
     (:as-number "666")
     ...)
 
+;; There has been some discussion of turning ROA generation into an
+;; imperative interface, in which case the following query would need
+;; to turn into object control protocol in the previous section.  The
+;; following is the older version of this in which the RE queries into
+;; the IRBE to find out rights to route.
+
 (list-rights-to-route :self-id 42)	; Self
 => (rights-to-route
     (as-number :ipv4 prefix-or-range :ipv6 prefix-or-range ...)
     (as-number "ipv6 prefix-or-range :ipv6 prefix-or-range :ipv4 prefix-or-range ...)
     ...)
 
+;; "Blind object signing" would probably be another imperative message
+;; to be added above, similar to whatever we end up with for ROAs.
+
 (report-error :self-id 42
 	      :error-token :your-hair-is-on-fire
 	      :bag-of-data whatever)