More old notes overtaken by events.

svn path=/rpkid/README; revision=2831

1 files changed, 0 insertions, 29 deletions

diff --git a/rpkid/README b/rpkid/README
index 2e7f763c..c734a4ef 100644
--- a/rpkid/README
+++ b/rpkid/README
@@ -162,32 +162,3 @@ TO DO:
         keeping ROAs up to date.
 
 	STATUS: Not started
-
-
-
-Other random notes:
-
-Being able to specify interaction with other servers (not running
-under testbed) in a testbed.yaml might be useful for interop tests.
-Kind of breaks testbed's fundamental model, though.  Replacing what
-testbed thinks is a leaf with somebody else would be easy, so maybe we
-could specify some way to hang a bunch of rpkids under an external
-parent?  Hmm, data needed would look a lot like testpoke.yaml, maybe
-we can reuse some of that language?
-
-There's a three-way tradeoff lurking in the publication protocol,
-manifest generation, and CRL generation:
-
-1) Consistancy issues for relying parties (eg, don't want to withdraw
-   something that's still listed in the manifest);
-
-2) Efficiency issues for the RPKI engine (eg, generating a new
-   manifest for each individual change during a batch run could be
-   expensive, would prefer to batch up the changes into a single
-   manifest run); and
-
-3) Coherency issues for the RPKI engine (don't want to defer things
-   that could result in loss of state if something bad happens).
-
-Considerations (1) and (3) have to dominate, which may mean we take a
-hit on (2).