RFC 2060
E213172
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2060 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1881429 — 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 2060 Context triple: [RFC 3501, obsoletes, RFC 2060]
-
A.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
B.
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.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
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.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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 2060 Target entity description: RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
A.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
B.
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.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
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.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments
ⓘ
technical standard ⓘ |
| appliesTo |
email clients
ⓘ
mail servers ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
IMAP4rev1 authentication and authorization model
ⓘ
IMAP4rev1 capabilities mechanism ⓘ IMAP4rev1 client-server interaction model ⓘ IMAP4rev1 command set ⓘ IMAP4rev1 error handling ⓘ IMAP4rev1 extension negotiation via CAPABILITY ⓘ IMAP4rev1 flag semantics ⓘ IMAP4rev1 literal and string syntax ⓘ IMAP4rev1 mailbox access control model ⓘ IMAP4rev1 mailbox hierarchy ⓘ IMAP4rev1 mailbox model ⓘ IMAP4rev1 mailbox subscription model ⓘ IMAP4rev1 message flags ⓘ IMAP4rev1 message retrieval operations ⓘ IMAP4rev1 message sequence numbers ⓘ IMAP4rev1 message store operations ⓘ IMAP4rev1 response formats ⓘ IMAP4rev1 search criteria ⓘ IMAP4rev1 server greeting and logout behavior ⓘ IMAP4rev1 server responses ⓘ IMAP4rev1 state machine ⓘ IMAP4rev1 unique identifiers (UIDs) ⓘ |
| language | English ⓘ |
| networkProtocol |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
| obsoletedBy | RFC 3501 ⓘ |
| obsoletes | RFC 1730 ⓘ |
| portNumber | 143 ⓘ |
| protocolFamily | IMAP ⓘ |
| protocolLayer | application layer ⓘ |
| protocolSpecified |
RFC 3501
ⓘ
surface form:
Internet Message Access Protocol version 4rev1
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| replacedBy | IMAP4rev1 specification in RFC 3501 ⓘ |
| rfcNumber | 2060 ⓘ |
| securityConsiderationsSection | Security Considerations ⓘ |
| series |
RFCs
ⓘ
surface form:
RFC
|
| shortTitle |
RFC 3501
ⓘ
surface form:
IMAP4rev1
|
| standardizes | client access to server-stored email ⓘ |
| status | Proposed Standard ⓘ |
| title |
RFC 3501
ⓘ
surface form:
Internet Message Access Protocol - Version 4rev1
|
| useCase |
management of email messages on a server
ⓘ
remote access to email messages ⓘ |
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 2060 Description of subject: RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.