[rfc-i] RFC2119 requirements language in security considerations?
paul.hoffman at vpnc.org (Paul Hoffman) Thu, 07 April 2016 21:54 UTC
From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Thu, 07 Apr 2016 18:54:31 -0300
Subject: [rfc-i] RFC2119 requirements language in security
considerations?
In-Reply-To: <5706BC88.2050903@gmail.com>
References: <56FAF0C2.6060000@KingsMountain.com>
<8ABA5F91-97AF-471B-83F8-0C1D03EAA2B0@vpnc.org> <5706BC88.2050903@gmail.com>
Message-ID: <82804D29-7C86-4B1C-9AE1-2A33BC04A019@vpnc.org>
On 7 Apr 2016, at 17:01, Brian E Carpenter wrote: >> This has been discussed occasionally in security WGs, with people >> noting that readers >> often only skim the Security Considerations section and thus might >> miss the requirements. > > Seriously? After all these years you find that implementers don't read > them, even when the > RFC2119 keywords are upper-cased? Yes. They even admit it freely. --Paul Hoffman
- [rfc-i] RFC2119 requirements language in security… =JeffH
- [rfc-i] RFC2119 requirements language in security… Paul Hoffman
- [rfc-i] RFC2119 requirements language in security… Brian E Carpenter
- [rfc-i] RFC2119 requirements language in security… Paul Hoffman
- [rfc-i] RFC2119 requirements language in security… Brian E Carpenter