RFC 2595
E700355
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2595 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928166 — 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 2595 Context triple: [RFC 8314, obsoletes, RFC 2595]
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
D.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- 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 2595 Target entity description: RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
D.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- F. None of above. chosen
Statements (35)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesToProtocol |
ACAP
ⓘ
IMAP ⓘ IMAP4 ⓘ
linked to:
IMAP
POP3 ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
use of TLS to secure ACAP
ⓘ
use of TLS to secure IMAP ⓘ use of TLS to secure POP3 ⓘ |
| definesMechanism |
STARTTLS for ACAP
ⓘ
linked to:
STARTTLS
STARTTLS for IMAP ⓘ
linked to:
STARTTLS
STARTTLS for POP3 ⓘ
linked to:
STARTTLS
|
| definesUsageOf |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| focusesOn |
application-layer security
ⓘ
email-related protocols ⓘ |
| obsoletedBy | RFC 8314 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
application configuration access protocol security
ⓘ
email security ⓘ secure email retrieval ⓘ |
| RFCNumber | 2595 ⓘ |
| specifies |
capability advertisement for TLS support
ⓘ
client and server behavior for TLS negotiation ⓘ error handling for TLS negotiation failures ⓘ |
| standardizes | negotiation of TLS on existing TCP connections ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Using TLS with IMAP, POP3 and ACAP ⓘ |
| updates |
security considerations for ACAP
ⓘ
security considerations for IMAP ⓘ security considerations for POP3 ⓘ |
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 2595 Description of subject: RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.