diff options
| author | Rob Austein <sra@hactrn.net> | 2008-06-04 16:27:52 +0000 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2008-06-04 16:27:52 +0000 |
| commit | d5d0045ae8544b63b26bec4fdaccf8fea81ebb0f (patch) | |
| tree | 10c2e360eeb287a715939663405e694fd6f0df19 | |
| parent | e5538e6f00165eed41e9a209984d06a2cbf6d6cc (diff) | |
Update notes on publication protocol
svn path=/rpkid/README; revision=1845
| -rw-r--r-- | rpkid/README | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/rpkid/README b/rpkid/README index 8f9a9594..854c4315 100644 --- a/rpkid/README +++ b/rpkid/README @@ -73,26 +73,25 @@ TO DO: STATUS: Not started - - Publication protocol and implementation thereof. Desirable - although not strictly required that protocol be agreed upon - among the RIRs. Tricky bit is making sure that repository - receives enough information to know whether parent has - authorized child to use parent's namespace in nesting case; in - theory this is straightforward but requires careful checking. - - ARIN can't host output of non-hosted RPKI engines without - this, and that's critical both to the security model as - discussed with ARIN staff in late 2006, hence this is a - required capability even for testing. + - Publication protocol and implementation thereof. + + Tricky bit is making sure that repository receives enough + information to know whether parent has authorized child to use + parent's namespace in nesting case; in theory this is + straightforward but requires careful checking. + + Current implementation just uses a configured path check and + does not attempt to trace back to permission from parent in + nested publication case. Class and method design is intended + to make it easy to drop in additional checks if needed. PRIORITY: Required for pilot - TIME REQUIRED: 3-4 weeks for implementation once protocol - settled, depending on how much of the existing left-right - protocol design and implementation can be reused. + TIME REQUIRED: 3-4 weeks for implementation. STATUS: Initial implementation seems to work, not seriously - tested yet. + tested yet. See above for notes on ACL checking. + - Resource subsetting (req_* attributes in up-down protocol), minimal implementation. Recognize this as correct protocol @@ -104,6 +103,7 @@ TO DO: STATUS: code written, not yet tested. + - rcynic does not yet handle manifests. This is both a real problem (manifests were added to plug a security hole) and a user acceptance problem (without manifest support rcynic |