[RFC.EE Home] [TXT|PDF|HTML] [Index]
BEST CURRENT PRACTICE
Independent Submission S. Bradner
Request for Comments: 0003 RFC.EE Project
Category: Best Current Practice February 2026
ISSN: 2070-1721
Requirement Keywords in RFC-Style Documents
Abstract
RFCs use a small vocabulary of capitalized keywords -- MUST,
SHOULD, MAY, and their negations -- to indicate the strength of a
requirement. This document is a short, self-contained summary of
the convention, suitable as a primer for readers and authors. It
is drawn from [BCP14] and does not replace it.
S. Bradner Best Current Practice [Page 1]
RFC 0003 Requirement Keywords February 2026
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of an independent submission. It has
been approved for publication by the RFC Editor, but is not a
candidate for any level of Internet Standard; see Section 2 of RFC
7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc0003.
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document.
S. Bradner Best Current Practice [Page 2]
RFC 0003 Requirement Keywords February 2026
Table of Contents
Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. The Keywords . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. MUST, REQUIRED, SHALL . . . . . . . . . . . . . . . . . . 4
2.2. SHOULD, RECOMMENDED . . . . . . . . . . . . . . . . . . . 4
2.3. MAY, OPTIONAL . . . . . . . . . . . . . . . . . . . . . . 4
3. Usage Conventions . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5
S. Bradner Best Current Practice [Page 3]
RFC 0003 Requirement Keywords February 2026
1. Introduction
Interoperability between independent implementations depends on a
shared understanding of what is required of an implementation,
what is recommended, and what is merely permitted. The RFC Series
uses a small set of English keywords to make this distinction
precise and machine-checkable.
When these words are written in ALL CAPS in an RFC, they carry the
specific meanings defined in [BCP14]. When written in lower case
they have their ordinary English meaning.
2. The Keywords
2.1. MUST, REQUIRED, SHALL
MUST, or the equivalents "REQUIRED" and "SHALL", mean that the
definition is an absolute requirement of the specification. An
implementation that does not comply is not a conforming
implementation.
MUST NOT, or "SHALL NOT", mean that the definition is an absolute
prohibition.
2.2. SHOULD, RECOMMENDED
SHOULD, or "RECOMMENDED", mean that there may exist valid reasons
in particular circumstances to ignore this item, but the full
implications must be understood and carefully weighed before
choosing a different course.
SHOULD NOT, or "NOT RECOMMENDED", carry the same force in the
negative direction.
2.3. MAY, OPTIONAL
MAY, or "OPTIONAL", mean that an item is truly optional. One
vendor may choose to include it; another may not. Implementations
that do not include a particular option MUST be prepared to
interoperate with those that do, though perhaps with reduced
functionality. Implementations that include the option MUST be
prepared to interoperate with those that do not.
S. Bradner Best Current Practice [Page 4]
RFC 0003 Requirement Keywords February 2026
3. Usage Conventions
These words SHOULD be used only where they are actually needed to
specify a requirement. Authors sometimes overuse them for
emphasis; this dilutes their force. If a sentence is not defining
a requirement, its key words should not be capitalized.
In particular, imperative sentences describing an algorithm ("the
server adds the entry to the cache") do not need capitalized
keywords unless the requirement on the implementation is
load-bearing.
NOTE: Authors SHOULD include a short paragraph near the start of the
document stating that the keywords have their [BCP14] meanings, so
that readers of the document are not left to guess.
4. Security Considerations
Misuse of requirement keywords can lead to interoperability
failures -- an implementation may believe itself compliant while
failing to satisfy what the author intended as a mandatory
requirement. Authors SHOULD review their use of capitalized
keywords carefully before publication.
5. References
[BCP14] Bradner, S. and B. Leiba, "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC 2119, RFC 8174,
May 2017
6. Author's Address
S. Bradner
RFC.EE Project
Email: [email protected]
S. Bradner Best Current Practice [Page 5]
0 comments
No comments yet.