Document Action: Key words for use in RFCs to Indicate Requirement Levels to BCP

The IESG <iesg-secretary@ietf.org> Wed, 29 January 1997 18:59 UTC

To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Sender: ietf-announce-request@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: Key words for use in RFCs to Indicate Requirement Levels to BCP
Date: Wed, 29 Jan 1997 13:57:56 -0500
Message-ID: <9701291357.aa25948@ietf.org>


  The IESG has approved the Internet-Draft "Key words for use in RFCs
  to Indicate Requirement Levels" <draft-bradner-key-words-03.txt> for
  publication as a Best Current Practices RFC. This document is not the
  product of an IETF working group. The IESG contact person is Fred
  Baker.


Technical Summary

   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, so that a uniform definition may be
   referenced rather than being repeated (or worse, not repeated) with
   slight changes in definition and force from document to document.

Working Group Summary

  Since this does not come from a working group, dissent if it exists
  will be discovered during the last call process. Having
  written/edited at several documents which could have benefitted from
  the ability to reference the definitions, this AD feels that the
  definitions given are within the spirit (if not the letter) of their
  common use, and should be non-controversial.

Protocol Quality

 This was reviewed by Fred Baker.

Document Action: Key words for use in RFCs to Ind… The IESG