RFC 2119
E185717
RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 2119 canonical | 4 |
| Key words for use in RFCs to Indicate Requirement Levels | 1 |
| RFC2119 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1649230 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2119 Context triple: [BCP 14, relatedTo, RFC 2119]
-
A.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
D.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2119 Target entity description: RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
-
A.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
D.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| appliesTo |
standards-track documents
ⓘ
technical specifications ⓘ |
| area | General ⓘ |
| author | Scott Bradner ⓘ |
| bcpNumber | 14 ⓘ |
| category | Best Current Practice ⓘ |
| clarifies | distinction between mandatory and optional requirements ⓘ |
| defines |
MAY
ⓘ
MUST ⓘ MUST NOT ⓘ OPTIONAL ⓘ RECOMMENDED ⓘ REQUIRED ⓘ SHALL ⓘ SHALL NOT ⓘ SHOULD ⓘ SHOULD NOT ⓘ requirement levels terminology ⓘ |
| definesUsage | capitalization of key words to indicate normative requirements ⓘ |
| documentFormat | text ⓘ |
| hasSection |
Acknowledgments
ⓘ
Introduction ⓘ References ⓘ Requirements Language ⓘ Security Considerations ⓘ |
| identifier |
RFC 2119
self-linksurface differs
ⓘ
surface form:
RFC2119
|
| influenced | normative language in other standards organizations ⓘ |
| intendedAudience |
authors of IETF specifications
ⓘ
readers of technical standards ⓘ |
| isReferencedBy | many Internet standards ⓘ |
| keywordStyle | uppercase key words ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 1123
ⓘ
surface form:
RFC 1123 (terminology portions)
|
| publicationDate | 1997-03 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| purpose | to ensure consistent interpretation of requirement levels ⓘ |
| repository | RFC Editor ⓘ |
| rfcNumber | 2119 ⓘ |
| scope | use of key words in IETF standards documents ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
RFC 2119
self-linksurface differs
ⓘ
surface form:
Key words for use in RFCs to Indicate Requirement Levels
|
| typeOfStandard | normative language specification ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 2119 Description of subject: RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Key words for use in RFCs to Indicate Requirement Levels
this entity surface form:
RFC2119