#161: Handling high-volume submissions Google's Aviator log recently exceeded its MMD slightly. This was: "caused by the (non-malicious) actions of some high-volume clients. Aviator's signer could not sequence the submitted certificate chains quickly enough to clear the backlog, exacerbated by the fact our protection against flooding did not activate when expected." https://groups.google.com/a/chromium.org/d/msg/ct-policy/ZZf3iryLgCo/mi- 4ViMiCAAJ
Inspired by OCSP, I think we should add a "tryLater" error code to add- chain and add-pre-chain, so that logs can explicitly communicate the fact that they're currently too busy to accept submissions. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-trans- [email protected] | [email protected] Type: enhancement | Status: new Priority: minor | Milestone: Component: rfc6962-bis | Version: Severity: - | Keywords: -------------------------------------+------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/161> trans <https://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
