- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 21 Nov 2014 12:50:52 +1100
- To: Yoav Nir <ynir.ietf@gmail.com>
- Cc: Mike Bishop <Michael.Bishop@microsoft.com>, HTTP <ietf-http-wg@w3.org>
On 18 Nov 2014, at 7:36 pm, Yoav Nir <ynir.ietf@gmail.com> wrote: > Regardless, unlike MAY and MUST, you can’t just use “SHOULD” and “SHOULD NOT” in a document. They require an explanation of why you should not, and under what circumstances your are allowed to do that something that your should not do. While it is good practice, this is not a hard and fast rule, Yoav. Certainly there has been many an RFC published with an unqualified SHOULD (or ten). Please don't portray your position as an absolute requirement of the IETF. > So, if we agree with you, we need to complete the sentence, “HTTP/2.0 clients and server SHOULD NOT use ciphers from this list unless …” "... unless the server is deployed to communicate with a known population of clients, or is willing to accept that some clients will refuse to communicate with it." Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Friday, 21 November 2014 01:51:20 UTC