RFC 2818
E40278
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2818 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T311106 — 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 2818 Context triple: [HTTPS, definedIn, RFC 2818]
-
A.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
B.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
C.
RFC 2246
RFC 2246 is the original specification of the Transport Layer Security (TLS) protocol version 1.0, defining the foundational standard for securing communications over computer networks.
-
D.
RFC 4346
RFC 4346 is the Internet Engineering Task Force (IETF) specification that defines Transport Layer Security (TLS) version 1.1, a cryptographic protocol for securing communications over computer networks.
-
E.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
- 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 2818 Target entity description: RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
-
A.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
B.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
C.
RFC 2246
RFC 2246 is the original specification of the Transport Layer Security (TLS) protocol version 1.0, defining the foundational standard for securing communications over computer networks.
-
D.
RFC 4346
RFC 4346 is the Internet Engineering Task Force (IETF) specification that defines Transport Layer Security (TLS) version 1.1, a cryptographic protocol for securing communications over computer networks.
-
E.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
HTTP clients
ⓘ
HTTP servers ⓘ web browsers ⓘ |
| area |
Applications
ⓘ
Security ⓘ |
| category | Standards Track ⓘ |
| defines |
interaction between HTTP status codes and TLS errors
ⓘ
requirements for caching in HTTPS ⓘ requirements for certificate chains in HTTPS ⓘ requirements for hostname verification ⓘ requirements for proxies and gateways using HTTPS ⓘ rules for certificate name matching ⓘ security requirements for HTTPS ⓘ server identity verification for HTTPS ⓘ use of TLS record layer for HTTP traffic ⓘ use of TLS with HTTP URIs ⓘ use of TLS with HTTPS URIs ⓘ use of default HTTPS port 443 ⓘ |
| definesProtocol | HTTPS ⓘ |
| focusesOn | transport layer security for HTTP ⓘ |
| goal |
prevent man-in-the-middle attacks on HTTPS connections
ⓘ
provide secure HTTP communication over the Internet ⓘ |
| intendedAudience |
implementers of HTTP clients
ⓘ
implementers of HTTP servers ⓘ protocol designers ⓘ security engineers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2817 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
HTTP
ⓘ
HTTPS ⓘ SSL ⓘ TLS ⓘ |
| RFCNumber | 2818 ⓘ |
| specifies |
HTTP over TLS
ⓘ
error handling for certificate validation failures ⓘ how HTTP URIs are interpreted over TLS ⓘ how clients establish secure connections to HTTP servers ⓘ how servers present certificates to clients ⓘ use of HTTP over SSL ⓘ |
| standardsBody |
IETF TLS Working Group
ⓘ
linked to:
TLS Working Group
|
| status | Proposed Standard ⓘ |
| title |
HTTP Over TLS
ⓘ
linked to:
HTTPS
|
| usesProtocol |
SSL
ⓘ
TLS ⓘ |
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 2818 Description of subject: RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.