RFC 4366
E893547
RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4366 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T10926987 — 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 4366 Context triple: [RFC 6066, obsoletes, RFC 4366]
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
C.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
D.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- 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 4366 Target entity description: RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
C.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
D.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- F. None of above. chosen
Statements (36)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines | TLS extensions ⓘ |
| definesConcept |
TLS client hello extensions
ⓘ
TLS extension negotiation ⓘ TLS server hello extensions ⓘ |
| definesExtension |
Certificate Status Request
ⓘ
Client Certificate URL ⓘ Max Fragment Length ⓘ
linked to:
Max Fragment Length extension
SNI ⓘ Server Name Indication ⓘ
linked to:
Server Name Indication extension
Status Request ⓘ Truncated HMAC ⓘ
linked to:
HMAC
Trusted CA Indication ⓘ |
| extendsProtocol |
TLS 1.0
ⓘ
TLS 1.1 ⓘ |
| focusesOn |
TLS client extensions
ⓘ
TLS server extensions ⓘ |
| intendedFor |
TLS implementers
ⓘ
security protocol designers ⓘ |
| obsoletedBy | RFC 6066 ⓘ |
| organization | Network Working Group ⓘ |
| protocol |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2246
ⓘ
RFC 4346 ⓘ RFC 6066 ⓘ |
| standardizes |
format of TLS extension messages
ⓘ
negotiation of TLS extensions ⓘ |
| status | Obsoleted ⓘ |
| title |
Transport Layer Security (TLS) Extensions
ⓘ
linked to:
TLS extensions
|
| updates | TLS 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 4366 Description of subject: RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.