#76: Normative client behavior specified in Section 3.4 Changes (by [email protected]):
* owner: [email protected] => [email protected] * status: reopened => new Comment: Propose this ticket be closed (fixed) as we've added the following text (section 9.2): "However, specifying the TLS clients' behavior once compliance or non- compliance has been determined (for example, whether a certificate should be rejected due to the lack of valid SCTs) is outside the scope of this document." I also think that the text on SCT validity is quite clear: "TLS clients SHOULD validate each SCT by computing the signature input from the SCT data as well as the certificate and verifying the signature, using the corresponding log's public key." So not sure what can be added, unless Steve Kent points to the problematic wording in draft 10. -- --------------------------+-------------------------------------- Reporter: [email protected] | Owner: [email protected] Type: defect | Status: new Priority: major | Milestone: review Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | --------------------------+-------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/76#comment:6> trans <http://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
