1.3.2 Requirements (original) (raw)

Connected: An Internet Encyclopedia
1.3.2 Requirements

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1122
Up: 1. INTRODUCTION
Up: 1.3 Reading this Document

Prev: 1.3.1 Organization
Next: 1.3.3 Terminology

1.3.2 Requirements

1.3.2 Requirements

In this document, the words that are used to define the significance of each particular requirement are capitalized. 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.3 Terminology

Connected: An Internet Encyclopedia
1.3.2 Requirements