RFC 9111
E5629
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 9111 canonical | 6 |
| Internet Standard (via HTTP core update, superseded by RFC 9111) | 1 |
| RFC 7234 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T53990 — 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 9111 Context triple: [HTTP, definedIn, RFC 9111]
-
A.
IEEE 802.1CM fronthaul standard
The IEEE 802.1CM fronthaul standard is a Time-Sensitive Networking (TSN) specification that defines Ethernet-based transport requirements and profiles for carrying mobile fronthaul traffic in 4G/5G radio access networks.
-
B.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
-
C.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
D.
IEEE 2413 IoT architecture standard
IEEE 2413 IoT architecture standard is a framework that defines a unified, scalable reference architecture and common vocabulary for designing and integrating Internet of Things systems across diverse domains.
-
E.
W3C Recommendation
A W3C Recommendation is a mature, stable web standard published by the World Wide Web Consortium to promote interoperability and best practices across the World Wide Web.
- 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 9111 Target entity description: RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
A.
IEEE 1028 (Software Reviews and Audits)
IEEE 1028 (Software Reviews and Audits) is an IEEE Computer Society standard that defines processes and procedures for conducting formal software reviews and audits throughout the software lifecycle.
-
B.
IEEE 802.1CM fronthaul standard
The IEEE 802.1CM fronthaul standard is a Time-Sensitive Networking (TSN) specification that defines Ethernet-based transport requirements and profiles for carrying mobile fronthaul traffic in 4G/5G radio access networks.
-
C.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
-
D.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
E.
IEEE 2413 IoT architecture standard
IEEE 2413 IoT architecture standard is a framework that defines a unified, scalable reference architecture and common vocabulary for designing and integrating Internet of Things systems across diverse domains.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| aimsTo |
improve network efficiency
ⓘ
improve web performance ⓘ |
| appliesTo |
HTTP semantics as defined in RFC 9110
ⓘ
HTTP/1.1 ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP caching semantics
ⓘ
linked to:
HTTP Caching
cache key concepts ⓘ freshness lifetime of cached responses ⓘ requirements for intermediaries acting as caches ⓘ rules for reusing HTTP responses ⓘ rules for storing HTTP responses ⓘ rules for validating cached HTTP responses ⓘ staleness of cached responses ⓘ strong validators ⓘ validators for HTTP caching ⓘ weak validators ⓘ |
| obsoletes |
RFC 7234
ⓘ
linked to:
RFC 9111
|
| publishedBy | Internet Engineering Task Force ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies |
Age header field semantics
ⓘ
Cache-Control header field semantics ⓘ ETag header field semantics ⓘ Expires header field semantics ⓘ Last-Modified header field semantics ⓘ Vary header field semantics ⓘ Warning header field semantics ⓘ cache revalidation mechanisms ⓘ conditions under which a response is cacheable ⓘ conditions under which a response is not cacheable ⓘ freshness model for HTTP responses ⓘ heuristic caching rules ⓘ private cache behavior ⓘ semantics of immutable directive ⓘ semantics of max-age directive ⓘ semantics of must-revalidate directive ⓘ semantics of no-cache directive ⓘ semantics of no-store directive ⓘ semantics of private directive ⓘ semantics of proxy-revalidate directive ⓘ semantics of public directive ⓘ semantics of s-maxage directive ⓘ semantics of stale-if-error directive ⓘ semantics of stale-while-revalidate directive ⓘ shared cache behavior ⓘ validation model for HTTP responses ⓘ |
| title | HTTP Caching ⓘ |
| updatesProtocol |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
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 9111 Description of subject: RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 9111