Minutes interim-2020-sidrops-02: Wed 16:00
minutes-interim-2020-sidrops-02-202006241600-00
| Meeting Minutes | SIDR Operations (sidrops) WG | |
|---|---|---|
| Title | Minutes interim-2020-sidrops-02: Wed 16:00 | |
| State | Active | |
| Other versions | plain text | |
| Last updated | 2020-06-24 |
minutes-interim-2020-sidrops-02-202006241600-00
Purpose of the meeting is to discuss 6486-bis
- currently RPs have differing results
Ground rules:
- publish new MFT and CRL atomically
- CA may publish additional items
- if an RPs view of a CA does not include the minimal set (i.e. what's on
the MFT?) the CA is excluded from OV calculations
Clarification:
- Items not a MFT need not be considered
Cached items may be used if they match the name and hash in a current manifest.
This is motivated by people pointing out that if cached items cannot be used
the RPKI is trivially DoS'ed.
Job talks about not trusting "rsync --delete", but deleting objects only when
they are found not to be relevant. However, this can lead to irrelevant files
being deleted and re-downloaded on every synchronisation. Steve Kent clarifies
that the MFT instructs the RP about what is relevant, but does not say what can
be deleted.
Tim will send a proposal to the WG about the use of rsync URIs in RRDP
Conclusion:
- Steve Kent will publish document
- Job Snijder will make an RP implementation matrix based on the text
- Other RP implementors are asked to fill out the matrix
Randy talks about the need for a better *automated* signalling mechanism from
RP software to operators. Jeff talked about relevant work in the IETF for this
- but I missed where it is - so if someone can comment on this?