Wayne, You asked: "Should we also ask about SPDY support?" I'm inclined to think no, because that's sort of an HTTP replacement over and above SSL/TLS. I'm not sure it falls in to the charter.
About RFC6277 (OCSP Algorithm Agility) good point, I'll add that. I created a new section for OCSP Responder (in addition to Server and Client) and also added the question to the Client survey. But what do you mean by "Does there need to be a question about stapling support for multiple signature algorithms?" Good point: "Should we ask what encoding is supported here (Punycode, UTF-8)" but I think I'll keep the questions to what's relevant for TLS/SSL (what happens if the user types the Punycode but the cert contains only the native name, and not, for example, how names are displayed). -Rick From: Wayne Thayer [mailto:[email protected]] Sent: Sunday, December 01, 2013 1:41 PM To: Rick Andrews Cc: [email protected] Subject: Re: [wpkops] Early draft of vendor questionnaire Rick - please find my comments attached. Thanks, Wayne From: Rick Andrews <[email protected]<mailto:[email protected]>> Date: Tuesday, November 26, 2013 at 5:27 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [wpkops] Early draft of vendor questionnaire Folks, Here's a very early draft, started by Tim with updates from David and me. I've turned on Track Changes; please feel free to add edits and comments. I'm sure there's many more questions we can ask. Please pile 'em on. -Rick
_______________________________________________ wpkops mailing list [email protected] https://www.ietf.org/mailman/listinfo/wpkops
