RFC 7540
E206428
RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 7540 canonical | 2 |
| HTTP/2 specification | 1 |
| RFC 7540 (HTTP/2 specification) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1853342 — 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 7540 Context triple: [RFC 7541, relatedTo, RFC 7540]
-
A.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
B.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
C.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
D.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- 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 7540 Target entity description: RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
-
A.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
B.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
C.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
D.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ Technical specification ⓘ |
| appliesTo |
HTTP clients
ⓘ
HTTP intermediaries ⓘ HTTP servers ⓘ |
| area | Applications ⓘ |
| bcp14KeywordsUsed | MUST, SHOULD, MAY as defined in RFC 2119 ⓘ |
| binaryFramingLayer | Yes ⓘ |
| category | Standards Track ⓘ |
| defines |
Hypertext Transfer Protocol Version 2
ⓘ
linked to:
HTTP/2
|
| definesConcept |
Flow-control window
ⓘ
HTTP/2 connection ⓘ HTTP/2 frame ⓘ HTTP/2 stream ⓘ Prioritization tree ⓘ Stream identifiers ⓘ |
| definesProtocol | HTTP/2 ⓘ |
| definesVersion | HTTP version 2.0 ⓘ |
| headerCompressionMechanism | HPACK ⓘ |
| intendedUse | General Internet ⓘ |
| introducesFeature |
Flow control
ⓘ
Header compression ⓘ Server push ⓘ Stream multiplexing ⓘ Stream prioritization ⓘ |
| keeps |
HTTP URIs from HTTP/1.1
ⓘ
HTTP methods from HTTP/1.1 ⓘ HTTP status codes from HTTP/1.1 ⓘ |
| language | English ⓘ |
| maintainsSemanticsOf | HTTP/1.1 ⓘ |
| obsoletes | RFC 2616 (partially) ⓘ |
| primaryGoal |
Enable multiplexing over a single connection
ⓘ
Improve HTTP efficiency ⓘ Improve web performance ⓘ Reduce latency ⓘ |
| publicationDate | May 2015 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedSpecification |
HPACK: Header Compression for HTTP/2
ⓘ
linked to:
HPACK
RFC 7541 ⓘ |
| relationshipTo | Based in part on SPDY protocol ⓘ |
| rfcNumber | 7540 ⓘ |
| securityConsiderationsDocumentedIn | Section 10 ⓘ |
| status | Proposed Standard ⓘ |
| stream | Standards Track ⓘ |
| title |
Hypertext Transfer Protocol Version 2 (HTTP/2)
ⓘ
linked to:
HTTP/2
|
| updates | HTTP/1.1 specification behavior (semantics preserved) ⓘ |
| usesUnderlyingTransport |
TCP
ⓘ
linked to:
Transmission Control Protocol
|
| workingGroup |
Hypertext Transfer Protocol (httpbis)
ⓘ
linked to:
HTTP/2
|
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 7540 Description of subject: RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 7540
linked to: RFC 7540