RFC 2817
E200697
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2817 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1808636 — 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 2817 Context triple: [RFC 2818, obsoletes, RFC 2817]
-
A.
RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
D.
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.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- 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 2817 Target entity description: RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
A.
RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
D.
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.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| alternativeTo | Using a separate port for HTTPS such as 443 ⓘ |
| area | Applications Area ⓘ |
| category | Standards Track ⓘ |
| definesClientBehavior | How an HTTP client requests TLS upgrade using Upgrade header ⓘ |
| definesInteraction |
Client-initiated protocol switch from HTTP to TLS
ⓘ
Server acceptance or rejection of TLS upgrade ⓘ |
| definesMechanism |
Establishing TLS over an existing HTTP connection
ⓘ
In-band upgrade from cleartext HTTP to TLS ⓘ Use of HTTP/1.1 Upgrade header to initiate TLS ⓘ |
| definesRequirementLevel | Implementation considerations for HTTP clients and servers supporting Upgrade to TLS ⓘ |
| definesServerBehavior | How an HTTP server responds to TLS upgrade requests ⓘ |
| definesStatusCodeUsage | 101 Switching Protocols ⓘ |
| definesTerm | TLS upgrade ⓘ |
| definesUseCase |
Securing HTTP traffic without changing the initial port
ⓘ
Upgrading a persistent HTTP connection to TLS ⓘ |
| documentType | Technical specification ⓘ |
| focusesOn | Transition from non-encrypted to encrypted HTTP on the same connection ⓘ |
| intendedUse |
Environments where port sharing between HTTP and HTTPS is desired
ⓘ
Scenarios requiring dynamic negotiation of TLS ⓘ |
| language | English ⓘ |
| obsoletedBy |
Later HTTP/HTTPS deployment practices favoring separate ports
ⓘ
RFC 7230 (indirectly, via HTTP/1.1 revision) ⓘ |
| obsoletes | RFC 2817 (Proposed Drafts or earlier versions) ⓘ |
| portUsage | Allows TLS over the same port as cleartext HTTP ⓘ |
| protocol |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| protocolVersion | HTTP/1.1 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
HTTP Upgrade mechanism
ⓘ
HTTPS ⓘ RFC 2616 ⓘ |
| relatedWorkingGroup | HTTP Working Group ⓘ |
| RFCNumber | 2817 ⓘ |
| scope | Application-layer security negotiation for HTTP ⓘ |
| securityProtocol |
TLS
ⓘ
TLS ⓘ
surface form:
Transport Layer Security
|
| series |
RFCs
ⓘ
surface form:
STD (Standards Track RFCs)
|
| standardsStatus | Proposed Standard ⓘ |
| statusAsOf2024 | Historic ⓘ |
| title | Upgrading to TLS Within HTTP/1.1 ⓘ |
| updatesProtocol | HTTP/1.1 ⓘ |
| usesHeaderField |
101 Switching Protocols status code
ⓘ
Connection ⓘ Upgrade ⓘ |
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 2817 Description of subject: RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.