====== RFC2119 - Key words for use in RFCs to Indicate Requirement Levels ======
[[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]]

<table>
<caption>Data sheet for RFC2119 Key words for use in RFCs to Indicate Requirement Levels</caption>
| Title                      | Key words for use in RFCs to Indicate Requirement Levels |
| Acronym                    | |
| Version                    | 1997 |
| Document Number            | RFC2119  Updated by [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:8174]]|
| Release Date               | March 1997  |
| Reference                  | [[https://tools.ietf.org/html/rfc2119]] |
</table>

  : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.


==== Abstract ====
  : // In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized.  This document defines these words as they should be interpreted in IETF documents.  Authors who follow these guidelines should incorporate this phrase near the beginning of their 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.

  : **Note:** that the force of these words is modified by the requirement level of the document in which they are used.


/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~