#94: Fetching of inclusion proofs: Why and when are clients expected to do this?
Comment (by [email protected]): Regarding the original question raised in this issue: (1) When is defined pretty clearly in https://tools.ietf.org/html/draft- ietf-trans-rfc6962-bis-11#section-9.2. (2) Why is explained in the introduction, albeit briefly. The distinction between a client having an SCT and a client having an inclusion proof that was clear in RFC6962 is now less sharp, as inclusion proofs can be directly provided to clients. There's benefit in explaining the distinction between a client only having seen an SCT and a client having checked inclusion by verifying an inclusion proof; I welcome suggestions regarding the relevant section in the RFC this should be described. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-trans- [email protected] | [email protected] Type: defect | Status: new Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | -------------------------+------------------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/94#comment:3> trans <https://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
