This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.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. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and ÖPTIONAL" in this document are to be interpreted as described in RFC 2119.
%0 Generic
%1 Bradner1997
%A Bradner, S.
%B RFC 2119 (Best Current Practice)
%D 1997
%I Internet Engineering Task Force (IETF)
%K ietf key-words oclcml requirement-levels rfc
%T IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
%U http://www.ietf.org/rfc/rfc2119.txt
%X This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.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. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and ÖPTIONAL" in this document are to be interpreted as described in RFC 2119.
@electronic{Bradner1997,
abstract = {{This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.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. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.}},
added-at = {2019-03-11T21:00:05.000+0100},
author = {Bradner, S.},
biburl = {https://www.bibsonomy.org/bibtex/234e370fc7a8fd21ea1a8f6c5d169d665/fairybasslet},
booktitle = {RFC 2119 (Best Current Practice)},
citeulike-article-id = {10094540},
citeulike-linkout-0 = {http://www.ietf.org/rfc/rfc2119.txt},
interhash = {630f9247a807f0708050f4fb3624c772},
intrahash = {34e370fc7a8fd21ea1a8f6c5d169d665},
keywords = {ietf key-words oclcml requirement-levels rfc},
posted-at = {2011-12-05 10:11:09},
priority = {2},
publisher = {Internet Engineering Task Force (IETF)},
timestamp = {2019-03-11T21:06:37.000+0100},
title = {{IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels}},
url = {http://www.ietf.org/rfc/rfc2119.txt},
year = 1997
}