On Dec 3, 2012, at 1:11 PM, Tim Moses <[email protected]> wrote: > Guys - I was also thinking that "field and extension processing" causes state > changes that are communicated to the user. So, rather than introduce an > additional document to cover this requirement, I prefer to make sure it is > adequately covered in the proposed existing set of documents.
Please note that the document that you thought covered "Capturing state changes that are visible to the user" is different than the one Jeff did. For example, I don't see how the state change of "starting TLS" to "TLS failed due to an expired certificate" has anything to do with "certificate, CRL, and OCSP field and extension processing". Jeff suggested that these visible state changes be in "TLS stack operation", which seems a heck of a lot more appropriate. --Paul Hoffman _______________________________________________ wpkops mailing list [email protected] https://www.ietf.org/mailman/listinfo/wpkops
