Key Words for Use in RFCs to Indicate Requirement Levels¶
Bradner, S. (1997). Key Words for Use in RFCs to Indicate Requirement Levels.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Rhetorical Velocity
- Open-source software and documentation: code composed knowing it will be forked and recombined; documentation written knowing fragments will be pasted into answers, posts, and training corpora; API contracts designed for re-export and embedding. Legal and contractual drafting: clauses drafted knowing they will be lifted into other documents and cited decades later, with defined-terms conventions and severability clauses as partial mitigations. Media and public relations: messaging that pre-constructs the sound-bites and visuals that will be excerpted and writes headlines for downstream re-use. Standards and protocols: specifications written knowing implementers read selectively, with conformance levels ("MUST"/"SHOULD"/"MAY") existing to shape behaviour under imperfect reading.
This sourceDefines MUST/SHOULD/MAY conformance levels that shape implementer behavior under selective reading of specifications.
Supported in partVerified against the work's full text
RFC 2119 defines requirement-level keywords for standards documents, supporting only the standards clause of this multi-domain claim, not its account of selective reading or the other domains.
“In many standards track documents several words are used to signify the requirements in the specification.”
- Open-source software and documentation: code composed knowing it will be forked and recombined; documentation written knowing fragments will be pasted into answers, posts, and training corpora; API contracts designed for re-export and embedding. Legal and contractual drafting: clauses drafted knowing they will be lifted into other documents and cited decades later, with defined-terms conventions and severability clauses as partial mitigations. Media and public relations: messaging that pre-constructs the sound-bites and visuals that will be excerpted and writes headlines for downstream re-use. Standards and protocols: specifications written knowing implementers read selectively, with conformance levels ("MUST"/"SHOULD"/"MAY") existing to shape behaviour under imperfect reading.
Mechanisms¶
- Modal Language Review Protocol
- It flags each keyword against its intended force under the RFC 2119 convention, where MUST, SHOULD, and MAY have precise, agreed meanings.
This sourceAssigns explicit requirement levels to the normative keywords MUST, SHOULD, and MAY for standards documents.
- It flags each keyword against its intended force under the RFC 2119 convention, where MUST, SHOULD, and MAY have precise, agreed meanings.
- Technical Standard Specification
- Disciplined use of normative keywords is what turns intentions into checkable obligations.
This sourceDefines normative keywords as explicit requirement, prohibition, and qualified-recommendation levels for specifications.
- Disciplined use of normative keywords is what turns intentions into checkable obligations.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 3 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
Registry ID ref:8b1d5604bd85 · see in the full table