Non-Normative Synonyms in RFCs
draft-hansen-nonkeywords-non2119-02

 
Document
Type Expired Internet-Draft (individual)
Last updated 2012-11-17 (latest revision 2012-05-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-hansen-nonkeywords-non2119-02.txt

Abstract

Specifications in RFCs contain normative keywords, as defined in RFC 2119, to signify requirements, permission or prohibitions. These include MUST, SHOULD and MAY, which are commonly recorded in all CAPITALS (but need not be). The words are sometimes also intended with non-normative meaning; this different usage can be confusing. Happily there are adequate alternatives for non-normative meanings. For such situations, this document provides some alternatives to the normative vocabulary of RFC 2119.

Authors

Tony Hansen (tony+nonkeywords@maillennium.att.com)
dcrocker (dcrocker@bbiw.net)

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