1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='RFC2119'>
4
5<front>
6<title abbrev='RFC Key Words'>Key words for use in RFCs to Indicate Requirement Levels</title>
7<author initials='S.' surname='Bradner' fullname='Scott Bradner'>
8<organization>Harvard University</organization>
9<address>
10<postal>
11<street>1350 Mass. Ave.</street>
12<street>Cambridge</street>
13<street>MA 02138</street></postal>
14<phone>- +1 617 495 3864</phone>
15<email>[email protected]</email></address></author>
16<date year='1997' month='March' />
17<area>General</area>
18<keyword>keyword</keyword>
19<abstract>
20<t>
21   In many standards track documents several words are used to signify
22   the requirements in the specification.  These words are often
23   capitalized.  This document defines these words as they should be
24   interpreted in IETF documents.  Authors who follow these guidelines
25   should incorporate this phrase near the beginning of their document:
26
27<list>
28<t>
29      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
30      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
31      "OPTIONAL" in this document are to be interpreted as described in
32      RFC 2119.
33</t></list></t>
34<t>
35   Note that the force of these words is modified by the requirement
36   level of the document in which they are used.
37</t></abstract></front>
38
39<seriesInfo name='BCP' value='14' />
40<seriesInfo name='RFC' value='2119' />
41<format type='TXT' octets='4723' target='http://www.rfc-editor.org/rfc/rfc2119.txt' />
42<format type='HTML' octets='17970' target='http://xml.resource.org/public/rfc/html/rfc2119.html' />
43<format type='XML' octets='5777' target='http://xml.resource.org/public/rfc/xml/rfc2119.xml' />
44</reference>
45