Y. Vanhullebus Internet Draft Document: Expires December 2009 June 2009 Usage of the keyword SHOULD in RFCs to indicate requirement level Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. 1. Abstract RFC-2119 describes usage of some key words, so people should know how to use them when writing RFCs, and how to understand them when reading RFCs compliant with RFC-2119. After some years of usage, some updates to those best practices seems to be needed to enhance security level of protocols and of their implementations. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. 3. SHOULD To ensure implementers won't forget/misunderstand security considerations when not doing something designed as "SHOULD", "SHOULD" keyword MUST NOT be used anymore in any RFC. 4. SHOULD NOT To ensure implementers won't forget/misunderstand security considerations when not doing something designed as "SHOULD NOT", "SHOULD NOT" keyword MUST NOT be used anymore in any RFC. 5. Security Considerations 6. References [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 7. Acknowledgments The authors would like to thank SSTIC team(s). 8. Author's Addresses Yvan Vanhullebus 9. Expiration This draft expires December, 2009 Full Copyright Statement "Copyright (C) The Internet Society (date). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into