Connected: An Internet Encyclopedia
1.2 Requirements
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 2068
Up:
1 Introduction
Prev: 1.1 Purpose
Next: 1.3 Terminology
1.2 Requirements
1.2 Requirements
This specification uses the same words as RFC 1123 [8] for defining
the significance of each particular requirement. These words are:
- MUST
-
This word or the adjective "required" means that the item is an
absolute requirement of the specification.
- SHOULD
-
This word or the adjective "recommended" means that there may
exist valid reasons in particular circumstances to ignore this
item, but the full implications should be understood and the case
carefully weighed before choosing a different course.
- MAY
-
This word or the adjective "optional" means that this item is
truly optional. One vendor may choose to include the item because
a particular marketplace requires it or because it enhances the
product, for example; another vendor may omit the same item.
An implementation is not compliant if it fails to satisfy one or more
of the MUST requirements for the protocols it implements. An
implementation that satisfies all the MUST and all the SHOULD
requirements for its protocols is said to be "unconditionally
compliant"; one that satisfies all the MUST requirements but not all
the SHOULD requirements for its protocols is said to be
"conditionally compliant."
Next: 1.3 Terminology
Connected: An Internet Encyclopedia
1.2 Requirements