@techreport{hansen-nonkeywords-non2119-04,
    number =    {draft-hansen-nonkeywords-non2119-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hansen-nonkeywords-non2119/04/},
    author =    {Tony Hansen and Dave Crocker},
    title =     {{Non-Normative Synonyms in RFCs}},
    pagetotal = 4,
    year =      2016,
    month =     feb,
    day =       26,
    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 RFC 2119 words are sometimes also used with non-normative meaning; this non-normative usage can be confusing and it is better to restrict the RFC 2119 words to be used solely as normative directives. Happily, natural languages permit variation in phrasing, so that meaning can be retained without use of this otherwise-normative vocabulary. For such situations, this document provides some alternatives to the normative vocabulary of RFC 2119.},
}