RFC 6176
E51131
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6176 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T338898 — 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 6176 Context triple: [SSL 2.0, prohibitedBy, RFC 6176]
-
A.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
B.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
C.
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.
-
D.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- 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 6176 Target entity description: 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.
-
A.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
B.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
C.
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.
-
D.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- F. None of above. chosen
Statements (31)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
RFC ⓘ |
| addresses | backward compatibility with SSL 2.0 ⓘ |
| appliesTo |
TLS clients
ⓘ
TLS implementations ⓘ TLS servers ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| definesPolicyFor | use of SSL 2.0 in TLS ⓘ |
| disallowsUseOf | SSL 2.0 ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | transport layer security ⓘ |
| language | English ⓘ |
| mandates | TLS clients and servers MUST NOT negotiate SSL 2.0 ⓘ |
| obsoletesProtocolVersion | SSL 2.0 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| purpose | to formally prohibit the negotiation of SSL 2.0 in TLS ⓘ |
| reason |
SSL 2.0 is insecure
ⓘ
linked to:
SSL 2.0
SSL 2.0 is obsolete ⓘ
linked to:
SSL 2.0
|
| relatedProtocol |
SSL
ⓘ
Secure Sockets Layer ⓘ
linked to:
SSL
TLS ⓘ Transport Layer Security ⓘ
linked to:
TLS
|
| securityProperty | removal of weak protocol version ⓘ |
| standardizes | prohibition of SSL 2.0 in TLS ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | Prohibiting Secure Sockets Layer (SSL) Version 2.0 ⓘ |
| updatesSpecification | TLS implementations ⓘ |
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 6176 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.