#126: text leaves open the possibility that a submitter might not verify the returned SCT
Comment (by [email protected]): I agree with Rob. Cases where a submitter may not need to verify the returned SCT is when it's submitting certificates for the purpose of making them known publicly. This is clearly covered by the current text. David, was there a particular case in mind where the standard should specify a submitter ought NOT to verify the returned SCT? -- -------------------------+------------------------------------------------- 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: <http://trac.tools.ietf.org/wg/trans/trac/ticket/126#comment:2> trans <http://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
