Additional Key words to Indicate Requirement Levels
draft-hoffman-additional-key-words-00

Document Type Expired Internet-Draft (individual)
Last updated 2008-01-15
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hoffman-additional-key-words-00.txt

Abstract

Some document authors want to express requirement levels using the traditional definitions of "MUST" and "SHOULD" from RFC 2119, but also want to express that there is an expectation that later versions of the document may change those requirements. For example, they may want to express "this SHOULD be implemented now, but we expect that this will become a MUST requirement in a future update to this standard". This document defines three new keywords, "MUST-", "SHOULD+", and "SHOULD-" to facilitate such definitions.

Authors

Paul Hoffman (paul.hoffman@vpnc.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)