CPPKI: Emphasize best-effort revocation + CAP trade-off #2932
Conversation
363f61d to
8a1248c
Compare
There was a problem hiding this comment.
Reviewed 1 of 1 files at r1.
Reviewable status:complete! all files reviewed, all discussions resolved
There was a problem hiding this comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @oncilla)
a discussion (no related file):
I think "Best effort" would be a much more accurate name that "Optimistic"
bc68b5b to
8e87085
Compare
There was a problem hiding this comment.
Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @kormat)
a discussion (no related file):
Previously, kormat (Stephen Shirley) wrote…
I think "Best effort" would be a much more accurate name that "Optimistic"
Added link between optimistic and best-effort
There was a problem hiding this comment.
Reviewed 1 of 1 files at r2.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @kormat)
Add the 'optimistic' qualifier to the certificate revocation process to make the known limitations more explicit. Specify that the TRC update must be synchronized amongst the available authoritative ASes to show which property of CAP we sacrifice.
Add the 'optimistic' qualifier to the certificate revocation process to make the known limitations more explicit. Specify that the TRC update must be synchronized amongst the available authoritative ASes to show which property of CAP we sacrifice.
8e87085 to
cac4f1a
Compare
There was a problem hiding this comment.
Reviewed 1 of 1 files at r3.
Reviewable status:
Add the 'optimistic' qualifier to the certificate revocation process to
make the known limitations more explicit.
Specify that the TRC update must be synchronized amongst the available
authoritative ASes to show which property of CAP we sacrifice.
This change is