RFC 6066
E258094
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 6066 canonical | 9 |
| RFC 6066 Section 4 | 1 |
| RFC 6066, Section 4 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2359751 — 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 6066 Context triple: [RFC 3546, obsoleteBy, RFC 6066]
-
A.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
B.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- 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 6066 Target entity description: RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
A.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
B.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ TLS specification ⓘ |
| appliesTo |
TLS 1.0
ⓘ
TLS 1.1 ⓘ TLS 1.2 ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
Client Certificate URL extension
ⓘ
Max Fragment Length extension ⓘ SNI extension ⓘ
linked to:
SNI
Server Name Indication extension ⓘ Status Request extension ⓘ TLS extension negotiation rules for specified extensions ⓘ TLS extensions ⓘ Truncated HMAC extension ⓘ
linked to:
HMAC
Trusted CA Indication extension ⓘ |
| definesField |
extension_data
ⓘ
extension_type ⓘ |
| definesUseCase | virtual hosting with TLS via SNI ⓘ |
| enables | selection of server certificate based on hostname ⓘ |
| identifier | RFC 6066 ⓘ |
| includesExtension |
client_certificate_url
ⓘ
max_fragment_length ⓘ server_name ⓘ status_request ⓘ truncated_hmac ⓘ trusted_ca_keys ⓘ |
| language | English ⓘ |
| obsoletes | RFC 4366 ⓘ |
| protocolFamily | TLS ⓘ |
| protocolLayer | transport layer ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| registry | TLS ExtensionType values ⓘ |
| relatedTo |
HTTPS virtual hosting
ⓘ
X.509 certificates ⓘ |
| series |
RFC
ⓘ
linked to:
RFCs
|
| standardizes |
format of TLS ClientHello extensions
ⓘ
semantics of several TLS extensions ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Transport Layer Security (TLS) Extensions: Extension Definitions ⓘ |
| updatesProtocol |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| workingGroup | TLS Working Group ⓘ |
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 6066 Description of subject: RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
Referenced by (11)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 6066
linked to: RFC 6066