RFC 3546
E47242
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3546 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T287158 — 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 3546 Context triple: [RFC 5246, obsoletes, RFC 3546]
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
C.
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.
-
D.
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.
-
E.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
- 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 3546 Target entity description: RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
C.
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.
-
D.
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.
-
E.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| appliesTo |
TLS 1.0
ⓘ
TLS 1.1 ⓘ RFC 5246 ⓘ
surface form:
TLS 1.2
|
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
Client Certificate URL extension
ⓘ
Max Fragment Length extension ⓘ SNI ⓘ Server Name Indication extension ⓘ Status Request extension ⓘ TLS extensions ⓘ HMAC ⓘ
surface form:
Truncated HMAC extension
Trusted CA Indication extension ⓘ |
| definesConcept |
TLS client hello extensions
ⓘ
TLS extension negotiation ⓘ TLS server hello extensions ⓘ |
| definesField |
TLS extension_data
ⓘ
TLS extension_type ⓘ |
| definesMessageBehavior |
ClientHello with extensions
ⓘ
ServerHello with extensions ⓘ |
| language | English ⓘ |
| obsoleteBy |
RFC 4366
ⓘ
RFC 6066 ⓘ |
| partOfSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| protocol |
TLS
ⓘ
TLS ⓘ
surface form:
Transport Layer Security
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
HTTPS
ⓘ
X.509 certificates ⓘ public key infrastructure ⓘ |
| rfcNumber | 3546 ⓘ |
| standardsBody |
TLS Working Group
ⓘ
surface form:
IETF TLS Working Group
|
| status | Obsoleted ⓘ |
| title |
ALPN (Application-Layer Protocol Negotiation)
ⓘ
surface form:
Transport Layer Security (TLS) Extensions
|
| updatesProtocol | TLS ⓘ |
| updatesSpecification | RFC 2246 ⓘ |
| useCase |
bandwidth optimization for TLS handshakes
ⓘ
certificate status checking in TLS ⓘ virtual hosting with 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 3546 Description of subject: RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.