ServerHello with extensions
E258095
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
All labels observed (3)
| Label | Occurrences |
|---|---|
| TLS ServerHello | 2 |
| ServerHello | 1 |
| ServerHello with extensions canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2359769 — 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: ServerHello with extensions Context triple: [RFC 3546, definesMessageBehavior, ServerHello with extensions]
-
A.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
B.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
C.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
D.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
E.
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.
- 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: ServerHello with extensions Target entity description: ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
A.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
B.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
C.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
D.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf | TLS handshake message variant ⓘ |
| direction | server-to-client ⓘ |
| extends | ServerHello ⓘ |
| followsMessage | ClientHello ⓘ |
| hasComponent |
Handshake message header
ⓘ
TLS record layer header ⓘ cipher_suite field ⓘ compression_method field ⓘ extensions field ⓘ random field ⓘ server_version field ⓘ session_id field ⓘ |
| hasProperty |
allows negotiation of additional security parameters
ⓘ
backward compatible with non-extension-aware clients in TLS 1.0–1.2 ⓘ |
| hasPurpose |
negotiate capabilities between client and server
ⓘ
negotiate optional protocol features ⓘ |
| introducedIn | TLS 1.0 ⓘ |
| mayIncludeExtension |
application_layer_protocol_negotiation extension
ⓘ
ec_point_formats extension ⓘ extended_master_secret extension ⓘ key_share extension ⓘ pre_shared_key extension ⓘ psk_key_exchange_modes extension ⓘ renegotiation_info extension ⓘ server_name extension ⓘ session_ticket extension ⓘ signed_certificate_timestamp extension ⓘ status_request extension ⓘ supported_groups extension ⓘ supported_versions extension ⓘ |
| partOf |
TLS handshake protocol
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| precedesMessage |
Certificate
ⓘ
EncryptedExtensions ⓘ ServerKeyExchange (TLS 1.2 and earlier) ⓘ |
| standardizedIn |
RFC 3546
ⓘ
RFC 4366 ⓘ RFC 5246 ⓘ RFC 8446 ⓘ |
| usedFor | feature negotiation in TLS handshakes ⓘ |
| usedInVersion |
TLS 1.0
ⓘ
TLS 1.1 ⓘ TLS 1.2 ⓘ TLS 1.3 ⓘ |
| usesField |
extension_data
ⓘ
extension_type ⓘ extensions length ⓘ |
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: ServerHello with extensions Description of subject: ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: ServerHello with extensions
linked to: ServerHello with extensions
linked to: ServerHello with extensions